privacy
policy.
Short version: Orbit runs on your machine, your data stays on your machine, your API keys never touch our servers, and we don't run a backend that could leak your conversations even if we wanted to. The long version follows.
Who this covers
This policy covers two surfaces: the marketing website at useorbit.dev and the Orbit desktop application. We are a single-founder company. References to we, us, and Orbit mean the same person.
What the website collects
The marketing site collects exactly one piece of personal data: the email address you submit to the early-access waitlist. We use it to email you when the desktop build ships. No newsletter, no drip sequence, no upsell.
The site does not currently set analytics cookies, ad cookies, or third-party tracking pixels. If that ever changes, this section will say so before the change is live.
What the app collects
The Orbit desktop app is local-first. Your prompts, conversations, skills, agents, memory entries, and any files you load are stored on your machine. Orbit does not run a backend that mirrors, syncs, or backs up your workspace.
The app collects no analytics or telemetry by default. If we ever add an opt-in telemetry signal for crash reports or feature usage, it will be off out of the box and clearly labelled in settings.
API keys
You bring your own API key for each model provider you connect (Anthropic, Google Gemini, OpenAI). Keys are stored on your device, keyed by provider id, and used only to make calls directly from your machine to the provider you selected. Keys are not transmitted to Orbit's servers because Orbit doesn't have any servers in that path.
Model providers
When you send a prompt, Orbit forwards it directly to the model provider you chose. Those providers receive your prompt, your context, and any attached files, and they process them under their own privacy policies and data handling commitments:
- Anthropic - default provider, Sonnet 4.6.
- Google - if you connect Gemini.
- OpenAI - if you connect a GPT model.
Orbit doesn't see, log, or store the contents of those exchanges.
Storage you bring
If you connect a personal cloud storage provider (e.g. Google Drive) for backup or sync, files move directly between your machine and that provider through your own account. Orbit doesn't see a copy.
Payments
When paid tiers are live, payments are processed by a third-party processor (Stripe). They receive the information needed to charge you - typically email, card token, and billing address. Orbit receives the resulting subscription status, not your full card details.
The Vault
If you publish a skill or agent to the Vault marketplace, the listing - including its title, description, and packaged contents - becomes visible to other Orbit users and is hosted by Orbit so it can be discovered and installed. Don't publish anything you don't want public.
Your rights
You can ask us what personal data we hold about you, ask us to correct it, ask us to delete it, or ask us to send you a copy. For the website, that essentially means removing your email from the waitlist - email neo@useorbit.dev and we'll do it within a reasonable time.
For the app, deletion is even simpler: uninstall it. Your local workspace is yours to delete on your own machine.
Children
Orbit is not directed to children under 13 (or under 16 where applicable). We don't knowingly collect personal data from anyone under that age. If you believe we have, contact us and we'll delete it.
Changes to this policy
When this policy changes meaningfully, the effective date at the top will update and material changes will be highlighted on this page. Continuing to use Orbit after a change means you accept the updated policy.
Contact
Privacy questions, deletion requests, or anything else data-related: email neo@useorbit.dev.