Legal
Privacy Policy
Last updated: 2 November 2026
walpio (“walpio”, “we”, “us”) is a WhatsApp Business gateway operated from India and provided to business customers worldwide. This policy explains what data we handle, why, who else processes it, how long we keep it and the choices you have. It describes what the service actually does today.
1. Who this covers
Three situations are covered: (a) visitors to this website, (b) people who contact us through the get-started form or by email, and (c) client workspaces — businesses that use the walpio service. For the personal data of a client's own customers (the people a client messages on WhatsApp), the client is the data controller and walpio processes that data on the client's instructions.
2. What we collect
- Website visitors: this site uses Cloudflare Web Analytics to count visits. It uses no cookies or other browser storage. It reports the page you viewed, the site that referred you, your browser, operating system, device type and country, and how fast the page loaded. We see only totals, not individual visitors, and it does not track you across other websites. The site sets no advertising cookies. Your light/dark theme choice is kept in your own browser. Cloudflare, which hosts the site, processes technical request data such as your IP address to deliver pages and protect the site from attacks.
- The get-started form: your name, work email, company, WhatsApp or phone number, the plan you pick, your expected monthly messages, your message, and which page you came from. We store the request in our database and email a copy to our team through Cloudflare Email Routing. Our team may add notes to the request as they follow it up (who wrote each note, and when). Your IP address is used only to count submissions per address, so repeated submissions can be stopped; that counter covers 30 minutes and is deleted in our nightly clean-up. When you agree to our Terms on the form, we keep which version you agreed to and when, with your request — not your IP address or browser.
- Email: whatever you choose to send us, such as your name, address, company and message.
- Client workspaces:
- team members' names, email addresses and passwords (passwords are stored only as hashes); sign-in attempts and requests to reset a password are counted per IP address and per email address (the address kept only as a hash) to stop password guessing and abuse — each counter for its window of 15 minutes to an hour, then deleted in our nightly clean-up; and the browsers and IP addresses each login has signed in from, with the email address only as a hash, so that someone guessing the password elsewhere cannot lock that person out;
- for someone a workspace admin or our team invites by email, the invitation's email address, name and role — kept until the person accepts it or it is cancelled, and otherwise deleted in our nightly clean-up 30 days after its link expires (the link works once, for 72 hours, and we keep it only as a hash). The activity log (below) records each invitation sent, sent again, cancelled or accepted, with the email address, like any other change;
- when a workspace admin accepts our Terms at sign-in: the version, the time, and theIP address and browser it was accepted from — the record of the agreement, kept while the workspace exists;
- an activity log of changes made in the workspace: who made each change, when, and what it was (which can name a customer's number, for example when the client marks a contact as opted out, or when a customer opts out or back in by sending a word such as STOP or START). When one of the client's admins blocks or unblocks a customer on one of its WhatsApp numbers, the entry records that customer's phone number; the list of blocked customers itself is held by WhatsApp, and we read it from Meta each time an admin opens it. It also records each sign-in to the workspace's dashboard and each failed one, and each read-only view a walpio operator opens (section 3). For a change made by a team member in the dashboard or by a walpio operator on the client's behalf, for a sign-in and for a view, it also records the IP address it came from — and, when we e-mail a link to reset a password that someone asked for on the sign-in page, the address it was asked from. We keep the log for about 13 months for security and to protect the account: if an account is misused, it shows who changed what, and from where. The workspace's admins can see all of it, IP addresses included — every team member's sign-ins and our operators' views among them — on the dashboard's Activity page; its developers see the same page without the email address an invitation was sent to — until the person accepts it and joins the team, whose members everyone on it can see — and without the phone number of a customer blocked or unblocked (for a block, how many); the workspace's agents and viewers do not see that page. walpio's operators can read it in our console too;
- the connected WhatsApp Business account and phone-number identifiers, and the Meta access credentials the client provides, encrypted with AES-256-GCM;
- API keys, stored only as hashes;
- the client's contacts for walpio — a technical and a business contact (name, email address and phone number) — its Meta Business ID, the planned go-live date, which of our team looks after the account, and our team's own notes about the account (who wrote each note, and when). The client's dashboard does not show these, nor the download of the workspace's data it offers; they are part of an export our team makes on request;
- the client's WhatsApp contacts: WhatsApp number or Meta's business-scoped user ID, profile name or username, notes the client adds, opt-out status, the customer's preferred language, and a preview (up to 160 characters) of the latest message in each conversation. The preferred language is a language code such as “ar” or “en”, used only to send the client's templates in that language: the client sets it, or, until the client does, we read it from the alphabet of the customer's latest text message (Arabic or Latin letters) — we draw no other conclusion from what a customer writes. For a customer who wrote from a Click-to-WhatsApp ad or a Facebook Page button, we also keep which ad it was (its ID, link and headline, as WhatsApp gives them) and when, and until when WhatsApp's free period for the conversation runs;
- message metadata — direction, recipient, timestamps, delivery status and errors, the template used, the pricing category Meta reports and the client's own reference — and a preview of up to 160 characters for the client's message log. For a message a customer sends, the metadata includes the identifiers WhatsApp gives with it: the ID and file type of a photo, video, voice message, document or sticker (not the file itself), the ID of the button or list option the customer chose, the ID of the message they replied or reacted to, and the ID of the ad that brought them to the chat. For a broadcast or a batch send, the record also keeps the values the client fills its template with — the same for everyone, or each recipient's own (a name, an invoice number, a link) — so each message can be sent, and sent again, with them.
- for a one-time verification code a client sends through us: the customer's WhatsApp number, when the code was sent and whether it was checked. We never store the code itself — only a keyed one-way hash of it, until the code is checked or soon after it expires (section 7), and the message log shows it masked.
We do not keep an archive of conversations, and the WhatsApp Cloud API gives the client no conversation history to read back from Meta. Unless the client chooses to keep its customers' full texts (below), our message log keeps, for each message, the metadata and the 160-character preview above, and that preview is all the dashboard shows; the full text of a message a customer sends then reaches the client only through the client's own callback URL, if the client has set one. The same holds for everything else a customer sends — a location, shared contact cards, the answers to a form: the callback carries it and we keep none of it beyond the preview (for a location, its name or address; for a photo, video or document, its caption or file name). We never store a photo, video, voice message or document a customer sends: it stays with WhatsApp, which keeps it for 7 days, and when the client's systems or its team in the dashboard ask for it, we fetch it from Meta with the client's own credentials and pass it on without keeping a copy. A file the client uploads to send is passed to Meta the same way. We hold full message content in these places, each for a limited time:
- a message waiting to be retried keeps its full content until Meta accepts it or the send finally fails;
- each callback we send the client is kept in our callback delivery log so it can be retried. For an incoming message the callback includes its full text, the customer's number or WhatsApp user ID, their profile name, and everything else WhatsApp sent with the message (a location, contact cards, a form's answers, a photo's caption and ID); the log keeps that content only until the callback is delivered or given up (about 8 hours of retries, never more than 72 hours) and then keeps the delivery record alone — the event, the IDs, the customer's number or user ID, the times and the result — for 30 days. The nightly backup never holds the text;
- only if the client turns it on (it is off unless the client does): the full text of what each customer writes — a text message, or the caption of a photo, video or document — for 7, 30 or 90 days from the message, as the client chooses, so the client's team can read it in the dashboard and the client's systems through our API. We keep it only for messages that arrive after the client turns it on. When the period ends we delete it in our nightly clean-up, and the message keeps its 160-character preview. Turning it off deletes what we keep at once; choosing a shorter period deletes at once what is older than it and keeps the rest only that long. If we cannot finish that at once — our job queue refused the rest, or its job was lost — what is left is deleted in our next nightly clean-up. In a link that starts with http:// or https://, we leave out of this copy what looks like its secret part: what follows /pay/, /reset/ and similar, the value of token=, code= and similar, and any other part that looks like a long random code; a link written without http:// or https:// is kept as the customer wrote it. It is never in our nightly backups; it is part of an export of the workspace's data and is deleted with the workspace;
- an incoming message we could not process even after repeated attempts (for example while our database is unavailable) keeps its content for up to 30 days, so our operator can run it again; then only a record of what failed is kept (section 7). It is never in the nightly backup.
When walpio refuses a send because no approved template fits its wording, the activity log records the refusal with the first 160 characters of the message and the customer's number shortened to its last four digits, so the client can see what to fix; every member of the client's team sees these refusals in the dashboard (Messages → Refused).
- Billing: we do not take card payments online and hold no card details. Plans are agreed with each client and invoiced directly; we keep the billing contact and invoice records.
3. How we use data
- To answer your request and, if you become a client, to set up and provide the service: sending WhatsApp messages through Meta's official Cloud API, tracking delivery, applying the 24-hour customer service window, and showing clients their own message logs.
- To keep the service secure: authentication, abuse prevention, rate limiting, troubleshooting and records of administrative actions.
- To help a client: a walpio operator may open a read-only view of the client's dashboard, for up to 30 minutes at a time, to answer a question or look into a problem. They see what the client's admins see and cannot change anything, and each view is recorded in the client's activity log with the operator's name, the reason they gave and when it ended.
- To manage plan agreements and invoices.
- We do not sell personal data, and we do not use client message data for advertising or for training anything.
4. Service providers (sub-processors)
| Provider | What it does for walpio |
|---|---|
| Cloudflare | Hosts this website and the walpio service, runs its database and stores its backups, and routes form notifications by email. It also counts visits to this website (Cloudflare Web Analytics). |
| Meta Platforms | Delivers WhatsApp messages through the WhatsApp Business Cloud API, under the client's own Meta account and Meta's own terms. |
Emails you send us, and the form notifications, arrive in the walpio team's email inbox. We disclose data to authorities only where the law requires it. This list is kept current on this page; the date at the top shows when it last changed.
5. Where data lives
The service runs on Cloudflare's global network, so data may be processed outside your country. Meta processes messages under its own terms. We deliberately minimise what we store — metadata, short previews and encrypted credentials rather than full conversations. The places where we hold full message text, each for a limited time and one of them only if the client turns it on, are described in section 2.
6. Security
Meta credentials are encrypted at rest with AES-256-GCM. Webhooks from Meta are verified by cryptographic signature on every event, and the callbacks we send clients are signed. Passwords and API keys are stored only as hashes, and API keys can be revoked at any time. Access to production systems is restricted to the people who operate the service.
7. How long we keep data
- Message records (metadata, including the identifiers described in section 2, the 160-character preview, and a broadcast's template values): up to about 13 months.
- Callbacks sent to a client: the delivery record 30 days; for an incoming message, its content — the full text, the sender's profile name, and a location, contact cards or a form's answers — only until the callback is delivered or given up (72 hours at most).
- Work that failed again and again (for example while our database is unavailable): when we cannot process an incoming message or another task after repeated attempts, we keep that task — for an incoming message, its content — for up to 30 days so our operator can run it again, then delete the content and keep a record of what failed (its kind, counts and IDs) for 30 days more. Never in the nightly backup.
- The full text of what customers write, only if the client turns this on: 7, 30 or 90 days from each message, as the client chooses, then deleted in the nightly clean-up; deleted at once when the client turns it off, and what is older than a shorter period the client chooses deleted at once too — what we cannot finish at once, in our next nightly clean-up. Never in the nightly backup.
- Verification codes: the code's hash until the check is over or, for a code nobody checked, usually within about 15 minutes of its expiry, and at the latest with the record (a code lives 15 minutes at most); the record that a code was sent and checked, 7 days. Never in the nightly backup.
- Photos, videos, voice messages and documents customers send, and files a client uploads to send: never stored by us; WhatsApp keeps a customer's file for 7 days and an upload for 30.
- Counters of form submissions (by IP address), and of sign-in attempts and requests to reset a password (by IP address and by email address, the address as a hash): each for its window of 15 minutes to an hour, then deleted in our nightly clean-up.
- The browsers and IP addresses a login has signed in from: 90 days after that login last signed in from them, and deleted with the workspace.
- Acceptances of our Terms: a workspace admin's (with its IP address and browser) while the workspace exists; a get-started request's (the version and the time only) deleted with the request.
- The activity log (records of administrative actions, sign-ins and our operators' read-only views, with the IP address of each change made in the dashboard or by a walpio operator, of each sign-in and of each view, and refused sends with their first 160 characters): up to about 13 months. Deleting a workspace deletes its activity log too, except one record that the deletion was made (when, and by which of our accounts), which expires on the same schedule.
- Backups: a copy of the database is taken nightly and kept for 35 days, so deleted data can remain in a backup for up to 35 days. Separately, our database provider (Cloudflare) keeps the database's own history, from which it can be restored as it was at any minute of up to the last 30 days; so for up to 30 days, what we have deleted or cleared — a verification code's hash or a failed task's content, for example — can still be recovered from it.
- Get-started requests and email: as long as needed to handle the request and any resulting business relationship, or until you ask us to delete them.
- Workspace account data (team, contacts with the preview of each contact's latest message, templates, settings): while the workspace is active. A contact's name, username, notes, preferred language, the ad they came from and message preview are cleared once the contact has exchanged no message for about 13 months; whether they opted out is kept. When a client closes its workspace, we delete this data on request.
- The client's contacts for walpio and our team's notes about the account: while the workspace exists; deleted with it. Our notes on a get-started request are deleted with the request.
- Invoices and billing records: as long as the law requires.
8. Your rights, export and deletion
You can ask us to access, correct, export or delete personal data we hold about you, or object to its use, by emailing [email protected]. Clients can ask for an export of their workspace data, or its deletion, the same way. These requests are handled by our team rather than automatically; we respond within 30 days. A workspace admin can also download the workspace's records at any time from the dashboard (Settings, Account & plan), after confirming their password: one file with the workspace and its settings, team members, API keys (each key's name, first characters, settings and dates — never the key itself), numbers, contacts, messages and their delivery history, templates, text rules, broadcasts, usage, callbacks, one-time code records, invitations, the full texts of what customers wrote that we keep for the client, and activity log, without passwords, invitation links or Meta credentials. The activity log in it is all of it, with the IP addresses section 2 describes: each sign-in and each failed one is in the file with the IP address it came from. It leaves out the sandbox's test data, the team's sign-in sessions, the separate records of the browsers and addresses each login has signed in from and of Terms acceptances (an acceptance is also in the activity log, without the browser), the tasks we could not complete, and our team's own notes and contacts for the account, which come with an export on request. If you are a customer of one of our clients, we will refer your request to that client, since they control that data.
9. Children
The service is for businesses and is not directed at children under 18.
10. Changes
If this policy changes, we will update this page and the date above. If a change materially affects how we handle client data, we will also tell clients by email.
11. Contact
Questions about privacy: [email protected].