Privacy policy
Ledger is accounting and stock software for small businesses, run by Vereon Ltd ("we", "us"). This page says what Ledger holds, why, who else handles it, how long we keep it, and what you can ask us to do. Write to us about any of it at info@vereon.tech. Last updated 25 October 2026.
Who is responsible
For your account and your subscription, we decide how the information is used (we are the "controller"). For what a business puts into Ledger — its books, and the names, contact details and tax numbers of its customers and suppliers — the business decides, and we handle it on their behalf (we are their "processor"). If a business that uses Ledger has your details because you buy from it or sell to it, that business is responsible for them; send requests to them first, and we help them answer. A business that needs a data processing agreement can ask us for one.
What we hold
- Your account: your name, email address and time zone, and your password (stored only as a one-way scrypt hash; Ledger runs its own sign-in). If you sign in with Google, Google's id for you; with Microsoft, Microsoft's id for your account (and its organisation's). Whether your email is confirmed, and which businesses you belong to with what role.
- The business's details: its name, address, contact details and tax numbers (such as an NTN and STRN, or a VAT number), its logo, its financial year and lock date, the payment instructions and bank details it chooses to print on its invoices, its chart of accounts, tax rates and money accounts, and who on the team did what and when.
- Its books: invoices, supplier bills, expenses, payments, transfers, journals and opening balances; its products and services, its stock and every movement of it; the bank statements it uploads and how each line was matched; the files it attaches, such as a supplier's bill or a receipt; and a log of each import (the file's name, and which rows came in and which didn't, with why).
- Customers and suppliers, as the business enters them: names, contact details, addresses, tax numbers, payment terms and the team's own notes, and what each owes or is owed, read from the books. Ledger holds what the business types in or imports; it collects nothing from the customers or suppliers themselves.
- Invoice links: an invoice can have a private link that opens its PDF, for the customer it was sent to. Anyone holding the link can open that one invoice, so it is long and unguessable, and it stops working if the customer's details are erased.
- Emails we send for a business: invoices and payment reminders to its customers, sent from Ledger's address in the business's name, with replies going to the business's own email. Each one is recorded against its document, so nothing sends twice. We also send the team's own emails: invitations, codes to confirm an email address, password resets and billing.
- Connected apps: if a business connects Register, Offr or Trazr (Vereon's other products), Ledger reads that product's accounting feed for the business: each sale with its lines and how it was paid, refunds and voids, expenses, supplier bills and what was paid on them, with the name, email and phone of the customer or supplier on each where the product has them, so they can be matched to the business's own customers and suppliers. The access Ledger reads it with is stored encrypted, and is deleted when the business disconnects.
- Leo and connected AI assistants: what you ask Leo, his answers and the drafts you approve, kept for a day so a conversation can carry on; and which AI assistants (Claude, ChatGPT, Gemini) you have connected to Ledger. What they draft is recorded under your name.
- Running the service: technical logs (time, address, errors) kept to keep Ledger working and secure. We don't track the pages you visit, and there is no advertising or analytics: not in the app, not on this site and not on invoices.
Why we use it, and on what basis
- To provide the service you signed up for — keeping the books, making invoices and their PDFs, sending the emails a business asks for, reading the apps it connects, billing the subscription: because it is needed to perform our contract with you or your business.
- To keep Ledger secure, prevent misuse and fix faults: because we have a legitimate interest in a safe, working product, which doesn't override your rights.
- To keep our own financial records: because the law requires it.
We do not sell your information, use it to advertise to you, or use it to train AI models. We never use a business's customers' or suppliers' details to market to them.
Google user data
Ledger asks Google for as little as it can, and only if you choose to sign in with Google:
- Signing in with Google (
openid,email,profile): we read your name, email address, whether Google has confirmed that address, and Google's id for you, to sign you in or create your account. We keep no Google token afterwards, and Ledger has no access to your Gmail, Drive or anything else in your Google Account.
We don't share Google user data with anyone, use it for advertising, sell it, or use it to train AI models, and no person at Vereon reads it unless you ask us to help with a problem or the law requires it. Ledger's use and transfer of information received from Google APIs adheres to the Google API Products User Data Policy, including the Limited Use requirements.
Microsoft user data
- Signing in with Microsoft (
openid,email,profile): we read your name, email address, whether Microsoft has confirmed that address, and Microsoft's id for your account, to sign you in or create your account. Signing in gives Ledger no access to your mailbox or files, and we keep no Microsoft token afterwards.
Leo and AI
Leo, Ledger's helper, runs on Amazon Bedrock in London: your questions and the parts of your books he needs to answer them stay in the UK under AWS, are not kept by the model provider, and are not used to train any model. AI assistants you connect yourself (Claude, ChatGPT, Gemini) see what you ask them to fetch from Ledger, under their own privacy terms. Neither can issue or void an invoice or a bill, record or allocate money, post a journal, reconcile the bank, export anything, or reach billing, the team or passwords.
Money and banks
Ledger records money; it never moves or holds it. Payments, expenses and transfers are what the business tells Ledger happened, and a bank statement is a file the business downloads from its bank and uploads. Ledger doesn't connect to any bank, and never sees a bank login, a card number or a PIN. The only payment Ledger takes is a business's own subscription, through Stripe.
Who else handles it
The people in your business see it according to their role. These providers handle it for us, each only as far as their job needs:
| Provider | What for | Where |
|---|---|---|
| Amazon Web Services | Runs Ledger (the site on Amplify, the API on Lambda), stores the files businesses attach, such as logos, receipts and suppliers' bills (S3), sends Ledger's emails (SES), and runs Leo's AI (Bedrock) | UK (London, eu-west-2) |
| MongoDB Atlas | The database, hosted on AWS in the same region | UK (London) |
| Stripe | Takes the business's subscription payment and keeps the billing records. Never the business's own money | EU and US |
| Only if you choose it: signing in with Google | Worldwide | |
| Microsoft | Only if you choose it: signing in with Microsoft | Worldwide |
Nobody else, unless the law requires it. Register, Offr and Trazr are run by us, Vereon Ltd, too: connecting one moves the business's own records between two of our products, under this policy.
Sending data outside the UK
Ledger runs in the UK (AWS London, eu-west-2), so your data mostly stays here. Stripe handles subscription billing in the EU and US, and Google and Microsoft handle sign-in where the table says, only if you choose them. When data leaves the UK it is protected the way UK law requires, by the UK's adequacy regulations (including the UK–US data bridge) or by the International Data Transfer Agreement or Addendum in our contract with the provider. Ask us for details.
How long we keep it
| What | How long |
|---|---|
| Your account | Until you delete it |
| A business's books and everything in them (documents, stock, customers and suppliers, attachments, statements) | As long as the business needs them: how long it must keep its books is set by its own tax law, so they stay until its owner closes the business, and are then deleted at once |
| Invoice links | As part of the invoice; erasing the customer's details stops the link working |
| Emails sent for the business (what was sent, to whom, when) | As part of the document's record, until the business is closed |
| What connected apps sent | As part of the books, until the business is closed; disconnecting deletes Ledger's access, and what was posted stays |
| Import logs | Until the business is closed |
| The team's activity history (who changed what, and when) | 2 years, or until the business is closed if that's sooner |
| Your conversations with Leo | 24 hours after the last message, then deleted |
| Billing records for the subscription | 6 years, at Stripe, because tax law requires it |
| Technical logs (time, address, errors) | A short rolling period, to keep Ledger working and secure |
| Database backups | A short rolling period; deleted data leaves them as they roll over |
Your rights
- See and take your data: your books are all visible in Ledger, and the owner, admins and accountant can export every report as a CSV. For a copy of everything we hold about you, write to us.
- Correct it: your own details are editable in Your profile, and the owner and admins edit the business's under Settings. A business's customer or supplier asks the business, which corrects them on their record.
- Delete it: you can delete your account from Your profile, and a business's owner can close the business from Settings, which deletes it and its records straight away. A business's owner or admins can erase one customer's personal details from that customer's page: their name, contact details, address and tax numbers go, from their invoices and payments too, and the money records stay without a name, because a business must keep its books. A customer can ask the business to do that.
- Object, or ask us to restrict how we use it: write to us.
We answer within a month. You can also complain to the Information Commissioner's Office (ico.org.uk) or, in the EU, your own data protection authority. If a business has your details as its customer or supplier, point your request at the business first, and we will help them answer it.
Cookies and storage in your browser
Ledger sets no advertising or analytics cookies, so there is nothing to opt into. It keeps what it needs to work in your browser: your sign-in, which of your businesses you last had open, your language, and which market's prices this site shows you. An invoice's link sets nothing at all.
Security
Everything travels encrypted. Passwords are stored only as one-way hashes, the access for connected apps is stored encrypted, invoice links are long and unguessable, and every record carries the business it belongs to, checked on every request. If something ever went wrong with your data, we would tell the Information Commissioner's Office within 72 hours and tell you without delay if it put you at risk.
Children
Ledger accounts are for businesses, and you must be 18 or over to use one.
Changes
If this page changes in a way that matters, we tell business owners by email first.