Security
Last updated 20 November 2026
In short: practices are kept apart from each other, sensitive details are encrypted, important actions are recorded, and the service is hosted in the United Kingdom.
1. Where your data is kept
- The service and its backups are hosted in data centres in the United Kingdom.
- Information travels over encrypted connections (HTTPS) between your browser and the service.
- Stored data sits on encrypted disks.
2. Keeping practices apart
Each practice's records are separated from every other practice's. Every request is checked against the practice the signed-in person belongs to, and one practice cannot see or search another's information.
3. Signing in
- Passwords are stored only as a one-way scrambled value, using a modern algorithm designed for passwords (Argon2). We cannot read them.
- A sign-in from a new device needs a one-time code sent by email.
- Sessions end after a period of inactivity and after a maximum length.
- Repeated failed attempts are slowed down and limited.
- Staff and clients sign in through separate doors with separate sessions.
4. Who can see what
- Each member of staff has a role, and each screen and action checks that role.
- Especially sensitive identifiers, such as National Insurance numbers and tax references, are encrypted individually, shown only to those who need them, and each viewing is recorded.
- Our own access to the live service is limited to the people who need it to run the service, and their actions are recorded.
5. A record of what happened
- The service keeps an audit trail of who did what and when.
- Signed documents are sealed so that a later change can be detected, with evidence of when and how each person signed.
- Permanent deletions are recorded in a chain that cannot be quietly altered.
- Our technical logs are designed not to contain the content of documents or messages.
6. Backups and continuity
The database and uploaded files are backed up regularly, and backups are kept separately from the live service for up to 30 days. A practice can also take a complete export of its own records at any time.
Backups protect against a failure of our systems. They are not a way to recover something a practice deletes or changes by mistake.
7. How we build
- Changes are reviewed and run through automated tests before release.
- Uploaded files are checked for type and size, and stored outside the reach of the web server.
- Web pages are protected against common attacks, including cross-site request forgery and script injection.
- We update the software components we depend on regularly, and prioritise security fixes.
8. Payments
We do not store card numbers or bank account details. Payments are handled by regulated payment providers, and the service never holds a practice's or a client's money.
9. What we do not claim
We do not currently hold an independent security certification such as ISO 27001 or Cyber Essentials. We will say so on this page when that changes. No system is perfectly secure, and each practice remains responsible for its own accounts, devices and staff.
10. If something goes wrong
If we become aware of a breach affecting a practice's data, we will tell that practice without undue delay, and where feasible within 72 hours, as set out in our data processing terms.
11. Reporting a security problem
If you believe you have found a security weakness, please email hello@chartercrew.co.uk. Our acceptable use policy explains how we handle reports made in good faith.