• Platform
  • How it works
  • Human Factors
  • FAQs
Register interest Sign in
Sign in Register interest

Data processing addendum

Last updated 22 September 2026 Operated by to be confirmed Governing law: England and Wales

The Article 28 terms under which HFS Central processes your employees' personal data on your behalf: instructions, sub-processors, breach notification, audit, deletion and the security measures we commit to.

On this page

  1. Parties and scope
  2. Details of processing
  3. Processor obligations
  4. Controller obligations
  5. Sub-processors
  6. Data subject requests
  7. Breaches
  8. Audit
  9. Return and deletion
  10. International transfers
  11. Liability
  12. Annex 1: security measures

All policies

  1. Privacy policy
  2. Terms of service
  3. Data processing addendum
  4. Cookie policy

1. Parties and scope

This addendum is between the company holding a HFS Central account (the Controller) and to be confirmed (the Processor). It applies whenever we process personal data on your behalf in providing the service and forms part of the terms of service. It is written to satisfy Article 28 of the UK GDPR. Where you also process data of people in the EU, the equivalent EU GDPR provisions apply.

2. Details of processing

Subject matterHosting a register of the Controller's workforce, delivering training modules to them and recording completions.
DurationThe life of the account, plus the 30-day read-only notice period after the owner asks to close it, or until earlier deletion on instruction.
Nature and purposeStorage, retrieval, display, sending of transactional email, and export, so that the Controller can meet its duties as an employer.
Categories of dataName, work email, role, sign-in activity, module assignments, completion dates and scores.
Data subjectsThe Controller's employees, workers, contractors and administrators.
Special category dataNone is required. The Controller must not enter any.

3. Processor obligations

We will:

  • process personal data only on your documented instructions, which are these terms, the settings you choose in the application and any written instruction you send us, unless the law requires otherwise, in which case we tell you first where we may;
  • make sure everyone with access is bound by confidentiality;
  • implement the technical and organisational measures in Annex 1;
  • engage sub-processors only under section 5;
  • help you respond to data subject requests under section 6 and meet your obligations on security, breach notification and impact assessments;
  • delete or return the data under section 9;
  • make available the information needed to show compliance and allow audits under section 8;
  • tell you straight away if we think an instruction breaks data protection law.

4. Controller obligations

You warrant that you have a lawful basis for the data you enter, that you have told your people the platform is in use, that you will not enter special category data, and that your instructions comply with the law. You are responsible for the accuracy of the data and for the access you grant to your own owners and admins.

5. Sub-processors

You authorise the sub-processors below. We will give you at least 30 days' notice by email before adding or replacing one. If you object on reasonable data protection grounds and we cannot resolve it, you may cancel and receive a refund of any prepaid period.

Sub-processorPurposeLocation
Hosting provider (to be confirmed)Servers, database, files and backupsto be confirmed
Cloudflare, Inc.DNS for our domainsGlobal
Stripe Payments Europe LtdPayments and invoicing for the Controller's billing contact, once online billing opens. Not used until then.Ireland, United States

Email is sent from a Postal mail server we operate ourselves; no third-party email service processes your data. No artificial intelligence service processes your data. Integrations you choose to connect (for example SafetyCulture) exchange data with that provider on your instruction; they are listed in the application with what they read.

Each sub-processor is bound by written terms no less protective than this addendum. We remain liable to you for their performance.

6. Data subject requests

If a data subject contacts us directly about data we process for you, we will not respond on the merits but will forward the request to you within five working days. The application lets owners view, correct, export and delete a person's record, which covers most requests without our involvement. Where you need more, we will help at no charge for reasonable requests.

7. Breaches

We will notify you without undue delay, and in any case within 48 hours of becoming aware, of a personal data breach affecting your data. Our security contact is [email protected]. The notice will describe what happened, the data and people likely affected, the likely consequences and what we are doing about it, with updates as we learn more. We will not notify a regulator or data subjects on your behalf unless you ask us to.

8. Audit

Once a year, on 30 days' written notice, you may audit our compliance with this addendum by reviewing the documentation we provide, which includes our security measures, sub-processor list and, where available, third-party assessments of our hosting provider. If that is not enough to satisfy a regulator, you may carry out an on-site or remote audit at your cost, during business hours, without disrupting other customers, under confidentiality.

9. Return and deletion

Throughout the agreement the owner can download a full export of everything the company holds from Settings → Company. You set how long each type of record is kept (for example closed incidents, at least three years); records under a legal hold you place, or that open work depends on, are never removed. When the owner closes the company it becomes read-only at once and is deleted from live systems after 30 days unless a legal hold is in place or the closure is cancelled. Backups age out after a period to be confirmed. We keep only what the law requires us to keep, such as invoices, and only for as long as it requires.

10. International transfers

Your records are stored in the location confirmed in your agreement (to be confirmed). Where a sub-processor processes data outside the UK, the transfer is covered by the UK International Data Transfer Agreement or the UK Addendum to the EU Standard Contractual Clauses, together with any supplementary measures needed. Copies are available on request.

11. Liability

Liability under this addendum is subject to the limits in the terms of service. Each party remains liable to data subjects and regulators as the UK GDPR provides.

Annex 1: security measures

  • Isolation: every company's data is tagged with its company at the row level and every query is constrained to the signed-in person's company. A request with no company context returns nothing rather than everything.
  • Access control: permissions the company configures per role, with site limits; two-step sign-in for privileged roles; platform staff see company data only through time-limited access the company approves, and every such session is logged.
  • Encryption: TLS in transit; credentials for connected services encrypted in the database; passwords stored as salted one-way hashes. Storage and backup encryption at rest: to be confirmed.
  • Files: kept on private storage, never public; each file opens only for people allowed to see the record it belongs to; type and size are checked from the file's content; malware scanning before storage where enabled for the deployment.
  • Authentication: per-person sign-ins, rate limiting on sign-in attempts, session expiry, signed one-time links for email verification and password reset.
  • Payments: when online billing opens, handled entirely by Stripe; card numbers never reach our systems.
  • Resilience: database backups (schedule to be confirmed); last restore test: not yet recorded; a public status endpoint reports database, queue and scheduler health.
  • Development: automated tests, including tests that prove company isolation, run before every release; dependencies are kept current; secrets are held outside the codebase.
  • People: confidentiality obligations for staff and contractors; access removed on departure.
Product
  • Platform
  • Modules and availability
  • Integrations
  • Maturity assessment
  • Human Factors
  • Pricing
For organisations
  • Register interest
  • How to get started
  • About
  • FAQs
Account
  • Sign in
  • Register interest
  • [email protected]
Legal
  • Privacy policy
  • Terms of service
  • Data processing addendum
  • Cookie policy
Email
[email protected]
Coverage
Built for UK organisations
Commitment
Your records stay yours
© 2026 HFS Central · Connected health, safety and Human Factors management · Privacy Terms Cookies · Built by CPH Solutions
Each organisation’s data kept apart Audit trail on every change No list prices, no automatic billing