Security
Security you can verify
Not declarations but mechanisms: each one can be checked in the database schema or in the code.
Protected at the database level
RLS · 67 tables
AES-256-GCM
Audit log
Mechanisms
Six things that do not depend on discipline
- 01
Data isolation
RLS in FORCE mode on 67 tables — it applies even to the table owner.
- 02
Key encryption
AES-256-GCM; the master key is never stored in the database.
- 03
Roles and permissions
Five roles with different boundaries; the API has per-action permissions.
- 04
Audit log
Who changed what, when and to what. Append-only, never edited.
- 05
Retention periods
Records are deleted on schedule — automatically, not by reminder.
- 06
Data subject requests
Access, deletion, portability — tracked separately with a 30-day deadline.
Isolation
Every customer sees only their own data
Not a filter in a query but a policy of the database itself: without the customer’s ID a query returns nothing.
Subprocessors
Who processes data during a call
| Link | Who | What they receive |
|---|---|---|
| Telephony | Your SIP carrier or your own PBX | the call audio channel |
| Speech recognition | Deepgram | audio → text |
| Conversation model | OpenAI or Anthropic | call text → reply |
| Speech synthesis | Deepgram · ElevenLabs · OpenAI | reply → voice |
| Recording storage | Your S3-compatible bucket | audio, only if you turned recording on |
Demo
Send us your
list of requirements.
We will go through it point by point and say plainly what already exists and what would need work.