On this page
- What can a session replay see?
- Consent: recording waits for your cookie banner
- Do you need a cookie banner for session recording?
- Is session recording legal? GDPR and US wiretap claims
- What did regulators say about session replay in 2026?
- What should a privacy policy say about session recording?
- How long to keep replays
- Who can watch session replays?
- Write down your team's rules
- A five-minute privacy check
- Frequently asked questions
- Try it on your site
- Sources
Session replay respects visitors' privacy when typing is masked in their browser, recording waits for consent in your cookie banner, your privacy notice says you record, and replays are kept for a short, stated period and opened only by people who need them. A tool can't be GDPR compliant on its own; what you do with it decides.
A replay is a record of a real person's visit, rebuilt from the page rather than filmed. They can't see it happening, so their only protection is the setup you choose, and each part of it is a setting or a habit you can check in an afternoon.
Key takeaways
- With no cookie banner, Session Recordings doesn't wait for consent before recording, so turn on your platform's banner (Shopify: Settings › Customer privacy; Wix: Privacy & Cookies) if you want to ask first.
- Test the banner in a private window: decline analytics and check that no visit appears, then accept and watch your visit show up marked LIVE.
- Name recordings, masking, your retention period and how to opt out in your privacy notice.
- Give each teammate their own login (Wix's Roles & Permissions, or a user in Shopify's Settings › Users), and point them to a replay with Share, which emails or copies a link that only people with access to your store or site can open; replays never get a public link.
- Masking hides what visitors type into form fields, not what your pages display: a page that greets a visitor by name shows that name in the replay, so check those pages before you share a screenshot.
What can a session replay see?
Pages, clicks, scrolling, taps and whatever text your pages display, but not what visitors type into form fields when that's masked in their browser, as it is in Session Recordings. The exception is the words a shopper submits in a Shopify store's search, which are shown. For the rules Session Recordings itself follows, see what it masks and keeps.
Masking replaces what a visitor types with placeholder characters. Where it happens matters. Masked on a server, the real words still made the trip. Masked in the visitor's browser, they never leave the device.
Session Recordings masks every form field in the browser, passwords and email addresses included, and the replay shows asterisks where someone typed into one. You can see that a field was filled in and where the visitor paused, never what they wrote. Nobody on your team can stumble across what a visitor typed into a field, because it was never recorded.
Masking covers typing, not what your pages display. Text already on a page appears in the replay as the visitor saw it, so a page that greets someone by name shows that name too, and on a Wix site so does an account page or an order confirmation with an address. On a Shopify store, checkout, its thank-you page and customer account pages are never recorded. Know which of your pages show personal details before you share anything from a replay.
On a Shopify store, searches are the one place typed words come through on purpose: the words a shopper submits in your store's search show in the replay, named in the Activity list, so you can see what shoppers search for. People sometimes type an order number or their own name into a search box, so treat search terms as visitor data.
| What the visitor does | What the replay shows |
|---|---|
| Opens pages, clicks, scrolls and taps | Each action, in order, on the rebuilt page |
| Types into any form field | Asterisks, and a Typing (masked) row in the Activity list |
| Opens a page that displays their details | The page as they saw it |
| Declines analytics cookies in your banner | Nothing, because the visit isn't recorded |
Recording tools don't all hide the same things. The typing column in our comparison of session recording tools for Wix shows what each one hides by default.

Consent: recording waits for your cookie banner
Session Recordings runs as an analytics script and follows your site's cookie consent. When your site shows a cookie banner, a visitor is recorded only after accepting analytics cookies. If they decline, nothing is recorded, and if they accept and later change their mind, recording stops. On Shopify, it reads each visitor's choice through Shopify's Customer Privacy, which Shopify's cookie banner and consent apps connected to it report to, and until a visitor allows analytics it sends nothing, sets no cookie and doesn't load the recording library.
A banner protects visitors only when it offers a real choice.
- Plain words. "We use analytics cookies, including recordings of visits, to improve this site" is clear.
- A visible Decline. Put it where people can see it, as easy to click as Accept.
- A way back. Wix's banner keeps a small privacy trigger on the page, and clicking it reopens the banner so visitors can change their choice.
- Recordings named. Mention them in the description of your analytics category.
Tools you paste in as code behave differently. Wix treats anything added under Settings → Custom Code as essential by default, which means it loads before the visitor chooses and can't be turned off. If you run a code-based recorder as well, open its Code Type tab and move it into the analytics category. How Hotjar's custom-code setup handles consent on Wix shows the setting in context.
Do you need a cookie banner for session recording?
If people in the EU visit your site, generally yes: storing or reading information on their device for analytics needs their consent first, which is what a banner collects. For visitors elsewhere, it depends on the rules where they are, which the legal section below covers. With no banner, there is nothing to wait for, so Session Recordings records every visitor from their first page, until the month's recordings are used.
To add Wix's own banner:
- Go to Privacy & Cookies in your site's dashboard.
- Click Add to Site next to Add a cookie consent banner.
- Review the Usercentrics information and click Agree & Add.
Wix's banner is run by Usercentrics and lets visitors allow Functional, Marketing and Analytics cookies separately. Until a visitor chooses, only essential cookies and scripts load.
To turn on Shopify's cookie banner:
- From your Shopify admin, go to Settings › Customer privacy.
- Click Cookie banner.
- Under Regions and content, keep the automated settings or choose the regions yourself.
- Adjust the banner's look and position to suit your store, and click Save.
Shopify asks you to publish a privacy policy before you use the banner. On a new store, automated settings are on, which set the banner up for visitors in the UK and EEA if you have active markets there. Where the banner shows, Shopify collects data that isn't essential only after a visitor consents.
Test your banner
Open your live store or site in a private browser window, decline analytics cookies and click around for a minute. Then open Replays in Session Recordings and check that no new visit appeared. Repeat in a fresh private window, accept analytics this time, and your visit should show up within moments, marked LIVE.

Is session recording legal? GDPR and US wiretap claims
It can be, when visitors are told and, where the law requires it, asked first. In the EU that means consent before recording starts, and in the US, wiretap lawsuits over session replay have gone both ways in court.
In the EU, two sets of rules meet. Article 5(3) of the ePrivacy Directive allows storing or reading information on a visitor's device only after they have consented with clear and comprehensive information, which is the rule behind cookie banners. The GDPR then covers the personal data itself, and several of its lines map straight onto a replay tool.
- Collect only what you need for the purpose (Article 5). Masking typing does much of this work.
- Keep data no longer than necessary (Article 5), which is why your notice should state a retention period.
- Withdrawing consent must be as easy as giving it (Article 7).
- People can ask you to erase their data (Article 17), and you must act on a request within one month, extendable by two further months for complex or numerous requests (Article 12).
In the US, the pressure has come mostly from lawsuits. Class actions have argued that session replay is a form of wiretapping, mostly under the California Invasion of Privacy Act (CIPA).
- In Javier v. Assurance IQ (2022), the Ninth Circuit let a claim go ahead from a visitor who said his session was recorded before he agreed to the site's privacy policy, rejecting the idea that agreeing afterward counted as consent. A federal court later dismissed the case because it was filed 14 months after the visit, past CIPA's one-year limit.
- In Mikulsky v. Bloomingdale's (June 2025), the same court revived a dismissed claim, finding the complaint plausibly alleged that session replay captured the contents of the shopper's communications, not just data about them.
- Lower courts have split, dismissing some of these claims and letting others go ahead.
After Mikulsky, Duane Morris advised companies to get explicit consent before such tools are enabled and to tell visitors specifically what content is captured.
For a small site, that comes down to four habits.
- Consent before recording starts. Run the banner test above to confirm your setup waits.
- A notice in plain words that names recordings, what they capture and what is masked.
- Masking in the browser, so typed details are never captured in the first place.
- A short retention period, written down and kept.
Session recordings, private by default
What visitors type into form fields is masked in their browser before it's sent, and recording follows your cookie consent. Free forever.

What did regulators say about session replay in 2026?
France's CNIL drafted a recommendation aimed at session replay tools in February 2026, and in April 2026 the UK's ICO finalised its guidance on cookies and similar technologies, which lists recordings of individual visitors among the things that need consent. Both expect visitors to be told what's recorded and asked first.
- The CNIL's draft recommendation (France). Published February 25, 2026 for a public consultation that closed April 22, 2026; the CNIL says it will review the contributions and adopt a final version, and on October 28, 2026 it still listed only the draft. It's aimed both at the companies that make session replay tools and at the sites and apps that use them. It covers collecting only what's useful for the purpose, what to tell users, and how to get consent through a consent management platform, including wording that may be used to ask.
- The ICO's final guidance (UK). Published April 29, 2026, it covers how PECR, and where relevant the UK GDPR, apply to cookies, tracking pixels, device fingerprinting and similar technologies, with changes from the Data (Use and Access) Act. Its "statistical purposes" exception allows storage or access without consent when its sole purpose is statistics about how a service or website is used, to improve it; the ICO says it's about how the service is used, not who uses it. Sites relying on it still have to tell people and give a simple, free way to object, and a third-party tool may only act on the site's behalf. The exception doesn't allow monitoring or tracking individual visitors: the ICO lists logs or recordings of individual visitors and the actions they took, unless they're kept for security, among the things that need consent.
- What it means for your store. Keep your cookie banner on (Shopify's or Wix's) if visitors come from the EU or the UK (Session Recordings waits for it), make sure what visitors type into form fields is masked, say how long you keep replays and name recordings in your privacy notice. The free session recording privacy notice template covers each of those points.
What should a privacy policy say about session recording?
That you record visits, what a recording holds, how long you keep it and how visitors can say no, in words a visitor can follow in one read. Cover these points:
- Why. You record how visitors use the site, to find and fix problems.
- What's recorded. Pages viewed, clicks, scrolling and taps.
- What's masked. What visitors type into form fields, before it leaves the browser, and any exception, such as the words they submit in your store's search, which Session Recordings shows on Shopify.
- Who records. The service that records the visits.
- How long. Your retention period.
- How to say no. How visitors can decline, or change their mind, in your cookie settings.
- Who to ask. How to contact you with questions or a request to delete their data.
Here is a sample paragraph to adapt and have checked against the rules that apply to you. If your site has no cookie banner, drop the sentence about analytics cookies, since recording doesn't wait for a cookie choice.
We record how visitors use our site, such as the pages they view, clicks, scrolling and taps, so we can find and fix problems. Anything you type into a form is masked in your browser before it is sent, so we never see it. Pages are recorded as you saw them. We only record visitors who allow analytics cookies, and you can change your choice at any time in our cookie settings. We keep recordings for your retention period. To ask about your data or have it deleted, email your contact address.
On a Shopify store, also say that the words visitors submit in your store's search are recorded, since Session Recordings shows them.
How long to keep replays
Say how long you keep recordings, and keep it short enough to defend. Session Recordings keeps each replay 30 days. A starred replay stays past that until you un-star it or the app's data is erased (on Wix, from its Privacy page; on Shopify, by email or about a month after you uninstall), so if you star replays, add a line saying a few recordings may be kept longer to fix a problem.
Choosing a period and handling deletion requests step by step are covered in how long to keep session recordings.
Who can watch session replays?
You and the people you give access: collaborators on your Wix site's dashboard, or users of your Shopify admin whose role includes the app. A replay is as private as that list.
- One login per person. On Wix, go to Roles & Permissions in your site's dashboard, click Invite Collaborators, enter their email, tick a role and click Send Invites. On Shopify, go to Settings › Users in your Shopify admin, click Add users and assign a role. Separate logins let you remove one person without affecting anyone else.
- The narrowest role that does the job. Each role is a list of permissions, and Wix lets you build custom roles. On Shopify, a role can give access to all apps or only the apps you tick.
- Remove people when they leave. On Wix, in Roles & Permissions, hover over their name, click the More Actions icon and select Remove. On Shopify, users are managed under Settings › Users.
Replays live in Session Recordings, in your Shopify admin or your Wix dashboard, and never get a public link. To point a teammate to one, use Share on the replay: it writes an email with a link to it, or copies the link, and only people with access to your store in Shopify, or your site in Wix, can open it. Add the moment that matters, such as 1:42, so they can jump straight there.
Keep screenshots of replays out of public places, and crop anything personal before a presentation. Watch replays to improve the site, not to follow one person's visits out of curiosity.
Write down your team's rules
If more than one person watches replays, put the rules in a short note everyone can find.
- Why you watch replays, in one sentence
- Who can open the dashboard, and who decides that
- Where screenshots and notes from replays may be shared, and where they may not
- What to do if a replay shows something personal, such as a name in a greeting
- Who answers when a visitor asks about their data
A five-minute privacy check
Run through this once, and again whenever you change your site or your tools.
- Open your cookie banner's settings (Shopify: Settings › Customer privacy; Wix: Privacy & Cookies) and confirm a banner is on, or that you've chosen to run without one.
- In a private window, decline analytics and confirm no new visit appears in Replays.
- Read your privacy notice for recordings, masking, retention and how to opt out.
- Check that the retention period in your notice matches what your tool keeps: 30 days in Session Recordings, plus any replays you star.
- Review who has access (Wix's Roles & Permissions, or Settings › Users on Shopify) and remove anyone who no longer needs it.
- Find your data controls. On Wix, open Settings in Session Recordings and click Export or erase; the Privacy and data page that opens lets you download the app's settings and records for your site (replays themselves can't be downloaded) or erase everything it holds, replays included. On Shopify there's no erase page in the app: email support@myuser.ai for a copy or to erase everything, or uninstall, and your store's data is erased about a month later unless you reinstall.
Frequently asked questions
Do you need consent for session replay?
For visitors in the EU, generally yes: storing or reading information on their device for analytics needs consent first, which is what a cookie banner collects. In the US, wiretap lawsuits over session replay have turned on whether consent came before the recording started. Asking through your banner and recording only people who agree is the safer setup under both, and Session Recordings records that way whenever your site shows a banner.
Is session replay GDPR compliant?
A tool can't be compliant on its own. What you do with it decides. The GDPR expects a lawful basis such as consent, a clear notice, no more data than you need, a limited retention period and a way to act on requests to access or erase data. Masking typing in the browser and following your cookie banner cover part of that; the notice and the retention period are yours to write and keep.
Can session recordings capture passwords or card numbers?
Not in Session Recordings. Every form field is masked in the visitor's browser, passwords and email addresses included, so the characters never reach the recording. Card fields run by a payment provider usually sit outside your own pages as well, and on a Shopify store, checkout is never recorded. Pages that display personal details on their own still appear as the visitor saw them, such as an account area on a Wix site; on a Shopify store, customer account pages are never recorded.
Can a visitor ask you to delete their session recording?
Yes. Ask when they visited and find the visit in Replays by date and time. On a Wix site, unless they were signed in as a member, a visitor is listed as Visitor plus a short code; on a Shopify store, every visitor is. Open each candidate to check the pages, then use Delete replay in the player; it can't be undone. If you can't find a visit, email support@myuser.ai with its date and start time. To remove every replay at once, use Erase on the app's Privacy page on Wix, or email support@myuser.ai on Shopify. Where the GDPR applies, you have one month to respond, which can be extended by two months for complex or numerous requests.
Try it on your site
Session Recordings masks what visitors type into form fields before it leaves the browser and follows the choices visitors make in your cookie banner. See how private session recording works on a Shopify store or Wix site.
Sources
For the Shopify parts, checked October 29, 2026:
- Shopify Help: Configuring customer privacy settings
- Shopify Help: Inviting users
- Shopify Help: Store permissions (app permissions)
- Shopify Dev: Configure theme app extensions (not on checkout pages)
For Wix, the law and the regulators:
- Wix Help: Displaying a Usercentrics for Wix Cookie Banner
- Wix Help: Categorizing Your Custom Code
- Wix Help: Roles & Permissions: Inviting People to Collaborate on Your Site
- Hunton Andrews Kurth: EDPB Publishes Guidelines to Clarify Scope of EU "Cookie" Notice and Consent Requirements (2023)
- GDPR Article 5: Principles relating to processing of personal data
- GDPR Article 7: Conditions for consent
- GDPR Article 12: Transparent information and time limits for requests
- GDPR Article 17: Right to erasure
- Squire Patton Boggs (Privacy World): California Federal Court Dismisses Session Replay Litigation Following Ninth Circuit Remand (2023)
- Duane Morris: Ninth Circuit Reversal Expands Potential Liability for Companies Using Session-Replay Technologies in California (2025)
- Norton Rose Fulbright: State of Play in Website and Privacy Litigation (2024)
- CNIL: Session replay, the CNIL launches a public consultation on its draft recommendation (February 25, 2026; checked October 28, 2026)
- ICO: Final storage and access technologies guidance published (April 29, 2026; checked October 28, 2026)
- ICO: Guidance on the use of storage and access technologies (last updated April 29, 2026; checked October 28, 2026)
- ICO: What are the exceptions? The statistical purposes exception (checked October 28, 2026)



