Skip to content

Security

How we protect the data in Orbit: yours, and your clients'.

Last updated

  • Data is stored in the EU, encrypted in transit and at rest, and kept apart per account and site.
  • Nothing publishes itself, and you can disconnect any integration at any time.
  • Our AI providers do not train their models on your data, and we tell you of a breach within 48 hours.

This page describes how we protect the data in Orbit: yours, and your clients'. Questions from your security or legal team go to privacy@goorbit.io. To report a security issue, write to hello@goorbit.io.

Where your data lives

Orbit's database, sign-in and file storage run on Supabase, in the EU (Ireland). The app, its API and the Orbit Pixel's endpoint run on Railway, in the EU (the Netherlands), and the pixel's traffic comes in through Cloudflare's network.

The AI models that draft, analyse and answer run at our AI providers, in the United States. They receive what a task needs and process it for that request. Every company that processes data for us is listed on the Subprocessors page, with where it is.

How it is protected

  • Encrypted in transit: every connection to Orbit uses HTTPS, and our API requires it.
  • Encrypted at rest by our database provider.
  • Kept apart: row-level security is switched on for every table in the database. From the browser, a person can reach only their own profile, notifications, invitations and team list; everything else goes through our backend, which checks on every request that the person belongs to the account and the site.
  • One customer never sees another's data: no other customer's site appears in your account, not as a competitor, a comparison or a benchmark.
  • Passwords are handled by our sign-in provider. We never see or store them.
  • Every request is checked: each call to our API carries a signed sign-in token that our server verifies, and requests are rate-limited.
  • AI tool connections through MCP need your approval, are stored only as a hash, and can be disconnected at any time.
  • Secrets live in our hosting provider's secret storage, never in our source code, and every change to our code is scanned for leaked secrets.
  • Logs: what we send our AI providers and what they answer is removed from our logs after 7 days.
  • Dependencies are checked automatically for known vulnerabilities.
  • Access to production data is limited to the people at Homiq BV who need it, and everyone we allow to process personal data is bound by confidentiality. Our support team can open every site, to help you and to keep Orbit working.

How Orbit works with your sites

  • Nothing publishes itself. Content reaches a CMS only when someone in your account publishes it.
  • You control every connection. Orbit uses the CMS and Search Console access you give it, and you can disconnect either at any time.
  • Deleting a site deletes its data, its files included.
  • Our AI providers do not train their models on your data.

If something goes wrong

If a personal data breach affects your data, we tell you without undue delay, and in any case within 48 hours of becoming aware of it, with what we know and what we are doing about it. The Data Processing Agreement sets out the rest.

Ask Orbit

Answers from every page of goorbit.io

Ask about what Orbit does, what it costs, or how it fits the way you work. Each answer links to the page that covers it.

Try asking