Privacy notice
This notice explains what personal information Journl holds, why, and what you can do about it. It is written to be read, not to be scrolled past. If anything is unclear, ask: support@journl.co.uk.
Who is responsible
Journl Ltd (company number 17498961, registered office 5 Unit H, Torrens Street, London EC1V 1NQ) is the controller for the personal data described in the first table below — information about you as a user of Journl.
For the personal data inside your books — the names and details of your customers, suppliers and staff — you are the controller and we are the processor. We hold that data on your instructions and under your account's terms, and we do nothing with it except run the service for you. The second table covers it. The Data Processing Addendum sets out exactly how we act for you.
Journl Ltd is registered with the Information Commissioner's Office as a data controller, registration number ZC266611.
Information about you, as a user
| What | Why | Lawful basis | Kept for |
|---|---|---|---|
| Your name and email address | To create your account, sign you in, and contact you about the service (a password reset, a receipt, notice of a change). | Contract | While your account is open, then 90 days. |
| Your password | To sign you in. Stored only as a one-way hash; we cannot see it. | Contract | As above. |
| Two-factor authentication secret and recovery codes | To verify it is you. Stored encrypted. | Contract, and our legitimate interest in keeping accounts secure | As above. |
| Your agreement to our terms: which version, for which business, the time, the IP address and the browser | To show what was agreed, by whom and when, if that is ever in question — including if a payment is disputed. | Contract, and legitimate interest — evidence of the agreement | While your account is open, then six years (the time within which a claim about a contract can be brought). |
| Sign-in records: the time, the IP address, the browser, and whether a device was remembered | To keep your account secure, spot unusual access, and let you see and end sessions. | Legitimate interest — security | Sessions for 30 days after last use; sign-in history for 12 months. |
| Technical logs: the requests our servers handle and any errors, with account and business identifiers (and, in an error, sometimes an email address) | To keep the service secure, look into incidents and fix faults. | Legitimate interest — security and running the service | 12 months, then deleted. |
| The business you keep books for: its name, company number, VAT number, addresses | To print on your invoices and returns, and to file with HMRC. | Contract | While the account is open, then 90 days. |
| The audit trail: what each user did, and when | So that a set of books can show who changed what. This is a core feature of the software, not incidental logging. | Contract, and legal obligation (accounting records) | With the books. |
| Your HMRC connection: the tokens HMRC issues when you connect, and the receipts for returns filed | To submit VAT returns on your instruction and prove they were received. | Contract, and legal obligation | Tokens until you disconnect or they expire; receipts for six years, as HMRC requires. |
| Fraud-prevention data sent to HMRC with each VAT submission: your IP address and port, a random device identifier kept in your browser, your Journl user reference, your browser, screen and window size, time zone, and when you last used two-factor sign-in | The law requires Making Tax Digital software to collect this and send it to HMRC with every submission, to help prevent fraud. We do this as our own legal duty, so for this data we are the controller, not your processor, even when the return is for a business you keep books for. | Legal obligation: the Delivery of Tax Information through Software (Ancillary Metadata) Regulations 2019 | Sent to HMRC and not kept by us. The device identifier stays in your browser until you clear it. |
| Payment details | To charge for your plan. Handled entirely by Stripe; we hold only the last four digits and the expiry, to show you which card is on file. | Contract | While the subscription runs, then 6 years for our own accounting records. |
| Launch offer use | To give the launch discount once only. When a discounted checkout is opened, and again when the subscription starts, we keep a record of the use: the business's Journl reference and its Stripe subscription reference; the business's company number and VAT number, in a standard form (not hashed); a one-way fingerprint of the email addresses of the person subscribing and of the business's owners (not the addresses themselves); and Stripe's fingerprint of the card or bank account that paid (not the card or account number). A company number, VAT number or owner added afterwards is added to the record. A later checkout, or a detail added later, that matches an earlier use is refused the discount or flagged for a person at Journl to review. | Legitimate interests (stopping the same business or person taking the offer twice) | 2 years from the use, then deleted; a checkout opened but never paid for, the next day. Kept for that time even if the business closes its account. |
| Emails you send us, and our replies | To help you. | Legitimate interest — support | 2 years. |
We do not use cookies for tracking or advertising. Journl uses browser storage only to keep you signed in and to remember which set of books you had open. There is no third-party analytics script, no advertising pixel, and no third-party tracking of any kind. The typefaces are served by Journl itself, so opening a page does not contact Google or anyone else. What the software keeps in your browser, and why, is listed on the cookies and browser storage page.
We do record how the software itself is used — which screens are opened, which features are used, and where something was refused or abandoned — so that we can improve it. This is sent only to our own servers, kept only in aggregate, and never used to identify or profile you as a person.
Information inside your books
Your books contain personal data about other people: your customers and suppliers (names, addresses, emails, bank details for payment runs), your staff if you record pay runs (each person's name and pay, tax, National Insurance, student loan and pension figures, typed in or imported from your own payroll software; Journl does not calculate pay or send it to HMRC), the people you invite to your books, and anyone named in a description. You are the controller of this data. We process it only to run the service, as your processor.
| What we do with it | What we do not do with it |
|---|---|
| Store it, encrypted at rest, in the United Kingdom. | Sell it, share it, or show advertising against it. |
| Display it to the people you have given access to your books. | Use it to train any model, or to build any product. |
| Send emails you ask us to send — an invoice, a statement, a reminder — to the addresses you provide. | Contact your customers or suppliers for any purpose of our own. |
| Include it in exports you request. | Look at it, except to provide support you have asked for or to investigate a fault, under confidentiality. |
| Delete it when you close your account, on the schedule below. | Keep it after you have left, beyond that schedule. |
If one of your customers or suppliers asks you what data you hold about them, Journl's export lets you answer. If they ask us directly, we will refer them to you, as their controller.
Who we share data with
Only the companies needed to run the service. Each is bound by a contract that limits what they may do with the data to providing their service to us.
| Who | What they do | Where |
|---|---|---|
| Amazon Web Services | Hosts the software and the database, and holds the backups. | London (eu-west-2). Data does not leave the UK. |
| Amazon Web Services (Simple Email Service) | Delivers the emails you send from Journl — invoices, statements, reminders — and our own account emails, from addresses at journl.co.uk. | London (eu-west-2). Data does not leave the UK. |
| HM Revenue & Customs | Receives VAT returns you file, with the fraud-prevention headers it requires. | United Kingdom. A public authority, not a processor. |
| Stripe | Takes payment for your plan. | Stripe Payments UK Ltd (United Kingdom); card data never passes through Journl |
| HMRC and the European Central Bank (through the Frankfurter rates service) | Publish the exchange rates Journl fetches. Nothing about you is sent to them. | — |
| Anthropic | Reads bills you upload or forward to Journl, to fill in the supplier, dates and amounts for you to check. Only the document is sent; it is not used to train models, and Anthropic deletes it within 30 days unless it is flagged under Anthropic's usage policy. | United States, under the UK Addendum to the EU Standard Contractual Clauses, in Anthropic's data processing addendum. We have assessed the risks of this transfer, relying on the UK government's analysis of US law. |
| Companies House | Looks up a company's registered details and filing dates when you add its number. Only the company number is sent. | A public register, not a processor. |
| TrueLayer (not yet in use) | Bank feeds: once you connect a bank account, fetches its transactions into your books on your instruction. The code is in the software but switched off; this row takes effect only when bank feeds are enabled, and account owners will be told before that happens. Until then nothing is sent to TrueLayer. | TrueLayer Limited (United Kingdom), an FCA-authorised open banking provider. Data does not leave the UK. |
| Microsoft 365, supplied by GoDaddy | Holds the support@journl.co.uk and security@journl.co.uk mailboxes: emails you send us and our replies. | Normally the United Kingdom: Microsoft keeps mailboxes for a UK account in its UK data centres. If any of it is held outside the UK, the transfer is protected by GoDaddy's data processing terms (the UK International Data Transfer Agreement and the UK–US data bridge). |
We will update this table before adding anyone to it. We do not share personal data with anyone else, except where the law requires — a court order, or a request from HMRC or the police that we are obliged to comply with — and then only what is required.
How long we keep things
- While your account is open: everything above, so the service works.
- After you close it: you can export everything first, in full. Your books and account are then kept read-only until their deletion is approved, no later than 90 days after your request, then deleted. Backups are overwritten within a further 35 days.
- What we must keep longer: records of what we invoiced you (six years, for our own tax); HMRC filing receipts (six years, for yours); the record of your agreement to our terms (six years, as evidence of the contract); technical logs (12 months from when each was made, for security). Nothing else survives closure.
Your rights
Under UK data protection law you can ask us to:
- Tell you what we hold about you (a subject access request). Most of it you can see in Settings; for the rest, email us.
- Correct anything wrong. Your own details you can change in Settings.
- Delete your data — by closing your account, which follows the schedule above. Note that accounting records you are legally required to keep are yours to export before you do.
- Export your data in a usable form. The software does this for your books at any time; for account data, email us.
- Object to processing based on legitimate interest, and we will stop unless we have a compelling reason not to.
We will answer within one month. There is no charge. If you are unhappy with our answer you can complain to the Information Commissioner's Office at ico.org.uk, though we would rather you told us first.
Security
- All traffic is encrypted in transit; the database and backups are encrypted at rest.
- Each business's data is isolated at the database level: a query for one set of books cannot see another's.
- Passwords are stored only as one-way hashes. HMRC access and refresh tokens are encrypted with a key held outside the database (AES-256-GCM), so the database never holds a token that works.
- Posted entries cannot be edited or deleted — corrections are further entries — so the record of what happened is permanent.
- If we ever discover a breach affecting your data we will tell you within 48 hours, the ICO where required, and HMRC where the breach touches data handled under Making Tax Digital. How to report a security concern to us is on our security page.
Children
Journl is for businesses. It is not intended for anyone under 18 and we do not knowingly hold data about children.
Changes to this notice
We will email you before any change that affects how your data is used. Minor clarifications may be made without notice; the date at the top always shows the current version.
Contact
Journl Ltd
5 Unit H, Torrens Street, London EC1V 1NQ
support@journl.co.uk
Data protection contact: the director, at support@journl.co.uk. (A formal Data Protection Officer is not required for a business of this size; naming someone responsible is still good practice.)