Legal
Sub-processors
Effective June 21, 2026
These are the vendors we use to deliver Informly. Each is bound by equivalent data-protection terms. We publish changes here and notify paid customers via email at least 30 days before adding a new sub-processor that handles end-customer data.
Current sub-processors
| Vendor | Purpose | Region | Transfer mechanism |
|---|---|---|---|
| Google Cloud Platform | Application hosting (Cloud Run), primary database (Cloud SQL · PostgreSQL), and object storage (Cloud Storage). | United States (us-central1) | EU SCCs · UK IDTA |
| Firebase (Google) | Account authentication and sign-in. | United States · global | EU SCCs · UK IDTA |
| Brevo (Sendinblue SAS) | Transactional and marketing email delivery. | European Union (France) | N/A — EU |
| Stripe | Payment processing and subscription billing. | United States · EU | EU SCCs · UK IDTA |
| Inngest | Background jobs and automation workflow orchestration. | United States | EU SCCs · UK IDTA |
| Cloudflare | Web app hosting, CDN, and WAF / DDoS protection. | Global edge | EU SCCs · UK IDTA |
Notifications
Subscribe to sub-processor change notifications by emailing privacy@informly.co. We'll add you to the list and notify you before any change.
Objections
Paid customers may object to a new sub-processor on reasonable data-protection grounds. See our DPA for the objection process.