Oracle is a coding assistant. We collect only what's needed to sign you in and run your builds — and we write down why, every time.
What we store
- Account — email address, display name, and the timestamps when the account was created and last seen. Stored in Supabase Postgres.
- Projects + conversations — the prompts you send, the assistant's replies, the tool calls it made, and the files it wrote into your workspace. Stored in Supabase; visible only to you via row-level security.
- Workspace files — the code, screenshots, and snapshots Oracle produces for you. Stored on a Railway persistent volume, namespaced to your user id.
- Usage metering — per-turn token counts and estimated cost, so we can show the session usage meter and cap runaway spend.
What we don't store
- Payment card details (Stripe handles those — we see a customer id and subscription state, nothing else).
- Passwords in plaintext (Supabase Auth salts and hashes).
- Third-party tracking pixels. No Google Analytics, no Meta, no Mixpanel.
What we send to AI providers
Your prompts, prior messages in the same conversation, and the relevant workspace files are sent to the model provider you have selected (Anthropic Claude, xAI Grok, or a local Ollama model) so the model can reason about them. Neither Anthropic nor xAI trains on API traffic by default. If you run Ollama locally, nothing leaves your machine.
Retention
Projects and conversations live for as long as your account does. Delete a project → its chats, workspace files, and snapshots are purged within 30 days. Close your account → the whole lot goes within 30 days, with no backup beyond.
Your rights
Export your data at any time from the account menu. Request deletion and we'll honor it within 30 days. For any privacy question, reach us at privacy@oracle.app.
AI-generated code
You own the code Oracle writes for you. We claim no rights over the output — use it freely, commercially or otherwise.