Trust

How Mabel protects your customers' information

A business that lets Mabel answer its customers trusts us with other people's information. This page says plainly what we do, and what we haven't done yet. Nothing here describes something that doesn't exist.

Last updated: 22 October 2026

Encryption

Data at rest and in transit.

Encrypted at restAll business data is stored encrypted with AES-256-GCM, on the server and in the database. The key is kept separately from the data.
HTTPS onlyAll traffic between the site, the app and the server uses HTTPS.
Secure storage on the phoneKeys and sign-in codes are kept in the phone's secure storage (Android Keystore) and are left out of phone backups.

What is not stored at all

Some things Mabel deliberately does not keep.

Card, ID and bank numbersMasked before saving when a customer types them in a conversation.
No payments by MabelShe sends the payment provider's link. Money actions in the app need two confirmations and a fingerprint.
Medical modeIn clinics and home care, medical details are not stored in conversations, SMS or the calendar. Mabel gives no medical advice.
No covert recordingMabel listens only when someone talks to her.

Who sees what

Roles, logs and sign-in.

Roles and permissionsEvery team member has a role, and sees only what that role allows.
Signed action logEvery action by Mabel and the team is logged. Each line is signed together with the one before it, so a deleted or changed line shows up. A manager can check this in one click.
Two-step verificationCodes from an authenticator app, on the site and in the app. The owner can require it for managers or for everyone.
Automatic sign-outIdle sessions end on their own. The owner chooses how fast.
DevicesEvery new device is logged. You can sign a device out, or reset access for someone who left.
Limited API keysEach key has only its own permissions and can be revoked anytime.

The site

Protections in the browser.

Content Security PolicyThe site runs only code the server signed for that page load, so code hidden in a message or a customer name does not run.
No outside server librariesThe server runs without third party code packages. App libraries are scanned for known issues automatically.
Rate limitsLimits on sign up, join codes and website questions, against guessing and abuse.

Retention and deletion

You decide how long things are kept.

Your retentionCustomer conversations are kept from 1 to 90 days, as the business chooses. Older data is deleted automatically.
Daily encrypted backupThe server checks that each backup can be restored. The last 30 are kept.
Deletion on requestAll data about one customer can be deleted at their request. The owner can export everything, or delete the business completely.

Suppliers

Each one receives only what it needs.

SupplierWhat forWhat it receives
Anthropic (Claude)Understanding the conversation and writing the replyConversation text, while answering
ElevenLabsMabel's voice and transcriptionAudio and text, during a call
TwilioPhone, SMS and WhatsAppPhone numbers and message content
Google FirebaseSign in with GoogleEmail and ID of staff members
RenderThe serverEverything, while processing
Neon (Frankfurt, EU)The databaseEverything, encrypted
SentryError reportsThe error message only, without content and without user details

What we have not done yet

  • No external certification yet, such as ISO 27001 or SOC 2.
  • No penetration test by an outside company yet. We plan one before a wide launch.
  • The data processing agreement is ready and is being reviewed by a lawyer.

Found a security problem?

Tell us what you found and how to reproduce it, without accessing other people's data or disrupting the service. We reply within 3 business days.

Contact: Mabelai.support@gmail.com

Read the data processing agreement ←