Orrery Privacy Policy
Effective date: 16 October 2026.
1. Who We Are
Orrery is operated by SuperNova Leap LLC ("we", "us", "our"). This policy describes how we collect, use, and share information in connection with the Service.
2. Information We Collect
- Account information: name, work email, job title, company name, and the company slug you choose at signup.
- Authentication information: managed entirely by our identity provider, Clerk (see subprocessors below) — we never see or store your password.
- Billing information: managed entirely by our payment processor, Stripe (see subprocessors below) — we never see or store your full card number.
- Customer Data: the business data you and your team enter into the Service (deals, contacts, notes, and similar records) to use its features.
- Usage data: log and diagnostic information generated by your use of the Service, used to operate and improve it.
3. How We Use Information
We use the information above to: provide and operate the Service; authenticate you and manage your account; process payments; communicate with you about your account and the Service; and improve the Service's reliability and features.
4. Subprocessors
We share information with the following subprocessors, each engaged for a specific purpose and bound by its own data protection obligations. This list is enumerated from what this platform's own staging configuration actually uses, not a generic template — reviewed 2026-09-22 and updated 16 October 2026.
| Subprocessor | Purpose |
| Supabase | Database hosting — all Customer Data and account records are stored in a Supabase-hosted Postgres database. |
| Vercel | Application hosting — every part of the Service runs as a Vercel deployment. |
| Clerk | Authentication — sign-in, session management, and organization membership. |
| Stripe | Payment processing — subscription billing and payment method storage. |
| Resend | Transactional email — welcome emails, invite notifications and the reports you schedule, sent to the addresses you give us; for Orrery Marketing, also the approval digest described in section 9. |
| GitHub | CI/CD and schema migrations; no Customer Data. |
| Nango | Integration provider, used only by Orrery Marketing (section 9) — holds the access tokens for the social accounts you connect and makes each publishing request on Orrery's behalf, so it carries the text of each post you publish. It also receives the connecting person's name and an Orrery reference for their workspace seat. No other Customer Data. |
Not enumerable from this review: the agent-runtime host and LLM provider that power the Service's own AI features are operated outside the systems this review had visibility into, and could not be confirmed as "actually configured" from this platform's own environment configuration. They will be named here once confirmed, not guessed at.
Telegram — operational alerts only, never Customer Data: we use Telegram internally for our own team's operational alerts (build/deploy notifications, provisioning progress, and security events such as an unauthorized attempt to reach our operator console). Those alerts can carry operational metadata — an account identifier, a workspace name, a provisioning step, or an error message — but never the content you store in the Service (your deals, contacts, notes, or files). It is purely an internal engineering tool.
5. Data Isolation
Your Customer Data is isolated from every other customer's — technically enforced at the database layer, not merely by application logic. Nothing you enter is used to train any model or shared with any other customer.
6. Data Retention
We retain Customer Data for as long as your account is active. If you cancel, you may export your data before or shortly after cancellation; data associated with a cancelled account is deleted per our standard retention schedule (to be finalized).
7. Your Rights
Depending on your location, you may have rights to access, correct, or delete your personal information. Contact us using the details below to exercise these rights.
8. Changes to This Policy
We may update this policy from time to time, particularly as we add or change subprocessors. Material changes will be communicated to active accounts before taking effect.
9. Orrery Marketing
This section applies only if you use Orrery Marketing.
Orrery Marketing, including our Orrery Pages app, lets your business publish posts it has written and approved to the LinkedIn member profiles and LinkedIn Pages its people connect. Orrery only publishes.
What we store. For each LinkedIn profile or Page you connect, we store:
- A connection ID: our integration provider's reference to the profile or Page you connected, so we can publish where you asked.
- The post ID LinkedIn returns for each post we publish for you.
- The post's public URL, so your team can see in Orrery where each post went live.
- A Page ID, when you choose a LinkedIn Page you administer to publish to.
Orrery also keeps its own record of each post: the text, who approved and published it, and when.
What we read but don't store. When we publish to your own profile, we ask LinkedIn for your member ID so the post is attributed to you. We use it for that one request and don't store it, and Orrery doesn't keep the name, email address or photo that LinkedIn's sign-in service may return with it. To publish to a Page, we read the list of Pages you administer only so you can choose one. Publishing to a Page is coming soon; until it's available, a Page post is made on LinkedIn and its link recorded in Orrery. We don't read or store your feed, connections, messages, followers, analytics or any other LinkedIn data.
Access tokens. Orrery never holds your LinkedIn access or refresh tokens. Nango, our integration provider (section 4), holds them and makes each publishing request on Orrery's behalf. Disconnecting a channel in Orrery deletes the connection at Nango, and with it the tokens. You can also revoke Orrery's access at any time from your LinkedIn account settings.
Why we use it. Only to publish the posts your business approves in Orrery, and to show your team what was published and where. Nothing is posted without a person in your business approving it and choosing to publish it. We don't sell this data, use it for advertising, share it with other customers, or use it to train any AI model.
Who can see it. Within Orrery, only people in your own workspace can see this data. Our staff access it only to run and support the service. Supabase, Vercel and Nango (section 4) process the LinkedIn data above for us, only to run the service.
Approval emails. People who approve posts get an email digest, sent through Resend (section 4), that lists the titles of the posts waiting for them.
How long we keep it.
- While a channel is connected, we keep its connection ID and, for a Page, its Page ID.
- After a disconnect, we keep the channel's record: its connection ID, which no longer works, who connected it and when. That way past posts stay attributed. Nango no longer holds any token for it.
- Post IDs, URLs and post records stay while your Orrery account is active, as your record of what was published.
- When an Orrery account is cancelled, this data is deleted with the rest of the account's data, as section 6 describes.
Deletion on request. You can ask us for a copy of the LinkedIn data Orrery holds about you, or to correct or delete it, at any time (section 7). Email us from the address on your account and tell us which profile or Page it concerns. We confirm the request and complete a deletion within 30 days. When we delete Orrery's record of a post, the post stays on LinkedIn; you can delete it there.
10. Contact
Questions about this policy: privacy@supernovaleap.com.