Who we are
SendAPI.email is an email sending service: apps send transactional email through its API, on Amazon SES, and their owners manage it in the panel at sendapi.email. It is run by CodeShant Technologies, "we" or "us".
We are the controller for the data of account holders. For the emails an app sends through us, the app's owner is the controller and we process that data for them, on their instructions.
Questions about privacy: [email protected].
What we collect
- Account data: your email address and your role. You sign in with a one-time code or link sent to your email, or with Google. We never store a password.
- Sign in with Google: Google confirms your email address and gives us a stable ID for your Google account, which we store to recognise you next time. We store nothing else from Google and cannot change anything in your Google account.
- Emails sent through the service: the sender, recipients, reply-to address, subject, body, attachments and custom headers. The body, the attachments and the header values are deleted as soon as the email is sent, blocked by the suppression list, or has failed. We keep the addresses, the subject, the names of attachments and headers, the status and the delivery events.
- Delivery events from Amazon SES: delivered, delayed, bounced (with the reply of the receiving mail server) and marked as spam. If the sending app turns tracking on: opens and clicks, with the clicked link and the IP address and browser or mail app that Amazon SES reports.
- Suppression list: addresses that bounced, marked an email as spam or were added by hand, with the reason, so that we don't send to them again. When an entry is removed, it stays in the history so apps can follow the changes.
- API keys: stored as a hash, plus their first 12 characters so you can tell keys apart. The full key is shown once, when it is created.
- Technical logs: the method, the page or API path (without its query string) and the IP address of requests, for security and debugging.
- Payments: when you buy credits, you pay on Stripe's page, and Stripe receives your account's email address and the card details you enter there. We never see your card details. We keep the pack, the amount, the date, Stripe's reference for the payment, the email address we send the purchase confirmation to, and when you asked at checkout for the credits to be added right away. See Stripe's privacy policy.
- Email sign-in tries: the IP address (for IPv6, its first half), so that one network can't request too many codes or accounts.
- Bot check on the sign-in forms: the forms run Cloudflare Turnstile, which receives signals such as your IP address, TLS fingerprint and browser to tell people from bots. Cloudflare's Turnstile privacy addendum explains what it does with them.
Why we may use it
- Contract (GDPR Art. 6(1)(b)): to run the service for account holders.
- Legitimate interests (Art. 6(1)(f)): to keep the service secure, stop abuse, and keep a suppression list so that people who bounced or complained are not emailed again.
- For recipients of emails, the app that sends the email decides what is sent and to whom. We handle that data for it, on its instructions.
How long we keep it
- Email bodies, attachments and custom header values: deleted when the email is sent, blocked or has failed.
- Email records, delivery events and the suppression list: for as long as the account exists.
- Purchase records: for as long as the account exists, and after that for as long as tax and accounting rules require.
- Sign-in codes and links expire after 10 minutes. A session lasts 30 days, or until you sign out.
- IP addresses of email sign-in tries: deleted after 30 minutes.
- Server logs: at most the latest 50 MB, deleted whenever the app is updated.
- Database backups: on our server, daily copies for 14 days and weekly copies for 8 weeks. Copies taken before an update or a restore, and the copies we keep offline, stay until we delete them.
To have your account and its data deleted, email [email protected].
Where your data is
On our own server in the European Union, run by Contabo. Emails are sent through Amazon SES in Stockholm, Sweden.
Who else handles data
These companies process data for us to run part of the service. We update this list before we add a new one.
| Who | What for | Where |
|---|---|---|
| Contabo | Our server: the app, its database and its backups | EU |
| Amazon Web Services | Amazon SES sends the emails and reports what happened to them; Amazon SNS brings those reports to us | Stockholm, Sweden |
| Cloudflare | Network, DNS, encryption and protection of sendapi.email, and the check on the sign-in forms that you are not a bot (Turnstile) | United States, EU edge |
| Sign in with Google, and the fonts of the panel | United States, EU | |
| Stripe | Payments for credit packs. For some uses, such as fraud prevention, Stripe is responsible for the data itself, under its own privacy policy | United States, EU |
Your rights under the GDPR
If you are in the EU, the EEA or the UK, you have the right to access, correct and erase your personal data, to restrict its processing in some cases, to get it in a machine-readable form, and to object to processing based on legitimate interests.
Email [email protected]. We answer within one month. You can also complain to your data protection authority.
If you received an email sent through SendAPI.email, the app that sent it decides what happens with your data. Ask that app first, or write to us and we will pass your request on.
Transfers outside the EU
Our server and Amazon SES are in the EU. Cloudflare, Google and Stripe may process data in the United States, under their own data processing terms and the EU Standard Contractual Clauses or another Article 46 mechanism.
Cookies
We set only the cookies the panel needs: one keeps you signed in, two short ones (10 minutes) hold a sign-in that is in progress, and one (1 hour) remembers the pack you picked if you click Buy before signing in. No advertising, analytics or tracking cookies. The panel loads its fonts from Google Fonts, so your browser sends its IP address to Google.
Changes
We may update this policy. The date at the top shows the last change.