Skip to main content
Draft — not yet reviewed or complete. This page describes what the Ordax product actually collects and why, but several facts (company details, ICO registration, exact retention periods, full processor list) are still placeholders — see the highlighted [example — TBC] markers below. This notice needs a legal/compliance review and every placeholder filled in before it can be treated as accurate or complete.

Privacy Notice

This notice explains what personal data Ordax collects when you create and use an account, why we process it, who we share it with, and what rights you have under the UK GDPR and Data Protection Act 2018. It covers the Ordax product itself — for terms specific to the closed beta programme, see the beta policies page.

Who we are

Data controller

[Company legal name — TBC], company number [Companies House number — TBC], registered at [registered office address — TBC] ("Ordax", "we", "us") is the data controller for the personal data described in this notice.

Ordax is registered with the UK Information Commissioner's Office (ICO), registration number [ICO registration number — TBC].

What we collect

Data we hold about you

Account and security data

  • Email address
  • Password — stored as a salted Argon2 hash, never in plain text
  • Two-factor authentication (TOTP) secret and backup codes, if you enable 2FA (mandatory at signup)
  • Consent records — which version of these terms you agreed to, and when
  • Security audit log — event type (signup, login, failed login, password change), timestamp, and IP address

Financial and tax data

  • Bank transaction and HMRC data, once you choose to connect them — via a direct, separate authorisation with your bank or HMRC. We never see or store your banking or Government Gateway login details, at any point.
  • [Confirm current status: connections not yet available / in development — TBC]

We only collect email and password at signup. Other details (such as your name and date of birth) are collected later, during account setup, and are described here once that flow exists — currently [describe onboarding data collection once built — TBC].

Why we use it

Purpose and legal basis

DataPurposeLegal basis
Email, passwordCreating and operating your accountNecessary for the contract with you
2FA secret, backup codesProtecting your account, given the financial data involvedNecessary for the contract with you
Audit log (IP, event, timestamp)Detecting fraud and abuse, rate limiting, lockoutLegitimate interest — account and platform security
Consent recordsProving what you agreed to and whenLegal obligation / legitimate interest
Marketing emailsSending product updates and tipsConsent — opt-in, unticked by default, withdrawable any time
Product analyticsUnderstanding usage to improve the productConsent — opt-in. [No analytics tool is connected yet — confirm before this applies — TBC]
Bank/HMRC data (future)Calculating your tax positionNecessary for the contract with you, once you opt in to connect an account

Retention

How long we keep it

  • Account data (email, password hash): [retention period — TBC] after account deletion
  • Security audit log: [retention period, e.g. 12–24 months — TBC]
  • Consent records: [retention period — commonly kept after deletion as proof of consent — TBC]
  • 2FA secret and backup codes: deleted immediately on account deletion or 2FA reset
  • Financial/tax data (future): [retention period, likely aligned to HMRC record-keeping requirements — TBC]

Sharing

Who we share data with

We do not sell your data. We share it only with service providers who help us run Ordax, each contractually bound to protect it:

  • Brevo — sends account, verification, and password-reset emails on our behalf
  • Cloudflare — provides bot protection (Turnstile) on our signup form
  • [Hosting provider — not yet chosen — TBC]
  • [Database provider — not yet chosen — TBC]
  • [Analytics provider, if/when one is connected — TBC]

Some of these providers may process data outside the UK. Where that happens, we rely on [transfer safeguard — e.g. UK International Data Transfer Agreement or adequacy decision, confirm per provider — TBC].

Security

How we protect your data

Passwords are hashed with Argon2 and never stored or logged in plain text. Two-factor authentication is required on every account. Traffic to Ordax is encrypted in transit. Session tokens are stored in HttpOnly, Secure cookies, inaccessible to page scripts. We never see or store your bank or Government Gateway login details.

UK GDPR

Your rights

As a UK data subject, you have the right to:

  • Access — ask what personal data we hold about you
  • Rectification — correct inaccurate or incomplete data
  • Erasure — request deletion where there's no lawful reason to keep it
  • Restriction — ask us to limit how we use your data
  • Portability — receive your data in a portable format, where applicable
  • Objection — object to processing based on legitimate interest, or to direct marketing at any time
  • Withdraw consent — for anything based on consent (e.g. marketing, analytics), at any time, without affecting your account

To exercise any of these, contact us using the details on this page. If you're not satisfied with our response, you have the right to complain to the Information Commissioner's Office (ICO) at ico.org.uk.

Eligibility

Age requirement

Ordax is only available to people aged 18 or over, confirmed at signup. We do not knowingly collect data from anyone under 18.

Changes

Updates to this notice

We'll update this page if what we collect or why changes, and material changes will be flagged to you at your next login. This version was last updated [effective date — TBC].