In short
- Hosting and databases: DigitalOcean, in Frankfurt. Media storage: Google Cloud, also in Frankfurt.
- Cloudflare protects every relay address and carries its traffic. Payments, error reporting, analytics and email each go through one provider.
- The proxy provider only handles numbers that use the optional proxy add-on.
- WhatsApp (Meta) is not our sub-processor: your numbers connect as your own linked devices.
- We announce new sub-processors [SUB-PROCESSOR NOTICE PERIOD] before they start.
This summary helps you find your way; the full text below is what applies.
1Our sub-processors
relay uses these companies to run the service. Each one processes personal data only to provide its part of the service, under a written agreement with data protection terms [CONFIRM CONTRACTS].
| Sub-processor | Purpose | Data categories | Location | Transfer safeguard |
|---|---|---|---|---|
| DigitalOcean [CONTRACTING ENTITY] | Cloud hosting: application servers, managed PostgreSQL and Valkey databases, and the WhatsApp gateway's volumes | Everything relay stores outside the media bucket: account details, WhatsApp messages, contacts and groups, API and webhook settings, WhatsApp session keys | Frankfurt, Germany (FRA1) | Data stored in the EU. [CONFIRM: DPA and SCCs for any access from outside the EU] |
| Google Cloud [CONTRACTING ENTITY] | Private media storage: the bucket that holds media files, profile pictures, files uploaded for sending and data exports | Photos, videos, documents and voice notes from your numbers' chats, profile pictures of contacts and groups, files you upload to send, and the data exports you request, which include message text | Frankfurt, Germany (europe-west3) | Data stored in the EU. [CONFIRM: DPA and SCCs for any access from outside the EU] |
| Cloudflare [CONTRACTING ENTITY] | DNS, proxy and content delivery, TLS termination and DDoS protection for every relay address: this website, the app and the API | IP addresses and the contents of requests and responses in transit, including message data passing between your browser or API client and relay | Global network [CONFIRM REGION] | [TRANSFER MECHANISM] |
| Stripe [CONTRACTING ENTITY] | Subscription billing and payments | Account owner's name and email, billing details, invoices. Card details are entered on Stripe's own pages and never reach relay. | [STRIPE ENTITY AND REGION] | [TRANSFER MECHANISM] |
| Sentry [CONTRACTING ENTITY] | Error reporting, from production systems only | Technical error details with internal ids and error codes. Set not to collect personal data; never message content. | [SENTRY REGION] | [TRANSFER MECHANISM] |
| PostHog [CONTRACTING ENTITY] | Product analytics, from production systems only | A few account events (sign-up, organization created, number connected or disconnected, subscription changes) with internal ids | European Union (PostHog EU cloud) [CONFIRM REGION] | Data stored in the EU. [CONFIRM WITH PROVIDER] |
| [EMAIL PROVIDER] | Transactional email: address verification, password resets, number alerts and deletion confirmations | Account owner's email address and name, and the content of those emails, which never include phone numbers or contacts | [EMAIL PROVIDER REGION] | [TRANSFER MECHANISM] |
| [PROXY PROVIDER] | Optional proxy add-on: routes a number's WhatsApp connection through an address in the number's country. Only for organizations that turn the add-on on. | The encrypted WhatsApp traffic of numbers using the add-on, and connection metadata such as IP addresses and traffic volume [CONFIRM WITH PROVIDER] | [PROXY PROVIDER REGION], matching each number's country | [TRANSFER MECHANISM] |
Swipe sideways to see every column.
Our infrastructure also relies on services that receive no personal data from you or your contacts, such as our code and container image hosting and the authority that issues our HTTPS certificates. They are not listed here.
2WhatsApp and Meta
WhatsApp (Meta) is not a sub-processor of relay. Your numbers remain your own WhatsApp accounts: relay connects to them as a linked device, the way WhatsApp Web does, at your request.
The messages you exchange travel through WhatsApp under your own relationship with WhatsApp, governed by its terms and privacy policy, not under a contract between relay and Meta.
relay is not affiliated with WhatsApp or Meta.
3Changes to this list
We will tell you about a new sub-processor at least [SUB-PROCESSOR NOTICE PERIOD] before it starts processing personal data, by [NOTICE CHANNEL].
To be told about changes: [SUBSCRIBE MECHANISM].
If you object to a new sub-processor on reasonable data protection grounds, you can raise it as set out in the Data Processing Agreement.
This page is versioned: the date at the top shows when it last changed.
4Contact
- Privacy questions
- support@wrelay.site
- Company
- [COMPANY LEGAL NAME], [REGISTERED ADDRESS]