Security & your data
Written for the person
who has to sign it off.
You are about to point something at your inbox, your calendar, your CRM and your billing. That deserves a straight answer about what happens next — including the parts where the answer is “not yet”.
Your workspace is the boundary
Every opportunity, contact and note is owned by one workspace and readable only inside it. That isolation is enforced on every query rather than by a filter someone remembered to add, and it's the single property our test suite checks hardest.
Where it lives
A managed Postgres database in the EU, plus Clerk for accounts and Stripe for payments. Model calls go through Vercel's AI gateway. No customer data is sold, shared, or used to train anything.
The agent reads; you approve
Nothing is sent on your behalf without you approving it. Drafts are drafts. Where the setup skill connects your sources it asks for read-only access wherever the vendor offers it — nothing in the workflow needs permission to send an email or move a deal.
You connect it, you can disconnect it
The connection between your agent and your workspace is an OAuth grant you make and can revoke. We never ask you to paste a password anywhere, and there is no password of ours to leak.
Admin actions are written down
Destructive actions — removing a colleague and deleting their pipeline, for instance — are recorded with who did it, when, and how much went. So an accident and a bad actor are distinguishable afterwards.
No card during the trial
The 7-day trial is entirely ours — no Stripe customer, no card, no payment method anywhere in the system until you decide to pay. There is nothing to auto-charge because nothing has been collected.
Answered plainly, including where the answer is no
A security page that only lists strengths tells you nothing, because every security page lists strengths. These are the ones that actually decide whether you can use us.
- Are you SOC 2 or ISO 27001 certified?
- No. Customer Magic is early and run by one person; an audit that says otherwise would cost more than the company has and would be theatre at this size. If that is a hard requirement for your organisation, we are not the right fit yet and I'd rather tell you now.
- Who at your end can see our data?
- Ben, and only to fix something you've reported or to keep the service running. There is no support team, no analytics vendor with a copy, and no data brokerage of any kind.
- Does our data train a model?
- No. Model providers are used under terms that exclude training on our traffic, and we don't fine-tune anything on customer data.
- What happens if we leave?
- Your workspace and everything in it is deleted on request, and the deletion cascades — memberships, opportunities, history. We keep what invoicing law requires us to keep and nothing else.
- Where do I report something?
- Reply to any email from us, or use the contact page. A security report gets answered the same day.
For the technically minded: access control is enforced per request and per workspace rather than in the interface; every route that touches your data authenticates and takes a rate-limit token, and that rule is asserted by tests that read the source rather than trusting a convention. Internal errors are logged and never returned to a caller. Secrets live in the environment, never in the codebase.
The controls are documented in the same commit as the code that implements them — a deliberate rule, because a security document that drifts from the system is worse than none.
Still have a question?
If your team has a security review process, send it over — I'll fill it in myself, and I'll tell you where we don't measure up rather than leaving you to find out.
See also: how it works and pricing.