Security and privacy
Built for the questions your security team will ask
Tarivra reads delivery data that matters to your business. Here is what it reads, who can see it, how it is protected, and what we have not done yet.
Read-only by default
Tarivra only reads your tools, except the decision and question items your leaders choose to send.
No passwords stored
Sign-in through single sign-on or a one-time code with MFA.
Your data stays yours
Never sold, never shared with other customers, never used to train AI models.
Audit log nobody can edit
Every sign-in and change, with who and when, kept for seven years.
The data Tarivra reads
- What it reads
- Work items under the items your teams label as programs: titles, status and status history, assignee names, dates, estimates, labels and links, and in ServiceNow change requests and the incidents they caused. Only in the projects, repositories and tables you grant.
- What it never reads
- Source code, repository files, pull request contents, file attachments, or anything outside the projects you grant.
- Personal data
- Names and work email addresses of users, brief recipients and the people named on work items. No payment card, health or other special-category data.
- Writing to your tools
- Only when someone chooses to send a decision or question to the team's tool, as a new item under the item it is about. Each write is in the audit log.
AI and your data
- No outside AI by default
- Every brief is written inside Tarivra by its own engine, and every sentence is checked against your data. No program data is sent to an AI provider.
- AI-written briefs, only if you ask
- Turned on for your organization only, after you agree in writing, under a data processing agreement with zero data retention.
- Your own AI assistant
- People may connect their own assistant, such as Claude or GitHub Copilot. It reads only what that person may see, changes nothing, and every question it asks is in your audit log. Your admin can see and revoke every connection.
Sign-in and access control
- Single sign-on
- SAML or OIDC with Okta, Microsoft Entra ID, Google Workspace and other identity providers. Your directory groups map to Tarivra roles.
- Multi-factor authentication
- Required. With single sign-on your identity provider's MFA applies; without it, a one-time code to the work email plus an authenticator app.
- Roles and need to know
- Viewer, Program owner, Executive, Auditor and Admin, plus restricted programs that only the people listed on them can see, in every page, export and brief.
- Approval before access
- Signing up gives no access. An admin approves each person with a role.
- Joiners and leavers
- With single sign-on, disabling someone in your directory ends their access within minutes.
- Tarivra staff
- Cannot see your data unless your admin grants a named engineer a read-only seat for a set time, with a reason. The grant and its use are in your audit log.
Encryption and infrastructure
- Hosting
- Amazon Web Services, US West (Oregon). Your data stays in that region. Enterprise customers can have a dedicated environment or Tarivra in their own AWS account.
- Encryption in transit
- TLS on every connection; the website and API use TLS 1.3, with HSTS.
- Encryption at rest
- Disks and backups are encrypted with AES-256. Connection credentials are stored as encrypted secrets, readable only by the service.
- Network
- Only HTTPS is open to the internet. There is no remote shell access from the internet, and the database accepts connections only from the server itself.
- Web protections
- A strict content security policy, clickjacking protection, rate limits on public endpoints, bot checks on public forms and parameterized database queries.
Monitoring, backups and incidents
- Monitoring
- Health checks every five minutes, with alerts on failed sign-in bursts, rejected tokens and security changes.
- Backups
- Nightly, encrypted, kept 14 days, with restores tested monthly.
- Retention and exit
- Export your data at any time. When you leave, all of it is deleted within 30 days, with written confirmation.
- Incident response
- A written plan to contain, investigate, recover and notify. Customers are told within 72 hours of confirming their data was affected.
Testing and compliance
- Security assessment
- In November 2026 the whole platform was assessed end to end, from the website and sign-in to the API, brief writer, data protection, hosting and integrations. No critical or high-severity issues were found. A summary is available under NDA.
- Certifications
- Tarivra is not yet SOC 2 or ISO 27001 certified. Its controls are designed to the SOC 2 Trust Services Criteria and ISO 27001 Annex A.
- Evidence for your audits
- Auditors download a compliance evidence pack for any period up to a year, mapped to SOX, ISO 27001 and SOC 2.
- Accessibility
- The product was reviewed against WCAG 2.2 AA.
- Agreements
- A mutual NDA before any demo, and a data processing agreement for customers who need one.
Subprocessors
| Company | Purpose | Location |
|---|---|---|
| Amazon Web Services | Hosting, storage, backups and logs | United States (Oregon) |
| WorkOS | Sign-in, single sign-on and directory sync | United States |
| Resend | Delivery of brief and notification emails | United States |
Slack and Google Chat receive the brief only if your admin connects a channel. We notify customers before adding a subprocessor.
Questions
Does Tarivra read our source code?
No. It reads work item records only, never source code, repository files, pull request contents or attachments.
Is our data sent to an AI service?
No. Tarivra writes every brief with its own engine, inside Tarivra. AI-written briefs are optional and only turned on after you agree in writing.
Where is our data stored?
In Amazon Web Services, US West (Oregon). Enterprise customers can choose a dedicated environment or their own AWS account.
Is Tarivra SOC 2 certified?
Not yet. Its controls are designed to SOC 2 and ISO 27001, and it produces audit evidence for your own SOX, ISO 27001 and SOC 2 programs.
Can you fill in our security questionnaire?
Yes. Email hello@tarivra.com and we send our standard answers or complete yours.
Security contact: hello@tarivra.com. See also how Tarivra works.