> For the complete documentation index, see [llms.txt](https://docs.screendesk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.screendesk.io/screen-recorder/record-and-capture/instant-replay/your-data-and-instant-replay.md).

# Your data & Instant Replay

What Instant Replay captures, what it doesn’t, and how Screendesk handles your data.

Instant Replay runs on websites you explicitly enable and keeps a short rolling buffer locally in your browser.

## Website controls

Use **Enable on this site** in the extension or **Settings → Manage Websites → Always Enabled Sites**.

Use **Blocked Sites** to keep a website disabled. Blocking takes precedence over enabling. Removing a site from Always Enabled Sites returns it to the default disabled state.

## Form input masking

Instant Replay masks form input values in the reconstructed page, including password inputs.

This applies to the page replay. It does not guarantee that sensitive information is removed from network requests, console logs, screenshots, or the pixels of a screen recording.

## Uploads and drafts

The replay buffer stays local. Choosing **Upload** sends the reviewed capture to your Screendesk workspace and creates a shareable link.

Choosing **Close** keeps the unfinished capture as a local draft. Drafts expire after seven days and do not sync between browser profiles or devices.

Capture storage is separate from usage analytics and error reporting. See [Capture privacy and permissions](/screen-recorder/settings/capture-privacy-and-permissions.md) and the [privacy policy](https://security.screendesk.io/screendesk-privacy).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.screendesk.io/screen-recorder/record-and-capture/instant-replay/your-data-and-instant-replay.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.