Plain answers about your mailboxes and your data.
Written from how the product works today.
- Gmail and Outlook connect through Google or Microsoft sign-in
- Data you upload is never sold or shown to other customers
- Suppression is checked on every send
- Nothing sends until you say so
Your mailbox, on your terms.
Sign in with Google or Microsoft
Gmail and Outlook connect through Google or Microsoft sign-in. Your password goes to them, not to us.
Encrypted tokens
The refresh tokens we keep for direct connections are encrypted with AES-256.
What we ask for
Most Gmail and Outlook mailboxes connect through our mailbox-connection provider, using Google or Microsoft sign-in. Direct connections ask Gmail for send, read, and modify access, and Outlook for IMAP and SMTP access. Google Postmaster: read-only.
Passwords, when a provider needs one
Other IMAP/SMTP mailboxes, and premium warming, need a password or app password. We store it so Senders, and MailReach for warming, can sign in for you. Use an app password you can revoke.
Leave anytime
Disconnect a mailbox in the portal, or revoke access from your Google or Microsoft account settings.
What you upload stays yours.
Scoped to your account
Your prospects, campaigns, and mailboxes are stored against your account in a shared database and looked up by your account ID. Hosting and daily backups are in the EU.
Not sold, not shown
We don't sell the data you upload, don't show it to other customers, and don't use it to train models. The one exception is the Senders-wide do-not-send list below.
One shared list, on purpose
Addresses that hard-bounce, fail verification, or opt out at senders.ai/opt-out go on a Senders-wide do-not-send list. It protects every sender's reputation, including yours.
Licensed data is different
Contacts you pull from our data sources are licensed data. We may cache them and serve them to other customers.
Who else handles it
Our subprocessors: hosting, mailbox connection, verification, warming, data sources, payments, and internal operations such as error monitoring, system email, and team notifications.
Take it with you
Export your prospects as CSV from Claude or ChatGPT, up to 5,000 rows a request. To have your data deleted, email privacy@senders.co.
Suppression runs on every send.
The same checks run whether a send starts in the portal, in Claude or ChatGPT, or with your Pod.
- Your do-not-contact list blocks an address. Your do-not-prospect list blocks a whole company domain, now and in the future.
- Hard bounces we detect, failed verifications, and public opt-outs are blocked across Senders.
- Every address is verified before first contact.
- Consumer addresses (Gmail, Yahoo, and the like) are blocked for cold outreach.
- Campaign mail includes an unsubscribe link. The unsubscribe page asks for a click to confirm, so link scanners can't opt people out by mistake.
- Hold lists pause a person or a domain without deleting them.
Control stays with you.
Sign-in, not API keys
Claude and ChatGPT connect through OAuth sign-in with PKCE, so there is no key to paste. Clients without sign-in can use an account token from the portal: treat it like a password.
Tools say what they do
Read-only tools are marked read-only. Tools that spend credits or send email are marked as such, so your assistant asks before it runs them.
Spend limits you set
Per-purchase, daily, and monthly caps, and auto top-up on or off. Changes need your confirmation and are logged.
The basics
HTTPS everywhere, with HSTS. Account passwords are stored as one-way hashes.
Have a question this page doesn't answer?
Email privacy@senders.co, or book 30 minutes and ask us directly.