A bridge, not an inbox

WasapFlow Bridge only connects your software to Meta's official WhatsApp Cloud API. Messages pass through us in real time. Your conversations, inbox and customer data live in your own system.

🖥️

Your system

Your inbox, contacts, orders and chat history. You control it.

🌉

WasapFlow Bridge

Passes messages through, signs webhooks, holds tokens encrypted. No inbox.

Meta WhatsApp

Delivers to your customers' phones on the official Cloud API.

We do not run an inbox, we do not read your customers' messages, and we do not build contact databases or sell data. When a customer replies, Meta sends it to us and we forward it straight to your webhook, and that is the end of our part.

Exactly what we keep, and for how long

"We store nothing" is not quite true for any API provider, so here is the full list.

DataWhyRetention
Message contentPassed through in transit only, between Meta and your endpoint.Not stored
Undelivered webhook eventsIf your endpoint is down, events wait in a buffer so you can replay them, so nothing is lost.Auto-deleted after 30 days
Delivery metadataMessage IDs, timestamps, delivery status and Meta pricing category, used for billing and delivery tracking. No message text.Account lifetime
Access tokensMeta's token for each connected WhatsApp account, used to send on its behalf.Encrypted (AES-256)
Broadcast jobs (optional feature)Only if you use our broadcast endpoint: the recipient list and template variables, so the job can run in batches.Until you ask us to delete
Your partner accountYour name, email, company, billing and support tickets. This is about you, not your customers.Deleted within 30 days of closure

Sub-processors

ProviderPurposeLocation
Meta PlatformsWhatsApp Business Platform: message deliveryPer Meta's terms
DigitalOceanServer hosting and databaseSingapore
CloudflareNetwork security, DDoS protection and TLSGlobal edge
StripePartner billing (your card details, never your customers' data)USA / global
BrevoAccount and billing emails to youEU

Security

One DPA for every country

Our Data Processing Agreement uses the processor terms that these laws have in common: acting only on your instructions, confidentiality, security, sub-processor notice, breach notice, help with data subject requests, and deletion at the end. It names the laws below. Where your law needs an extra transfer mechanism (for example standard contractual clauses), we add it on request.

🇲🇾 MalaysiaPersonal Data Protection Act 2010 (as amended)
🇪🇺 EU / EEA, incl. 🇪🇸 SpainGDPR
🇬🇧 United KingdomUK GDPR & Data Protection Act 2018
🇹🇷 TürkiyeKVKK, Law No. 6698
🇸🇦 Saudi ArabiaPersonal Data Protection Law (PDPL)
🇦🇪 United Arab EmiratesPDPL, Federal Decree-Law No. 45 of 2021
🇶🇦 QatarLaw No. 13 of 2016 (PDPPL)
🇧🇷 BrazilLGPD, Law 13.709
🇲🇽 MexicoLFPDPPP
🇨🇴 ColombiaLaw 1581 of 2012
🇨🇱 ChileLaw 19.628
🇵🇪 PeruLaw 29733
🇸🇬 SingaporePDPA 2012
🇮🇩 IndonesiaPDP Law No. 27 of 2022
🇮🇳 IndiaDPDP Act 2023

Data Processing Agreement (PDF)

Download it, fill in your company details and sign. Then email it to [email protected] and we will countersign and send it back. Version 1.0 · KOBARAN TEGUH SDN. BHD. (202601001919 / 1664016-P)
Download DPA Meta Tech Provider proof

This page summarises our practices; the signed DPA and our Privacy Policy are the binding documents.