You are handing Orion your inbox. Here is what happens to it.

Every OAuth token Orion holds — Google, Plaid, GitHub, Strava, and the rest — is encrypted with AES-256-GCM before it is written to the database. The key lives in the server environment, not in the database, so a copy of the database is not a copy of your accounts.

Data in transit is encrypted with TLS. Access to production data is restricted.

Orion never sees or stores a password for any service you connect. You sign in with Google, and every other connection is an OAuth grant you approve on the provider's own screen. Orion holds a revocable token, and you can revoke it without going through us.

• ·Your email address and display name.
• ·Encrypted access and refresh tokens for each service you connect.
• ·The briefs Orion has written for you, so you can read back through them.
• ·Your vault: the notes, wiki pages, people and projects you create in Orion.
• ·A private search index over your own vault, briefs and message history, so the assistant can answer "what did I decide about the vendor contract". It stores both a numerical representation of each passage and the passage text.
• ·Basic product usage: brief ratings and which features you use.

• ·It does not keep full copies of your email or calendar. Beyond the search index above, message content is read to write your brief and not retained.
• ·It does not sell your data, and it does not use it for advertising of any kind.
• ·It does not train general AI models on your data. Your content is sent to Anthropic — and, for the search index, OpenAI — solely to produce your output, and both are contractually bound not to train on it.
• ·Your search index is never pooled with anyone else's and is never used to answer another person's question.
• ·No human reads your data, except with your explicit consent, to resolve a support issue you raised, to investigate abuse, or where the law requires it.

Orion's use of information received from Google APIs follows the Google API Services User Data Policy, including the Limited Use requirements. Orion requests Gmail, Google Calendar and your Google email address, and nothing else. The exact scopes and the reason for each are listed in the privacy policy.

You can revoke Orion's access to your Google account at any time, yourself, at myaccount.google.com/permissions. Orion stops being able to read anything immediately.

Orion is not read-only, and pretending otherwise would be the wrong kind of reassurance. With the permissions you grant, it can draft an email, create or move a calendar event, complete a task, and write to your own wiki. It does this when you ask, and during the morning review on the comments you left for it. It cannot touch a service you have not connected, and it never sends mail on your behalf: there is no "send" action, so a drafted reply sits in your Gmail drafts until you read it and press send yourself.

• ·Briefs are kept so you can read past ones. Tokens are kept while the integration is connected.
• ·Text conversations with Orion are deleted automatically after a fixed retention window (see the privacy policy for the current number).
• ·Disconnect a single source at any time from Settings → Integrations. The stored token is deleted and revoked with the provider.
• ·Delete your account and everything — vault, briefs, search index, phone number, tokens, profile — is permanently deleted within 30 days.
• ·Ask for an export at any time and you get a copy of everything Orion holds.

Orion lets you publish a wiki page as a share link. That link is the only credential — anyone holding it can read the page without an Orion account, and the link does not currently expire. Treat a share link as public. If you need one taken down, email privacy@hi-orion.com.

Orion is operated in the United States by Eric Scott Walpert, doing business as Orion. It runs on Vercel, with Postgres and authentication on Supabase, language models from Anthropic, and text messaging through a registered A2P carrier campaign.

Orion is in private beta and is not SOC 2 or HIPAA certified. Claiming otherwise would be the easiest sentence on this page to write and the worst one to be caught on. What exists today is the engineering above: encrypted tokens, TLS, restricted production access, per-user isolation enforced in the database, and a deletion path that actually deletes. Orion's Google integration has been submitted for third-party security assessment under Google's CASA programme.

Email security@hi-orion.com. Reports are read by the person who wrote the code, and you will get a reply. No bug bounty yet — credit and a fast fix are what is on offer.