What we collect, what we don't, and why.
Orbit treats your data as a liability, not an asset. This policy explains exactly what we hold, how we use it, the vendors that help us run the service, and the rights you have over it.
Last updated · June 20, 2026
What this policy covers.
This policy explains how Orbit ("Orbit," "we," "us") handles personal information when you visit chooseorbit.com, talk to us about the product, or use the Orbit customer portal and service.
It doesn't replace any agreement you have with us. Where a signed agreement or data processing agreement covers the same ground in more detail, that agreement governs.
Who's responsible for your data.
Orbit is a US-based business operated by Orbit (the entity behind chooseorbit.com). For privacy questions, requests, or notices, reach us at sam@chooseorbit.com.
If you're an enterprise buyer running a vendor review, a data processing agreement (DPA) is available on request and governs our handling of your business data.
Controller for your account, processor for your data.
There are two kinds of information here, and we play a different role for each. For your account information — the thin layer we hold to run your login and workspace — we're the controller, and this policy governs it.
For your business data — the leads, contacts, calls, and recordings that live in your CRM and dialer — we act only as a processor, on your documented instructions, to deliver the service. You remain the controller. If someone whose information lives in your CRM asks to access or delete it, that request goes to you, not to us.
We keep the minimum, and no parallel CRM.
Your leads, contacts, and raw records stay where they already live — in your CRM and your dialer. We don't build a parallel copy of your CRM, and we never sell your data or share it for anyone else's advertising.
To deliver the service, recordings and transcripts are processed through the sub-processors listed below, and we keep the derived outputs the product needs — transcripts we work from, the tickers and scores we generate, and a log of the actions we take. We treat all of it as a liability to minimize, not an asset to accumulate.
The account information we hold.
As controller, the information we keep to run your account is:
- Account details — your name, email, and a login credential, which is either a password stored only as a salted hash (scrypt) or a Google OAuth token if you sign in with Google.
- Service configuration — the ticker definitions you give us.
- Activity logs — a record of the actions Orbit takes for you, so the work stays auditable.
On the marketing pages of chooseorbit.com (home, about, security, this page) we collect nothing: no accounts, no analytics scripts, no advertising or marketing pixels, no tracking cookies. The only outbound touchpoint is the "Book a call" page, which schedules through Google Calendar — Google's privacy policy applies to that booking.
Only what sign-in needs.
The marketing pages set no cookies and run no analytics or advertising trackers. The customer portal sets only strictly-necessary, HTTP-only secure session cookies required to keep you signed in — no advertising or analytics cookies. Because we use only essential cookies, there's no consent banner.
How we use what we keep, and on what basis.
We use the information above only to run the service:
- to authenticate you and operate your account;
- to deliver the service — generate your tickers, surface coachable calls, and take the actions you configure;
- to communicate with you about your account, support, and changes to the service;
- to secure, maintain, and improve Orbit;
- to meet our legal obligations.
Where data-protection law requires a legal basis, we rely on: performance of our contract with you (operating your account and delivering the service); our legitimate interests (securing, maintaining, and improving the service, and account communications); and legal obligation (tax and record-keeping). Where we act as a processor on your business data, you determine the legal basis.
Access you grant, and can revoke.
To deliver the service, you issue Orbit OAuth tokens or scoped API keys against your CRM, dialer, calendar, and email. You decide what we can read and write, and every action Orbit takes is logged in your CRM's native audit trail — visible to you, owned by you.
You can revoke our access at any time from your own admin panel. When you do, we can no longer read or write to your systems. We may retain the derived outputs already generated — transcripts, tickers, scores, and action logs — as described in Retention, unless you ask us to delete them.
The vendors behind the service.
We rely on a small set of vendors to run Orbit:
- Vercel — hosts the website and application.
- Neon — managed PostgreSQL (US-East) for the account layer; encrypted at rest, TLS in transit.
- Google — OAuth sign-in and Calendar scheduling.
- A speech-to-text provider — transcribes call recordings.
- An AI provider — scores and analyzes call transcripts to generate your tickers.
Where we send a vendor your recordings or transcripts, we do so only to perform that function. Our agreements with these vendors limit them to providing their service to us, rather than using your content for their own purposes such as advertising or model training. A current list of our named sub-processors is available on request and under our DPA, and we give notice before adding a new one.
We hold it while you're a customer.
We keep account information and the derived service outputs (transcripts, tickers, scores, action logs) for as long as your account is active. When you off-board, your integration tokens are revoked, our access ends, and your raw business data continues living where it always did — in your systems.
We delete or anonymize the information we hold on request, except where we're required to keep certain records to meet a legal obligation.
How we protect what we hold.
Passwords are stored only as salted scrypt hashes, sessions live in HTTP-only secure cookies, and the account database (Neon) is encrypted at rest with TLS in transit. Production access is limited to the founding team, protected by single sign-on with hardware-backed 2FA, with credentials held in a managed vault.
If we become aware of a security incident affecting personal information we hold, we'll notify affected customers without undue delay and cooperate on remediation. We don't yet hold SOC 2 Type II or ISO 27001, and we won't pretend otherwise — our Security page lays out the current state. No method of storage or transmission is ever perfectly secure.
Access, correction, deletion.
For the account information we hold as controller, and depending on where you live, you may have the right to:
- access the personal information we hold about you;
- correct it if it's wrong;
- delete it;
- receive it in a portable form;
- object to or restrict certain processing.
To exercise any of these, email sam@chooseorbit.com and we'll respond within a reasonable period. If your information lives in a customer's CRM rather than our account layer, that customer is the controller — direct your request to them, and we'll support them in responding.
California and other US states.
If you're a California resident (or in a state with similar law), you have the right to know what personal information we collect, to access, delete, and correct it, and to opt out of its sale or sharing. The categories we collect are identifiers (name, email) and account credentials.
Orbit does not sell your personal information and does not share it for cross-context behavioral advertising — so there's nothing to opt out of in that respect. We won't discriminate against you for exercising any of these rights.
Where your data is processed.
Orbit is US-based and the account layer is hosted in the United States (Neon, US-East). We don't currently target the EEA or UK. If you access Orbit from outside the US, your account information is processed in the US; for your business data, your own transfer arrangements govern, with Orbit acting as processor.
Not for children.
Orbit is a business product and isn't directed to anyone under 18. We don't knowingly collect personal information from children.
Updates to this policy.
If we change this policy, we'll post the new version here and update the "Last updated" date above, and we'll take reasonable steps to flag material changes that affect how we handle your information.