Ready for any legal review
Where the data lives, what Orbit does with it and who helps: the terms, privacy and security documents lawyers and procurement ask for, in one place.
Agreements
What you sign up to, how we process data for you, and who helps.
Privacy and security
What we collect, what the Orbit Pixel stores, and how the data is protected.
What legal teams ask first
The short answers. Each one is set out in full in the documents above.
Stored in the EU
Orbit’s database, sign-in and files are in Ireland, and the app runs in the Netherlands.
A DPA with every account
It is part of the Terms, so it applies from the first site, without a signature. You or your client stay the controller.
Never used to train AI
Orbit trains no models on your data, and its AI providers may not either. They receive only what a task needs.
Works with your consent banner
The Orbit Pixel’s one cookie can wait for a visitor’s yes, through Google Consent Mode or your own code, while every visit is still counted. It sets no third-party cookies and stores no IP addresses.
Every sub-processor listed
With what each one receives and where it is, and an email before one is added.
Breach notice within 48 hours
With what we know and what we are doing about it.
Questions about privacy and security
In the EU. Orbit’s database, sign-in and files are at Supabase in Ireland, and the app runs at Railway in the Netherlands. The AI models that draft and analyse process what a task needs in the United States, under the European Commission’s Standard Contractual Clauses or the EU-U.S. Data Privacy Framework. The Subprocessors page lists every company and where it is.
Yes. The DPA is part of the Terms, so it applies to every account from the start, without a signature. You or your client are the controller and Orbit is the processor or sub-processor. If your organisation needs a signed copy, write to privacy@goorbit.io.
Yes. Set it to wait for consent and it follows Google Consent Mode, which Cookiebot, OneTrust, Usercentrics, CookieYes and most other consent tools can send, or a call from the site’s own code. Only its one cookie waits: until the visitor says yes, it stores nothing in the browser and still counts the visit, and after a yes it recognises them when they come back. A later no removes what it kept, and counting goes on without it.
Only what a task needs. To draft, analyse and answer, Orbit sends the relevant site content, search data and the question to its AI providers, Anthropic and OpenAI, which process it for that request. Visitors’ IP addresses and anything typed into a site’s forms are never recorded, so they are never sent.
No. Orbit trains no models on your data or your clients’ data, and its AI providers’ terms don’t allow them to train on it either. Each site’s data is used for that site only, and never shown in another customer’s workspace.
Yes. The Privacy Policy and the DPA cover the Swiss Federal Act on Data Protection as well as the GDPR. The data is stored in the EU, which Switzerland recognises as adequate, and transfers beyond it use the Standard Contractual Clauses with the Swiss amendments or the Swiss-U.S. Data Privacy Framework.
If a breach affects your data, Orbit tells you within 48 hours of becoming aware of it, with what is known and what is being done, and helps you inform your clients and your authority. The DPA sets out the rest.
Deleting a site deletes its data, files included. Removing a site only archives it: its history stays, and the pixel keeps recording while its code is on the website. When an account ends, its data is deleted or returned within 90 days.
Something these pages don’t answer?
Write to privacy@goorbit.io for a signed copy of the DPA, or with any question your legal or security team has. Or book a demo to see how Orbit fits the way you work and where it can help.


