Is session replay GDPR compliant? A guide for founders who build with a coding agent and sell in the EU or UK
Session replay can be used under the GDPR, but it is not compliant by default. If you sell to people in the EU or UK, you need a lawful basis and, in most cases, consent before the script runs. You also need to mask personal data, set a retention period and sign a DPA with the vendor. This is not legal advice. Read November 14, 2026.
This page is for founders who build their site with a coding agent and then find out they sell to people in the EU or UK. We read the law texts and eight vendors' own documentation on November 14, 2026, and we read the UserProof recorder's source code for the last section. Where a vendor page would not load or did not say, the table says "not stated". No tool on this page is called compliant, because compliance depends on how you set it up.
What does the law actually say?
Five texts matter. They are EU texts. The UK has its own versions, which we did not read.
- GDPR Article 4(1) defines personal data as "any information relating to an identified or identifiable natural person". The same article lists an "online identifier" as a way to identify someone. A visitor ID counts if it can be tied to a person.
- GDPR Article 6(1) says processing needs a lawful basis. Two candidates are consent (6(1)(a)) and legitimate interests (6(1)(f)).
- GDPR Article 5(1)(c) and (e) require data that is "adequate, relevant and limited to what is necessary" and kept in identifiable form no longer than necessary.
- GDPR Article 28 (read November 14, 2026) requires a contract or other legal act that binds a processor to you, the controller, and sets out what it processes and for how long.
- ePrivacy Directive 2002/58/EC, Article 5(3) allows storing information on a visitor's device, or gaining access to information already stored there, only with the visitor's consent. Two exceptions exist: sending a communication, and what is strictly necessary for a service the visitor explicitly asked for.
The European Data Protection Board's Guidelines 2/2023 on the technical scope of Article 5(3) explain which techniques the rule reaches. The EDPB lists the final version 2.0 with the date 16 October 2024. Read the guidelines, or have your lawyer read them, before you decide that your script falls outside the rule.
Does session replay need cookie consent?
For EU visitors, usually yes. Article 5(3) is not about cookies by name. Its text covers any storing of information on the device and any access to information already stored there. A recorder that writes a visitor ID to local storage is inside that wording, the same as one that sets a cookie. The strictly necessary exception covers a service the visitor asked for, such as a shopping cart. It is hard to describe a replay of their visit as that.
That is our reading of the text, not a ruling. Vendors lean the same way. Mouseflow's GDPR page says you may need active and explicit consent. Microsoft Clarity began enforcing consent signals for EEA, UK and Switzerland visitors on October 31, 2025, per its Consent Mode page. The GDPR lawful basis is a second, separate question. Many teams use consent for both.
The practical step: load the recorder only after your consent banner records a yes, and stop it when the visitor withdraws.
What personal data does a recording hold?
Anything the recorder captures that relates to an identifiable person. Four kinds turn up:
- Identifiers. A visitor ID, a session ID, and often an IP address on the server side.
- Page content. Names, emails, addresses and balances shown to a logged-in visitor.
- Visitor input. Typed values and selected text, depending on the tool.
- Behavior. Clicks, scrolls and pages viewed. On its own this is thin, but it is tied to the identifier.
The fix for the middle two is masking, covered next. The fix for the first and last is a lawful basis and a short retention period.
How do 8 session replay tools handle consent, EU data and masking?
We read each vendor's own pages on November 14, 2026. A cell says "not stated" when the page we read did not say it, or when the page would not load. Page dates are the dates the pages show.
| Tool | Consent, in the vendor's words | Where data is stored | Masking attribute or class | Pages read and their dates |
|---|---|---|---|---|
| UserProof Ours | The snippet has no consent prompt or consent API. You load the script tag yourself, so you decide when. No cookies; visitor ID in localStorage, session ID in sessionStorage | Privacy policy: servers and database at Hetzner, in Germany | data-exclude attribute on an element, or selectors in the script tag's own data-exclude | Recorder source (public/sdk.js) and privacy policy (last updated Oct 18, 2026), read Nov 14, 2026 |
| Microsoft Clarity | Consent signal enforcement for visitors from the EEA, UK and Switzerland starts Oct 31, 2025. Consent Mode is on by default for those regions | FAQ: "stored in the Microsoft Azure cloud service"; no region stated | data-clarity-mask="True" and data-clarity-unmask="true", or CSS selectors in Settings. Default mode is Balanced | Consent Mode page (updated Dec 5, 2025), masking page (Nov 1, 2024), FAQ (Oct 16, 2026) |
| Hotjar | Not stated | Not stated | data-hj-suppress, as an attribute or a class, hides all text, images and video inside the element, children included. Inline SVGs cannot be suppressed | Masking: Hotjar help article on suppressing text, images, videos and input, read in a browser Nov 14, 2026 (no date shown). Consent and hosting: Hotjar pages returned 403 to our fetch, so those cells are not filled |
| FullStory | Help article: "Unmask is the default state for data capture" unless the account uses Private by Default. Consent classes fs-exclude-without-consent, fs-mask-without-consent, fs-unmask-with-consent work with its FS.consent API | Not stated | fs-exclude, fs-mask, fs-unmask CSS classes | Help article and developer privacy classes page, neither shows a date |
| PostHog | GDPR guide: if a user opts out you must stop all data capturing and processing. Replay masks inputs by default; general text is not masked by default | Privacy page: PostHog Cloud EU has "servers hosted in Frankfurt" | ph-no-capture CSS class; config maskAllInputs and maskTextSelector | Replay privacy, GDPR and privacy pages, none shows a date |
| LogRocket | Not stated | Not stated | data-private attribute; password fields are never recorded | Privacy docs (updated Mar 9, 2026), GDPR docs (updated Apr 27, 2026) |
| Mouseflow | GDPR page: "You may need to obtain active and explicit consent to track users on your website(s)." Keystrokes in fields with personal data are masked by default for most accounts | GDPR page: "EU customer data is stored within the EU." It cites the EU-U.S. Data Privacy Framework and Standard Contractual Clauses for transfers | Classes mf-masked with mf-listen (masks, keeps clicks) and mf-excluded (drops the element); or CSS selectors in Website Settings (ID, class or path) | Code article (Feb 14, 2025), masking help article (Aug 14, 2026); GDPR page shows only a 2026 copyright |
| OpenReplay | Not stated | Not stated | data-openreplay-obscured and data-openreplay-hidden; input values obscured by default | Sanitize data docs, no date shown |
Three things stand out. Of the seven tools other than ours, only Clarity states a start date for consent enforcement, and only PostHog and Mouseflow name an EU location. And each tool uses a different masking name, so a rule you write for one does nothing in another. The free snippet generator at hide sensitive data in session replay prints the right attribute for each tool from one CSS selector.
How do you mask personal data?
- List what a visitor sees. Account pages, billing, addresses, support chats and rich-text editors are the usual ones.
- Mark each area with the tool's attribute from the table, on the outermost element. Hotjar and Clarity say their markers cover the children; check the doc for the tool you use.
- Prefer exclude over mask for editors and notes. A masked element still records the click and its position. An excluded one drops more.
- Test it. Open your browser's Network tab, click inside the area, and check that your own test text is not in the request. Check your tool's docs on whether a new rule reaches recordings already made, and test before traffic arrives.
For UserProof the steps are on how to keep part of your site out of UserProof recordings.
What about the EU-US Data Privacy Framework and where data is stored?
Where the servers sit changes what you must check. Data kept in the EU raises fewer transfer questions. Data sent to the US needs a transfer mechanism, and you need to know which. Mouseflow's GDPR page names the EU-U.S. Data Privacy Framework and Standard Contractual Clauses. PostHog says its EU Cloud runs on servers in Frankfurt. Clarity says only "Azure", with no region. For each vendor, read the DPA and the subprocessor list, not the homepage.
How long should you keep recordings?
The GDPR gives no number. Article 5(1)(e) says no longer than necessary, so you pick a period and can explain it. Set it to the shortest window that still lets you fix a problem. Clarity's FAQ (page dated October 16, 2026) says it keeps recordings 30 days, with favorites and a random sample kept up to 9 months. UserProof's privacy policy (updated October 18, 2026) says raw events are kept 7 days on Free and 90 days on paid plans.
Do you need a DPA?
Yes, if the vendor processes visitor data for you. Article 28 requires the contract. PostHog's privacy page says a DPA is self-serve and available on every plan including free. LogRocket's GDPR page says it offers one and describes you as controller and itself as processor. Mouseflow's GDPR page links its DPA. Hotjar, FullStory, Clarity and OpenReplay: not stated on the pages we read.
What does UserProof record, and what does it not?
From the recorder source (public/sdk.js) and the privacy policy, read November 14, 2026:
| Item | What UserProof does |
|---|---|
| Field values | Never recorded. It stores field type, name, label, time in focus and whether the field held anything. Password fields are always excluded |
| Clicks | Position, element and the element's text, cut at 50 characters. A click on a rich-text editor stores up to the first 50 characters of its text, so put data-exclude on editors |
| Selected or copied text | Up to 200 characters, never from inside a form field |
| Keyboard | Shortcuts only: Ctrl+F, Escape, Ctrl+C. Never what was typed |
| Page address | Sent without the query string or hash |
| Errors | JavaScript error messages, cut at 200 characters |
| Device details | Browser user agent, screen size, language and platform |
| Storage on the device | No cookies. An anonymous visitor ID in localStorage and a session ID in sessionStorage |
Inside data-exclude | Click text becomes "[masked]"; selections, copies, mouse movement and field events are not recorded |
| Retention and servers | 7 days on Free, 90 on paid. Servers and database at Hetzner in Germany |
What UserProof does not give you today: it has no built-in consent prompt, so you gate the script tag yourself. Its privacy policy and terms do not mention the GDPR or a DPA by name, and the policy does not say whether IP addresses are stored. Ask through the contact link on the privacy policy before you rely on it for EU visitors. Because the visitor ID sits in local storage, our reading is that Article 5(3) applies to it too.
UserProof is free for 3 sites and 5,000 recorded visits a month; Pro is $29 a month for 50,000 visits and Scale is $99 a month for 250,000. See pricing. For other tools with a free plan, see the best free session replay tools.
What should you do before turning replay on?
- Pick a lawful basis and write it down. For EU visitors, plan on consent.
- Gate the script behind your consent banner. That also keeps its load time off visits that never agree; see how much a recorder slows a page.
- Mask or exclude every area with personal data, and test it.
- Set the shortest retention you can live with.
- Sign the vendor's DPA and read its subprocessor list.
- Update your privacy policy to say what you record and for how long.
- Ask a lawyer who knows your market. This page is not legal advice.
Sources, read November 14, 2026
- GDPR Articles 4(1), 5(1)(c) and (e), 6(1) and 28 (Regulation (EU) 2016/679), read on the gdpr-info.eu copy of the Official Journal text: definitions, principles, lawfulness and processors
- ePrivacy Directive 2002/58/EC Article 5(3), read on legislation.gov.uk
- EDPB Guidelines 2/2023 on the technical scope of Article 5(3), final version 2.0 (listed 16 October 2024): edpb.europa.eu
- Microsoft Clarity consent and masking (Consent Mode page updated Dec 5, 2025; masking page Nov 1, 2024; FAQ Oct 16, 2026): Consent Mode, Masking content, FAQ
- FullStory: privacy help article and privacy classes (no dates shown)
- PostHog (no dates shown): replay privacy, GDPR guide, privacy and DPA
- LogRocket: privacy (updated Mar 9, 2026) and GDPR (updated Apr 27, 2026)
- Mouseflow: GDPR page, code article (Feb 14, 2025) and masking help article (Aug 14, 2026)
- Hotjar: suppressing text, images, videos and input (no date shown)
- OpenReplay: Sanitize data (no date shown)
- UserProof recorder source (public/sdk.js) and privacy policy (last updated October 18, 2026)
- UserProof plans: getuserproof.com/pricing
FAQ
Is session replay GDPR compliant?
Not by default. The GDPR does not ban session replay, but you need a lawful basis first. You must also keep data to what is necessary, and sign a processor contract with the vendor. In the EU the ePrivacy rule on accessing a visitor's device usually means consent first. This is not legal advice.
Does session replay need cookie consent?
Usually yes for EU visitors. ePrivacy Directive Article 5(3) allows storing information on a device, or reading information already stored there, only with consent, unless it is strictly necessary for a service the visitor asked for. Session replay is hard to call strictly necessary. The rule is not limited to cookies. Ask a lawyer about your case.
What personal data does a session recording hold?
Anything the recorder captures that relates to an identifiable person, including an online identifier such as a visitor ID, text on the page, and text the visitor selects or types. UserProof records behavior events, never field values, but a click on a rich-text editor stores up to its first 50 characters, so mark editors with data-exclude.
How long should I keep session recordings?
The GDPR sets no number. Article 5(1)(e) says personal data may be kept in identifiable form no longer than necessary for the purpose. Pick the shortest window that lets you fix the problem. UserProof keeps raw events 7 days on Free and 90 days on paid plans; Clarity says 30 days (read November 14, 2026).
Do I need a DPA with a session replay vendor?
If the vendor processes visitor data for you, Article 28 requires a contract that binds it as your processor. PostHog says a DPA is self-serve on any plan, and LogRocket and Mouseflow point to theirs. UserProof's privacy policy and terms do not mention a DPA (read November 14, 2026), so ask first.
What does UserProof record and not record?
UserProof records page views, clicks, scroll depth, selected or copied text (up to 200 characters), field focus and abandonment, JavaScript errors and timing. Field values are never recorded and password fields are always excluded. It sets no cookies, but stores an anonymous visitor ID in localStorage and a session ID in sessionStorage.