Legal
Privacy Notice
Last updated: 13 November 2026
This notice explains how Hydra Consultancy Services Ltd trading as HydraTax uses personal data, as required by Articles 13 and 14 of the UK GDPR. It covers visitors to our website, people who hold a HydraTax account, and — in the "Client data" section — the individuals whose data our customers (accountants and businesses) process in HydraTax.
1. Who we are
The data controller for account and website data is Hydra Consultancy Services Ltd, trading as HydraTax.
- Company number: 14633422 (Companies House record)
- Registered office: [TODO: registered office address exactly as on Companies House]
- ICO registration: [TODO: ICO registration number (Z…) — pay the data protection fee at ico.org.uk]
- Privacy / data-rights contact: info@hydratax.uk
- Data Protection Officer: [TODO: confirm with counsel whether a DPO is required; if not, say 'not appointed'] — [TODO: DPO / privacy lead name (or 'Privacy lead')] (info@hydratax.uk)
- Post: [TODO: postal address for written data-rights requests (usually the registered office)]
2. Our two roles
Controller. For the data we need to run your HydraTax account (your name, email, practice, billing and security data) we decide why and how it is used, so we are the controller.
Processor. When a practice or business puts its clients', employees' or officers' data into HydraTax (for example payroll records, ledgers, tax identifiers, uploaded documents), that customer is the controller and we are its processor. We only process that data on the customer's documented instructions under our Data Processing Agreement. If you are one of those individuals, please contact the practice or business that holds your data first — we will help them respond to you.
3. Your account data — what, why and how long
We collect this information from you directly (when you register, pay, contact support or use the service) and automatically from your device (for example sign-in, security and error logs). The table shows each category, why we use it, our lawful basis and how long we keep it. Periods in the table are the ones our systems actually enforce.
| Data | Purpose | Lawful basis | Retention |
|---|---|---|---|
| Account & profile (name, email, practice membership, role) name, email address, practice name, role / module access | Create and run your HydraTax account and authenticate you. | Contract (Art 6(1)(b)) | For as long as your account is open. Self-service deletion removes it immediately, or after a 14-day cancellation window if you are a sole practice owner. |
| Two-factor settings (channel, backup email, mobile number) 2FA channel, alternative email, mobile number | Protect accounts with a second factor (UK GDPR Art 32). | Legitimate interests (Art 6(1)(f)); Contract (Art 6(1)(b)) | Until you disable 2FA or delete your account. |
| One-time sign-in codes (hashed) code hash, masked destination, expiry | Verify a sign-in attempt. | Legitimate interests (Art 6(1)(f)) | 24 hours (codes expire within minutes). |
| Orders, subscription and invoice records billing email, plan, amounts, Stripe customer / subscription IDs | Take payment, issue invoices and keep our own accounts and VAT records. | Contract (Art 6(1)(b)); Legal obligation (Art 6(1)(c)) | 7 years from the transaction (6 years from the end of the accounting period per HMRC / Companies Act record-keeping). [source 1][source 2] |
| Support tickets and correspondence with us name / email, message content, page URL, attachments (by email only) | Answer queries, fix problems and defend or evidence disputes. | Legitimate interests (Art 6(1)(f)); Contract (Art 6(1)(b)) | 3 years after the ticket is resolved. |
| Public feature requests and votes display name, optional email, request text, voter key | Collect product feedback. | Legitimate interests (Art 6(1)(f)) | Request text until removed; the optional author email is deleted after 12 months. |
| Email preferences & unsubscribe records reminder / marketing preferences, unsubscribe token, unsubscribe timestamp | Send service reminders and honour marketing opt-outs (PECR). | Contract (Art 6(1)(b)); Consent (Art 6(1)(a)); Legitimate interests (Art 6(1)(f)) | Until you delete your account. |
| Security events (sign-in anomalies, data exports, erasures) event type, user id, hashed IP address, timestamp | Detect, investigate and document security incidents (UK GDPR Art 32, 33(5)). | Legitimate interests (Art 6(1)(f)); Legal obligation (Art 6(1)(c)) | 12 months (breach register entries are kept for 6 years). |
| Data-rights request register and deletion requests requester email, request type, dates, outcome | Meet and evidence the one-month response duty (UK GDPR Art 12). | Legal obligation (Art 6(1)(c)); Legitimate interests (Art 6(1)(f)) | 6 years (limitation period for claims). [source] |
| Webhook de-duplication and WhatsApp bot session state event ids, phone number, session stage | Process each external event once and hold conversation state. | Legitimate interests (Art 6(1)(f)); Customer's instructions (Art 28) | 30 days (bot sessions: 30 days after last activity). |
| Pending team invitations email, display name, invite token | Let a practice owner invite a colleague. | Legitimate interests (Art 6(1)(f)); Contract (Art 6(1)(b)) | 30 days if not accepted; accepted invites are purged after 30 days. |
| Cookies & browser storage (strictly necessary only) session cookies, security cookies, form drafts, HMRC fraud-prevention device id | Sign-in, 2FA, security, saved drafts and HMRC-mandated fraud-prevention headers. | Legitimate interests (Art 6(1)(f)); Legal obligation (Art 6(1)(c)) | Session or up to the lifetimes listed on /legal/cookies; you can clear browser storage at any time. [source] |
We do not sell personal data and we do not use it for advertising or profiling.
4. Client data (we are the processor)
The table below is the default treatment of data a customer places in HydraTax. The customer (the controller) decides how long to keep each record and can export or erase a client at any time from the client's page; we then delete it from our systems as described. Statutory retention periods apply to the customer, not to us — a customer who erases a client is responsible for keeping any records the law requires.
| Data | Purpose | Lawful basis | Retention |
|---|---|---|---|
| Practice activity log (who did what in the desk) actor user id / email, action summary, client reference | Give practice administrators an operational audit trail. | Customer's instructions (Art 28) | 12 months. |
| Client records (name, UTR, NINO, VRN, contact, Companies House data) name, UTR, NINO, date of birth, address, email, phone | Prepare and submit the filings the practice instructs. | Customer's instructions (Art 28) | Until the practice removes the client or closes its account. The practice decides how long its own records are kept. |
| Payroll & employee data held for client employers name, NINO, date of birth, address, pay and deductions, tax code | Run PAYE / RTI (FPS, EPS) for the client. | Customer's instructions (Art 28) | Employers must keep payroll records for 3 years from the end of the tax year; the practice decides. We hold them until the practice instructs deletion. [source] |
| Returns & ledgers (VAT, CT600, Self Assessment, accounts, bank transactions) financial figures, bank transactions, HMRC receipts | Prepare filings and keep supporting evidence for the practice. | Customer's instructions (Art 28) | Statutory minimums: companies 6 years from the end of the financial year; Self Assessment 5 years after the 31 January deadline; VAT 6 years. We hold until the practice instructs deletion. [source 1][source 2][source 3] |
| Uploaded client documents (files) scans, statements, invoices, ID evidence uploaded by the practice | Store supporting documents for the practice. | Customer's instructions (Art 28) | Until the practice deletes the document or client. |
| Client emails, WhatsApp messages and task inbox email addresses, message previews, attachments metadata | Record correspondence the practice sends/receives through HydraTax. | Customer's instructions (Art 28) | 6 years from sending, aligned with typical practice record-keeping; the practice may delete earlier. |
| HMRC OAuth tokens and Government Gateway credentials (encrypted) OAuth access/refresh tokens, encrypted gateway user id / password | Submit to HMRC on the practice's instruction. | Customer's instructions (Art 28) | Until disconnected, replaced, or the client / account is erased. |
| Submission audit evidence (hash-chained) actor id, action, entity id, HMRC status / correlation id, payload hash | Evidence that a filing was prepared and submitted, and tamper-evidence for disputes with HMRC. | Legal obligation (Art 6(1)(c)); Legitimate interests (Art 6(1)(f)); Customer's instructions (Art 28) | 7 years from the event. [source] |
5. Who we share data with
Statutory recipients (only when you instruct a filing)
- HM Revenue & Customs (HMRC) — Receives VAT, Corporation Tax, Self Assessment and PAYE submissions on your instruction. Independent controller / public authority.
- Companies House — Receives confirmation statements and accounts; we also read the public register. Independent controller / public authority.
Service providers (processors / sub-processors)
These organisations help us run the service under written contracts that limit them to our instructions. The same list is maintained on our sub-processor page.
| Provider | What it does for us | Data | Location | Transfer safeguard |
|---|---|---|---|---|
| Supabase, Inc. | Authentication, Postgres database, file storage | Account, practice and client records; authentication data | [TODO: Supabase project region (e.g. London / EU / US)] | [TODO: confirm transfer mechanism in the signed vendor DPA (UK adequacy / UK–US Data Bridge / UK IDTA or Addendum)] |
| Netlify, Inc. | Application hosting, serverless functions, edge delivery | All data in transit; request metadata and logs | US-headquartered with global edge network; function region [TODO: Netlify function region] | [TODO: confirm transfer mechanism in the signed vendor DPA (UK adequacy / UK–US Data Bridge / UK IDTA or Addendum)] |
| Cloudflare, Inc. (R2 object storage, D1 database) | Uploaded document storage and heavy desk tables (payroll, ledger, VAT, bank) | Client documents; payroll, ledger, VAT and bank-transaction rows | [TODO: R2 bucket jurisdiction and D1 location hint] | [TODO: confirm transfer mechanism in the signed vendor DPA (UK adequacy / UK–US Data Bridge / UK IDTA or Addendum)] |
| Stripe (Stripe Payments UK Ltd / Stripe, Inc.)independent controller for its own purposes | Subscription billing and card payments | Billing name/email, plan, payment-method tokens (we never see full card numbers) | UK / EEA / US | [TODO: confirm transfer mechanism in the signed vendor DPA (UK adequacy / UK–US Data Bridge / UK IDTA or Addendum)] |
| Resend, Inc. | Transactional email (receipts, reminders, 2FA codes, client emails) | Recipient email address, message content | US / EU [TODO: Resend region setting] | [TODO: confirm transfer mechanism in the signed vendor DPA (UK adequacy / UK–US Data Bridge / UK IDTA or Addendum)] |
| Twilio Inc.only if enabled | SMS one-time codes for two-factor authentication | Mobile number and the one-time code message | US / global | [TODO: confirm transfer mechanism in the signed vendor DPA (UK adequacy / UK–US Data Bridge / UK IDTA or Addendum)] |
| Meta Platforms Ireland Ltd (WhatsApp Business Cloud API)only if enabled | Client document bot over WhatsApp | Client phone number and the messages exchanged with the bot | Ireland / US | [TODO: confirm transfer mechanism in the signed vendor DPA (UK adequacy / UK–US Data Bridge / UK IDTA or Addendum)] |
| Neon, Inc.only if enabled | Serverless Postgres (fallback/auxiliary database) | Same categories as Supabase where enabled | [TODO: Neon region] | [TODO: confirm transfer mechanism in the signed vendor DPA (UK adequacy / UK–US Data Bridge / UK IDTA or Addendum)] |
| Clerk, Inc.only if enabled | Legacy authentication provider (only if configured instead of Supabase Auth) | Account identity and session data | US | [TODO: confirm transfer mechanism in the signed vendor DPA (UK adequacy / UK–US Data Bridge / UK IDTA or Addendum)] |
| Google LLC / Google Ireland Ltdonly if enabledindependent controller for its own purposes | Optional 'Continue with Google' sign-in (via Supabase Auth) | Google account id, name and email if you choose Google sign-in | US / EEA / UK | Google acts as its own controller for the sign-in; see Google's privacy policy. |
We may also disclose data where the law requires it (for example a court order) or to protect our rights, and to professional advisers under confidentiality.
6. International transfers
Some providers above process data outside the UK (notably in the United States). Where they do, we rely on a UK-recognised safeguard: UK adequacy regulations (including the UK Extension to the EU–US Data Privacy Framework, for certified US recipients), or the UK International Data Transfer Agreement / UK Addendum to the EU Standard Contractual Clauses, together with a transfer risk assessment.
Where our data is hosted: [TODO: Supabase project region and Netlify function region (UK/EU/US) — record in docs/security/ropa.md]. You can ask us for a copy of the safeguards at info@hydratax.uk.
7. Your rights and how to use them
Under UK data protection law you have the right to:
- be informed (this notice);
- access a copy of your personal data;
- have inaccurate data corrected;
- have data erased ("right to be forgotten") — not where we must keep it by law, see the retention tables;
- restrict our processing in certain cases;
- receive your data in a structured, machine-readable format (portability) where we rely on contract or consent;
- object to processing based on legitimate interests, and to direct marketing at any time;
- withdraw consent at any time where we rely on it (this does not affect earlier processing).
Self-service (signed-in account holders)
Go to Settings → Privacy & data (/settings/privacy) to download a JSON copy of your account data or to delete your account. Practice owners and administrators can export or erase an individual client from that client's page.
By email or post
Write to info@hydratax.uk. We may need to verify your identity. We respond within one calendar month (extendable by up to two further months for complex or numerous requests, in which case we tell you why). There is no fee unless a request is manifestly unfounded or excessive.
8. Automated decisions
We do not make decisions about individuals based solely on automated processing that produce legal or similarly significant effects (UK GDPR Art 22). HydraTax performs rule-based calculations (for example tax figures from HMRC rates) and suggestions that a qualified human reviews before anything is filed.
9. Security
We use encryption in transit, access control on every database table (row-level security) and server-side authorisation checks, encrypted storage of HMRC credentials, two-step verification for accounts, append-only audit and security logs, and time-limited sessions. If a personal data breach is likely to put people at risk we notify the ICO within 72 hours and affected people without undue delay. See our security & breach policy.
11. Children
HydraTax is a professional service for people aged 18 or over and we do not knowingly collect children's data for our own purposes. Our customers may record data about employees or clients who are under 18 (for example apprentices); they are responsible for that processing and we handle it only on their instructions.
12. Complaints
Please contact us first at info@hydratax.uk so we can try to put things right. You also have the right to complain to the Information Commissioner's Office: https://ico.org.uk/make-a-complaint/ · telephone 0303 123 1113.
13. Changes
We will update this notice when our processing changes and tell account holders about material changes by email or in the service. The date at the top shows the latest version.