Session replay
Is Smartlook GDPR compliant?
Smartlook may only run after the visitor has agreed. It is not strictly necessary for the website to work, so loading it on arrival, before any choice, is the single most common way sites get this wrong.
- Category
- Session replay
- Needs consent
- Yes
- Leaves the EEA
- No
- Can be self-hosted
- No
- Recognised by
- smartlook.com, smartlook.cloud
- Typical cookies
- SL_C_*
What does Smartlook do?
Czech session recording for web and mobile apps. EU hosting removes the transfer question, but replaying a session remains processing that a visitor has to agree to first.
Does Smartlook need consent?
Yes. Smartlook is Session replay, which is never strictly necessary for a website to function. Under ePrivacy Article 5(3), and its national transpositions, storing or reading anything on the device for that purpose requires consent first, and that consent has to be as easy to refuse as it is to give.
ePrivacy Art. 5(3) · TDDDG § 25 (DE) · TKG 2021 § 165(3) (AT) · GDPR Art. 6(1)(a)
Does Smartlook send data outside the EEA?
No. Smartlook keeps processing inside the EEA, which removes the third-country question entirely. You still have to name it as a recipient in your privacy policy.
What can I use instead of Smartlook?
| Needs consent | Leaves the EEA | Can be self-hosted | |
|---|---|---|---|
| Smartlook | Yes | No | No |
| Mouseflow | Yes | No | No |
How do we detect Smartlook?
We load your page in a real browser as a first-time visitor who clicks nothing, then look at what it contacted. Smartlook is recognised by requests to smartlook.com and smartlook.cloud, and we report whether it merely loaded or actually sent data, and whether it set a cookie before any choice was made.
Check your websiteThis describes the service as it is normally deployed. Your own configuration decides what actually happens, which is what a scan of your site shows. Not legal advice.