Set up your bannerConfigure Your ToolsSession Recording and Heatmaps

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.

  1. Configure the third-party service.
  2. Map the selected configuration in the Consenter Manager.
  3. 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.

ConfigurationSummary
Configuration A — Lower riskIP anonymisation on; forms and sensitive elements masked; no user identification; after consent.
Configuration B — Higher riskIP 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 areaWhere to configure itConfiguration A — Lower riskConfiguration B — Higher risk
1Processing purposesOperator decisionImprove the serviceImprove the service
2IP address anonymisationProject privacy settingsOnOff
3Form and element maskingPrivacy settings; CSS classes on sensitive elementsAll form inputs maskedDefault
4Visitor identificationsmartlook('identify', …) / visitor-info APINot usedUsed
5LoadingConsenter script blockingAfter consentAfter consent
6RetentionPlan-dependentShortest plan optionPlan 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 fieldConfiguration A — Lower riskConfiguration B — Higher risk
Processing purposesImprove the serviceImprove the service
Tracking methodFirst party tracking (cross-session)First party tracking (cross-session)
IdentifierDevice identifiersDevice identifiers, IP address, Direct identifier
Data categoriesBrowsing and interaction data, Device characteristics, Device identifiers, IP address anonymisedBrowsing and interaction data, Device characteristics, Device identifiers, IP address, direct identifier, User-provided data, Users' profiles
Legal role of data recipientProcessorProcessor
Personalisation modelNo personalisationNo personalisation
Maximum storage durationPer planPer plan
Processing locationEU; United States as potential access locationEU; 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

On this page