Privacy notice

This notice explains what the Oort website and Oort Pro collect. Both are run by Marcus Jonathan Ong (enskild firma, a Swedish sole trader), Smörkärnegatan 21, 412 78 Gothenburg, Sweden. We are the controller of the data described here. Contact us at privacy@oortcloud.dev.

VAT number: SE960505691101

What we collect

• Early-access list. If you join, we store your email address, the date and which page you used (home or pricing). We store no IP address and no browser details.
• Your account. When you sign in, Clerk keeps your sign-in details: your email address, and your name and picture if you use GitHub or Google. Our database keeps your Clerk user id and when the account was created.
• Billing. When you subscribe, Stripe collects your payment details, billing address and email, and a tax id if you give one. We never see your card number. Our database keeps your Stripe customer id, your plan, the subscription status and the renewal date.
• Oort Pro keys and usage. For each key: the first 12 characters, a one-way hash of the key, the name you gave it, and when it was created, last used and revoked. For each month: how many saves and recalls you used, and how many embedding inputs, rerank calls and Jev calls the relay passed on. Numbers only, no content.
• CLI sign-in. When you run oort login, we keep a one-way hash of the request's secret, a short code, when it started and was approved, the country Cloudflare reports for the request (not the IP address), and the operating system and computer name the CLI sends, so the approve page can show you which computer asked. An hourly job deletes each request once it is an hour old.
• Requests and logs. Cloudflare runs our website and the relay, so it necessarily sees your IP address, browser details and approximate location to answer each request. We have turned off Cloudflare's request logs for both. Our own code logs only a status code and how long a request took: no IP address, path, headers or content. We do not store your IP address anywhere.
• Aggregate visit counts. When switched on, Cloudflare Web Analytics counts page views without cookies and without following you across sites. We see totals, not people.
• Sign-in cookies. Clerk sets cookies that keep you signed in. They are strictly necessary; see cookies. The console is still a demo with sample data and sends nothing to us.

To stop abuse we count requests for about a minute: per IP address on the early-access form and when oort login starts a sign-in, per key and per account on the relay, and failed relay sign-ins per IP address. The counters live in memory or in Cloudflare's rate limiter and expire on their own; we never save them.

What leaves your machine with Oort Pro

In plain words:

• Your memories stay on your computer. They live in the Oort store on your machine. Oort Pro does not copy them to us.
• To save a memory, the Oort engine sends the text it is saving to TypeSafe (Jev decides whether and how to keep it), to Anthropic (Claude Haiku writes the short memory) and to Voyage AI (to turn it into a vector).
• To recall, it sends your search text to Voyage AI to turn it into a vector, and the search text with the candidate memories to Voyage AI to rank them.
• Our relay passes these requests on. They go through relay.oortcloud.dev, which swaps your Oort key for ours and forwards them. The relay does not store or log what you send or what comes back. It keeps only the monthly counts and when each key was last used.
• Each provider processes the request to answer it, under its own API terms.
• With your own keys instead of Pro, the same requests go straight from your machine to the providers, and nothing reaches us.

Why we use it, and our legal basis

• Early-access list: to tell you when Oort Cloud opens. Basis: your consent (GDPR Article 6(1)(a)), given when you tick the box. You can withdraw it at any time.
• Account, keys, usage counts and the relay: to provide Oort Pro to you. Basis: our contract with you (Article 6(1)(b)).
• Invoices and payment records: to meet bookkeeping law. Basis: legal obligation (Article 6(1)(c)).
• Request logs, rate limits and aggregate analytics: to keep the service safe and know which pages are useful. Basis: our legitimate interest (Article 6(1)(f)).

How long we keep it

• Early-access list: until Oort Cloud opens plus 12 months, or until you ask us to remove you, whichever is first.
• Account, keys and usage counts: while your account exists. We delete them within 30 days after you ask us to close it.
• Invoices and payment records: 7 years, as Swedish bookkeeping law requires.
• CLI sign-in requests: at most about two hours.
• Status-and-timing logs and aggregate analytics: as long as Cloudflare keeps them, then gone.

Your rights

You can ask for access to your data, correction, erasure, a copy to take elsewhere, or to object to its use, and you can withdraw consent. Write to privacy@oortcloud.dev from the email on your account or on the list. You can also complain to the Swedish supervisory authority, Integritetsskyddsmyndigheten (IMY), at https://www.imy.se, or to the authority in your own country.

Who receives it, and transfers

Our processors are Cloudflare, Clerk, Stripe, Brevo, Voyage AI, TypeSafe and Anthropic. The subprocessor list says what each one does. Some process data outside your country. Where they do, transfers rely on the EU Standard Contractual Clauses, or on the EU-US Data Privacy Framework where the company is certified. We do not sell your data and we do not share it for advertising.

Hosted Oort Cloud

Hosted Oort Cloud is not open yet. Its terms and data processing agreement will be published before it opens.