WhatsApp Share
How to configure WhatsApp Share at different risk levels and map it in the Consenter Manager.
This work is licensed under CC BY-SA 4.0
Typical processing purposes: Unlock additional website features
Overview
This guide explains how to implement different privacy configurations for WhatsApp share and click-to-chat buttons and how to reflect them in the Consenter Manager.
- Configure the third-party service.
- Map the selected configuration in the Consenter Manager.
- Update your privacy policy to reflect the actual implementation.
The configurations are comparative examples, not guarantees of legal compliance. Verify that the guide matches your product edition, implementation, and current provider documentation.
At a glance
Scope. WhatsApp share links (wa.me/?text=…) and click-to-chat links (wa.me/<number>) on the website. WhatsApp is operated by Meta (WhatsApp Ireland Limited in the EU; Meta Platforms, Inc., US).
What the service does in this scope. A click-to-chat or share link is a plain URL to wa.me that opens WhatsApp with an optional pre-filled message. Implemented as a plain link, it sends no request to WhatsApp before the visitor clicks. Third-party JavaScript widgets for WhatsApp buttons exist and may load additional scripts.
Configurations included.
| Configuration | Summary |
|---|---|
| Configuration A — Lower risk | Plain wa.me link; nothing loaded before the click. |
| Configuration B — Medium risk | Third-party WhatsApp widget script; loaded after Consenter consent. |
Configuration A without consent. A plain link sets nothing on your website; mention WhatsApp in the privacy policy. For B, map the widget provider (not WhatsApp) as the data recipient.
Step 1 — Configure WhatsApp Share
| # | Configuration area | Where to configure it | Configuration A — Lower risk | Configuration B — Medium risk |
|---|---|---|---|---|
| 1 | Processing purposes | Operator decision | — | Unlock additional website features |
| 2 | Button type | Website code | <a href="https://wa.me/..."> | Widget script |
| 3 | Loading | Consenter script blocking | — | After consent |
Step 2 — Map the configuration in the Consenter Manager
| Consenter Manager field | Configuration A — Lower risk | Configuration B — Medium risk |
|---|---|---|
| Entry needed | No | Yes (for the widget provider) |
| Processing purposes | — | Unlock additional website features |
| Tracking method | No tracking | Per widget provider |
| Identifier | No identifier | Per widget provider |
| Data categories | — | Browsing and interaction data, IP address |
| Legal role of data recipient | — | Per widget provider |
| Personalisation model | — | No personalisation |
| Maximum storage duration | — | Per widget provider |
| Processing location | — | Per widget provider |
How is this guide?
Shape Consenter Together
Consenter is built on an open and participatory process that grows through community collaboration. Whether you share feedback, improve the documentation, or contribute to the Risk Configuration Guides or Technical Integration Guides, your expertise helps make Consenter more privacy-friendly, interoperable, and useful for everyone—including your own users and services: Get finally your benefits and control the risks when sharing personal data.
Need Help?
Last updated on