Flowmails for privacy-sensitive products: email data that never leaves your D1
Products that handle health, finance, legal, or any other regulated category usually have a hard requirement: email data must live in infrastructure the team controls. Most hosted ESPs meet that requirement with contractual language; Flowmails meets it with an architecture where the inbox, outbox, and routing rules are stored in the Cloudflare D1 of the team's own account. There is no Flowmails-side database containing the data, and the Worker that processes every message runs in the team's account. Compliance reviews can verify the architecture by reading the table layout, not by reading a vendor's privacy addendum.
What hurts today
The privacy-sensitive products pain points
Hosted ESPs are a data-processor relationship — they hold your mail
Sub-processor disclosures multiply when an ESP uses sub-processors
Data residency audits get harder the more third parties touch the data
How Flowmails answers
What you get instead
Inbox / outbox / routing rules / API keys all live in your D1
Worker that processes every message runs in your Cloudflare account
Flowmails-side infrastructure only brokers the connection and renders the dashboard — it has no message body access
FAQ
Common questions from privacy-sensitive products
Other personas