Legal
Security & breach policy
Last updated: 13 November 2026
This page summarises the technical and organisational measures we use (UK GDPR Art 32) and how we respond to a personal data breach (Arts 33 and 34). It describes controls we operate; it is not a certification — we do not claim ISO 27001, SOC 2 or similar unless and until we publish a certificate.
Security measures
- HTTPS (TLS) for all traffic.
- Database row-level security with deny-by-default tables, plus server-side checks that every request is scoped to the signed-in user's practice. Privileged (service-role) access is used only on the server after those checks.
- Two-step verification, time-limited sessions, and role / module access inside a practice. Destructive client actions are limited to owners and administrators and need typed confirmation.
- HMRC and similar credentials encrypted at rest (AES-256-GCM); secrets, tokens and password hashes are never included in data exports or logs.
- Append-only audit trail of filings and an append-only security-event log; identifiers such as NINO and UTR are masked in list views.
- Data minimisation and automatic deletion of short-lived data (such as one-time codes) on a schedule — see the retention tables.
- Sub-processors bound by written terms and listed publicly.
If a personal data breach happens
- Detect & contain. Anyone who suspects a breach reports it immediately to the security contact below. We contain the incident first (revoke credentials / sessions, isolate systems) and preserve evidence.
- Assess. We record the facts — what happened, which data and how many people, the likely consequences — in an internal breach register, whether or not it is reportable.
- Notify the ICO within 72 hours. Where we are the controller and the breach is likely to result in a risk to people's rights and freedoms, we report to the Information Commissioner's Office without undue delay and no later than 72 hours after becoming aware, even if some details are still being established.
- Tell affected people. Where the risk is high we tell the individuals concerned without undue delay, in plain language, with what happened, likely effects and what to do.
- Tell our customers. Where we are the processor we notify the affected practice (the controller) without undue delay and within 48 hours of becoming aware, so it can meet its own 72-hour duty.
- Learn. We fix the cause, review the incident and update our controls.
Report a security issue or suspected breach
Email info@hydratax.uk ([TODO: create a dedicated security@ mailbox/alias and replace securityEmail]). Please include what you saw and when, but never send passwords or other secrets.
Regulator: Information Commissioner's Office — ico.org.uk, telephone 0303 123 1113.