Skip to content
Guides

How your account and your customers' data are kept secure

Encryption, hashed passwords, role-based access and payments handled by Stripe. A plain-English account of how your data is protected, and your part in it.

The short version
  • Data is encrypted in transit and at rest, with managed backups.
  • Passwords are hashed, and card numbers never reach our servers.
  • Access is by role, and enforced on the server.

A fair question from any business

You are being asked to put your customers' names, numbers and conversations into someone else's system. You should know how they are looked after. This guide sets it out in plain English, without the jargon that usually surrounds the subject. The same commitments are published on our trust page, where they can be read by anyone and compared with what we do. If something here matters to your own customers, you are welcome to point them to it.

In transit and at rest

Everything that travels between your phone or computer and our service does so over an encrypted connection, the same kind your bank uses. Once stored, data sits on encrypted infrastructure with managed backups. In practical terms, somebody listening on a café wifi network can't read your enquiries, and a copy of the stored data would be unreadable without the keys.

Passwords and sign-in

Passwords are never stored in readable form. They are hashed, which means even we can't see what yours is. Strong passwords are required. Two-factor authentication is available to every user and can be made compulsory for the whole team by an owner. Those three measures together deal with the commonest ways in which online accounts are broken into, which are reused passwords and guessable ones.

Who can see what

Access is by role. Only Business Owners reach the settings, exports and billing. Other roles work with enquiries and bookings. A restaurant's host stand uses a separate link that shows the door sheet and floor map and nothing else. These limits are enforced on the server, so they can't be bypassed by someone typing an address into a browser.

Payments

When your customers pay an invoice by card, the payment is handled by Stripe, which exists to do exactly that. Card numbers never touch our servers, and we never see or store them. The money goes to your own Stripe account. Your receptionist never asks a caller for card details either, so there is no point at which a card number is spoken or typed into your account.

Your side of it

Good security is shared. Give each person their own login. Require two-factor. Remove leavers the day they go. Keep the number of owners small. Set retention periods so that recordings aren't kept without reason. Be careful with exports once they are on a laptop. Each of those is in your hands, takes minutes, and does as much for your customers' privacy as anything on our side.

Questions people ask

Is my data encrypted?

Yes. Data is encrypted in transit over HTTPS and stored on encrypted infrastructure with managed backups.

Do you store my customers' card details?

No. Card payments are handled by Stripe. Card numbers never reach our servers and we never see them.

Do you use my customers' conversations to train AI for others?

No. Your leads and knowledge base are used to run your account and nothing else, and we do not sell data.

This is what Lead Capture AI does for you

She answers the calls you can’t, knows your business, and texts you the details in seconds. Your number is live the day you sign up, and the first 7 days are free with no card.