The promise
Torvane reads your documents so that people don't have to. That means it is handed a great deal of material a business would not want leaked, altered or lost. Three commitments follow from that, and the rest of this page is the detail behind them.
- Your documents are only ever read. A file that arrives — by upload or from a connected mailbox — is never executed, never rendered, and never trusted.
- Your documents are yours. They are not used to train public AI models. You can export everything, at any time, in one click.
- Nothing irreversible happens automatically. Deletion always requires a human decision.
Every file is treated as hostile
Document ingestion is the attack surface of a product like this: a business receives files from customers, suppliers and strangers, and forwards them straight to us. Torvane assumes any file may be an attack and screens it before it is processed:
| What it stops | How |
|---|---|
| Executables disguised as documents | The real file type is read from its magic bytes and checked against
its claimed extension. An .exe renamed to
.pdf is quarantined, never processed. |
| Macro-enabled Office files | Blocked by extension, and allowed .docx/.xlsx
are inspected inside for a macro payload. |
| Known malware | A scanning layer runs on the bytes at the door, before anything is queued. ClamAV is supported where available. |
| Decompression bombs and zip bombs | Image dimensions are checked from the header without decoding the pixels; archive expansion ratios and file counts are capped. |
| Malicious XML (billion laughs, XXE) | Office XML is parsed with entity expansion and external entities disabled. |
| Files that crash or hang the parser | Every parse runs under a hard timeout with page and size caps. The file is quarantined; the worker survives and carries on. |
| PDFs carrying JavaScript or auto-open actions | Detected and flagged for a human. Torvane does not execute them — it warns you before you open the file in a real viewer. |
| Prompt injection inside document text | Torvane treats document text as data, never as instructions. Text attempting to give the AI orders is flagged for review and not acted on. |
A quarantined file is stored but never processed, never appears in search or folder listings, and can only be downloaded by an administrator who explicitly confirms it — an action that is itself logged.
Application security
- Tenant isolation, enforced by the database. Every query is scoped to the organisation — and each organisation's data is isolated by the database itself, not only by application code. Row-level security is forced on every table that holds customer data, and the service connects as a least-privilege database role: it cannot bypass those rules, cannot change the database's structure, and has no access to anything outside Torvane's own schema. A query that forgot to filter by organisation would still return nothing from another organisation. This is tested against a real PostgreSQL database — every API route is tried with another organisation's identifiers — and was verified on the live service.
- Role-based access, plus department ACLs. Admins, managers and employees see different things; employees see only the departments assigned to them.
- Passwords are hashed with bcrypt. Reset links are random, single-use, expiring, and stored only as a SHA-256 hash — a database dump contains nothing that can be redeemed.
- Breached passwords are refused. Whenever a password is set — at sign-up, reset or change — it is checked against the Have I Been Pwned list of passwords exposed in known data breaches. Your password never leaves our server: only the first five characters of a one-way hash are sent, and the comparison happens here. The check runs at the moment a password is set, not continuously afterwards, and if the breach list cannot be reached the password is accepted rather than blocking you.
- Sessions can be revoked. Changing your password, or choosing "sign out of all sessions", invalidates every other signed-in device immediately.
- Content Security Policy. Scripts load only from our own origin under a per-request nonce; there are no inline event handlers anywhere, framing is denied, and MIME sniffing is disabled.
- Downloads are always attachments, served with the content type derived from the file's verified type rather than its claimed extension, so a file cannot be coaxed into rendering in your browser.
- Connector credentials (for example a mailbox app password) are encrypted at rest with Fernet and are never echoed back.
- Everything Torvane does is audited — what it classified, renamed, filed or flagged, with its confidence and reasoning, and who approved what.
What Torvane is allowed to do on its own
Autonomy is scoped deliberately. The riskier the action, the less Torvane is permitted to do without a person.
| Level | Actions | Who decides |
|---|---|---|
| Automatic | Reading, classifying, renaming, tagging, detecting duplicates, and filing when confidence is high | Torvane, with every step logged and reversible |
| Needs approval | Low-confidence filing and restructuring | An admin or manager, from the Inbox |
| Never automatic | Deletion | A human requests it; an administrator approves it. This is the only path that removes a document. |
| Learned rules | A rule from a correction that a manager or employee asks Torvane to remember, or any rule whose check shows it would change other documents | An administrator confirms it before it is used |
| Never automatic | Sending a draft | Torvane only drafts. A person copies it, downloads it or opens it in their own email app, and sends it. |
External sharing is not implemented as an AI action at all.
Torvane learns only what a person confirms, shows every rule and preference with the reason for it, and never learns anything about payments, recipients or permissions.
Where your data lives, and who touches it
Documents, extracted text, the search index and account records are hosted in the United Kingdom. An encrypted backup copy is held in the European Union (Netherlands).
We use a small number of sub-processors. The full, current list with the contractual detail is in the Privacy Policy and the Data Processing Agreement:
| Who | What for |
|---|---|
| Anthropic | Provides the large language models used to analyse documents and prepare drafts you ask for. Processes document content transiently to return results and does not use customer data to train its models. Your organisation's name (and any other names you tell us it trades under) is sent with each document, so that the model does not mistake your organisation for the other party on the document. |
| Oracle Cloud Infrastructure (Oracle) | Application hosting and document storage, in the United Kingdom (London). |
| Supabase, Inc. | Managed PostgreSQL database — account records, document metadata,
extracted text, search index and audit log — in the United Kingdom (London, on
Amazon Web Services eu-west-2). |
| Backblaze, Inc. | Off-site encrypted backups. Holds a nightly copy of the document store and the database, encrypted at rest (AES-256), retained for 30 days and used only to restore the service after a loss. Held in the European Union (Netherlands). |
| Stripe (Stripe Payments Europe, Limited) | Payments, through Stripe's hosted checkout: card details go directly to Stripe and never reach Torvane. Stripe is our processor for the payment service and an independent controller for fraud prevention, legal compliance and its own product improvement. It never receives document content. |
Transactional email (address confirmation, password resets, notifications) is sent through a provider-agnostic layer. No email provider is engaged at the time of writing; when one is, it becomes a sub-processor and will be named here and in the Privacy Policy and DPA before it is used.
What we don't do
- We do not train public AI models on your documents.
- We do not sell or share your data for advertising or any other purpose.
- We use no analytics or advertising cookies. The only cookies and browser storage are what is strictly necessary to keep you signed in securely and to remember your cookie choice — all documented in the Cookie Policy, which is checked against what the code really writes.
- Our emails contain no tracking pixels and no remote images. We do not record whether you opened one.
- We do not delete your documents automatically, and we do not act on instructions found inside them.
What we can't claim yet
Torvane is a new product. The following would be dishonest to imply, so we are saying it plainly:
- We hold no security certifications. We are not SOC 2, ISO 27001 or Cyber Essentials certified. Nothing on this site should be read as suggesting otherwise.
- No independent penetration test has been carried out yet. The defences described above are implemented and covered by an automated adversarial test suite, but they have not been reviewed by an external security firm.
- We do not offer an uptime guarantee or a service level agreement at this stage. This is stated in the Terms of Service too.
- Our legal documents are awaiting solicitor review. Every one of them says so on its face.
We would rather lose a sale than overstate any of this.
The legal documents
- Privacy Policy — what we collect, the lawful basis for each purpose, retention, international transfers, and all eight of your data-subject rights, including how to complain to the ICO.
- Data Processing Agreement — the Article 28 processor terms, for customers who need them on file.
- Terms of Service — including the plain statement that AI output can be wrong and should be checked where it matters.
- Cookie Policy — the complete list of what is stored on your device.
We are registered with the Information Commissioner's Office under number ZC183768.
Reporting a security problem
If you believe you have found a vulnerability, please tell us before telling anyone else, and give us a reasonable chance to fix it. Email security@torvane.ai with enough detail to reproduce the issue.
We will acknowledge your report, keep you updated, and we will not pursue or support legal action against anyone who reports a genuine issue in good faith and does not access, alter or destroy other people's data while finding it.