Security overview
Orrin security overview
This document lists Orrin’s security practices and the status of each one. It says exactly what the Security page says. Orrin holds no certification.
- 01
Workspace isolation
Every document, passage, question, operation, key and audit entry belongs to one workspace, and every read and write is checked against it. Workspaces share infrastructure, never data.
In place - 02
Signing keys and tokens
Each workspace generates its own Ed25519 signing keys; the private key is shown once and never stored. Your backend signs a token of at most fifteen minutes for each user, carrying their id, role and scopes, and the assistant checks its signature, audience and expiry on every request. Orrin never holds a shared service account for end user actions.
In place - 03
Previews before any change
Every action request produces a preview first, showing the operation Orrin matched, its confirmation level and the parameters it needs. A preview never calls the vendor’s API, and only operations the vendor switched on can be matched.
In place - 04
Audit log
Every workspace records who did what and when: documents added, reindexed or removed, questions asked, previews shown, operations imported and relabelled, keys created and revoked, members invited and removed. The full log downloads as CSV.
In place - 05
Encryption in transit and at rest
All traffic uses TLS. Account and workspace data is stored in Google Cloud Firestore, which encrypts it at rest.
In place - 06
Deletion
Deleting a document removes it and its passages from the index at once. Workspace data is kept until it is deleted, and a whole workspace or account is deleted on request.
In place - 07
Prompt injection defenses
Answers are quoted from retrieved passages, so document text cannot steer the assistant. Only operations a vendor switched on can be matched, and a preview never calls the vendor’s API.
In place - 08
No training on customer data
Customer documents and questions are never used to train models.
In place - 09
Subprocessors
Vercel hosts the site and runs the console’s server code in the United States (Washington, D.C.). Google Cloud Firebase stores workspace data in Firestore’s United States multi region and handles sign in through Firebase Authentication, including Google and GitHub sign in when a user chooses them. Resend delivers our email: access requests, and the messages and answers of Orrin support. A new subprocessor is named here before it receives any data.
In place - 10
Incident contact
Security reports go to the contact address on this page. Affected workspaces are told within seventy two hours of a confirmed incident.
In place
Contact: miracle@orrin.live