> 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/settings/capture-privacy-and-permissions.md). # Capture privacy and permissions Screendesk Screen Recorder captures the screen content you choose and can attach browser diagnostics. Review both before sharing. ## Camera, microphone, and screen access Camera and microphone permissions are requested when you set up those devices. Each device has a separate on/off toggle. For desktop recording, Chrome asks which screen, window, or tab to share. Your operating system may also require screen-recording permission. Choose the narrowest surface that includes what you want to show. ## Technical context Captures can include console logs, network requests, URLs, browser and device information, and interaction context. These can contain personal information or sensitive application data. Instant Replay masks form input values in the reconstructed page. That masking does not apply to pixels in screen recordings or screenshots, or guarantee that sensitive values are removed from logs or network requests. Close sensitive pages and notifications before recording. Review screenshots, the surrounding full screenshot for cropped captures, and attached diagnostics before uploading. ## Local captures and drafts The Instant Replay buffer and unfinished drafts are stored locally in your browser profile. Capture content is sent to your workspace when you choose **Upload**. Drafts expire after seven days. Local storage is not a backup. Clearing extension storage or removing the extension can remove unfinished captures. ## Settings you can control * **Manage Websites** controls where Instant Replay is enabled or blocked. * **Track user interactions** controls additional click and navigation context. * **Usage Analytics** controls usage analytics. Turning it off does not disable error and warning reporting. Read the [Screendesk privacy policy](https://security.screendesk.io/screendesk-privacy) for more information. --- # 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/settings/capture-privacy-and-permissions.md?ask=&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.