Privacy Policy
In short
We don't keep your customers' conversations. The text and files of WhatsApp messages are not stored permanently: they pass through our system while being delivered and are then deleted. The only exception is the Coexistence history, if you choose to receive it: we keep it encrypted until we deliver it to you, never more than 7 days.
We do keep, for a limited time, metadata about each message. Of the identifier Meta gives each message —which contains the contact's number— we keep only an irreversible fingerprint since 28/09/2026; older records hold it in full and are deleted automatically after 30 days. We also keep your account, number and payment data. Everything has a daily backup that lasts up to 30 more days.
Below is the full list, item by item, with how long we keep each one, who else receives data and in which country, and how to ask us to delete your account (we do it within 15 days).
Technical detail of data and subprocessors → Where the data is, how long we keep it and which providers receive it, on one page.
Who we are
WAIA Connect is a product of ZZIA, the software brand of Consulta Automática (owner: Mariano Porcile, Córdoba, Argentina), which connects WhatsApp Business numbers to its customers' systems using Meta's official API (Cloud API and Coexistence). We operate under the app IAutoresponder (Meta App ID 1488010632180493) and are a Meta-verified technology provider.
Our servers are in the United States: they are Google Cloud servers in the us-central1 region (Iowa). The database, backups, queues and logs live there.
Two different roles. For your account data (you, your team, your payments) we are the controller. For your contacts' data that passes through the service (the people who write to you or whom you write to) we act on your behalf, as a processor (in Brazil, operador): you decide whom you write to and why, and we only process it to provide the service.
This policy is the product-specific one and prevails on what it covers; the owner's general framework is the ZZIA privacy policy, published at zzia.info. We describe what the system actually does, as measured.
Message content
We don't store WhatsApp message content permanently. A live message body passes through our system when needed —when sending it to Meta, or when forwarding an inbound message to your system— and is kept only until it is delivered:
· A message we forward to your system: if your system accepts it, the content is deleted right away. If it doesn't answer, we retry for up to 8 hours and 36 minutes and then delete it anyway.
· A message you send through the API: kept until Meta accepts or rejects it.
· Never longer than 73 hours: if our system stopped, the record expires at 72 hours and the automatic cleanup, which runs every hour, deletes it entirely.
The exception: the Coexistence history, only if you choose to receive it. Before you connect a number via Coexistence we ask whether you want us to deliver the history of your conversations; your answer is stored with its date. If you answer yes, we request it from Meta once (up to 6 months, both sides, no groups) and keep that content encrypted (AES-256-GCM) until your system receives it, and never more than 7 days: whatever was not delivered is deleted after 7 days anyway. The choice is now: Meta shares it only once, when connecting, and you have to accept sharing it in the WhatsApp Business app. If you still haven't received it by the fifth day, we let you know in the panel and by email. It is not written to server logs or to the audit log, and it is not included in the database backups. We process it on your behalf, like the rest of the content. If you answer no, we do not request it from Meta. Either way, the history stays on your phone.
Attachments (photos, audio, documents) are never stored: when you download one, it streams through our server straight from Meta without being written to disk. We keep only its identifier, type, size and a fingerprint of the file, for 7 days since last use.
⚠ A message that happens to be in transit at the time of the daily backup stays in that backup, for up to 30 days (see «Backups»).
Your contacts' phone numbers
Meta gives every message an identifier (it calls it wamid). That identifier contains the contact's phone number, encoded —not encrypted—.
Since September 28, 2026 we do not store that identifier: we store an irreversible fingerprint (HMAC-SHA256 with a secret key of ours), which lets us match each message with its delivery statuses (sent, delivered, read, failed) and from which the number cannot be recovered. We keep it for 30 days.
Records from before that date do contain the original identifier, and with it the number: they are not migrated; they are deleted automatically after 30 days —the last one on October 28, 2026—, plus up to 30 days in backups.
We don't store your contacts' numbers anywhere else in the database, with one exception: if a contact asked not to receive messages, or Meta restricted you from writing to them, we store their number as an irreversible fingerprint (SHA-256 with a key specific to your account), with no time limit, so we never write to them again.
What we keep and for how long, item by item
«You» is the business that subscribes to WAIA Connect. «Your contacts» are the people you talk to on WhatsApp.
| Data | What it includes | How long |
|---|---|---|
| Your account and team | Business name, website, country, time zone; name and email of each team member; their Google identity (identifier and email) | While the account exists |
| If you appear in Customers | If you authorize it in your panel, we show your business name, logo and website on the customers page; you can withdraw it whenever you want. We keep the date, the IP, who authorized it and the version of the accepted text, and once a week we check that your website responds (and whether it links to ours) | While you authorize it; the record, while the account exists |
| What you told us when you joined | If you answered the three sign-up questions: what you will connect, with which tool and how you heard about us, with the date (or that you skipped them). We use it to show you the guide that fits and to know where sign-ups come from | While the account exists |
| If you connect your number with another company's link | What you write on the signup screen if it stops ("Tell us on which screen it stops") reaches the company that sent you the link and us as is, together with the attempt and Meta's error code, so they can help you | While the attempt record exists |
| Where you came from | Campaign tags, Google or Meta click identifier, referring site and landing page of the first and the last contact before creating the account | While the account exists |
| Your connected numbers | Business phone number, display name, Meta identifiers, the access token, encrypted, and whether you chose to receive the Coexistence history, with the date | While the account exists (a disconnected number keeps its record) |
| Message log | Which of your numbers, inbound or outbound, type, status, date, Meta error code, the shape of the send (without the text) and an irreversible fingerprint of Meta's identifier (since 28/09/2026; before that, the identifier itself, which contains the contact's number) | 30 days |
| Content of a message in transit | Text, number and file references of a live message while it is being delivered | Until delivered; at most 8 h 36 min with retries; never more than 73 h |
| Attachments | Only identifier, type, size and fingerprint. Never the file | 7 days since last use |
| History Meta sends when connecting via Coexistence: metadata | The same metadata as the message log, without the text | 30 days |
| Coexistence history you chose to receive: content | Text, number and file references of your conversations from up to 6 months back, encrypted. Only if you answered yes when connecting. Not included in backups | Until delivered; never more than 7 days |
| Phone address book (Coexistence) | We don't request it when a number is connected, since 28/09/2026. For numbers connected before that, Meta may keep sending it when a contact changes on the phone: we discard it on arrival, without storing it or forwarding it to your system | Not stored |
| Contacts who don't accept messages | Their number as an irreversible fingerprint and the reason | No time limit (so we never write to them again) |
| Usage counters | Message counts per day. Nothing personal | No time limit |
| Your WhatsApp templates | The text you wrote for your templates and their examples | While the template exists |
| Your endpoints (webhooks) | Your system's address and its secrets, encrypted | While they exist |
| Panel notices | What happened and with which of your numbers | While the account exists |
| Emails we send you | To whom, which email, subject, when and whether it arrived. If open tracking is turned on, also when you first opened it and when you first tapped a link (only those two dates: not your IP address, your device or which link). The data used to build it is deleted after 72 h | 365 days |
| Bounced emails | The address | No time limit (so we never write to it again) |
| Attempts to connect a number | Step, outcome, IP address, your number and a technical browser trace (which includes your Facebook user identifier) | Technical trace 30 days; the attempt 365 days |
| Payments | Charges, subscriptions and the payment processor's notifications. With Polar they include the payer's name, email, billing address and, sometimes, IP | No time limit: it is accounting evidence. If the account is deleted, they are anonymised (see below) |
| Audit log | Who did what and when in the account, with the IP address | No time limit: it is security. If the account is deleted, it is anonymised |
| Contact form requests | Name, email, company, the message and a fingerprint of the IP | No time limit; deleted on request |
| Emails you send us | If you write or reply to our address: sender, subject, when, and what you wrote (without the quoted part of our email and without attachments), linked to your account so we can answer you | 365 days |
| Visits to this site | Page, date, referring site and campaign. No IP, nothing that identifies you | 180 days |
| System and number health | Technical measurements. Nothing personal | 30 days |
| Server logs | The IP address and requested path of each visit. No phone numbers or emails | A few days: they overwrite themselves |
| Backups | The whole database, as it was at backup time | 30 days |
Backups
We make one backup of the whole database per day (at 04:30 UTC) and keep it for 30 days; after that it is deleted automatically. Backups are encrypted (AES-256) and live on our Google Cloud server.
That's why every period on this page extends up to 30 more days in a backup: a piece of metadata deleted from the database after 30 days can exist in a backup until day 60. And data we delete on request disappears from the last backup 30 days later.
Backups exist to restore the service after a disaster. They are not used for anything else.
Who else receives data, and in which country
We use few providers, and each receives only what its part needs:
| Provider | Country | What for | What it receives |
|---|---|---|---|
| Google Cloud | United States | The servers (infrastructure processor) | Everything we keep, as described on this page: database, backups, queues and logs |
| Meta (WhatsApp) | United States | The messaging channel | The content and numbers of every message —it is the channel by definition— and the data of your numbers and your WhatsApp account |
| Google (sign-in) | United States | Sign-in | Your sign-in; it returns your name and email to us |
| Resend | United States | Sending our emails | Your email address, the subject and body of each email we send you (sometimes naming your number). If open tracking is turned on, Resend adds an invisible image and routes links through its server to tell us you opened the email or tapped a link |
| Cloudflare | United States | Domain names (DNS), forwarding the email you write to hola@waiaconnect.com and, on the contact form, checking that whoever writes is a person (Turnstile) | The emails you send us and, on the contact form, the IP and technical browser data, no advertising cookies. It does not see API or panel traffic |
| Polar | United States | Payments in US dollars, as merchant of record (invoices and settles taxes) | Payer's name, email, billing address and IP, and the payment. Polar handles the card: we never see it |
| MercadoPago | Argentina | Payments in Argentine pesos | The payment email, the amount and your account identifier. MercadoPago handles the card: we never see it |
| AI provider (one at a time: Google Gemini, OpenAI or Anthropic) | United States | Proposing the answer to a support request, which a person usually reviews before it is sent | The text of your request and of your messages in that request, and a summary of your account (country, language, plan, status of your numbers and of the sign-up). Never payment data, nor the content of your WhatsApp messages. We use its commercial API: according to its terms, it does not train models on what we send and keeps it to detect abuse: up to 30 days (Anthropic and OpenAI) or for a limited period (Google), longer if it detects abuse or the law requires it |
Your own system (the endpoint you configure) receives the full content of messages: it is their destination, and you choose it.
When you write us a support request, an AI system may propose the answer using our approved answers. Requests about payments, complaints or legal matters are always answered by a person. For that, the text of the request is sent to our AI provider (see the table); it does not use it for training, and we do not store your name, email or phone number in our answer bank.
We do not sell or share data with anyone for advertising, with one exception: if you arrived through a Google ad, we may tell Google that the account connected a number, only with the click identifier and the date —never your name, your email or your number— to measure the ad.
International transfer
We are in Argentina and data is stored and processed in the United States (Google Cloud, Meta, Resend, Cloudflare, Polar and the AI provider). If you are in Brazil, Argentina or another country, that is an international data transfer.
We make it because it is necessary to provide the service you signed up for (in Brazil, LGPD art. 33, IX, with art. 7, V), and with providers that apply their own data protection terms to their customers. In Argentina, Law 25,326 (art. 12) applies. If you have a question about this, write to us.
When you visit this site
We count how many times each page is opened and how many times each file is downloaded (the n8n workflows, the API contract, the documentation). We measure it ourselves, on our own server, and we store exactly four things: which page, when, which site the link came from, and which campaign —if the link carried one—.
In this log we store nothing that identifies you. Not your IP address (not even hashed or truncated), not which browser you use, not a device fingerprint, not an identifier that would let us recognise you across visits. From the referrer we keep only the site (for example google.com), never the full address of the page you were on.
The consequence is deliberate: this log cannot tell whether two visits are the same person, and we don't want it to. That's why we count visits, not visitors. The only thing that carries from one visit to the next are the functional cookies described below, and all they carry is which kind of route you arrived by —in the first four, a value shared by everyone who arrives the same way, not an identifier of yours; in the fifth and sixth, in more detail—: if you later create an account, that route is stored alongside it. If you never create an account, nothing of yours remains.
We use no third-party analytics —no Google Analytics or equivalent—: nobody but us sees your visit, and there is not a single line of tracking JavaScript on these pages.
Cookies: this site uses no tracking or advertising cookies. It does use up to six first-party, functional cookies. The first remembers which campaign brought you, if you arrived through a campaign link. The second remembers what kind of channel you arrived by —a search engine, an AI assistant, a social network, another site, or no referrer— without storing which site exactly. Both last 30 days and serve to recognise the origin if you create an account later. The third is set only if you arrived through a campaign link, lasts one day, and exists so the same visit is not counted twice. The fourth is set only if you pick a language in the header selector: it stores that language and nothing else, lasts one year, and keeps the home page from switching your language.
None of the first four carries personal data and none is shared with anyone. And the first two cannot recognise you across visits: they store a value shared by everyone arriving through the same campaign or the same kind of channel, so they cannot tell two people apart. The third does recognise your browser, and only within the same day: that is exactly what it exists for —not counting you twice— and it expires after 24 hours.
The fifth and sixth are set only when you arrive from a link or from another site: they store the link's campaign tags (utm_source, utm_medium, utm_campaign, utm_term, utm_content), the click identifier that Google or Meta add to their ads and links (gclid, fbclid), which site you came from (only the site, never the page) and which page you landed on, with the date: the fifth, the first contact; the sixth, the last. They last 90 days. Unlike the others, the click identifier does tell that click apart from any other, although it does not say who you are. If you create an account, they are stored with it; if not, nothing of yours remains.
This visit log is kept for 180 days and is then deleted automatically. Like any web server, ours records the IP address of each request in a technical log that overwrites itself within a few days.
If a reseller brought you
If you opened your account through a reseller (a commercial partner who promotes Connect), that reseller sees only: that your account exists, its name, the country, the plan, the status, since when you've been a customer and the amounts collected from that account (and the commission they generate). They never see your emails, your phone numbers, your WhatsApp numbers, your message content, your connections or your consumption. That separation is a system rule, not a setting. If you later open another account with the same email, the same WhatsApp number or the same Meta account, that account stays with the same reseller: to do that we compare those details, without showing them to the reseller.
Your number is yours
You own your WhatsApp Business Account (WABA) and your number. If you stop using Connect, your number stays yours and you can connect it to another provider. We don't hold it hostage or block it.
Security
Access tokens and secrets are stored encrypted (AES-256-GCM). API keys are stored as a fingerprint: not even we can read them. All traffic goes over HTTPS. Each account is isolated from the others at the data level. Backups are encrypted.
Security incidents
If we detect a security incident that affects your account's data (unauthorized access, a leak or a loss), we notify the account owner by email without undue delay from the moment we become aware of it, without waiting to confirm it, and within 72 hours at most. We tell you what happened, which data was affected, what we did and what we recommend you do. Where applicable, we also notify the data protection authority.
Cancelling and deleting your account
Cancelling the subscription (from the panel) stops the charges; the service goes on until the end of the paid period. Then sending is blocked, and 30 days after the block receiving is cut too, with a notice 7 days before. None of that deletes the data: message logs go away after 30 days as always, and the rest stays in case you come back.
To delete your account, write to hola@waiaconnect.com from the account's email address. We delete it within 15 days and let you know when it's done. If you have an active subscription, we cancel it first.
What is deleted: everything in the list above —the account, your team, your numbers, your templates, your endpoints, notices, the message log, emails and connection attempts—.
At Meta: we stop receiving your WhatsApp account's messages and discard the access token. Your WhatsApp account and your number remain yours; we delete nothing of yours at Meta.
What remains, anonymised: the payment evidence and the audit log, because they are accounting and security records. The amount, date and identifiers remain; the name, email, address and IP are removed. If you pay through MercadoPago (Argentina), you get the ARCA electronic invoice by email, issued by Mariano Porcile; if you pay through Polar, you get Polar's receipt, as Polar sells as the merchant.
Backups are not edited: deleted data disappears from the last backup 30 days later.
Your rights and how to exercise them
You can access your account data from the panel, correct it, cancel your account and unsubscribe from our emails via the link in each email or from the panel.
To access, correct, take away or delete your data, object to processing, or for any question about it, write to us at hola@waiaconnect.com. You can also direct the request to the owner at mporcile@gmail.com, the address Consulta Automática registers for these requests at zzia.info. It's the same owner behind both sites.
If you are a contact of one of our customers (someone who wrote to a business that uses WAIA Connect), the controller of your data is that business: ask them. If you write to us, we pass your request on to them.
Changes to this policy
If we change this policy we update the date above and, if the change is material, we notify you via the panel or email.
⚠ This is an operational, honest text describing how the service works; it is not legal advice and does not replace review by a lawyer. If in doubt, write to us at hola@waiaconnect.com.