A database for each account
Your records are never mixed in with another customer's.
In short: your records are kept apart from everyone else's, encrypted on disk, behind a sign-in you can protect with a second step, and never sold. This page says what we do about the things people worry about, where you can see it in the product, and what we do not claim.
Last updated: 22 October 2026
Your records are never mixed in with another customer's.
AES-256 on every database, backup and uploaded file.
Add an authenticator app to your password.
Payments are taken by Stripe, not by us.
No advertising, no analytics trackers.
Kept for up to a year, and checked.
The first worry: is what I enter private, from other customers and from the people who run the service?
No. Every account's records are kept in a database file of its own, and the service opens only the one that belongs to the account you are signed in to.
Only the few people who run the service, through an administrator area that is separate from the customer app and needs more than a password.
You decide who joins your account and what role they have. Taking someone out ends their access straight away.
See it:Settings > Team
It is kept in your account's own database, with the same protection as everything else. You decide what to enter; we handle it only to run the service for you.
See it:Roles in the Privacy Policy
No system is perfectly safe, so the useful question is: what stands in the way, and what is left if something does go wrong?
It would be unreadable. Every database, every backup and every uploaded file is encrypted with AES-256, with a different random key for each account.
Guessing is cut off, and your password is never stored in a form that can be read - not even by us.
It does not have to be. Anyone can add a second step: a six-digit code from an authenticator app on their phone.
See it:Settings > My account > Two-step sign-in
You can see every device that is signed in, end any of them, or end all but the one in your hand.
See it:Settings > My account > Where you are signed in
We close off the common ones and check the rest with automated tests.
Two different worries: paying for CostBridge, and the bank or card statements that households may choose to import.
No. Payments are taken by Stripe, a payment company that is built for it. Your card number never reaches CostBridge.
See it:Settings > Billing
Importing a statement is optional, and CostBridge can only read the file you choose: it has no connection to your bank and cannot move money.
Trust includes being able to get your records back, take them with you, and have them deleted.
It is backed up every day, and the backups are kept for up to a year.
Yes to both. Your reports and lists download as CSV, Excel and PDF, we can send you a full copy on request, and you can ask for your account to be deleted.
See it:Your rights: Privacy Policy
We do not sell it, we do not use it for advertising, and we use no analytics or advertising trackers.
How we find out, how we tell you, and how you can tell us.
If a breach puts people at risk we tell the people affected without undue delay, and the Information Commissioner's Office where the law requires it, within 72 hours where we can.
Please tell us. Email support@costbridge.co.uk with "Security" in the subject, and say what you saw and where. We treat these as urgent.
See it:security.txt
We use open, well-known standards rather than inventing our own. Each one says whether we use it directly, rely on a company that holds it, or only follow its guidance - and the ones we do not hold are listed too.
The encryption standard used by governments and banks, with 256-bit keys.
At CostBridge: Every database (SQLCipher) and backup is encrypted with it, and every uploaded file and stored secret is sealed with AES-256-GCM, which also detects tampering.
The standard that encrypts everything between your browser and a website, and the header that tells browsers never to fall back to an unencrypted connection.
At CostBridge: The whole site and the service behind it are served over HTTPS, plain-http addresses are sent to HTTPS, and browsers are told to keep to it.
A deliberately slow one-way function made for passwords, so a stolen list of them is very costly to crack.
At CostBridge: Passwords are stored only as bcrypt hashes with a per-password salt; they cannot be read back, even by us.
The open standard behind the six-digit codes in Google Authenticator, Microsoft Authenticator, 1Password and similar apps.
At CostBridge: Any authenticator app that follows the standard works with CostBridge two-step sign-in. Each code is accepted once.
The standards behind "Sign in with Google" and "Sign in with Apple".
At CostBridge: We check the signed identity token each provider gives us before anyone is signed in. Those accounts have no CostBridge password to steal.
A signed, short-lived pass your browser shows with each request.
At CostBridge: The pass lasts minutes, is kept in memory only, and is checked against a session on our server on every request, so ending a session takes effect at once.
The security standard for anyone who handles payment card numbers.
At CostBridge: Card numbers are entered with Stripe, which is certified to the highest level of PCI DSS (Level 1). They never reach CostBridge, and Stripe's messages to us are accepted only with a valid signature.
The industry list of the most serious risks to web applications: broken access control, weak authentication, injection, misconfiguration and so on.
At CostBridge: Our internal security review was organised around it. Each of the protections on this page answers one of its categories.
The data protection laws for people in the UK and the European Union, enforced in the UK by the Information Commissioner's Office.
At CostBridge: Our Privacy Policy is written for them: who is responsible for what, why data is used, how long it is kept, your rights, and telling you about a breach without undue delay.
A standard place on a website where security researchers find out how to report a problem.
At CostBridge: Ours is at /.well-known/security.txt and points to the same contact as this page.
The independent certifications and tests that a company can pass to prove its security to others.
At CostBridge: We do not hold them yet, and we will not display a badge for one until we do. Until then this page tells you what we do so you can judge it yourself.
Security is shared. These few habits close the gaps that no service can close for you.
A security page that only says good things is not worth much. These are the limits.
A small number of companies handle data for us, each for one purpose and under a contract. The full list, with the legal detail, is in the Privacy Policy.
| Company | What for |
|---|---|
| SmarterASP.NET | Hosting: the servers and storage |
| Stripe | Card payments and subscriptions |
| An email delivery provider | Sending the emails the service needs |
| Google and Apple | Only if you choose to sign in with them |
Ask us anything about how your data is handled. A real person will answer.