Privacy policy
Halloway builds models that understand people, teams and companies. That makes privacy part of the product, not a page at the bottom of it. This policy explains what we collect, why, how long we keep it, and how you can see, change or remove it.
The short version
- We collect only what the job needs, and every fact carries its source and date.
- Your company’s data trains only your company’s private model. Never anyone else’s.
- A person makes every hiring decision. Orbit never rejects anyone on its own.
- Your own employees are read at team level only, in groups of five or more. Nobody is named or scored.
- We do not sell personal information, and we never will.
- Anyone can ask what we hold, correct it, or have it removed.
01Who we are
Halloway is the trading name of HALLOWAY LTD, a company registered in England and Wales under number 17275096, with its registered office at 66 Paul Street, London, England, United Kingdom, EC2A 4NA. We build Orbit 1.0, a People World Model for hiring and team planning.
Questions about privacy go to privacy@halloway.ai.
02Who this policy covers
| Who | What it means |
|---|---|
| Website visitors | Anyone who visits halloway.ai or contacts us. |
| Customers and their teams | Companies that use Orbit, and the recruiters, managers, executives and people teams who sign in. |
| Candidates and professionals | People whose professional information appears in Orbit, because they are in the market or a customer is considering them. |
| Customers’ employees | People who work at a customer, when that customer uses Orbit’s team, executive or people features. |
03Our role
Data protection law separates the organisation that decides why data is used (the controller) from the one that handles it on their behalf (the processor). Our role depends on the data.
| Data | Halloway’s role |
|---|---|
| Website, enquiries, customer accounts and billing | Controller |
| Halloway’s market model, built from public professional information | Controller |
| Everything inside a customer’s private workspace: their ATS, HR system, notetaker, email, goals, notes and decisions | Processor, acting on the customer’s instructions under a data processing agreement |
04What we collect, and where from
- Website visitors. The contact form needs only a work email. Company and role are optional. Our servers log IP address and browser type for security. If you accept analytics cookies, we count page visits without identifying you.
- Customer accounts. Each team member’s name, work email, role and permissions, how they use Orbit, and the notes, comments and decisions they add. Billing details are held by our payment provider. We never store card numbers.
- Applicant tracking systems. Roles, stages, assignments, outcomes and the candidates in them.
- HR systems. Teams, reporting lines, titles, levels, start dates, locations and leaving dates. We do not read performance reviews, health, leave, disciplinary or demographic information. For People features we do not connect employer HR pay bands by default. Where relevant, Orbit may use publicly available market compensation signals together with self-declared pay or level data your admins choose to provide.
- Interview notetakers. Transcripts and notes of interviews the customer recorded with the consent the law requires, for people in the customer’s projects only.
- Email and calendar. With a recruiter’s permission, Orbit uses the narrowest send access Google or Microsoft offers, reads only replies to threads Orbit started, and checks availability to book interviews. Message bodies are never logged.
- Goals and roadmaps. Read-only goals, deadlines and progress from tools such as Linear, Jira, Asana or Notion, through connections the customer’s admin sets up.
- Ask Orbit and our MCP server. The questions people ask Orbit, from our app or from AI tools like Claude or ChatGPT, and the answers. Kept for 12 months by default. The customer can choose a shorter period.
- Public professional information. Roles held, employers, dates, skills, projects, publications and other work people have published professionally.
We do not deliberately collect information about health, ethnicity, religion, sexual orientation, political views, trade union membership or other special categories, we do not infer them, and we do not analyse voice, face or tone.
05How we use it, and why we are allowed to
| Purpose | Lawful basis |
|---|---|
| Replying to enquiries and arranging briefings | Legitimate interests, and steps you ask for before a contract |
| Providing, securing and supporting Orbit | Contract with the customer |
| Building and maintaining the market model from public professional information | Legitimate interests, under a recorded assessment. You can object at any time and we will stop. |
| Finding and assessing candidates for a customer | The customer’s basis, usually legitimate interests. We act on their instructions. |
| Team-level analysis of a customer’s own employees | The customer’s basis. The customer must tell its employees, and we supply a template notice and an impact assessment pack. |
| Drafting outreach and interview emails | The customer’s basis. A person sends every email from their own mailbox. |
| Measuring which pages of our website help | Consent, which you can withdraw at any time |
| Tax, accounting and legal obligations | Legal obligation |
06How Orbit reaches its answers
- Orbit never makes a decision about a person on its own. It never rejects a candidate, and nothing reaches an ATS or a candidate’s inbox until a person acts.
- Every reading opens to the evidence behind it, with sources and dates, so a person can check it.
- Where evidence is missing, Orbit says so rather than marking someone down.
- Risk and health readings about a customer’s own people are shown for teams of five or more, never for individuals.
- You can ask a customer, or us, for an explanation of how Orbit read your information and for a person to review it.
07What we will never do
- Sell or rent personal information.
- Use one customer’s data to train or improve another customer’s model, or show it in anyone else’s benchmarks.
- Score, rank or flag a customer’s individual employees for risk of leaving.
- Infer protected characteristics.
- Use advertising or cross-site tracking cookies.
09Moving data between countries
Customer workspaces are hosted in the United Kingdom (London) and the United States (New York), using Google Cloud regions appropriate to each workload. Where information leaves the UK or the European Economic Area, we rely on an adequacy decision or on approved safeguards, such as the UK International Data Transfer Agreement or the EU Standard Contractual Clauses, with the additional measures they require.
10How long we keep it
| Information | How long |
|---|---|
| Enquiries | For as long as needed to handle your enquiry, unless you become a customer |
| Customer account data | The life of the contract, then deleted or anonymised within a reasonable period agreed in your contract |
| Workspace data | Under the customer’s retention settings. Returned or deleted within 30 days of the contract ending |
| Ask Orbit conversations | 12 months by default. The customer can set a shorter period |
| Interview transcripts | The customer’s setting, 12 months by default |
| Public professional information in the market model | While it stays relevant to the market, reviewed at least every two years, and removed on request |
| Suppression records | Kept so that someone who opted out is never added again. We keep only a hashed form of their email |
| Audit logs | as long as needed for security and compliance |
11Your rights
You can ask us for a copy of your information, to correct it, to delete it, to restrict or object to how we use it, to receive it in a portable form, and to withdraw consent. You can also object to the market model including you at any time.
The quickest route is our data deletion request form: enter your email and confirm from the link we send. For anything else, write to privacy@halloway.ai. We reply within one month. We may ask you to confirm who you are first.
If we cannot resolve a concern, you can complain to the Information Commissioner’s Office in the UK, or to the data protection authority where you live or work.
12Security
- Every customer’s workspace is isolated from every other.
- Information is encrypted in transit and at rest.
- Connections to other tools are read-only unless the customer turns on sending, and Orbit’s own MCP server has no tools that change anything.
- Access is limited to the people who need it, and every view, export and send is logged.
- Anything returned by another company’s systems is treated as data, never as instructions.
13Children
Orbit is a professional tool and is not intended for anyone under 18. We do not knowingly collect information about children.
14Changes to this policy
If we change this policy in a way that matters, we will say so at the top of this page and tell customers by email before the change takes effect.