Security · In transit and at rest
Encryption and data access
Everything travels over HTTPS and the most sensitive data is stored encrypted with AES-256-GCM.
In transit: the journey of a message
Tap each leg to see how it's protected.
Your client Server
The server sets HSTS and redirects to HTTPS whenever the proxy reports that the request came in over HTTP.
At rest
ID numbers, email addresses and internal notes on contact records are encrypted with AES-256-GCM before being stored, with a key that lives on the server and not in the database.
Conversations are stored so you can see them in your dashboard. They aren't end-to-end encrypted, because the receptionist has to read them to reply.
- HTTPS and HSTS everywhere
- AES-256-GCM on sensitive data
- Encryption key kept outside the database
- Name
- Marta SampleNo field encryption
- Phone
- 600 000 000No field encryption
- ID number (DNI)
- 00000000TAES-256-GCM
- marta@example.comAES-256-GCM
- Internal notes
- Prefers afternoonsAES-256-GCM
- Chat messages
- “Any slots on Thursday?”No field encryption
This is not end-to-end encryption
Even if someone walked off with a copy of the database, your customers' ID numbers, email addresses and notes couldn't be read without the server key.
