Encrypted in transit and at rest
HTTPS protects data on its way to you. The database and file-storage providers encrypt it where it is stored.
Your HR records are stored in the EU and UK, encrypted, and each person in your organisation sees only what their role allows. Every provider HollyHR uses is listed publicly, so you can check us against your own requirements.
HollyHR checks this each time someone opens a record or makes a change, not just when they sign in.
Some actions ask for a fresh check even when you are signed in: full personal-data, organisation and payroll exports, permanent erasure, bank-detail changes, and role and ownership changes.
A support or security session for HollyHR staff is time-limited, recorded and shown to you in Settings.
Your HR records are in the EU (Frankfurt). Uploaded documents and database backups are in the UK (London).
HTTPS protects data on its way to you. The database and file-storage providers encrypt it where it is stored.
Selected bank, tax, government ID and pay values get a second layer of encryption inside HollyHR.
Documents are stored privately in the UK (London). A person allowed to open one gets a link that expires after 60 seconds. Storage is unlimited on every plan (fair use), up to 25 MB a file.
Every night HollyHR backs up the whole database to AWS London. Each copy is locked so it cannot be changed or deleted early, and is kept for 35 days.
To restore, HollyHR loads a backup into a separate database and checks it before repairing live data. HollyHR last rehearsed a full restore of its production database this way on 19 July 2026.
A System Admin can download an organisation export from Settings on any plan, without a support ticket or a fee.

What HollyHR collects, why it is used and the rights available.
The controller and processor duties behind the service.
Every named provider, purpose, location and safeguard.
The rules for accounts, API keys, uploads and connected tools.
How to report a security problem and the rules for testing.
Current operational information and incident updates.
Each person in your organisation sees only what their role allows, and HollyHR staff can see your data only during a recorded support or security session. Data is encrypted in transit and at rest, with an extra layer on selected bank, tax, government ID and pay values. Documents are private and shared through short-lived links, and sensitive actions are recorded.
Primary HR records are in the EU and the application runs in the EU and USA, while uploaded documents and HollyHR database backup copies are stored in AWS London. Supporting providers, including email, billing, support and human mailbox services, have their own regions and transfer terms, so HollyHR does not claim that all processing stays in the UK.
The customer controls its organisation data. HollyHR processes that data to provide the service under its Data Processing Agreement. Customers can prepare an organisation export without opening a support ticket, but some provider records and legal-retention evidence have separate handling boundaries.
Yes. Anyone can add a passkey or an authenticator app for two-step sign-in, and accounts with an authenticator app verify at every sign-in. A System Admin can require two-step sign-in for admins or for everyone, in Settings under Sign-in & domain. Full personal-data, organisation and payroll exports, permanent erasure, bank-detail changes, role and ownership changes, Slack, Teams and payroll connections, and security settings ask for a fresh check first. HollyHR staff need MFA to enter the admin workspace.
Not through blanket impersonation. HollyHR staff can see your data only during a support or security session, which is time-limited, limited to your organisation, recorded and shown to you in Settings. Staff must pass multi-factor sign-in to start one, and revealing sensitive details asks for a fresh check. During a session staff can see your people records, so HollyHR does not claim they can never see customer data.
HTTPS protects service traffic and the managed database and object-storage providers encrypt data at rest. HollyHR also applies authenticated application encryption to selected bank, tax or government identifier and compensation values.
HollyHR backs up the whole database every night and stores each copy in AWS London. Copies are locked so they cannot be changed or deleted early, and are kept for 35 days. To restore, HollyHR loads a backup into a separate database and checks it before repairing live data; HollyHR last rehearsed a full restore of its production database this way on 19 July 2026. HollyHR does not publish recovery-time (RTO) or recovery-point (RPO) targets today.
No. HollyHR does not publish an uptime SLA or uptime target today. Live service status and incident updates are at https://status.hollyhr.com/. Enterprise agreements can include negotiated contract terms and an SLA.
HollyHR has documented incident and personal-data-breach procedures, production health checks and a public status page. Under its Data Processing Agreement, HollyHR will tell an affected customer without undue delay after becoming aware of a personal data breach affecting that customer's data.
No. HollyHR is not currently certified to ISO 27001, SOC 2 or Cyber Essentials, and it has not completed an external penetration test.
An authorised customer can prepare a structured organisation export with named CSV areas, eligible uploaded files and a manifest. Ordinary leaver offboarding archives access; it is not data erasure, and the person's records remain. Verified erasure removes or anonymises identifying live data, queues known document and avatar objects for deletion, and keeps only the records it must keep for legal, audit and operational reasons. Provider-side records need separate handling, while backup copies age out rather than disappearing instantly.
No software makes an employer automatically compliant. HollyHR provides a DPA, sub-processor register, access controls, export, DSAR and erasure routes to support UK GDPR duties. The customer still decides lawful basis, notices, permissions, retention and how the service is used.
Holly runs in Amazon Bedrock: GLM 4.7 Flash in AWS London by default or, from 1 December 2026, Claude Haiku 5.5 in AWS's UK and EU Regions. AWS states that Bedrock does not use prompts or responses to train AWS models or share them with model providers. AWS keeps no copy of Holly's requests or answers and does not log them. HollyHR itself keeps Holly questions and answers for 30 days. A customer-selected agent connected through API or MCP follows that provider's own retention, training, region and sub-processor terms.
See HollyHR with your own team, or bring us a security question first. You can start without a card or sales call.