Legal
Sub-processors
Effective May 1, 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 |
|---|---|---|---|
| Amazon Web Services | Infrastructure (compute, storage, networking) | US · EU · APAC | EU SCCs |
| Cloudflare | CDN, WAF, DDoS protection | Global | EU SCCs |
| PostgreSQL · RDS | Primary database (via AWS) | Customer-selected | EU SCCs |
| Twilio | SMS delivery, voice (where used) | US · global | EU SCCs |
| Postmark | Transactional email delivery | US | EU SCCs |
| Stripe | Payment processing, billing | US · EU | EU SCCs |
| Datadog | Production observability, metrics, logs (no PII) | US · EU | EU SCCs |
| Sentry | Application error monitoring | US · EU | EU SCCs |
| Linear | Internal issue tracking (no end-customer data) | US | N/A |
| Vercel | Hosting for the public marketing site only | Global edge | EU SCCs |
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.