Privacy policy
Contents
What we collect
- Account details: your name and work email, and, if you sign in with Google, the basic profile Google shares (name, email, whether the email is verified). We never receive your Google password.
- Workspace data: members, roles, teams, projects, records, questions, answers, Decision Audits and feedback.
- Connected tools: data needed from connected code hosts, Jira and other services. Credentials are sealed with AES-256-GCM before they are stored and are never shown again.
- Usage and security logs: sign-ins, company audit actions and service-protection logs.
- Safety and incidents: when content is refused under the acceptable use policy, we keep who sent it, where, the category and a fingerprint of the text, never the text itself. Security incidents keep what happened, with credentials removed.
Why we use it
We use data to deliver governance, answers, audits and billing; secure ODIN; and prevent abuse. We do not sell personal data.
AI models and training
Company data reaches AI models only after company opt-in. Code and records are never used for training without opt-in, off by default.
Where it is kept and how it is protected
Company data is isolated by row-level security. HTTPS encrypts traffic; disks and backups are encrypted. Tokens and sign-in links are hashed. See Security.
Who can see it
Company members see data according to their roles; connected apps act within granted permissions. Staff access it only for operations, support or security. Infrastructure vendors process data under contract.
How long we keep it
Data stays while your company uses ODIN. Deleted companies may be restored within 30 days; afterward their data is deleted. Backups expire on their schedule.
Your choices and rights
Request access, correction, export or deletion at privacy@viliha.com. Company admins manage members, workspaces and connected apps.
Changes
We update this page when practices change and revise the date above.