Some analytics dashboards do not just tell a site owner that you visited a page.
They can reconstruct how you moved through it.
That category is usually called session replay.
The name sounds like a screen recording, but many systems do not capture literal video. They record enough page structure and interaction events to rebuild an animation of the visit later.
Microsoft Clarity describes its own recordings this way: the service captures page information from the DOM along with user actions such as mouse movements, clicks, and scrolling, then reconstructs the session for playback. See Microsoft Clarity’s current FAQ.
The browser becomes a source of choreography
A replay can show where the visitor moved the pointer.
Where they clicked.
How far they scrolled.
Which page state appeared after a menu opened.
How long they hesitated before moving elsewhere.
For usability work, that can be genuinely useful. A developer can discover that visitors repeatedly click something that is not a button, fail to notice a form field, or abandon a page at the same confusing step.
The privacy issue is that interaction detail can reveal much more than an ordinary page-view counter.
Redaction determines what the recording actually contains
Modern session-replay products usually include masking controls.
Microsoft says Clarity masks sensitive content by default, always masks text entered in input boxes and drop-downs, and lets administrators choose stricter or looser masking for other page elements. It also says masked content is not uploaded to Clarity. See Clarity’s masking documentation.
That is an important distinction.
Saying this site uses session replay does not tell you exactly what sensitive information was captured.
You need to know the product, version, configuration, page structure, and masking rules.
A properly configured system may exclude fields that would be dangerous to record.
A poorly configured one can expose much more.
Visitors usually see the interface, not the recorder
The strange part is psychological.
A person experiences an ordinary webpage.
They do not necessarily experience it as a recording surface.
Nothing about scrolling halfway down an article feels like a deliberate disclosure of behavioral data.
Yet those movements can become analytics events.
That gap between interface and instrumentation is central to the Surveillance Economy.
A click can be both an action and a measurement.
A pause can be both indecision and a data point.
The replay does not need a camera.
The webpage already knows enough about its own behavior to reconstruct much of what happened.