Sub-processors
These are the companies we rely on to run DearConvert. If you are a customer, they process data on our behalf so that we can process it on yours.
Our sub-processors
| Provider | What it does for us |
|---|---|
| Cloudflare | Serves your published pages at the edge, provisions SSL for custom domains, and provides bot protection where you enable it |
| DigitalOcean | Object storage for your uploaded files and your published page files |
| Resend | Sends transactional email such as password resets, lead notifications and usage warnings |
| PayPal | Processes subscription payments. We never receive or store card numbers |
| Sentry | Error and crash reporting, where enabled |
| DigitalOcean | Runs our application servers and database |
Hosting regions and full entity details are being added to this table. Ask us if you need them for a security review before then.
Tools you connect yourself are not on this list
When you connect Mailchimp, Kit, Google Sheets, Slack, Loops, Zapier or your own webhook, or you switch on Meta's Conversions API, you are instructing us to send data to a service you control under your agreement with that provider. Those are your processors, not ours, which is why they are listed separately here rather than mixed in above.
Changes to this list
We will publish changes to this page before a new sub-processor starts handling customer data, and we will give customers a reasonable period to object on data protection grounds. To be notified of changes, email team@dearconvert.com and ask to be added to the list. A subscription mechanism is coming.
One connection worth naming
When a published page uses a custom font, the page currently loads the font file from Google's servers, so the visitor's browser contacts Google. Google is not processing data on our behalf here, but the connection is real and we would rather list it than hide it. We are moving to serving font files ourselves. Choosing a system font avoids it today.