Security and compliance
Last updated 10 November 2026
This page lists what we do to keep Halo Benefits secure and to meet data protection law. Each measure shows where it stands.
- In place
- Done and working today.
- Underway
- Started or booked.
- Planned
- Agreed and scheduled.
Certifications and testing
| Measure | Status | Where it stands |
|---|---|---|
| Cyber Essentials | Underway | Assessment booked with an IASME-accredited assessor. |
| Cyber Essentials Plus | Underway | Assessment booked with an IASME-accredited assessor. It follows Cyber Essentials. |
| ISO 27001 | Planned | Work towards certification runs from December 2026 to June 2027. |
| Independent CREST penetration test | Underway | Booked for November 2026. |
| Load test | In place | In October 2026 we tested the service with 200 people using it at once, in a test environment. It met our speed targets with no errors. |
How we protect information
| Measure | Status | Where it stands |
|---|---|---|
| Encryption | In place | Information is encrypted when it moves between you and Halo Benefits, using TLS 1.2 or higher. The database, its backups and uploaded documents are encrypted when stored. |
| Sign-in | In place | People sign in with a code sent by email. Employer admins also use an authenticator app. Demo accounts use the emailed code. |
| Session time limit | In place | A signed-in session ends after 30 minutes without use, and after 8 hours in any case. |
| Audit log | In place | Changes, approvals and downloads are recorded in an audit log for each employer. The service can only add entries to it. |
| Employer separation | In place | Each employer's records are kept apart from all others. A database query must name one employer, or it is refused. |
| Backups and restore test | In place | The database is backed up every 6 hours. Backups are encrypted, held in London apart from the database, and kept for 30 days. We test that a backup restores. The last timed test was on 29 October 2026. |
| Monitoring and alerts | In place | Alarms tell our engineers about errors, slow pages, downtime and bursts of refused sign-ins. Threat detection is switched on for our Amazon Web Services account. |
| Code checks | In place | Every code change is scanned for passwords and keys before it is merged. The software packages we depend on are checked every night for known vulnerabilities. |
| Incident plan | In place | We have a written incident plan, adopted on 21 October 2026. If personal information is affected, we tell each affected employer within 24 hours of finding out. |
Privacy and data protection
| Measure | Status | Where it stands |
|---|---|---|
| ICO registration | In place | Registered with the ICO: ZC050335. |
| Privacy and AI risk assessments | In place | We completed and signed off a data protection impact assessment and an AI risk assessment on 10 October 2026. Updates for features added since then are awaiting sign-off. |
| Where information is held | In place | The database is in Frankfurt, Germany. The app's processing and our backups are in London, United Kingdom. |
| Sub-processor list | In place | We publish every company that handles information for us, with what it does, where it works and what it sees. |
| Privacy notice | In place | Our privacy notice explains what we hold, why, who sees it, how long we keep it and your rights. |
Company and contact
Halo Benefits is a trading name of GRW Halo Ltd, registered in Scotland (SC861469). Registered office: 93 George Street, Edinburgh, EH2 3ES.
For security questions, email hello@halobenefits.com.
