Security and data handling
Where your data lives, who can reach it, and what we do when something breaks.
This page exists because buyers ask, and because a claim you cannot check is not worth much. Everything below describes the system as it runs today, not a roadmap. If something here is not good enough for your review, tell us and we will tell you plainly whether we can fix it.
Last reviewed: 17 November 2026
Where it runs
Our own server in France (EU). Not a shared SaaS platform — the same machine runs the CRM, the console and your database.
Who can reach it
Named people only, with a one-time email code and a role. Every privileged action is written to an audit log.
Backups
Nightly, off-site, encrypted at rest in Cloudflare R2. A separate check verifies every backup is fresh and non-empty each morning.
Sign-in, roles, and a log of who did what.
- Sign-in is a single-use code emailed to a named address — there is no password to leak and no shared login. Codes expire, and repeated wrong guesses lock the challenge.
- Two roles. Superadmin can manage infrastructure, play or delete call recordings, and export data. Operator works the pipeline and cannot touch recordings, exports or credentials.
- Logins, data exports, recording playbacks and deletions, credential reveals and every record change are appended to an audit log — including the failures.
- Third-party keys (telephony, email, DNS) are encrypted at rest with AES-256-GCM and are readable only from the server, never from the browser.
What we keep, and for how long.
| Data | Where | Kept |
|---|---|---|
| CRM records, deals, invoices, tickets | Self-hosted Twenty database on our server | For as long as you are a client, then exported or deleted on request |
| Call recordings | Our server, not a third-party recorder | 90 days, hard cap 5 GB — deleted automatically |
| Call metadata | Our server | With the client record |
| Backups | Cloudflare R2 (encrypted) | Rolling, per service — ask us for the current window |
Recording is off unless it is turned on for a workspace, and a spoken notice plays to the person called before any recording starts. We will sign a data processing agreement (DPA) with any client who needs one, and we will add your clauses rather than hand you ours and stop listening.
Live status, and backups that are checked rather than assumed.
Every service we run is probed on a schedule, and the results are public — no login to see them. Separately, an independent check opens each client's most recent backup every morning and fails loudly if it is missing, stale or empty: the failure we care about is the one where the backup stopped working weeks ago and nobody noticed.
Backups are nightly, so the most data at risk in a disaster is one day. We will give you the date of our most recent restore test on request, because a backup nobody has restored is a hope, not a plan.
The companies that touch your data.
Short list on purpose. We self-host what we can, so the CRM, the console, the mail server and the backups stay on our own machine.
| Provider | What it does | Location |
|---|---|---|
| Contabo | The virtual server every client system, database and backup job runs on | France (EU) |
| Cloudflare | DNS for client domains, and encrypted off-site storage for backups (R2) | Global network |
| Amazon Web Services (SES) | Sends transactional email — invoices, quotes, notifications | Global network |
| Telnyx, Twilio, Plivo | Telephone calls placed from the dialler, and their call records | US / EU / India |
| Razorpay | Card payments on our own checkout pages — card details never reach our server | India |
| DeepSeek | The AI assistant inside the console, only when a team member uses it | China |
What we do not claim.
- We are not SOC 2 certified and not ISO 27001 certified. If your process requires either, say so early — we will tell you what it would take and whether it is realistic for this engagement, rather than quietly losing six weeks to it.
- One server, one region (EU). There is no multi-region failover. The honest disaster-recovery answer is a restore from the nightly backup, timed with you.
- We do not use your data to train models, and we do not sell or share it. The AI assistant is optional per workspace.
Tell us, and we will tell you what we did about it.
Email sanjay@maysanlabs.com with what you found and how to reproduce it. We aim to acknowledge within two business days and to tell you when it is fixed. We will not pursue anyone who reports in good faith, stays within their own account, and gives us time to fix it before publishing.
Machine-readable: /.well-known/security.txt
Related: Privacy policy · Terms of service · Ask us a question