Security & data

What we do

Workspace isolation

Every workspace is separated at the database level using row-level security, so other customers cannot read your prospects, campaigns or notes.

Server-side authorisation

Permissions are checked on the server for every request, not just hidden in the interface.

Human approval is enforced

A message cannot be marked as sent unless a person approved it first. The database itself rejects anything else, even from our own server code.

Suppression respected

Recipients on a workspace’s suppression list are blocked from being marked as sent.

Append-only records

The audit log and the credit ledger cannot be edited or deleted after the fact, so changes are traceable.

Plan limits in the database

Credit balances never go below zero and plan limits are enforced by the database, not only by the app.

Secrets stay on the server

API keys and other secrets are kept in server environment variables and are never sent to the browser.

Safe website checks

When we fetch a prospect’s public website, requests are guarded against being pointed at internal or private network addresses.

Payments

Card payments are handled by Stripe. Card numbers never reach our servers.

Who processes data for us

Supabase (database and sign-in), Stripe (payments), Anthropic (AI text generation), search and places providers such as Serper and Google Places, and our hosting provider. We share only what each needs to do its job. See the Privacy Policy for detail.

What we have not done yet

We have not completed an independent security certification such as SOC 2 or ISO 27001, and two-factor sign-in is not yet available. We would rather tell you that than imply otherwise. If these matter to your business, ask us where we are.

Report a problem

If you think you have found a security issue, please tell us privately before sharing it publicly through our contact form.