Skip to content

Your people data,
kept yours.

Orbit reads some of the most sensitive data a company holds. Here is how we protect it, who can see it and what the model will and will not do with it.

Your workspacePrivate instance
Model trained on your data onlyOn
Data regionUK and EU
Employee readingsTeam totals only
Automatic rejectionsNever
Support accessOff until granted
Audit logEvery action

Four promises, built into the product.

A private model for every customer

Each workspace is separate. What Orbit learns from your company stays in your workspace and never trains anyone else's model.

Only what it needs

You choose which systems to connect and what each seat can see. Connections can be paused or removed at any time.

Team totals for your people

Readings about employees appear only for groups of five or more. Nobody gets a score.

A person always decides

Orbit never rejects, moves or contacts anyone on its own. Every action is taken, and logged, by a person.

The detail your security team will ask for.

Everything here is covered in more depth in the security pack.

EncryptionData is encrypted in transit and at rest. Tokens for connected systems are encrypted with keys held in our cloud provider's key service.
Where data livesWorkspaces are hosted in the UK, EU and US. You choose the regions at set-up.
Sign-in and accessSingle sign-on with Google or Microsoft, multi-factor authentication for admins, and permissions set by seat: recruiter, hiring manager, exec and people team.
Audit logSign-ins, invitations, role changes, exports and settings changes are written to an audit log that cannot be edited or deleted.
Support accessOur support team sees your workspace only when an admin grants time-limited access. Every view is logged.
Retention and deletionYou set how long data is kept, including Ask Orbit conversations. At the end of your contract we return or delete your data, as you choose.
Sub-processorsListed in our privacy policy. We tell you before adding or replacing one, and you can object.
CertificationsSOC 2 and ISO 27001 aligned; formal certifications in progress.

Ready for the rules that apply to hiring tools.

The EU AI Act treats AI used in hiring and employment as high-risk. Orbit is built around what the Act asks for.

GDPR and UK GDPR

You are the controller and we are your processor, under a data processing agreement. Orbit can find, export, correct and delete a person's data across your workspace.

Read more →

EU AI Act

A person decides, every output is explained with its evidence and every action is logged. Model documentation is available on request.

Works councils

Employee insights stay off for EU workspaces until you confirm notice and consultation are done. Templates are in the admin panel.

US privacy laws

Candidates and employees can know, correct and delete their information, and are never treated differently for asking.

Read more →

Talk to us about security.

The security pack, our data processing agreement and model documentation, on request.

Request the security pack

Security and privacy questions

Is our candidate data shared with other customers?
No. Each company runs a separate Orbit instance. What your model learns from your hires and interviews is used for you only. It does not improve another customer's shortlists.
Where is data hosted?
Production data is hosted in the UK and EU on enterprise-grade cloud infrastructure. We publish details on subprocessors and regions in our security documentation and DPA.
Is Halloway GDPR compliant?
Yes. We act as processor for customer workspace data and support GDPR and UK GDPR rights. Customers can use our DPA, subprocessors list and privacy documentation for enterprise review.
Are candidate scores stored?
Orbit does not store opaque scores on people. It shows signals with evidence: trajectory, fit to team, culture and timing, each with reasons a recruiter can explain to a hiring manager.

See how a private model works in Orbit, and read why your candidate data should stay yours.