Privacy policy

1. Who we are and how to reach us

waplugin is operated by Rafael Xavier (Brazil; LGPD baseline). For privacy questions, access, correction, or deletion requests, contact support@waplugin.cloud.

waplugin is an independent third-party service. It is not affiliated with, endorsed by, or sponsored by WhatsApp or Meta.

2. What this policy covers

This policy covers waplugin.cloud, the waplugin console, and the backend that syncs a WhatsApp account you link as a companion device and makes authorized messages available to the AI assistant or webhook receiver you choose. WhatsApp protects messages with end-to-end encryption in transit; linking waplugin as a device means intentionally making authorized messages available to waplugin processing and, where you authorize it, to your selected assistant or webhook endpoint.

Use waplugin only for conversations you are comfortable sharing with these services. Avoid highly sensitive personal, medical, legal, or financial information.

3. Categories of personal data we collect

• Account and contact identifiers: phone numbers, WhatsApp IDs (JIDs), display names, and chat metadata needed to route, show coverage, and enforce per-account isolation.
• Message content you authorize: text, delivery state, and attachments from linked accounts in retained mode; processed in memory and discarded in strict zero-retention mode.
• Credentials and Grants: WhatsApp session credentials, pairing material (kept in memory only, never written to databases or logs), per-phone read/send consent records, and operation outcomes (pending, confirmed, uncertain).
• Support and preference data: messages you send to support, language and console preferences, and subscription state.
• Content-free telemetry: aggregated usage, performance, and error counters. We do not put message bodies, contact identifiers, phone numbers, QR material, credentials, or search terms in analytics or monitoring labels.

4. Purposes of use

• Link and maintain your WhatsApp companion-device connection.
• Ingest, index, and serve retained reads (search, catch-up) you request.
• Deliver authorized sends, reactions, and webhook events with honest status.
• Enforce per-phone permissions, retention modes, revocation, and deletion.
• Operate, secure, and debug the service; prevent abuse; provide support.

We collect the minimum data needed for these purposes. Tool inputs request only task-specific fields, and tool responses return only data directly relevant to your request — no diagnostic, session, trace, or logging identifiers unless strictly required.

5. Categories of recipients

• The AI provider you choose (for example ChatGPT, Claude, or another compatible assistant) receives authorized message content when you connect it.
• Webhook receivers you configure receive the events you subscribe them to.
• Infrastructure processors hosting waplugin storage, compute, and content-free analytics (including managed PostgreSQL and Firebase/Google services) process data to operate the service.

We do not sell personal data. We never enable advertising sharing, and message content is never used to train shared models. Shared workers process multiple accounts in one service; they are not private per-account sandboxes.

6. Data retention timelines

• Strict zero message-content retention: message bodies and derived content stay memory-only. Crashes, redeploys, or long outages can lose delivery with no replay. Device/session credentials and content-free status still persist.
• Retained history: committed messages, indexes, and any durable webhook outbox persist until you pause, revoke, or delete the account. Deletion revokes access first, then removes live rows, indexes, grants, and allowed outbox content.
• Backups and replicas: point-in-time-recovery copies, replicas, and database write-ahead logs age out on the backup window; they are not erased instantaneously. Restore procedures reapply prior deletion and revocation decisions.
• Session credentials and consent records persist in all modes until sign-out, revocation, or deletion.
• Analytics keeps the shortest useful retention; aggregates are purpose-bound and de-identified where retained longer.

Deleting an account key does not erase copies already disclosed to your assistant or webhook receivers, nor does it instantly erase backups. Pause sync is not revoke access; sign-out is not revoke; deletion is a separate action.

7. Controls and your rights

• Per-phone read, send-messages, and send-reactions grants you can change anytime.
• Retention-mode selection, sync pause, access revocation, sign-out, and deletion.
• LGPD rights (confirmation, access, correction, anonymization, blocking, deletion, portability, and consent withdrawal) via support@waplugin.cloud.
• Non-essential analytics consent with persistent preference controls.

We do not collect payment-card data, protected health information, or government identifiers through waplugin tools. Please do not send them to support either.

8. Security

Access controls, encryption in transit and at rest, minimal retention, careful monitoring, and bounded retries. No cloud integration can claim your messages remain visible only to you and their original recipients once you authorize AI or webhook access.

9. Changes to this policy

Material changes will be posted here with a new effective date before they take effect. Continued use after the effective date constitutes acceptance.