# Session replay

> Watch real visits play back like a video - every click, scroll, and rage-tap - with sensitive input masked by default.

Source: https://oakdata.co/docs/using/replay

---

**Session replay** turns a visit into a video you can watch: the pages they saw, where they moved and clicked, where they hesitated, and where it broke. It's the difference between knowing a metric dropped and *seeing* why.

••••••••••

0:121:48Inputs masked

A replay: the visitor's screen on tape, with a scrubber and event markers below.

## Finding a replay

Open **Replays** for the full list, or reach one in context: from a [person's profile](https://oakdata.co/docs/using/people), from an [event](https://oakdata.co/docs/using/events), or from an error - every recorded session links straight to its tape. Replays that hit an error or a rage-click are flagged so you can jump to the interesting ones.

## Input masking

Recording real screens means handling real data carefully. OakData masks the risky parts by default:

- **All inputs are masked** - text you type, passwords, card fields - captured as blocks, never characters.
- **You control the rest** - mark any element to mask, block, or explicitly allow, so you record exactly what you mean to.

> **Nothing sensitive leaves the browser** Masking happens in the SDK before anything is sent - masked content is never transmitted or stored. See [replay privacy](https://oakdata.co/docs/concepts/replay-privacy) for the masking model and the attributes that control it.

## Where to next

- [Replay privacy](https://oakdata.co/docs/concepts/replay-privacy) - The masking model and how to tune it.

- [People & visitors](https://oakdata.co/docs/using/people) - Jump from a profile straight to the tape.