Security
Financial data deserves financial-grade restraint.
This page describes what we do today, in specific terms. It avoids marketing language on purpose. When something is not yet in place, it says so.
Control pathone sensitive action
RunningRequest · sensitive action
pendingA member deletes a raw file
The request arrives with the session cookie (host-scoped, SameSite=Lax) and the member's workspace context.
Workspace isolation
pendingRow-level security filters the query
Row-level security policies restrict members’ data access to their respective workspace. Server-side administrative access requires separate controls.
Private storage
pendingThe object lives in a private bucket
Raw files are stored under the workspace prefix. The server processes them to extract text. Confirmation of raw-file deletion requires the storage object to be absent.
AAL2 · step-up
pendingSecond-factor verification (AAL2)
Invitations, role changes, member removals and deletion of files or a workspace require an enrolled authenticator and a TOTP-verified session (AAL2), with the permissions required for the action.
Audit event
pendingActor · action · object · time
The application attempts to record a manual deletion in the audit trail. When recorded, the entry identifies who performed the deletion and when. If the audit write fails, the deletion can still go ahead. The audit trail also records rule confirmations, finding decisions and membership changes.
Each control exists in the code today and is exercised by the automated tests.
Architecture
The path a document takes through Truviate and the controls that apply along the way.
- Browser
Session cookie scoped to the host, SameSite=Lax, refreshed server-side on every request.
Implemented - Workspace boundary
Database row-level security policies restrict access through a user session to the workspaces the user belongs to. Privileged server operations are handled separately.
Implemented - Private storage
Raw files are stored in a private bucket under the workspace prefix. The server reads them for tasks such as text extraction, validation and import. Members with the required permissions and a session verified by a second factor can delete files in the application. A daily task attempts to purge files due for deletion.
Implemented - Extraction
A model proposes billing terms from the agreement text. Proposals are labelled and stored apart from rules.
Implemented - Human-confirmed rules
Only a person turns a proposal into a rule. Versioned, dated, attributed.
Implemented - Deterministic calculation
The engine calculates results deterministically from confirmed billing rules and the evidence provided. The Evidence Trace shows the recorded calculation steps.
Implemented
Each control below exists in the codebase and is exercised by the automated test suites. Verification against the hosted production environment is part of the launch gate and is not claimed here.
Tenant isolation
Business records such as agreements, rules, uploaded files, findings and decisions are associated with a workspace. Database row-level security policies restrict access through a user session to workspaces the user belongs to. Privileged server operations use separate access checks.
Elevated service credentials are used only on the server, never from the browser. They serve payment webhooks and subscription lookups, the daily retention run, the public Free Preflight request form (whose table no signed-in user can read) and the persistence of the calculation engine’s output once the caller’s membership has been checked. The authentication email hook is protected by a separate shared secret.
Storage and retention
- Uploaded files are written to a private storage bucket. There are no public objects.
- Text extraction takes place on the server. Storage policies for access through a user session check membership of the relevant workspace and the permissions required for the action.
- In the application, a member with the required permissions and a session verified by a second factor (AAL2) can delete a raw file. The server then removes the object from storage and the text extracted from it; it is not merely hidden. The deletion is written to the audit trail, within the limits stated in annex 2 of the data processing agreement.
- The default retention period for raw files is 30 days; the workspace owner can choose a period from 7 to 90 days. Each file's scheduled purge date is set when it is uploaded. A daily process attempts to delete raw files that are due and their extracted text. A failure can delay completion; no deletion within 24 hours is guaranteed.
- When a file is successfully purged, the original and the text extracted from it are deleted. The workspace may retain derived data. Confirmed billing rules and AI proposals, along with their clause excerpts, are linked to the client agreement and may be reused in later cycles. Normalized imported rows, findings with their calculation inputs and steps, and confirmation or rejection decisions are associated with the preflight. File metadata, including its name, size and fingerprint, is associated with the workspace record. Abandoning a draft cycle or archiving a client leaves the corresponding records in place and hides them from view. Separate retention and deletion rules apply to these data. A technical deletion record may remain after a workspace is deleted. Backups are handled separately.
AI boundary
AI is used only to read the agreement and propose billing rules, each confirmed by someone on your team. Line matching and every calculation are done by a deterministic engine, without AI.
- Nothing the model proposes affects a financial finding until a person confirms it.
- The model never calculates money. All amounts are produced by a deterministic engine from confirmed rules and imported evidence, in integer minor units, with every step recorded.
- Agreement text is sent to the AI provider from our servers only, over encrypted connections. The provider processes it to answer the request; under its standard API terms it may keep inputs and outputs for up to 30 days, and longer, up to two years, if an exchange is flagged for a policy violation. We have not signed a zero-data-retention agreement.
Analytics and monitoring
We record product events (a preflight was created, a rule was confirmed) and application errors so we can keep the service working. These events carry identifiers and timings, not content. Contract excerpts, invoice lines, amounts and file contents are excluded from analytics and error reports.
Access and sessions
- Authentication is handled by our identity provider; passwords are never stored by us in plain form.
- Sessions are cookie-based: the session cookie is scoped to the truviate.com host, sent with SameSite=Lax, and refreshed server-side on every request.
- Workspace membership determines what a user can see and do. Removing a member blocks subsequent access requests that check membership. It does not cancel a run already started. An upload link already issued remains valid until its expiry, two hours after issue; it can write its designated file, but the removed person cannot read or submit that file in Truviate.
- Connections between browsers and the service, and between the service and its suppliers’ APIs, use TLS. Email delivery is handled separately by the email supplier.
Multi-factor authentication and step-up
- Time-based one-time password (TOTP) multi-factor authentication is required before the first document upload: an upload without an enrolled authenticator is refused, and the app sends you to the enrolment screen and back to the upload.
- Inviting a person, changing a role, removing a member and deleting files or a workspace require an enrolled authenticator and an AAL2 session, with the permissions required for the action. Other security actions apply the account’s MFA policy.
- From the security settings you can sign out every other session, or every session including this one. A password change also signs out your other sessions.
Audit trail
- The audit trail records rule confirmations, finding decisions and membership changes, including who acted and when. The application also attempts to log manual deletions with the actor and time. A manual deletion can still succeed if its audit entry cannot be written.
- Findings retain the inputs and steps recorded for their calculations. Reproducing a result requires the relevant inputs and the corresponding engine version.
Retention and purge
- In the application, a member with the required permissions and a session verified by a second factor (AAL2) can delete raw uploads. A daily task is scheduled to purge each file after the purge date set when it was uploaded, using the retention period applied to that upload. A removal that fails or exceeds a pass’s budget is left for a later pass. Purges of registered documents and manual deletions are written to the audit trail, within the limits stated in annex 2 of the data processing agreement.
- Deleting a workspace removes its active application data. A technical deletion record is retained. Backups are handled separately. The last owner of a workspace is protected against accidental removal.
Implemented today, production status and known limits
Implemented in the application and exercised by automated tests
- Tenant isolation
- Storage and retention
- AI boundary
- Multi-factor authentication and step-up
- Audit trail
- Retention and purge
- Sign-in, sign-up and password-reset requests made through Truviate’s application are limited using counters shared across its servers.
Production status and known limits
- If the shared counter is unavailable, each server instance temporarily applies its own count. Limits on uploads, extractions and runs are counted per server instance.
- Transactional email from a verified sending domain, the authentication email hook and bot protection on sign-in and public forms are in service in production and have been tested there since 22 September 2026.
- No independent third-party security review has been commissioned; none is in progress. See below for what we don’t claim yet.
What we don’t claim yet
Truviate has not yet completed a third-party security certification or independent audit. We would rather say that plainly than borrow a badge. The controls above are the ones actually in place; if you need something specific for your own review, ask and we will answer directly.
Data processing agreement
The contractual measures are set out in annex 2 of the data processing agreement, which forms part of the terms of service.
Responsible disclosure
If you believe you have found a security issue, write to support@truviate.com with enough detail to reproduce it. We acknowledge reports promptly, keep you informed while we investigate, and do not pursue researchers who act in good faith.