Subprocessors
Last updated: October 1, 2026
Openwake uses the companies below to process customer data on its behalf. Each is bound by a written agreement that protects that data. We give account owners at least 30 days' notice by email before adding a subprocessor, and customers may object as described in the Data Processing Addendum at openwake.ai/legal/dpa.
| Subprocessor | Purpose | Customer data involved | Location |
|---|---|---|---|
| Akamai Technologies, Inc. (Linode) | Hosting of the service and its database, and provider-held server backups | All customer data | United States |
| Resend, Inc. | Sending email: sign-in codes, invitations, alerts and service notices | Recipient email address and the content of the message | United States |
| Stripe, Inc. | Payments, subscriptions and tax calculation for paid plans | Billing contact, billing address and payment details. Openwake never receives the full card number | United States |
| Cloudflare, Inc. | The Turnstile check on the sign-in form, when it is switched on, which tells a browser from a script | IP address and browser characteristics of the person signing in; never the email address | United States, served from a global network |
Services you choose to connect
If you configure an alert to a Slack webhook or sign in through your own identity provider, data goes to that service under your agreement with it. These are not Openwake's subprocessors.
What we do not use
We use no advertising, analytics or session recording services on customer data, and under our current configuration no AI provider receives customer data. Cloudflare, Inc. is also our DNS provider, which answers name lookups only; traffic to Openwake does not pass through it.
Services that hold no customer data
GitHub, Inc. holds the public anchors of Openwake's evidence ledger: head hashes and signatures only, never customer data.