Skip to content

Security and compliance

Where your data is kept, the agreements that cover it, how it is encrypted and backed up, who can reach it, how it is deleted and how to report a security problem.

Reference8 min read

This page is for whoever answers your company's security questionnaire. Everything here describes how Bifröst Orbit works today. The legal pages on bifrostorbit.com are the binding version.

Where your data is

Orbit, every satellite and their database
Provider
IONOS
Where
Two servers in Spain. The standby keeps a live copy of the database and takes over if the main server fails.
Uploaded files and backups
Provider
Amazon Web Services (Amazon S3)
Where
Ireland
Email: sign-in codes, invitations, notifications
Provider
Resend
Where
Sent from Ireland
Domain names, network delivery and protection against attacks
Provider
Cloudflare
Where
Cloudflare's worldwide network

CMS Orbit's search by meaning (Gravity) runs on our own servers in Spain too, with an open model, so content is not sent to another company to be searched.

Cloudflare is the one exception to keeping data in the EU: traffic may pass through its network outside the EU, under the EU-U.S. Data Privacy Framework and Standard Contractual Clauses.

A few more providers do one job each: Slack for our support chat, Sentry for error reports (stored in Germany), DeepL for machine translation when someone asks for it, OpenRouter for Insights Orbit's weekly summaries and Orbit AI, the assistant in Bifröst Orbit, every satellite, the docs and our website (through its EU region, with no data kept), Microsoft for Entra sign-in when you connect your own tenant, Google for Google sign-in when you turn it on, and Stripe for paying for your plans. Apple will deliver push notifications once the Orbit app for iPhone is released. The sub-processors page lists every one, with what it does, where and under which safeguards.

Services you connect with your own account, such as your own identity provider for OpenID Connect, SAML or SCIM, your Stripe account in Booking, Commerce and Travel Orbit, your Twilio account for text messages, your calendars, an AI provider you add a key for, or the services you connect under Connections, such as your own bucket, Cloudinary, Slack or Algolia, receive data because you send it to them, under your own agreement with them. They are not our sub-processors.

Agreements

  • Data processing agreement: our DPA under Art. 28 GDPR is part of the terms of service, so it applies from the moment your organisation uses Bifröst Orbit, with nothing extra to sign. Its annex lists the technical and organisational measures.
  • Sub-processor changes: announced on the sub-processors page at least 30 days before they take effect, so you can object.
  • Breaches: we tell you without undue delay, and within 48 hours where possible.
  • Audits: you can audit us, or appoint an auditor, at most once a year unless there is a breach or an authority requires it.
  • Privacy: the privacy policy says what we collect, why and for how long.

All legal documents are also in one PDF. Questions go to legal@bifrostorbit.com.

Encryption

  • In transit: every connection uses TLS, and browsers are told to use HTTPS only. The copy of the database between our servers travels through an encrypted tunnel.
  • Secrets you give us: SSO client secrets, Stripe keys, Twilio tokens, calendar connections, AI provider keys, keys and tokens for the services under Connections, webhook secrets and booking form answers marked sensitive are stored encrypted with AES-256-GCM. Screens show only their last four characters.
  • Keys and codes: API keys, agent keys, SCIM tokens and sign-in codes are stored only as hashes, so they can't be read back, not even by us. A key is shown once, when it is created.
  • Files and backups at rest: uploaded files and the backups are stored in Amazon S3, which encrypts them at rest. If you connect your own bucket, new uploads are stored there instead, in your own account.
  • The database at rest: the database, and a cache of recently served files, sit on the servers' disks in Spain. They are protected by access controls on the servers and the data centre's physical security. We don't add encryption at rest to those disks.

Backups and outages

  • Live copy: the standby server copies each change to the database as it happens.
  • Backups: every hour the databases are backed up to Amazon S3 in Ireland, off the servers, and the last 48 are kept. A nightly backup is kept for 14 days.
  • Files are stored in Amazon S3 from the start.
  • Tested: switching to the standby was tested in production on 29 October 2026, and production backups were restored on a separate machine on 8 November 2026.

The trust centre says what happens in each kind of outage and what you can count on.

Who can reach your data

  • Your people sign in with SSO, a passkey or an email code: there are no Bifröst Orbit passwords. For a passkey, Orbit keeps only its public key, and owners and admins can switch passkeys off. Email codes expire after 10 minutes, work once and stop working after five wrong tries. A browser session lasts at most eight hours, and signing out ends it at once in every satellite. See Choose how your people sign in.
  • Roles are checked on the server for every request, and every record belongs to one organisation, which every read and write is limited to. See Roles across satellites.
  • AI agents act for one person, never with more rights than they have, and page changes they draft in CMS Orbit need a person's approval.
  • Our team: Bifröst Orbit's platform admins are our own staff who run the service. To give support and keep the service running and secure, they can open every organisation in Orbit, and every satellite except CMS Orbit with the Admin role. In CMS Orbit they need to be added like anyone else. Changes they make in a satellite appear in its audit trail under their own name. Each time one of them opens your organisation in Orbit or a satellite, Orbit's audit trail records it, once an hour for each place, marked as a platform admin. Changes they make in Orbit are recorded there the same way. The DPA says the same.

Records of what happened

  • Changes: each satellite keeps its own record. CMS Orbit's audit log says who changed what, when and on whose behalf, including AI agents and API keys, and can be downloaded as CSV. How far back you can look depends on the plan: 30 days on Starter, a year on Growth and everything on Enterprise. The other satellites each have an audit trail for their Admins. Orbit's own audit trail, for owners and admins, records members invited, removed or given another role, ownership handed over, sign-in settings (providers, passkeys, required SSO and role mapping), every change SCIM provisioning makes, the organisation's name, logo and regions, plans and billing, deleting the organisation, and every visit by our platform admins. See The audit trail.
  • Sign-ins: Orbit records each sign-in attempt, with the email address, the way of signing in, whether it worked and when. These records are kept for 12 months, and erased sooner when the person deletes their account.
  • Server logs have email addresses and IP addresses removed before they are stored, and are kept for 14 days.
  • Error reports sent to Sentry have email addresses, IP addresses, cookies and sign-in details removed first.

Deleting your data

  • Deleting in a satellite: pages, files, products, trips and most other things go to a bin first, where they can be restored. They stay there until an owner empties it for good. A CMS Orbit website can also empty its bin by itself after 30, 60 or 90 days, if you choose that in its settings. Erasing a person's data on request, such as a customer or a candidate, deletes it straight away.
  • Deleting the organisation: an owner confirms with a code sent by email. Every satellite then erases the organisation's data, including CMS Orbit's files in Amazon S3, and Orbit removes its members, sign-in settings, audit trail and the organisation itself. If paid time is left, the owner can choose to delete at the end of the paid period. See Deleting for good.
  • Backups: erased data can remain in backups for up to 14 days, until they are replaced.
  • People's accounts: an account belongs to the person, not to your organisation. Someone who has signed in keeps their account, and any other organisations they belong to, after you remove them or your organisation is deleted, until they delete it themselves. With no organisation left they can still sign in and create one, but can't open any satellite. Accounts that were invited but never used are deleted when they no longer belong to any organisation.
  • Taking your content with you: each CMS Orbit space can be exported as one JSON file from its settings before you leave.

Reporting a security problem

If you find a vulnerability in Bifröst Orbit, email security@bifrostorbit.com. A person on our team reads every report. You can also use Report a vulnerability on any of our public repositories on GitHub, and security.txt lists the same address.

  • What to send: what you found and where, with the steps to reproduce it, what someone could do with it, and how to reach you.
  • While you test: use your own account and organisation, and stop and tell us if you reach another organisation's data. Don't run denial-of-service or load tests, and give us a reasonable time to fix the problem before you tell anyone else.
  • What we do: confirm we have your report, fix what we confirm with the most serious first, and tell you when it's fixed. We credit you if you'd like, but don't pay bounties.

The trust centre has the full rules.

Was this page helpful?

Read next