toSend Subprocessors

Reliable email for websites, apps, and the agencies that run them.

SaaS / Email delivery tosend.com
Subprocessors
5
Locations
4
Categories
2
Last scanned

5 subprocessors

Name Category Purpose Location Data processed
Amazon Web Services, Inc. ↗ DPA Cloud Infrastructure Email delivery via Amazon SES. United States Germany (European Union) for teams on the EU (Frankfurt) sending region Email envelopes (from, to, subject), message bodies while being sent, sender reputation signals, bounce and complaint feedback.
Cloudflare, Inc. ↗ DPA Cloud Infrastructure Email data plane (Workers, D1 database, R2 object storage, KV cache, Queues, Analytics Engine) and hosting for the public marketing website (tosend.com) on Cloudflare Pages. European Union API request metadata, email logs, message bodies (encrypted at rest, deleted after 14 days), suppression entries, webhook delivery logs, IP addresses, user-agent strings, public website access logs.
Fly.io, Inc. ↗ DPA Cloud Infrastructure Routing for the SMTP relay (smtp.tosend.com). Used only when you send over the SMTP protocol; API and SDK sends never touch it. Germany (European Union) Messages submitted over SMTP, in transit only (envelope, headers, body and attachments, plus the API key used as the SMTP password), and connecting IP addresses.
Hetzner Online GmbH ↗ DPA Cloud Infrastructure Hosting for the customer dashboard (dash.tosend.com) — the control-plane UI where customers manage their account, domains, API keys, webhooks, and billing. Germany (European Union) Account identifiers (email, hashed password, session tokens), tenant and organization settings, domain verification records, API key metadata, webhook configuration, billing view data, IP addresses, user-agent strings, server logs, and any data submitted through dashboard forms.
Stripe, Inc. ↗ DPA Payment Processing Payment processing, subscription billing, and credit purchases. United States Billing name and address, email address, last four of card and brand (full card numbers are handled by Stripe and never reach our systems), invoice and transaction history.

No changes recorded yet. Changes will appear here after the next scan detects updates.