Legal

How RelayOne handles WhatsApp data

Last updated November 17, 2026

WhatsApp / Meta Cloud API

Inbound messages, sender number, profile name, delivery status

HTTPS webhook

TLS in transit · HMAC-SHA256 signature verified before processing

RelayOne (Supabase Postgres)

Row-level security per account · access tokens AES-256-GCM at rest

Account members only

Role-scoped access (owner / admin / agent / viewer), enforced by RLS

Data flow from the WhatsApp Business Cloud API to role-scoped account members. Sub-processors are listed below.

1. Summary

This page describes, in plain language, how RelayOne receives, transmits, stores, restricts access to, retains and deletes data obtained through the WhatsApp Business Platform (Cloud API). It is intended for Meta App Review and for anyone who wants to understand how WhatsApp/Meta data flows through the Service.

2. What we receive from the WhatsApp/Meta Cloud API

When a customer connects their WhatsApp Business number, RelayOne receives, via Meta’s Cloud API webhooks, the following data:

  • Inbound messages sent to the business (text, media and interactive replies).
  • The sender’s phone number and WhatsApp profile name.
  • Delivery and read status of outbound messages.
  • Message template review/status updates.

We request only the permissions needed to operate a WhatsApp business inbox and pipelines (e.g. whatsapp_business_messaging and whatsapp_business_management) and use the data solely to provide the Service to the connecting business.

3. What we receive from Instagram and Messenger

A business can also connect its Facebook Pages and the Instagram professional accounts linked to them. Through Meta’s webhooks and Graph API, RelayOne then receives:

  • The Page or Instagram account’s id, name, username and profile picture.
  • Customer messages and attachments, and message reactions, read receipts and delivery status.
  • Comments on the connected account’s posts.
  • The sender’s public profile details (name, username, profile picture) and their Meta-scoped ids (PSID for Messenger, IGSID for Instagram).

We use this data only to show and answer those conversations and comments in the shared inbox, to run the business’s own automations, flows and AI replies, and to send replies on its behalf, including human-agent replies up to 7 days after the customer’s last message. It is transmitted, stored and access-controlled exactly as described for WhatsApp data on this page. Page access tokens are encrypted at rest, never shown in the browser, and destroyed on disconnect. We do not sell this data or use it for advertising.

4. How the data is transmitted

All communication with the Meta Cloud API occurs server-side over HTTPS/TLS. Inbound webhooks are delivered to a single endpoint that verifies Meta’s HMAC-SHA256 signature (using our app secret) before any payload is processed, so unsigned or tampered requests are rejected. Access tokens used to call the Cloud API are never exposed to the browser.

5. How the data is stored

Data is stored in a managed Supabase Postgres database. Every table enforces row-level security (RLS) so that records are strictly scoped to the owning account and cannot be read across tenants. WhatsApp access tokens are encrypted at rest using AES-256-GCM before being written to the database; the encryption key is held only in server-side configuration.

6. Who can access the data

Only members of the account that owns the WhatsApp connection can access its messages and contacts, and only according to their role (owner, admin, agent or viewer). Access is enforced at the database layer by RLS, not merely in the UI. RelayOne personnel do not access customer message content except where strictly necessary for support or security and where permitted by our agreements.

7. Retention and deletion

Data is retained for as long as the account is active and needs it to operate the inbox and pipelines. Account members can export their data and delete contacts, conversations or the entire account from within the product; deletion removes the associated records from the primary database within a commercially reasonable period, subject to limited legal retention requirements.

Export and deletion tools live in the app:

8. Disconnecting and removing Instagram and Messenger data

There are three ways to end an Instagram or Messenger connection. Each one marks the connection as disconnected, destroys its stored Page access token and, once no other connection needs it, removes RelayOne’s app from the Page so Meta stops sending its events:

  • Disconnect: an account admin disconnects the Page or Instagram account in Settings → Channels.
  • Deauthorize: the user removes RelayOne in their Facebook or Instagram settings. Meta calls our deauthorize callback (/api/meta/deauthorize) with a signed request, which we verify with our app secret before acting. We disconnect every Page and Instagram account that user connected.
  • Data deletion: the user submits Meta’s data-deletion request. Meta calls our data-deletion callback (/api/meta/data-deletion), which does the same and returns a confirmation code and a status page where the request can be checked.

These actions remove the Meta integration only. The business’s own contacts, conversations and messages are the business’s data; they stay in its workspace until the business deletes them or its account, as described under retention and deletion above. Requests about that content go to the business, and we assist as its processor.

9. Sub-processors

The third parties that may process this data on our behalf are:

  • Supabase — Managed Postgres database, authentication and file storage — the primary system of record. (United States / EU).
  • Meta Platforms (WhatsApp Business Cloud API, Instagram and Messenger) — Sending and receiving WhatsApp, Instagram and Messenger messages and comments on your behalf via the official Meta platform APIs. (United States / global).
  • Stripe — Subscription billing and payment processing. (United States).
  • Resend — Transactional email (invitations, notifications, password resets). (United States / EU).
  • AI model providers (OpenAI, Anthropic) — Generating reply drafts and running the optional AI assistant, using RelayOne's own provider credentials rather than a key you supply. Only engaged when you enable AI features. (United States).