| Provider | Purpose | Data boundary |
|---|---|---|
| Cloudflare | Relay compute, encrypted storage, delivery state, security, DNS, and public website | Encrypted payloads, public key material, opaque routing and usage state, and request metadata |
| Vercel | Console and documentation hosting | Console requests, authentication session data, and project administration |
| WorkOS | Console authentication and organization identity | Account, organization, and authentication data |
| Stripe | Payments, subscriptions, tax, invoices, and billing portal | Billing identity, payment status, subscription data, and Relay aggregate usage mapped inside Console |
| Expo, Apple, Google, and browser push services | Data-only device wake delivery | Provider token, project routing, and opaque wake payload; no message plaintext |
| Better Stack | Availability monitoring and public status | Probe results, endpoint status, and sanitized operational metadata |
| Google Workspace | Business email and support communications | Contact details and communication content |
OpenE2EE does not give these providers message plaintext, device private keys, ratchet state, or attachment keys. Some providers can process network metadata that their role inherently requires. The Privacy Notice describes the complete boundary.
We will update this list before adding a subprocessor that handles a new material category of customer data. Send questions to privacy@open-e2ee.dev.