01Who we are
SadaSend provides a transactional email API. When you send email through us, you are the data controller for your recipients’ personal data and SadaSend is your data processor. When you use our website and dashboard, we are the controller for your own account data.
For any privacy question, including requests to access or delete data, contact us through our official privacy channel upon public launch.
02What we collect
- Account data — your name, email address, company name, and authentication credentials. Passwords are hashed; we never store them in a readable form.
- Billing data — handled by our payment processor. We store a customer reference and your plan, never full card numbers.
- Sending domain data — the domains you verify, their DNS records, and the DKIM key pairs we generate for them.
- Email content and metadata — the messages you send, their recipients, subjects, headers, bodies, attachments, and the delivery events they generate.
- Usage and diagnostic data — API requests, error traces, and aggregate volume statistics.
03How long we keep email content
Message bodies and delivery logs are retained according to your plan. This is a product limit and a privacy control at the same time — shorter retention means less of your recipients’ data sitting on our systems.
| Plan | Message bodies and logs | Delivery events |
|---|---|---|
| Free | 1 day | 30 days |
| Pro | 7 days | 90 days |
| Scale | 30 days | 90 days |
04Suppression lists are kept longer, on purpose
When an address hard-bounces, marks your mail as spam, or unsubscribes, we record it on your account-wide suppression list and keep it for the life of your account. Deleting that record would allow the same address to be emailed again, which is precisely the harm the suppression exists to prevent.
A suppression record contains the address, the reason, and a timestamp. Nothing else.
05Subprocessors
We use a small number of third parties to run the service — for delivery, storage, payments and monitoring. Each is bound by a data processing agreement, and none of them receives more of your data than the job requires.
The current list, naming each subprocessor and what it processes, is available on request upon public launch. We will send it to any customer or prospective customer, and we will tell you before we add one.
06Where data is processed
Our primary infrastructure runs in the United States. If you require EU data residency, contact us before you build on the service — we would rather tell you honestly that it is not available yet than have you discover it during a compliance review.
07What we do not do
And when we do look at a message body — because you asked us to, or during an abuse investigation, or under legal compulsion — you can see that we did. Every access is listed in your dashboard under Data access: who opened it, when, and why. You do not have to take this section on trust.
- We do not sell your data, or your recipients’ data, to anyone.
- We do not use the content of the email you send to train machine learning models.
- We do not read your message bodies except when you explicitly ask us to help debug a specific message, or where we are legally compelled.
- We do not add tracking pixels or rewrite your links unless you turn on open and click tracking yourself.
08Your rights
Depending on where you live, you may have the right to access, correct, export, or delete your personal data, to object to processing, and to lodge a complaint with a supervisory authority.
You can export your account data and delete your account from the dashboard at any time. Deleting an account removes message content within 30 days, with the exception of suppression records and any data we must keep for tax or legal reasons.
09Cookies
The marketing site loads two third-party measurement tools: Vercel Web Analytics, which is cookieless and records no personal data, and Google Tag Manager. Tag Manager sets no cookies by itself — it is a container that loads whatever tags we configure in it, and any tag we add that does set cookies will be named here before it goes live.
The dashboard sets a single session cookie required to keep you signed in.
10Changes to this policy
If we make a material change we will email account holders at least 30 days before it takes effect. The date at the top of this page always reflects the current version.