Consentfolio Trust & legal
Sub-processors
The table below lists everyone Consentfolio uses to help deliver the service, what they're used for, and where relevant, where they process data.
| Sub-processor | Purpose | Location |
|---|---|---|
| DigitalOcean | Hosting and compute for Consentfolio's application and database | London, UK (LON1 data center, providing UK data residency) |
| Cloudflare | DNS, CDN, TLS termination, and DDoS protection at the network edge | Global edge network |
| Stripe | Payment processing: handles billing data only, never website-visitor consent data | See Stripe's own published sub-processor list |
| Resend | Transactional email: account and billing notifications only, never website-visitor data | See Resend's own published sub-processor list |
| Microsoft 365 | Internal business email for the Consentfolio team only: not used for any customer or visitor data | N/A (internal use only) |
A few notes on scope:
- Website-visitor consent data (the receipts described in retention.md) is hosted on DigitalOcean, behind Cloudflare, and does not pass through Stripe, Resend, or Microsoft 365.
- Billing data (what you're charged, payment method details) is handled by Stripe and does not include any website-visitor data.
- Account notification email (things like billing receipts or account alerts sent to you as a Consentfolio customer) goes through Resend; it does not include website-visitor data.
If we add or change a sub-processor, this page is the place to check.
Questions? consentfolio.com · This page is documentation, not legal advice.