How we handle data
Privacy policy
Last updated 10 October 2026 · version 2026-10-10.1
1. Who we are
Adequacy is operated by Amzu Information Technology Ltd, a company registered in England and Wales (company number 08516330). Our registered office is Apollo House, Hallam Way, Whitehills Business Park, Blackpool, England, FY4 5FS.
We are the controller of the personal data this policy describes: we decide why and how it is used. The policy covers the website, the chat, the REST API and the MCP server (the “Service”). To contact us, see section 11.
We build a data-protection product, so we hold ourselves to the standards we help you meet. We collect the minimum needed to run the Service. We don’t sell personal data or use it for advertising.
2. What we collect
- Account data. Clerk runs sign-in for us. It processes your email address, and a hash of your password if you set one. If you sign in with Google, Clerk also receives the basic profile Google shares: your name, email address and profile picture. For each session, Clerk also processes your IP address and details of your browser and device. Our own database holds your Clerk user ID and the accounts you belong to, not your name, email address or password.
- API keys. For each key: the name you give it; its first characters in clear (
gdpr_sk_and 8 more), so you can tell keys apart; a one-way hash of the full key (we never store the key itself); who created it (their Clerk user ID); when it was created, expires and was revoked; and its scopes (REST API, MCP server or both). - Usage records. For each question sent to the AI model: the account and user ID, the channel (chat, API or MCP), the question’s length, token counts, whether it counted as overage, and the time. When a chat follow-up’s search rewrite leads to no answer, we record the account and user ID, the channel, the time and the rewrite’s token counts. Usage records never hold the text of your questions.
- Chat history. The questions you ask in the chat workspace and the answers we give, with their cited sources, are stored with your account so you can return to them. Only you can see them: not other members of an organisation account, and there is no admin view of them. You can rename or delete a conversation, or delete all your history, at any time in the chat.
- AI-generated answers. An AI model, Anthropic’s Claude, writes each answer from the official passages it cites. Answers are labelled as AI-generated in the chat, in API and MCP responses and in PDF exports. To find the passages, we send Voyage AI the text we search with. To write the answer, we send Anthropic your question and the passages. For a chat follow-up, Anthropic also receives the conversation’s recent questions and answers, and first rewrites your question, with those earlier turns, into a search query; that query is what Voyage AI receives, so it may carry words from earlier in the conversation. Section 4 says what each provider receives and keeps.
- Answer traces. For each answer, linked to its usage record: which passages of the official sources were retrieved, which of them the answer cited, the AI model used, whether an answer was given, and a one-way fingerprint (SHA-256 hash) of the text we returned. Traces never contain your question or the answer text. We use them to find who received answers based on a source later found to be wrong or tampered with.
- Questions sent through the REST API or the MCP server. We process them in memory and pass them to Voyage AI and Anthropic to find passages and write the answer. We don’t store them.
- PDF exports. When you export a conversation or an answer, the PDF is made on our server from your stored chat history and sent to your browser. We don’t keep a copy.
- Waiting list. If you join the waiting list while new accounts are paused: your name and email address, and, if you give them, your company and how you would like to buy (directly, AWS Marketplace or Google Cloud Marketplace). We also record when you joined, the version of this policy in force when you joined, and which page you joined from, which tells us which pages lead people to the waiting list. Your email address goes to Clerk only when we invite you to create an account; Clerk then emails you the invitation. We record when we invited you, and we can see in Clerk whether the invitation is still open, was accepted or has expired.
- Contact-form messages. Your name, email address, subject and message; the message’s status, our internal notes, and which team member handled it. A copy is emailed to our team mailbox.
- Anti-spam checks on our forms. When you start on the contact or waiting-list form (by focusing a field, typing or sending), your browser loads Cloudflare Turnstile, which checks that a person is using the form. Cloudflare then processes your IP address and browser and device signals, as its Turnstile privacy addendum sets out. When you send the form, our server checks the result with Cloudflare, passing your IP address, and keeps your IP address in memory for about an hour to limit repeated submissions. We don’t store it in our database. Clerk’s sign-up form runs a similar Cloudflare check.
- Hosting logs. Railway, our hosting provider, logs each request to our servers: your IP address, your browser (user agent), the page or API path, and the time. Our backend doesn’t write an access log of its own, and our application logs avoid personal data, though some error lines name an account or user ID.
- Billing data. If you buy a plan from us directly, you pay on Stripe’s own checkout page: your card or other payment details go to Stripe, never to us. At checkout you give Stripe your email address, a billing name and address and, if you choose, a tax ID such as a VAT number. Stripe issues the invoices and receipts. We keep the Stripe IDs that link your account to its Stripe customer and subscription, the subscription’s status and dates, and we read your invoices from Stripe to list them in your dashboard. When you accept the Subscription Agreement we record which version you accepted, when, and for which checkout, and send the version and time to Stripe with the subscription.
3. Why we use it, and our legal basis
The UK GDPR and the EU GDPR require a legal basis for each use of personal data. Ours are:
- Providing the Service you signed up for: your account, the chat and its history, API keys, the REST API and MCP server, usage limits and PDF exports. Contract (Article 6(1)(b)).
- Handling your request to join the waiting list, and inviting you. Steps you asked us to take before a contract (Article 6(1)(b)).
- Recording which page you joined the waiting list from. Legitimate interests: learning which pages lead people to the waiting list.
- Keeping the Service secure and preventing abuse: rate limits, the anti-spam checks on our forms, and hosting logs. Legitimate interests (Article 6(1)(f)): keeping the Service safe and available.
- Answer traces. Legitimate interests: finding who received answers based on a source later found to be wrong or tampered with, so we can put it right.
- Replying to messages you send us. Legitimate interests: answering people who contact us.
- Taking payment for a plan you buy, invoicing it, and managing the subscription. Contract (Article 6(1)(b)).
- Keeping billing and tax records, and answering lawful requests from authorities. Legal obligation (Article 6(1)(c)).
We don’t rely on consent for anything. We use no analytics or advertising, and the browser storage we use is strictly necessary (section 9). Where we rely on legitimate interests, you can object (section 8).
4. Who else processes it
We share personal data only with the providers below. They process it for us under data processing terms, except where we say otherwise.
Anthropic — writes the answers (Claude)
- Receives
- Questions from the chat, the REST API and the MCP server, with the official passages we found for them. For a chat follow-up, also the conversation's last six exchanges, each message cut to 2,000 characters. We don't send your name, email address or account ID with them.
- Where
- The United States, and other countries where Anthropic runs its models.
- Safeguard
- Standard contractual clauses with the UK Addendum, in Anthropic's data processing addendum. Anthropic is not certified under the Data Privacy Framework.
- Training and retention
- Anthropic's commercial terms forbid it to train models on our content. It deletes API inputs and outputs within 30 days, but may keep content flagged for breaking its usage policy for up to 2 years.
Voyage AI (MongoDB) — turns text into search vectors
- Receives
- The text we search with: your question, or, for a chat follow-up, a search query rewritten from it and the earlier turns.
- Where
- The United States.
- Safeguard
- The EU–US Data Privacy Framework with its UK Extension (MongoDB's certification covers Voyage AI), and standard contractual clauses with the UK Addendum in Voyage's data processing agreement.
- Training and retention
- We have opted out of Voyage using our data to train its models. With that opt-out, Voyage deletes what we send once it has processed it.
Clerk — sign-in and accounts
- Receives
- Your account and session data (section 2), and your email address if we invite you from the waiting list. Clerk sends the sign-in and invitation emails.
- Where
- The United States.
- Safeguard
- The EU–US Data Privacy Framework with its UK Extension; standard contractual clauses with the UK Addendum as a fallback.
Cloudflare — anti-spam checks and bot protection
- Receives
- Your IP address and browser and device signals, once you start on our contact or waiting-list form, and on Clerk's sign-up form (Turnstile). Cloudflare also protects Clerk's servers and sets bot-management cookies there (section 9).
- Where
- Cloudflare's global network.
- Safeguard
- The EU–US Data Privacy Framework with its UK Extension; standard contractual clauses with the UK Addendum.
- Own use
- Under its Turnstile privacy addendum, Cloudflare also uses these signals, as a controller, to improve its bot detection.
Resend — emails our team
- Receives
- Each contact-form message in full (your name, email address, subject and message), emailed to our team mailbox. For a waiting-list sign-up, only the entry's number: no personal data.
- Where
- The United States.
- Safeguard
- The EU–US Data Privacy Framework with its UK Extension; standard contractual clauses with the UK Addendum.
Microsoft (Microsoft 365, Exchange Online) — our team mailbox
- Receives
- The emails Resend sends our team: each contact-form message in full, and for a waiting-list sign-up only the entry's number.
- Where
- The data location of our Microsoft 365 account. Microsoft may also process data in the United States and other countries where it operates.
- Safeguard
- Microsoft's data protection addendum. Microsoft Corporation is certified under the EU–US Data Privacy Framework with its UK Extension.
Stripe — payments, invoices and the billing portal
- Receives
- If you buy a plan directly: your email address, the billing name, address and any tax ID you give at checkout, your payment details (entered on Stripe's own pages; we never receive them), and our ID for your account. Stripe creates the invoices and receipts, and runs the customer portal where you manage the subscription.
- Where
- The United States, and other countries where Stripe operates.
- Safeguard
- The EU–US Data Privacy Framework with its UK Extension (Stripe, Inc. is certified); standard contractual clauses with the UK Addendum in Stripe's data processing agreement.
- Own use
- Stripe is also a controller for its own purposes, such as preventing fraud and meeting its legal duties as a payment provider, under its own privacy policy.
Railway — hosting
- Receives
- Our servers and database run on Railway, so it holds everything the Service stores. Its logs record each request (section 2).
- Where
- The United States.
- Safeguard
- The EU–US Data Privacy Framework with its UK Extension; standard contractual clauses with the UK Addendum as a fallback.
Two others receive data when you use particular features, and handle it under their own privacy policies:
- Google, if you choose Sign in with Google. Google acts as an independent controller for that sign-in.
- jsDelivr, a public content delivery network. Our API reference loads fixed versions of its Swagger UI files from jsDelivr, so opening that page sends your IP address and browser details to jsDelivr. Nothing else reaches it.
5. Transfers outside the UK and EU
We are based in the UK. Most of our providers process data in the United States, and Anthropic, Cloudflare and Microsoft may process it in other countries too. Where a country has no adequacy decision (or, for the UK, adequacy regulations), we rely on:
- the EU–US Data Privacy Framework and its UK Extension (the UK–US data bridge), for certified US providers; or
- the European Commission’s standard contractual clauses, with the UK’s International Data Transfer Addendum.
Section 4 says which applies to each provider. To get a copy of these safeguards, contact us (section 11).
6. How long we keep it
- Account data, API keys and usage records — while your account exists. Revoked and expired keys stay listed until then. The dashboard shows up to the last 365 days of usage.
- When your account is deleted — we delete your API keys (and every key of an account you were the only member of), your memberships, any account left with no members, and your chat history. Usage records stay for counts and billing, with your user ID replaced by “deleted”. A subscription you bought for your own account is cancelled at once, so you are not charged again. An organisation account that holds a subscription stays as the organisation’s billing record, without you in it. Clerk deletes your sign-in account. For about a day after an account is deleted, we keep a one-way hash of the user ID, so a still-valid sign-in can’t recreate the account.
- Chat history — until you delete it in the chat (one conversation or all of them), or your account is deleted. A conversation is deleted automatically 12 months after its last question.
- Answer traces — deleted after 365 days. They hold no personal data once your account is deleted.
- Questions sent through the REST API or MCP server — not kept after the answer is returned. The usage record keeps only their length.
- PDF exports — not kept: made when you ask and sent to your browser.
- Contact-form messages — deleted at the latest 12 months after they arrive, or sooner if you ask. The copy emailed to our team mailbox is deleted on the same schedule.
- Waiting list — deleted 12 months after you first join, when your invitation is accepted, expires or is withdrawn, or sooner if you ask us to remove you. If your invitation is still open when your entry is deleted, we revoke it. Clerk keeps a record of each invitation, with your email address, after it has been revoked or has expired: Clerk lets us revoke an invitation but not delete it. If you ask us to erase your data, we also ask Clerk to delete that record. Once you accept an invitation, your account data is kept as described above.
- Subscription Agreement acceptances — while your account exists; Stripe keeps the version and time with the subscription, as part of the billing records below.
- Billing records — Stripe keeps the invoices, payments and billing details for six years after the financial year they belong to, as UK tax and company law requires us to keep them, even after your account is deleted. We delete our link to your Stripe customer when your account is deleted.
- IP addresses in our rate limits — held in memory for about an hour, never in our database.
- Hosting logs — kept by Railway for up to 30 days.
- Database backups taken before a software upgrade — deleted after 7 days. Until then they may still hold data that you or we deleted.
Section 4 says how long Anthropic and Voyage AI keep what we send them.
7. Automated decisions
We make no decisions about you based solely on automated processing that have legal or similarly significant effects on you. An AI model drafts the answers to your questions; it does not decide anything about you.
8. Your rights
Under the UK GDPR and the EU GDPR, you have the right to:
- access the personal data we hold about you, and get a copy;
- have inaccurate data corrected;
- have your data erased. You can delete your chat history yourself at any time in the chat. To close your account and erase your data, ask us; where your account menu offers it (Manage account), you can delete the account yourself. Either way, we then erase what we hold as section 6 describes;
- restrict how we use your data;
- object to any use based on our legitimate interests;
- data portability: receive the data you gave us under our contract in a machine-readable format, or have it sent to another provider. You can also export any conversation as a PDF from the chat.
To use a right, contact us (section 11). We may ask you to confirm who you are, for example by writing from the email address on your account. We reply within one month; for complex requests we may need up to two more months, and we will tell you if so. It is free, unless a request is clearly unfounded or excessive.
If you live outside the UK and the EU, your local law (such as India’s DPDP Act, Hong Kong’s PDPO, Australia’s Privacy Act 1988 or New Zealand’s Privacy Act 2020) may give you similar rights. Contact us the same way.
Complaints
Please tell us first, so we can try to put things right. You also have the right to complain to the UK regulator, the Information Commission (formerly the Information Commissioner’s Office, ICO):
- online: ico.org.uk/make-a-complaint
- by phone: 0303 123 1113
- by post: Information Commission, 4th Floor, No.3 Circle Square, 5 Hawkshaw Street, Manchester M1 7BL
If you are in the EU or the EEA, you can also complain to the data protection authority where you live or work, or where you think the problem happened. See the European Data Protection Board’s list of EU data protection authorities.
10. Children
The Service is for businesses and for people aged 18 or over. It is not directed at children, and we don’t knowingly collect their data. If we learn that a child has an account, we close it and erase their data.
11. Contact and changes
For privacy questions, to use your rights or to complain to us, use the contact form or write to Amzu Information Technology Ltd, Apollo House, Hallam Way, Whitehills Business Park, Blackpool, England, FY4 5FS. Please put “Privacy” in the subject.
We announce material changes to this policy on this page, with a new date and version number. Questions about using the Service are covered by our terms.