Security and data
Your code and training
Your code and records are never used to train a model unless your company opts in. The setting is off by default. Viliha improves from what it owns (its own records and docs, public open-source code) and from anonymous product signals, such as which answers were accepted.
AI models
Cited answers, checks and audits need no model. Nothing from your projects is sent to a model provider until your company turns it on and chooses the provider; then credentials are removed from what is sent, and daily use is capped.
Where data lives
Viliha runs on Amazon Web Services in the United States (us-east-1). A choice of region comes with the Business plan.
How it is kept apart
- Each company's data is isolated in the database itself, by row-level security, not only by the application.
- Sessions, sign-in links, invitations and API tokens are stored only as hashes.
- Integration credentials are never stored in settings; settings name where the secret is kept.
- Every change to members, roles and settings is written to the company's audit log.
Certifications
Viliha is not yet SOC 2 certified. The controls are documented against our security standard, and the audit starts as customers require it.