Privacy
policy

Who we are

This website and the Orrin console are run by Orrin, registered in Nigeria under number 8529658, of 21 Road, G Close, Festac Town, Lagos, Nigeria. Reach us through the access form or at miracle@orrin.live.

What this website collects

When you send the contact form, we receive the details you enter: your name, work email, company, role, platform size, topic and message. We use them only to reply to you and to follow up on your request. The form goes through a delivery service configured on the deployment, and the request is not stored anywhere else by this website.

The hosting provider keeps standard server logs, such as IP address, browser type and the pages requested, for security and reliability. This website sets no analytics cookies and runs no advertising trackers. The live demo sends what you type to our server, which answers it from the help center and API of Brickwren, an example platform written for this site. The text is processed in memory and not stored, and your IP address is held in memory only to limit how many requests one address can make. The language model behind the demo runs on our own server, so no AI model provider receives what you type.

What the console stores

When you create an account we store your name, your email address and the workspaces you belong to, with your role in each. Passwords are handled by Firebase Authentication and never stored by Orrin; if you sign in with Google or GitHub, that provider shares your name and email with us. Signing in sets a session cookie, which the console needs to work.

Inside a workspace we store what you and your teammates put there: documents and the passages indexed from them, with the numbers our own language model computes from each passage to match it by meaning, questions asked and the answers given, imported API operations and their settings, the public half of each signing key, invitations, support tickets, daily usage counts and the audit log. Every item belongs to one workspace and is never shared with another. Requests sent to us through Contact Orrin reach the Orrin support team with your name, email address and workspace, and our answers are emailed to you and kept with the request in your workspace. Customer documents and questions are never used to train models.

Deleting a document removes it and its passages at once, and conversations, the audit log and daily usage download as CSV from the console at any time. Workspace data is otherwise kept until it is deleted: ask us and we provide a full copy of a workspace, or delete a workspace or an account.

End users of a vendor’s software use the assistant under that vendor’s own privacy terms, with Orrin acting as a processor for the vendor. For each conversation in a vendor’s product, Orrin stores the questions, the answers and previews it gave, and the user id, role and company the vendor’s token named, in that vendor’s workspace, where the vendor can read and export them. The token itself is checked and not kept, and Orrin never sees the user’s password or session. A data processing addendum is available on request.

Retention

Access requests are kept as long as needed to reply and to follow up, and deleted on request.

Your rights

You can ask what we hold about you, ask for it to be corrected or deleted, and object to its use. Use the access form with the Support topic, or email miracle@orrin.live.

Subprocessors

Vercel hosts this website and runs the console’s server code in the United States. Google Cloud Firebase stores account and workspace data in Firestore’s United States multi region and handles sign in. Email to our addresses is hosted by Namecheap, and access requests and support email are delivered by Resend. A new subprocessor is named on the Security page before it receives any data.

Changes

Changes to this policy are published on this page.