Security & your data
Your client list is your business.
Chalmsy holds the things a business can least afford to lose — your clients, your pricing, your contracts and your books. This is a plain description of how that's kept safe, written for anyone who runs on clients, not just one trade — and it includes the parts we haven't done yet. For UK and EU businesses, our Terms carry full GDPR processor commitments.
What's already in place.
Isolated at the database
Every business's rows are separated by row-level security in the database itself — not by the interface choosing what to hide. A request for another account's data comes back empty, because the boundary lives below the app, not inside it.
No password to steal
Sign-in goes through Google. Chalmsy never sees, sets or stores a password, so there's nothing in our database for anyone to take — and you keep whatever two-factor protection already guards your Google account.
Encrypted in transit
Everything is served over HTTPS with strict transport security, so browsers refuse to connect any other way. Your documents and images live in access-controlled storage, not on a public URL anyone could guess.
Roles for staff
Give a team member the run of the work — bookings, clients, schedules — while margins, costs and the books stay out of sight. The people who need the diary never have to see the money.
Your records leave with you
Invoices and the books export to CSV, the whole workspace — clients, bookings, proposals — exports as a JSON backup, and every proposal and invoice is already a PDF in your possession. No exit negotiation, no records held hostage.
No card details held
Invoices carry your own payment terms and bank details, so clients pay you directly. Their card numbers never pass through Chalmsy — the safest way to hold a card number is to never hold it.
Google access
Why it asks for your inbox — and what it does with it.
Connecting Google is what lets Chalmsy show an enquiry next to the booking it belongs to, drop an event on your calendar, and file a signed contract into your own Drive. It's a fair question what that access is really for — so here it is, one line at a time.
- Mail — to read the enquiry threads you open in Chalmsy, and to send proposals and invoices from your own address, so they arrive from you and not a no-reply robot.
- Calendar — to create and show the events behind your bookings, and nothing else on your calendar.
- Drive — so you can find and attach your own files without leaving Chalmsy, and so the documents it produces land back in a folder you choose. It never edits or deletes anything it didn't create.
- Nothing is mined — your mail isn't scanned to train a model, sold, or shared with any other business on Chalmsy.
- The AI's side of this — what Claude is, exactly what it reads, and the commitment that your content is not training material — is written plainly on its own page.
- Revoke whenever you like from your Google account's security settings, without deleting a thing in Chalmsy. Sign-in is the one grant to keep — it's how you get back in.
| Sign-in How you log in — required | Connected |
| Gmail Read opened threads · send as you | Connected |
| Calendar Booking events only | Connected |
| Drive Files you choose to attach | Connected |
| Photos Only the photos you hand-pick | Connected |
One Google connection covers all of these, so setup is a single step. Revoke it whenever you like from your Google account.
Being straight with you
What we haven't done.
Every security page lists its strengths. Here are the gaps too — you'd rather read them now than discover them after you've moved your business across.
We're not SOC 2 or ISO 27001 certified yet.
Those audits are slow and expensive, and Chalmsy is young. The controls described above are real and in place, but they haven't been independently certified. If your procurement needs a certified vendor, we're not that yet — and we'd rather tell you plainly than imply otherwise.
We're young, and growing slowly on purpose.
Signup is open and self-serve, but the customer base is intentionally being grown slowly enough to support properly while the product matures. You're joining something early — the trade-offs of that are listed on this page, not hidden.
Backups are our provider's. Export is yours, one click, always.
The database runs on managed infrastructure, and we don't yet offer a self-serve backup-and-restore you can run yourself. If you need something recovered, ask and we'll do what can be done — but exporting your own records now and then is a sensible habit with any supplier, us included, and with Chalmsy it's one click.
Drafting sends text to Claude — which never trains on it.
When you generate or polish a proposal, the brief and the relevant prior proposals are sent to our AI provider to produce the draft. That text is not used to train their models. And every AI feature is optional — write your proposals by hand and the rest of Chalmsy works exactly the same.
Keep your own copies anyway. Any supplier, not just us.
Not because we expect to lose anything, but because a business that can't produce its own records without a supplier's cooperation is in a weak position. Export is one click, and it always will be.
Found something?
Tell us properly.
If you believe you've found a security problem, email security@chalmsy.com. We'll confirm we've received it, keep you posted while we fix it, and we won't pursue anyone who reports something in good faith and gives us a reasonable chance to put it right.
Stay calmsy
Questions we haven't answered?
Ask us anything about how your data is held. We'd rather have the conversation before you sign up than after.