Smartlook
How to configure Smartlook at different risk levels and map it in the Consenter Manager.
This work is licensed under CC BY-SA 4.0
Typical processing purposes: Improve the service
Overview
This guide explains how to implement different privacy configurations for Smartlook 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 Smartlook web SDK for session recordings, heatmaps and events. Smartlook.com, s.r.o. (Brno, Czech Republic) acts as processor under its DPA; Smartlook is part of Cisco.
What the service does in this scope. Smartlook records visitor sessions. Smartlook states that all its data is stored on EU servers and lists, as the situations in which customers process personal data, recording forms with personal data, not anonymising IP addresses, and using the visitor-info API or integrations. The data retention period depends on the purchased plan. Its first-party cookies include a session ID and a visitor ID (SL_C_…_SID, SL_C_…_VID).
Configurations included.
| Configuration | Summary |
|---|---|
| Configuration A — Lower risk | IP anonymisation on; forms and sensitive elements masked; no user identification; after consent. |
| Configuration B — Higher risk | IP addresses stored; visitor identification through the API (name, email); after consent. |
No configuration without prior consent. A persistent visitor ID cookie is set. Smartlook's old GDPR consent API is marked discontinued; block the SDK in Consenter until consent.
Step 1 — Configure Smartlook
| # | Configuration area | Where to configure it | Configuration A — Lower risk | Configuration B — Higher risk |
|---|---|---|---|---|
| 1 | Processing purposes | Operator decision | Improve the service | Improve the service |
| 2 | IP address anonymisation | Project privacy settings | On | Off |
| 3 | Form and element masking | Privacy settings; CSS classes on sensitive elements | All form inputs masked | Default |
| 4 | Visitor identification | smartlook('identify', …) / visitor-info API | Not used | Used |
| 5 | Loading | Consenter script blocking | After consent | After consent |
| 6 | Retention | Plan-dependent | Shortest plan option | Plan default |
Step 2 — Map the configuration in the Consenter Manager
Processing location. EU servers. Smartlook belongs to Cisco Systems, Inc., a US enterprise subject to the US CLOUD Act; the United States is listed as a potential access location.
| Consenter Manager field | Configuration A — Lower risk | Configuration B — Higher risk |
|---|---|---|
| Processing purposes | Improve the service | Improve the service |
| Tracking method | First party tracking (cross-session) | First party tracking (cross-session) |
| Identifier | Device identifiers | Device identifiers, IP address, Direct identifier |
| Data categories | Browsing and interaction data, Device characteristics, Device identifiers, IP address anonymised | Browsing and interaction data, Device characteristics, Device identifiers, IP address, direct identifier, User-provided data, Users' profiles |
| Legal role of data recipient | Processor | Processor |
| Personalisation model | No personalisation | No personalisation |
| Maximum storage duration | Per plan | Per plan |
| Processing location | EU; United States as potential access location | EU; United States as potential access location |
Privacy-policy follow-up
- Smartlook as processor; recordings; cookies; IP anonymisation (A); identification (B); EU storage; potential access by US authorities.
Verification checklist
- No Smartlook requests before consent.
- IP anonymisation setting matches the mapping.
- Recordings reviewed for unmasked personal data.
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