Companies / toSend / Subprocessors
toSend provides email sending through WordPress plugins, SMTP, or an API, with email data stored in the EU and sent from Frankfurt. It serves website owners, developers, and agencies managing sites for clients.
Summarized from its homepage on 15 Nov 2026.
Subprocessors of toSend
toSend declares 5 subprocessors.
From the company's own list.Read the source
| Subprocessor | Purpose |
|---|---|
| Email delivery via Amazon SES. | |
| 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. | |
| Routing for the SMTP relay (smtp.tosend.com). Used only when you send over the SMTP protocol; API and SDK sends never touch it. It passes each message straight to our Cloudflare data plane and stores nothing. | |
| Hosting for the customer dashboard (dash.tosend.com) — the control-plane UI where customers manage their account, domains, API keys, webhooks, and billing. | |
| Payment processing, subscription billing, and credit purchases. |
Vendor's own statement, retrieved from the source URL on the date shown. StrataDB does not verify the underlying claim. Data sources.
See toSend's full stack
Every vendor with its source and date, and an alert when toSend adds or drops one. The same lookup works for any company.
- Every company and vendor, with its public source
- 100 API calls a month, plus MCP and the Chrome extension
- Work email only. No card, no sales call