
Security and data protection
Your health and safety records include incidents, training and, sometimes, health information about your people. This page explains in plain terms how Featherstone Safety Ltd protects them, including where we fall short of what larger suppliers offer.
Checked against the live service: 13 November 2026 · See also: Privacy Policy · Subprocessors · Data Processing Schedule
Where your data is stored
The live service runs in Ireland (EEA): the database is hosted by Supabase in AWS eu-west-1, and the application’s server-side processing runs in Vercel’s Dublin region. While we prepare to move our hosting to London, a copy of the database and uploaded files is kept in Supabase’s London region, used only to rehearse the move.
Some providers we rely on may process data outside the UK and EEA: transactional email (Resend) and, only if your organisation switches it on, Featherstone AI (Anthropic). Those transfers are covered by the Standard Contractual Clauses and the UK International Data Transfer Addendum. So we cannot say that all of your data is processed in the UK. The subprocessor list sets out every provider, what it holds and where, and the privacy policy covers the rest.
Keeping each organisation's records separate
Every customer has its own workspace, and every table in the application database has row level security switched on, so the database itself refuses to return one organisation’s records to another. The few server operations that need wider access check who is asking and which workspace they belong to before they run.
Inside your workspace, admins decide who can see and change what: admins, managers and members have different permissions, and admins can make registers read-only for members.
Signing in
- Sign-in is handled by Supabase’s authentication service. Passwords are stored only as hashes; we never see them.
- Every user can switch on two-factor authentication with an authenticator app, under Account, Security. We recommend it for every admin.
- Each request is checked on the server against the signed-in session, never against an identity the browser supplies.
- Our own application routes are rate limited to slow down automated abuse.
Encryption and files
- All traffic uses HTTPS. Browsers are told to use HTTPS only (HSTS, with preload), and pages cannot be framed by other sites.
- Data is encrypted at rest by the hosting providers.
- Uploaded files, such as certificates, safety data sheets and evidence, are kept in private storage. They are opened through short-lived signed links, never a permanent public address.
A tamper-evident audit trail
Changes to records are written to an audit log that records who did what and when. Each entry is cryptographically linked to the one before it (SHA-256), so altering or deleting an entry breaks the chain. Admins can check the chain at any time with the “Verify chain” button on the Audit Log page.
Backups and getting your data out
A scheduled job takes a compressed copy of the database every night and keeps it for 30 days in GitHub’s infrastructure, separately from the database provider, with access restricted to the company’s director.
You can export your records to PDF and CSV whenever you like. If you cancel, your account stays accessible for 30 days so you can export everything you need. The details are in the Data Processing Schedule (DPS 11 and DPS 14).
Payments
Subscriptions are billed through Stripe. Card details are entered on Stripe’s own pages and never reach our servers. Messages from Stripe to the Hub are checked against Stripe’s signature before anything is changed.
Featherstone AI
AI assistance is off until an admin of your organisation switches it on, and nothing is sent to an AI provider while it is off. When it is on, only the details needed for each answer or draft are sent, with the names attached to records removed. How Featherstone AI works and how it handles your data.
Working offline on site
The Hub keeps working without signal. To do that, records you have opened are stored by the browser on that device. That copy is protected by the device, not separately encrypted by the Hub, so use a device passcode and sign out of shared devices.
If something goes wrong
If a personal data breach affects your data, we will tell you without undue delay and, where feasible, within 72 hours of becoming aware of it, as set out in DPS 13. To report a security concern or a suspected vulnerability, email thomas@featherstonesafetyhub.co.uk.
Certifications and supplier questionnaires
Featherstone Safety Hub does not currently hold ISO/IEC 27001 or Cyber Essentials certification, and we do not claim it does. If your organisation needs a supplier security questionnaire completed, email thomas@featherstonesafetyhub.co.uk and we will answer it.
Who we are
Featherstone Safety Ltd, registered in England and Wales, company number 17410006. Registered office: 14/2E Docklands Business Centre, 10–16 Tiller Road, London, E14 8PX. ICO registration 00013953517. Questions about security or data protection: thomas@featherstonesafetyhub.co.uk.
© 2026 Featherstone Safety. Featherstone Safety Ltd, registered in England and Wales, company number 17410006.