tawk.to
How to configure tawk.to 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 the tawk.to chat widget 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. The tawk.to chat widget, published by tawk.to Inc..
What the service does in this scope. The widget sets tawk_uuid_propertyId (visitor tracking, 6 months), twk_idm_key (session), TawkConnectionTime (session) and twk_token_* in local storage; tawk.to classifies most of them as essential. IP addresses are processed using cookies. Property settings allow disabling IP recording, and a consent form can be required on the widget for all visitors or only for visitors from the EU.
Configurations included.
| Configuration | Summary |
|---|---|
| Configuration A — Medium risk | Widget after Consenter consent; IP recording disabled; consent form for EU visitors. |
| Configuration B — Higher risk (default configuration) | Widget after consent; IP recording on; visitor monitoring visible to agents. |
⚠ Recommendation — "essential" classification. tawk.to classifies
tawk_uuid_propertyId(6 months, visitor tracking) as essential. A 6-month visitor identifier set before the visitor uses the chat is not obviously strictly necessary under § 25(2) TDDDG; load the widget after consent unless your DPO or independent counsel confirms otherwise.
Step 1 — Configure tawk.to
| # | Configuration area | Where to configure it | Configuration A — Medium risk | Configuration B — Higher risk (default configuration) |
|---|---|---|---|---|
| 1 | Processing purposes | Operator decision | Unlock additional website features | Unlock additional website features |
| 2 | Loading | Consenter script blocking | After consent | After consent |
| 3 | IP recording | Property settings | Disabled | Enabled |
| 4 | Consent form | Require consent form: None / All / Only for visitors from EU | Only for visitors from EU | None |
Step 2 — Map the configuration in the Consenter Manager
Processing location. Per tawk.to's DPA; tawk.to Inc. is treated here as a US enterprise subject to the US CLOUD Act. Verify the entity and hosting in the DPA.
| Consenter Manager field | Configuration A — Medium risk | Configuration B — Higher risk (default configuration) |
|---|---|---|
| Processing purposes | Unlock additional website features | Unlock additional website features |
| Tracking method | First party tracking (cross-session) | First party tracking (cross-session) |
| Identifier | Device identifiers | Device identifiers, IP address |
| Data categories | Browsing and interaction data, Device characteristics, Device identifiers, User-provided data | As A, plus IP address, Non-precise location data |
| Legal role of data recipient | Processor | Processor |
| Personalisation model | No personalisation | No personalisation |
| Maximum storage duration | 6 months | 6 months |
| Processing location | Per DPA; United States | Per DPA; United States |
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