Each company kept apart
Every record belongs to one CRM, and the database itself refuses to show it to anyone outside that CRM. Automated checks try to read across companies and must be refused.
Connected accounts locked away
Access to your Google or Microsoft account is encrypted, never sent to your browser, and never shown to AI.
You control who sees what
Roles decide who can see and change each module and field, and every change to a record is kept in its history.
Keeping each company's data separate
All customers share one database, and separation is enforced inside it with row-level security: every request is checked against the CRM it belongs to and the person's role in it, so a mistake in the app can't show one company's data to another. We test this with automated checks that attempt to cross the line and must fail, and we re-run them whenever the database changes.
Connected accounts
- Access credentials for connected accounts are encrypted with AES-256-GCM. The key is kept outside the database, and the database refuses to store a credential that isn't encrypted.
- Credentials are never sent to your browser, written to logs, or included in anything sent to AI.
- We ask only for the access each feature needs, and only when you turn it on. Email access is read-only.
- Sign-in to a provider uses its standard secure flow (OAuth with PKCE), and a connection can only be finished by the person who started it.
- Every connection, renewal and disconnection is recorded in a history that can't be edited or deleted, which your CRM's admins can read.
People and permissions
- Each person in a CRM has a role. Roles decide which modules and fields they can see or change.
- Changes to records are kept in a history showing who changed what, and when.
- Only the person who started a CRM and the admins they choose can manage its settings and connections.
Infrastructure
- Chaudie runs on Cloudflare, and all traffic is encrypted in transit with HTTPS.
- Data is stored with Supabase on Amazon Web Services in the United States (Northern California), encrypted at rest.
- Passwords are hashed by our sign-in provider; we never see or store them.
AI
AI (from Anthropic) receives only the text a task needs. Under Anthropic's commercial terms, that data isn't used to train its models. AI proposes designs and changes; the decision to build or apply them is yours, and routine work like syncing is done by ordinary code, not AI.
What we don't have yet
We'd rather tell you than have you find out:
- No independent audit or certification yet, such as SOC 2.
- No two-step sign-in yet.
- No self-serve export yet. Ask us and we'll send you a copy of your data.
We'll update this page as each one changes.
Reporting a problem
If you think you've found a security issue, email support@chaudie.com. Please give us a chance to fix it before telling others, and don't access or change other people's data while testing. We'll reply, keep you updated, and credit you if you'd like.