Privacy
Privacy policy
What we collect, why, who it goes to and how long we keep it. We collect what we need to file your VAT returns and run the service, and nothing else. We don’t sell your data or use it for advertising.
Last updated 13 October 2026
Who we are
Plain MTD is a trading name of BEARJS LTD, registered in England and Wales, company number 09429147. Registered office: 82A James Carter Road, Mildenhall, IP28 7DE. For the personal data described here, BEARJS LTD is the data controller, except where an accountant uses Plain MTD for their clients (see accountants and their clients).
Questions about your data, or requests to use your rights: email privacy@plainmtd.co.uk. Anything else about Plain MTD: support@plainmtd.co.uk.
ICO registration number: ZC270704
Plain MTD is not an HMRC or GOV.UK service. It’s for businesses and isn’t meant for anyone under 18.
What we collect and why
The law asks us to name a lawful basis for each use. “Contract” means we need it to provide the service you signed up for. “Legal obligation” means the law requires it. “Legitimate interests” means a reasonable business need that doesn’t override your rights.
| What | Why | Lawful basis |
|---|---|---|
| Your email address and name | To create your account, sign you in, and send you emails about your account and returns. | Contract |
| Sign-in details, if you use them: if you continue with Google, your Google account ID, picture and the sign-in keys Google gives us (stored encrypted); for a passkey, its public key, the name you give it, the kind of device or password manager that holds it and whether it’s backed up; and how you signed in to each session | To sign you in the way you chose. | Contract |
| Your account and practice details: business or practice name, who is a member and their role, and a practice’s Agent Reference Number (ARN) | To run the account and decide who can do what. | Contract |
| VAT registration numbers (VRNs) and business names | To connect to HMRC and fetch and file returns for the right registration. | Contract |
| Your HMRC connection (the access keys HMRC gives us when you sign in to HMRC) | To call HMRC for you without asking you to sign in to HMRC every time. | Contract |
| From HMRC, once you connect: your VAT periods and due dates, the returns HMRC holds for you (including ones filed with other software), your VAT charges, repayments and payments, and for a practice, whether each client has authorised it | To show what’s due and what’s been filed. We keep periods and returns; charges and payments are shown, not stored. | Contract |
| Your settings: reminder emails and theme | To send the reminders you asked for and show Plain MTD the way you chose. | Contract |
| Your spreadsheet and the nine VAT box figures in it | To check the figures and submit your return. | Contract |
| Submitted returns: the figures, HMRC’s receipt, and who filed them (their name and email at the time) | To show you what was filed, and so either of us can prove what was sent if it’s ever questioned. | Contract, and legitimate interests (defending legal claims) |
| Returns we’re checking with HMRC: the figures and who sent them, when we can’t tell straight away whether HMRC received a return | To find out whether it was filed, and use or give back the credit for it. | Contract |
| Device and connection details: IP address, a device ID, browser, screen and window size, time zone | HMRC requires every piece of MTD software to send these with each request, to help it prevent fraud. | Contract (we can’t file for you without them), and legitimate interests (preventing fraud, which HMRC requires of all MTD software) |
| Purchases: which credits you bought, when, and the Stripe payment reference, and the billing name, address, business name and VAT number you give Stripe at checkout | To give you credits, issue VAT invoices (which show your billing details) and keep our own tax records. Stripe handles your card; we never see the card number. | Contract, and legal obligation |
| Request logs and error reports, including a record of each request we make to HMRC for you (not what was sent) | To keep the service running and secure, to fix faults, and to help you if something goes wrong with HMRC. We take email addresses, VRNs, tax figures and HMRC keys out of error reports, and we don’t put names in them. | Legitimate interests |
| How the site is used: pages and buttons clicked, with the text on them hidden | To find and fix confusing parts of the service. Linked to an internal ID, never your name or email, and not kept with your IP address. You can turn it off (see cookies and your device). | Legitimate interests |
| Our own record of what our staff do in your account (for example a refund), and why | So every action we take on an account can be checked. | Legitimate interests |
You need to give us an email address to have an account, and HMRC requires the device and connection details before we can file. Without them we can’t provide the service.
We don’t make automated decisions about you that have legal or similarly significant effects. Checks on your spreadsheet only tell you whether the figures add up; you decide whether to submit.
What we send to HMRC
When you connect to HMRC, you sign in on HMRC’s own site and HMRC gives us access keys to act for you. We never see your Government Gateway password. We store the keys encrypted.
We send HMRC your VRN (or, for an accountant, your Agent Reference Number and each client’s VRN, and the VAT registration date HMRC asks for to request authorisation), the nine box figures when you submit, and the device and connection details HMRC requires with every request (including your IP address and port and an anonymous Plain MTD user ID). HMRC is responsible for what it does with that data; see HMRC’s privacy notice.
Accountants and their clients
When an accountant or bookkeeper uses Plain MTD to file for their clients, the practice decides what client data to enter and why. For that client data (client names, VRNs, VAT registration dates used to request HMRC authorisation, and their returns), the practice is the data controller and BEARJS LTD is its processor: we handle it only to provide the service to the practice, under our data processing terms.
On the practice’s instruction, we keep each return filed for its clients while the practice has an account with us, and then for 6 years from the date each return was submitted, unless it asks us to delete them sooner. When a practice removes a client, we delete the client’s other data after 30 days.
If you’re a client of a practice, ask the practice first about your data. We’ll pass on any request that reaches us.
For the practice’s own staff accounts, BEARJS LTD is the controller, as for any other user.
Who else handles your data
We use a small number of suppliers to run the service. Cloudflare, Resend, Sentry, PostHog and our email provider handle data only on our instructions, under a written contract. Stripe and Google use your data for their own purposes too (Stripe to take payments and prevent fraud, Google to sign you in), as their own privacy policies explain.
| Supplier | What for | Outside the UK |
|---|---|---|
| Cloudflare | Hosts the service, database and backups | Its network runs worldwide, including the US. Cloudflare is certified under the UK Extension to the EU-US Data Privacy Framework. |
| Resend | Sends our emails | Sent from the EU (Ireland), which UK adequacy regulations cover. Resend is a US company certified under the UK Extension to the EU-US Data Privacy Framework. |
| Signs you in, only if you choose Continue with Google | US. Google is certified under the UK Extension to the EU-US Data Privacy Framework. | |
| Stripe | Takes card payments | US and elsewhere. Stripe is certified under the UK Extension to the EU-US Data Privacy Framework. |
| Sentry | Error reports | Stored in the EU, which UK adequacy regulations cover. Sentry is a US company certified under the UK Extension to the EU-US Data Privacy Framework. |
| PostHog (EU) | Usage analytics | Stored in the EU, which UK adequacy regulations cover. PostHog is a US company certified under the UK Extension to the EU-US Data Privacy Framework. |
| Google Workspace | Holds the emails you send to support@, privacy@ and security@ | US and elsewhere. Google is certified under the UK Extension to the EU-US Data Privacy Framework. |
Where a supplier handles data outside the UK, we rely on the UK’s adequacy regulations (including the UK–US data bridge for certified US companies) or on the ICO’s International Data Transfer Addendum. The table shows which. Email privacy@plainmtd.co.uk for a copy of the safeguards. Our database runs in Cloudflare’s Western Europe region.
We’ll also share data if the law requires it, for example with HMRC or the police under a valid legal request, and with a buyer if BEARJS LTD or Plain MTD is ever sold, who would have to keep to this policy. We never sell your data.
How long we keep it
Keeping VAT records for 6 years is your duty (or your accountant’s), not ours: your own spreadsheet is your record. We keep a copy of what we filed for you for the same period so either of us can show what was sent (for a practice’s clients, as the practice instructs us).
| Data | Kept for |
|---|---|
| Uploaded spreadsheet | Deleted once the return is submitted. If you never submit it, deleted after 30 days. |
| Submitted returns (figures, HMRC’s receipt, who filed: name and email) | While your account is open, then 6 years from the date each return was submitted. A practice’s clients’ returns are kept the same way, as the practice instructs us, unless it asks us to delete them sooner. |
| A removed client’s or disconnected VAT registration’s other data (unfiled periods, authorisation requests, HMRC’s copies of returns filed elsewhere, and its name and VRN if nothing was filed for it) | Deleted after 30 days, counted from when the client is removed or the registration disconnected, unless it’s connected again before then. |
| HMRC connection keys | Deleted when you disconnect from HMRC or close your account. |
| Account details (name, email) | Deleted when you close your account, unless you also belong to another account (they stay for that one), and except where they’re part of a submitted return we still have to keep. Closing a practice doesn’t delete its staff’s own sign-in details: they can still sign in to any other account they belong to. |
| Purchase records and invoices | While your account is open, because they make up your credit balance. Then 6 years from each purchase, for our own tax records. |
| Signed-in sessions (including your IP address and browser) | Deleted when you sign out, or within a day of expiring. A session expires 30 days after you last used it. |
| Sign-in links we email you | Deleted within a day of expiring. Each link works for 5 minutes. |
| Staff invitations (the email address invited) | 30 days after the invitation expires. |
| Email address changes (your old and new address) | 1 year after the change, or 30 days if you never confirm it. Deleted when you close your account. |
| The email address a voucher code is reserved for (when we make a code for one person) | Removed within a day of the code being used, or 30 days after the code expires or is withdrawn. The record that the code was used is kept. |
| Request logs, including a record of each request we make to HMRC for you (not what was sent) | Up to 30 days. |
| Error references (the IDs of the account, return and request involved when something went wrong on our side: no names, email addresses or figures) | 90 days. |
| Error reports (Sentry) | 30 days. |
| Usage analytics (PostHog) | Up to 1 year. Linked to an internal ID, not your name or email. |
| Records of the emails we send you (Resend) | 30 days. |
| Payment records at Stripe | Kept by Stripe under its own privacy policy. |
| Backups of all of the above | Deleted data can stay in our database backups for up to 30 days before it’s gone for good. |
Before you close your account you can download every return you filed, with HMRC’s receipts.
Cookies and your device
We don’t use advertising or tracking cookies, so there’s no cookie banner. We store only these on your device, each needed for the service to work or to remember a choice you made:
- sign-in cookies, so you stay signed in, and short-lived ones while you sign in with Google or a passkey
- a short-lived cookie while you connect to HMRC, so nobody else can complete the connection
- a theme cookie, remembering light, dark or high contrast
- a device ID in your browser’s storage, which HMRC requires us to send with every request
- an analytics cookie, only if you turn usage analytics off, so it stays off in this browser
- if you turn usage analytics off in Settings, a note in your browser’s storage that you did, so it stays off in that tab
We use PostHog (EU) to count which pages and buttons are used, with the text hidden, so we can improve the service. It stores nothing on your device. You can turn it off in Settings, or with the usage analytics switch on this page, without signing in. When you buy credits, you pay on Stripe’s own page, which uses its own cookies to prevent fraud.
Usage analytics
On for this browser.
Keeping it safe
- Everything is sent over an encrypted connection.
- HMRC access keys are encrypted before they’re stored.
- There are no passwords to leak: you sign in with a link sent to your email, with Google, or with a passkey. A passkey’s private key never leaves your device; we only keep its public key.
- Every request is checked so you only ever see your own account’s data, and staff only see their practice’s clients.
- We take email addresses, VRNs, tax figures and HMRC keys out of our logs and error reports, and we don’t put names in them.
If a breach puts your data at risk, we’ll tell you and the ICO as the law requires.
Reporting a security problem: if you think you’ve found a weakness in Plain MTD, email security@plainmtd.co.uk. Please don’t include real customer data.
Your rights
You have the right to:
- see the personal data we hold about you and get a copy
- have it corrected if it’s wrong
- have it deleted, unless we have to keep it (see how long we keep it)
- ask us to restrict how we use it
- take it with you in a machine-readable format
Where we rely on legitimate interests (error reports, usage analytics, keeping records to defend claims), you can object, and we’ll stop unless we have a compelling reason.
Email privacy@plainmtd.co.uk. It’s free, and we’ll reply within one month. We may ask you to confirm who you are first.
Changes and complaints
Changes to this policy
If we change what we collect or who we share it with, we’ll update this page and its date. For significant changes we’ll email you first.
Complaints
To complain about how we’ve used your data, email privacy@plainmtd.co.uk. We’ll acknowledge it within 30 days, look into it, and tell you the outcome. If you’re not happy with our answer, you can complain to the Information Commissioner’s Office at ico.org.uk/make-a-complaint or on 0303 123 1113.
See also our terms of service.