Security and trust

Where the money and the notes sit.

Your clients book, sign and pay on a page with your name on it. Here’s what sits behind that page, including what we haven’t done yet.

The money

It goes to your bank. There’s no balance with us in between.

Stripe takes the paymentStripe is PCI DSS Level 1, the highest level. Card numbers go from your client’s browser straight to Stripe and never touch our servers.

The account is yoursIt’s connected under your name and your tax details. Payouts land in your bank on Stripe’s normal schedule, whatever happens to us.

We never hold your fundsThere’s no wallet, no float and no withdrawal step. We aren’t a payment institution, and we can’t move your money.

We can’t charge your clientA saved card can be charged only against an invoice you created.

Disputes come to youEach one arrives with the agreement your client signed, the time they signed it, and the booking attached.

Your clients’ data

How the notes and records you keep on your clients are protected.

Encrypted in transit and at restTLS 1.2 or better on every connection, and AES-256 on stored data. The credentials you connect, your calendar and your sending account, are sealed under a separate key, so reading the database isn’t enough to use them.

Your notes are private to youA note you keep on a client never appears on their page, in a reminder or in any email we send for you. We don’t read it when we answer a support message.

A client’s page isn’t a public URLIt opens from a signed link tied to their email address. Nobody can feasibly guess it, and you can revoke it.

No passwords anywhereNot for you and not for your clients. There’s no password database to breach, and no reused password to inherit somebody else’s breach from.

The app runs with the narrowest access it canThe app connects to the database as a role that can read and write your rows and nothing else. It can’t alter the schema, create a role or read a password hash, and that’s checked in production.

Delete means deletedRemove a client and their record, notes and history go at once, then leave the backups within 30 days. We keep the invoice and payment history the law requires, with their name taken off it.

If we go away

If WorkWith stops, here’s what you keep.

Your payments are independent of usYour Stripe account belongs to you. If WorkWith stopped existing tomorrow, money owed to you would still reach your bank.

Export is always availableOne button on Me exports everything as spreadsheets: clients, sessions, invoices, payments, agreements and offers. It works while you subscribe, after you cancel, and if we shut down.

Canceling doesn’t close your linkYour page keeps taking bookings and payments after you cancel.

Six months of noticeIf we wind down or are acquired, you get at least six months’ notice and a working export before anything is switched off. The terms say so.

Being straight with you

What we have

Encryption in transit and at rest. Seven days of point-in-time recovery on the database. Stored third-party credentials, sealed under their own key. An application role that can’t reshape the database or escalate itself. And no passwords anywhere in the product.

What we don’t, yet

We don’t have a SOC 2 report, an ISO 27001 certificate or a third-party penetration test. All three are on the list.

Are you a therapist with HIPAA obligations? Talk to us before you sign up, and we’ll tell you whether we’re right for your practice today.

Found something? Tell us.

support@workwith.page · we reply to every report, and we don’t threaten researchers

Get in touch →