Privacy policy
How this gateway handles personal data — what it stores, what it sends to Meta, and how to have it deleted.
Last updated 2026-09-09.
OPERATOR in src/routes/legal.js before
relying on this page or submitting it to Meta.
This service is operated by [legal entity not set]. It is a messaging gateway: businesses connect their own WhatsApp Business accounts to it and use it to send WhatsApp messages to their own customers.
Your data and your customers'
There are two different relationships here, and they are worth keeping apart.
| Whose data | Our role |
|---|---|
| The business using this gateway — its account, logins and API keys | We decide how this is handled, and this policy governs it. |
| The people that business sends messages to — recipients | We process it only to carry out sends the business asked for. What that business may send, and on what basis, is its responsibility, not ours. |
If you received a message sent through this gateway and want it explained, corrected or stopped, the business that sent it is the right place to ask. Contact us and we will point you to them.
What we process
Account
Your business name, a contact email address, and a login. Passwords are stored only as a one-way hash — we cannot read yours. We record when a login was last used.
WhatsApp connection
When you connect a WhatsApp number, we store its phone number ID, the WhatsApp Business Account ID, the business portfolio ID, the display number, and an access token that lets us send on your behalf. The token is encrypted at rest and is never displayed back to anyone, including us — it can be replaced, but not read out of the system.
API keys
Keys are stored as a hash for authentication. A second, encrypted copy is kept so the operator console can show a key to you again after it was issued; that copy is masked once a key is revoked.
Messages
For each message you send: the recipient's phone number, the message text or the name of the approved template used, which of your numbers sent it, any reference you attached, the delivery state, timestamps, and the error reason and WhatsApp error code if it failed. This is what makes your message log and delivery reporting work.
Technical
Server logs of requests made to the gateway, kept for operating and securing the service.
We do not use advertising trackers, and we do not sell personal data or share it with anyone for their own marketing.
Sharing with Meta
Delivering a WhatsApp message means sending it to Meta. Every message you send through this gateway — the recipient's number and the content, or the template and its parameters — is transmitted to Meta Platforms through the WhatsApp Cloud API, using the credentials for the number you connected. Meta then delivers it and reports back whether it was sent, delivered, read, or failed.
Meta's own handling of that data is governed by Meta's terms for business messaging and the WhatsApp privacy policy, not by this one.
When you connect a number using Connect with Meta, Meta gives us an authorisation code which we exchange for an access token scoped to your account alone, together with your WhatsApp Business Account, business portfolio and phone number IDs. We use these only to send the messages you ask us to send and to receive delivery reports for them. We do not use them to read your other Meta assets, and we do not use them for anything on our own behalf.
Aside from Meta, we share personal data only with the infrastructure providers that host this service, and where the law requires it.
Incoming messages
If someone replies to one of your WhatsApp numbers, Meta delivers that reply to this gateway. This is a send-only service: incoming messages are counted in the server log and discarded. They are not stored, not shown in your message log, and not readable through the API.
How long we keep it
Message records are kept for as long as your account is open, so your log and reporting stay complete. They are not deleted on a timer. If you want a shorter retention period, ask — see Deleting your data.
Account records are kept while your account is open. When an account is closed we delete its messages, its connected numbers and their access tokens, and its API keys.
How it is protected
- Access tokens for your WhatsApp numbers are encrypted at rest.
- Passwords and API keys are stored as one-way hashes for authentication.
- Traffic to and from the gateway is served over TLS.
- Every account's data is scoped to that account throughout the system. A message can only be sent from a number belonging to the account that sent it, and one account cannot read another's messages, numbers or keys.
- Delivery reports from Meta are rejected unless they carry a valid signature.
No system is perfectly secure. Your API keys are bearer credentials — anyone holding one can send messages as you, so keep them server-side and revoke any key you think has leaked.
Deleting your data
You can remove your data yourself or ask us to do it.
Yourself, from the portal
- Disconnect a WhatsApp number. Sign in, open Senders, and revoke the number. Its access token stops being used immediately and nothing further is sent from it.
- Revoke an API key. Ask your account manager to revoke it; the key stops working at once.
By asking us
Email [contact address not set] from the address on your account and say what you want removed — your whole account, or just your message history. We delete the account, its message records, its connected numbers and stored access tokens, and its API keys, and confirm when it is done. We aim to complete this within 30 days.
Removing your data here does not remove it from Meta. Messages already delivered exist on WhatsApp, on the recipient's phone, and in your WhatsApp Business Account — Meta's own tools are where you manage that.
Depending on where you live you may also have the right to a copy of your data, to have it corrected, or to object to how it is handled. The same address reaches us for any of those. Your message log can be exported as CSV from the portal at any time.
Changes
If this policy changes in a way that affects you, we will tell you at the contact address on your account before the change takes effect. The date at the top always reflects the current version.
Contact
[contact address not set] .