In short
- Hosting and databases: DigitalOcean, in Frankfurt. Media storage: Google Cloud, also in Frankfurt.
- Cloudflare protects every relay address and carries its traffic. AI features, push notifications, error reporting, analytics, email and app updates each go through one provider.
- AI features (opt-in): OpenRouter, with Anthropic and Google as model providers, on zero-data-retention endpoints.
- WhatsApp (Meta) is not our sub-processor: your numbers connect as your own linked devices.
- We announce new sub-processors at least 30 days 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.
| Sub-processor | Purpose | Data categories | Location | Transfer safeguard |
|---|---|---|---|---|
| DigitalOcean | 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. |
| Google Cloud | 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. |
| Cloudflare | 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, including outside the EU | EU–US Data Privacy Framework or standard contractual clauses |
| Sentry | Error reporting, from production systems only | Technical error details with internal ids and error codes. Set not to collect personal data; never message content. | Germany (EU) | Data stored in the EU. |
| PostHog | Product analytics for the mobile app, from production only | Internal user and organization ids; no screen, tap or session recording | European Union (PostHog EU cloud) | Data stored in the EU. |
| ZeptoMail (Zoho) | 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 | European Union | Data stored in the EU. |
| OneSignal | Push notifications to browsers and phones | The recipient's user id and generic notification texts with conversation and number ids; never message content, names or phone numbers | United States | EU–US Data Privacy Framework or standard contractual clauses |
| OpenRouter | AI features, only for organizations that turn AI on: routes each AI request to the model provider, through zero-data-retention endpoints only | The conversation excerpts, customer details, knowledge-base passages and voice-note audio an AI request needs; nothing is kept after the answer | United States | EU–US Data Privacy Framework or standard contractual clauses |
| Anthropic, through OpenRouter | The language model (Claude) behind reply drafts, rewrites, translations, summaries, triage and automatic replies | The text of an AI request: conversation excerpts, customer details and knowledge-base passages; nothing is kept after the answer | United States | EU–US Data Privacy Framework or standard contractual clauses |
| Google Cloud Vertex AI, through OpenRouter | Voice-note transcription (Gemini), when an organization has AI and voice-note transcription on | The audio of inbound voice notes; nothing is kept after the transcript is returned | United States or Google's global endpoints | EU–US Data Privacy Framework or standard contractual clauses |
| Expo | Delivery of mobile app updates | Device and app version details, and the IP address, when the app checks for an update | United States | EU–US Data Privacy Framework or standard contractual clauses |
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 30 days before it starts processing personal data, by email to each organization's owner and on this page.
To be told about changes, you don't need to do anything: the owner of every organization receives these emails.
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@relayhelpdesk.com
- Operator
- wrelay (Mohammed Belaidi, auto-entrepreneur), Douar Chlouh, Deroua, 20430 Berrechid, Morocco