Section 01Who we are
Duoledger is Making Tax Digital bookkeeping software for people with UK property income, self-employment income, or both. The service is provided by Duoledger Ltd, a company registered in England and Wales (company number 17450275, registered office 61 Albert Bridge Road, London SW11 4QA).
For the personal data described in this policy, Duoledger Ltd is the data controller. We are registering with the Information Commissioner's Office (ICO) as a data controller and will publish our registration reference on this page as soon as it is issued. Our data protection contact is privacy@duoledger.co.uk.
We are not required to appoint a statutory Data Protection Officer, but a named person is accountable for privacy at Duoledger and answers every request sent to the address above.
Section 02The short version
We are a bookkeeping tool, not an advertising business. We do not sell your personal data, we do not sell or share your bookkeeping or bank data with advertisers or data brokers, and we do not use your financial records to train our own AI models. Bank connections are read-only and you can revoke them at any time. You can export your books or delete your account whenever you want.
The rest of this policy sets out the detail required by the UK GDPR and the Data Protection Act 2018, including our lawful bases, our processors and your rights.
Section 03The data we collect
We collect only what the service needs to work. In practice that falls into eight groups.
| Category | What it includes | Where it comes from |
|---|---|---|
| Account data | Name, email address, hashed password or federated sign-in identifier, account settings, sign-in timestamps and IP address. | You, when you register and sign in. |
| Subscription and billing data | Plan, subscription and trial status, billing email, billing country, invoices, payment outcomes and the last four digits and card brand shown by our payment provider. | You and Stripe. Full card numbers are never sent to or stored on our systems. |
| Bookkeeping data | Properties and their addresses, ownership shares, tenancies, self-employment trades, income and expense transactions, categories, mileage, notes and attachments, plus the tax years these are assigned to. | You, and any bank feed or receipt you choose to import. |
| Open Banking data | Account name, sort code and account number in masked form, balances, and transaction date, amount, description, merchant and reference for the accounts you connect. | Your bank, through TrueLayer, with your explicit consent. |
| Receipt and document data | Images and PDFs you upload, plus the vendor, date, amount, tax and description extracted from them. | You, plus automated extraction you review before saving. |
| HMRC integration data | Your HMRC authorisation tokens, National Insurance number and Unique Taxpayer Reference where needed for submission, business identifiers returned by HMRC, submission history and the anti-fraud header data HMRC requires (see section 7). | You and HMRC, once you connect your HMRC account. |
| Technical and usage data | Device and browser type, operating system, screen size, timezone, IP address, pages and features used, error reports and security logs. | Automatically, when you use the site or app. |
| Support and communications data | Emails, in-app messages, feedback, beta reports and any attachments you send us. | You, when you contact us. |
Special category and criminal offence data
We do not ask for special category data. Bookkeeping records can incidentally reveal such information — for example a transaction description that names a medical provider, or a tenant's details you record in a note. Please avoid entering more than you need. Where such content does appear, we process it only as part of providing the bookkeeping service to you and apply the same protections described in section 11.
Data about other people
Your records may contain personal data about tenants, clients, suppliers or co-owners. For that data you are the controller and we act as your processor, handling it only on your instructions and for the purposes of running the service. You are responsible for having a lawful basis to enter it and for telling those people how their data is used where required.
Section 04Why we use your data, and our lawful basis
Under the UK GDPR we need a lawful basis for every use of personal data. Ours are set out below.
| Purpose | Data used | Lawful basis |
|---|---|---|
| Creating and securing your account, authenticating you, enforcing plan limits | Account, technical | Contract — necessary to provide the service you signed up for |
| Recording, categorising and reporting your income and expenses | Bookkeeping, receipt, Open Banking | Contract |
| Importing transactions from a bank you connect | Open Banking | Consent given to your bank and to us at the point of connection, which you may withdraw at any time |
| Taking payment, managing trials, renewals, refunds and dunning | Account, subscription and billing | Contract, and legal obligation for tax and accounting records |
| Preparing and sending quarterly updates and final declarations to HMRC on your instruction | Bookkeeping, HMRC integration | Contract, and legal obligation for the anti-fraud header data HMRC mandates |
| Service emails: confirmations, receipts, deadline reminders, security and outage notices | Account, subscription | Contract, or legitimate interests in keeping you informed about a service you use |
| Support, debugging, and investigating a report you raise during beta | Support, technical, and the minimum records needed to reproduce the issue | Contract and legitimate interests in fixing faults |
| Product analytics, reliability monitoring and improving categorisation accuracy, using aggregated or de-identified data wherever possible | Technical, usage | Legitimate interests in operating and improving the software, balanced against your privacy and limited to what we cannot learn from aggregates |
| Preventing fraud, abuse and unauthorised access; keeping security logs | Account, technical | Legitimate interests in protecting our users and systems, and legal obligation to keep data secure |
| Marketing emails and product updates to people who ask for them | Account, marketing preferences | Consent, or legitimate interests under the soft opt-in for existing customers, with an unsubscribe link in every message |
| Non-essential cookies and measurement | Technical, usage | Consent, requested through our cookie banner |
| Complying with law, responding to lawful requests, and establishing or defending legal claims | Any relevant data | Legal obligation and legitimate interests |
Where we rely on legitimate interests you can ask us for our balancing assessment, and you can object at any time using the contact details in section 16.
Section 05Open Banking and bank feeds
Bank feeds are optional. If you use them, we connect through TrueLayer, an account information service provider authorised and regulated by the Financial Conduct Authority. Only FCA-authorised firms are permitted to access bank data through Open Banking APIs in the UK.
- You authenticate directly with your bank. Duoledger never sees or stores your online banking credentials.
- Access is read-only. We cannot move money, set up payments or change anything in your bank account.
- We request account details, balances and transaction history only for the accounts you select.
- You can withdraw consent at any time in Duoledger, or in your bank's app or online banking. We stop retrieving new data as soon as the consent is revoked.
- Under FCA rules, ongoing access requires periodic reconfirmation rather than re-authentication with your bank every 90 days (TrueLayer explains the change). We will prompt you when a reconfirmation is due.
Imported transactions are categorised automatically where we are confident, and routed to a review inbox where we are not. No import is filed to HMRC without your explicit review and instruction. Revoking a bank connection does not delete transactions already imported into your books, because those are now your accounting records; you can delete them yourself, or ask us to.
Section 06Receipt capture and automated processing
When you upload a receipt or invoice, the image is stored in a private, per-user location and passed to an AI extraction service to read the vendor, date, amount and description. The result is shown to you as an editable preview, and nothing is written to your books until you confirm it.
- Extraction currently runs on Cloudflare Workers AI, processed as an inference request rather than retained by the model provider for training.
- We do not use your receipts, transactions or bookkeeping records to train our own models.
- Automated categorisation and OCR are decision support, not automated decision-making with legal effect. Every figure remains editable and you are the one who confirms it.
- You can delete an uploaded receipt at any time. Deleting the receipt does not automatically delete a transaction you created from it.
Beta note. Extraction accuracy is still being validated on real receipts. Always check the preview before saving, and keep your original documents for the retention period HMRC requires.
Section 07HMRC submissions and anti-fraud data
If you connect your HMRC account, you grant Duoledger permission through HMRC's own authorisation screens to read your obligations and send updates on your behalf. We store the resulting access and refresh tokens encrypted, and you can disconnect at any time in Duoledger or in your HMRC account.
HMRC requires every piece of MTD software to send fraud prevention headers with each API call. These describe the device and connection used to submit — for example device identifiers, operating system and browser version, screen size, timezone, local and public IP addresses and licence identifiers. We are legally obliged to send them accurately, and we cannot switch them off. HMRC processes that data under its own privacy notice for the prevention and detection of fraud.
Duoledger is registered with HMRC's Software Developer Support Team and is working through the recognition process for Making Tax Digital for Income Tax. Until recognition completes, you can keep your books in Duoledger and file through your existing route; no data migration is needed when filing becomes available.
Section 09International transfers
We aim to keep customer records in the UK or the EEA. Some providers listed above operate or support their services from outside the UK. Where personal data leaves the UK, we rely on one of the following safeguards:
- UK adequacy regulations, including the UK Extension to the EU–US Data Privacy Framework where the provider is certified;
- the International Data Transfer Agreement, or the EU Standard Contractual Clauses together with the UK Addendum;
- a transfer risk assessment plus technical measures such as encryption in transit and at rest.
You can request a copy of the relevant safeguard for any provider by emailing us.
Section 10How long we keep your data
| Data | Retention | Why |
|---|---|---|
| Account and bookkeeping records | For as long as your account is active | To provide the service |
| Records after you close your account | Deleted or anonymised within 30 days, unless you ask us to keep them or we must retain them under the rows below | Your instruction and our contract |
| Tax records submitted to, or prepared for, HMRC | Up to 6 years from the end of the relevant tax year | Self-employed and landlord records must be kept for at least five years after the 31 January submission deadline for the tax year concerned (GOV.UK). We keep a margin so your evidence outlives the deadline. |
| Invoices and payment records | 6 years from the end of the accounting period | Companies Act and tax obligations on us |
| Receipt images | With the transaction they support, or until you delete them | Evidence for your records |
| Open Banking transaction data | Kept in your books once imported; raw feed data is discarded when a connection is revoked | Your accounting records versus consent-based access |
| Security and access logs | Typically 12 months | Security monitoring and incident investigation |
| Support correspondence | 24 months after the conversation closes | Continuity of support and dispute handling |
| Marketing preferences and suppression lists | Until you object, and then a minimal record indefinitely | To honour your opt-out |
You can export your books at any time from within the app, and we recommend doing so before you close your account.
Section 11How we protect your data
- Encryption in transit using TLS 1.3, and at rest using AES-256.
- Row-level authorisation enforced on the server for every read and write, so records are scoped to the account that owns them.
- Integration secrets and HMRC tokens held in a dedicated encrypted store, not in application code or plain database columns.
- Monetary values stored as integer pennies to prevent rounding drift in your records.
- Least-privilege administrative access, multi-factor authentication on internal accounts, and audit logging of privileged actions.
- Automated backups with restore testing, and change control over deployments.
- No storage of full card numbers anywhere in our systems — card data is handled by Stripe.
No system is completely secure. If a personal data breach is likely to result in a risk to your rights and freedoms, we will report it to the ICO within 72 hours of becoming aware and tell you without undue delay where the risk is high. You help by using a strong, unique password, enabling any available second factor, and telling us promptly at privacy@duoledger.co.uk if you suspect unauthorised access.
Section 13Marketing
We send service emails you cannot opt out of while you hold an account — for example payment receipts, security notices, deadline reminders tied to your obligations, and material changes to these terms.
Product news, tips and offers are separate. We send them only where you have opted in, or where you are an existing customer and the message concerns similar services under the soft opt-in in the Privacy and Electronic Communications Regulations. Every marketing email carries an unsubscribe link, and you can also email us to stop them. Unsubscribing from marketing does not cancel your subscription.
Section 14Your rights
Under UK data protection law you have the right to:
- Be informed — through this policy and the notices in the app.
- Access a copy of the personal data we hold about you.
- Rectification of inaccurate or incomplete data.
- Erasure where we no longer need the data and no legal obligation requires us to keep it.
- Restriction of processing while a dispute about accuracy or basis is resolved.
- Portability — receive the data you gave us in a structured, commonly used, machine-readable format, or have it sent to another provider where technically feasible.
- Object to processing based on legitimate interests, and to direct marketing at any time with no exceptions.
- Withdraw consent where consent is our basis, such as bank connections and non-essential cookies.
- Not be subject to solely automated decisions with legal or similarly significant effects. We do not make such decisions.
Much of this is self-service: you can view and edit your records, export your books, manage bank and HMRC connections, and delete your account from within the app. For anything else, email privacy@duoledger.co.uk. We respond within one month and will tell you if we need to extend that by up to two further months for a complex request. There is no charge unless a request is manifestly unfounded or excessive. We may ask for proof of identity before releasing data.
Section 15Children, and changes to this policy
Children
Duoledger is for adults running a property or self-employment business. The service is not directed at children and we do not knowingly collect data from anyone under 18. If you believe a child has created an account, tell us and we will remove it.
Third-party sites
Our pages link to sites we do not control, such as GOV.UK, HMRC and our providers. Their privacy practices are their own and this policy does not cover them.
Changes
We update this policy as the product develops — the live bank feed and HMRC filing modules are current examples. The version and date at the top always reflect the current text. For material changes we will notify account holders by email or an in-app notice at least 14 days before they take effect, unless a change must be made sooner for legal or security reasons. Previous versions are available on request.
Section 16Contact and complaints
Privacy and data protection: privacy@duoledger.co.uk
General support: support@duoledger.co.uk
Post: Duoledger Ltd, 61 Albert Bridge Road, London SW11 4QA
If you are unhappy with how we have handled your data, please tell us first so we can put it right. You also have the right to complain to the Information Commissioner's Office, Wycliffe House, Water Lane, Wilmslow, Cheshire SK9 5AF, helpline 0303 123 1113.
See also our Terms and Conditions, which govern your use of Duoledger.