Release note (legal finalization required)
This page includes placeholders for legal entity details, mailing address, and/or governing law venue that must be finalized before public release.
Legal & Trust
Subprocessors
Effective date: February 23, 2026 • Last updated: February 23, 2026
This page lists major third-party service providers that may process data on behalf of DoSurely to support the platform.
How to Use This List
This list identifies major subprocessors and infrastructure providers that may be used to operate DoSurely. Actual provider usage can vary by feature set, deployment environment, region, and customer configuration.
We may update this list from time to time as our services evolve. Material changes may also be shared through customer communications where required by contract.
Current Subprocessors
| Subprocessor | Purpose | Data Categories | Region | Policy | Notes |
|---|---|---|---|---|---|
| Stripe | Payments, subscriptions, and billing operations | Billing identifiers, transaction metadata, customer contact and invoice data | Varies by customer/payment region [TO CONFIRM] | Policy | Payment card details are processed by Stripe, not stored in full by DoSurely. |
| Google / Firebase | Authentication, messaging, and push notification services | Account identifiers, device tokens, messaging metadata | Varies by service and configuration [TO CONFIRM] | Policy | Specific Firebase features may vary by deployment. |
| Cloudflare | Storage/CDN/network services (including object storage where configured) | Stored files/attachments, request metadata, network traffic metadata | Varies by configuration and service region [TO CONFIRM] | Policy | Usage may vary by environment and customer deployment. |
| Hosting / Cloud Provider | Application hosting and infrastructure runtime | Application data, logs, and infrastructure telemetry | [TO CONFIRM] | — | Provider may vary by deployment environment. |
| Email Provider | Transactional email delivery | Email addresses, message metadata, delivery events | [TO CONFIRM] | — | Provider may vary by deployment and customer settings. |
| SMS / Messaging Provider (e.g., Twilio) | SMS notifications and messaging integrations when enabled | Phone numbers, message metadata, delivery events | [TO CONFIRM] | Policy | Used only when messaging features are configured and enabled. |