Does your website use third-party services? Get GDPR compliant in minutes.
Try FlowConsentFree plan · 10-min setup
Uzerly is a European session replay and behavioural analytics platform that records visitor sessions, heatmaps and rage clicks to drive UX improvements.
Uzerly is a European session replay and behavioural analytics platform used by product and UX teams to understand how visitors interact with a website. The tag records page views, mouse moves, clicks, scroll, form interactions and rage clicks, and reconstructs each session as a video like replay enriched with funnels and heatmaps.
Uzerly writes a first party visitor cookie used to stitch sessions, a session cookie that ties the recording to the current visit and a sample cookie that decides whether the visitor is part of the recording cohort. The recording payload includes URLs, DOM mutations, viewport size, mouse and keyboard events. Form fields are masked by default but can be unmasked by the operator.
Session replay processes detailed behavioural data and can capture personal data through forms, so prior consent is required under article 5(3) of the ePrivacy Directive and article 6(1)(a) GDPR. The CNIL and other DPAs have repeatedly stressed that consent for replay must be specific and that sensitive forms (passwords, payment, health) must always be masked.
Get GDPR compliant in 10 minutes
Free plan available · No credit card required
Block the Uzerly script in your CMP under a dedicated session replay category. Keep field masking on by default, exclude payment and authentication pages from recording, set short retention, and never re identify a visitor from a replay without an explicit secondary consent.
Uzerly stores European session recordings on Hetzner and OVH infrastructure in Germany and France. There are no US sub processors in the recording or analysis pipelines, which simplifies the privacy notice and avoids Schrems II level transfers.
Sign the Uzerly DPA, run a DPIA, configure aggressive masking, exclude sensitive pages, set retention to ninety days or less, train UX and product teams on what they are allowed to use the replays for, and review the recordings sample annually with the data protection officer.
Websites using Uzerly must obtain user consent under GDPR regulations.
DPIA considerations
A DPIA is recommended whenever session replay is enabled. The processing involves systematic monitoring of behaviour, may capture form data and can lead to identification, all of which trigger high risk thresholds in WP248 and most national DPA guidance.
Sample consent text
We use Uzerly to record sessions and produce heatmaps so we can improve usability. By accepting, you allow Uzerly to set cookies, capture your interactions and store the recording on EU servers, with sensitive form fields masked by default.
Third-party domains contacted
uzerly.comcdn.uzerly.comreplay.uzerly.comCookies placed
| Name | Type | Duration | Purpose |
|---|---|---|---|
| uz_visitor | Functional | 13 months | First party Uzerly visitor identifier used to stitch sessions for behaviour analysis. |
| uz_session | Functional | Session | Ties the current session replay to the active visit. |
| uz_sample | Functional | 24 hours | Indicates whether the visitor is part of the sampled cohort that is recorded. |
Uzerly collects user analytics data — you legally need a consent banner. Try FlowConsent free.
Uzerly writes a first party visitor cookie used to stitch sessions, a session cookie tied to the current visit and a sample cookie that decides whether the visitor is recorded. Tags loaded after consent may also set additional cookies.
Yes. Session replay is a non essential, behaviour heavy processing that requires prior opt in consent under article 5(3) of the ePrivacy Directive and article 6(1)(a) GDPR.
Consent is the only realistic basis for the recording. Legitimate interest is generally insufficient because of the systematic nature of the monitoring and the risk of capturing personal data through forms.
No. Uzerly stores European session recordings on Hetzner and OVH infrastructure in Germany and France. There are no US sub processors in the recording pipeline.
Yes. Session replay meets the WP248 high risk thresholds, especially the systematic monitoring criterion, so a DPIA is expected before activating the tool.
Block the script in your CMP, keep aggressive masking, exclude sensitive pages from recording, sign the DPA, set retention to ninety days or less, and limit access to replays to a small documented team.
Other session replay platforms with EU friendly settings include Hotjar with EU residency, Contentsquare, Mouseflow, Smartlook, Glassbox EU and self hosted rrweb based stacks for full control.
List the Uzerly visitor, session and sample cookies, describe the recording purpose, name Uzerly as a processor located in the EEA, mention the masking configuration and provide a clear opt out from your CMP.