> For the complete documentation index, see [llms.txt](https://help.dscout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.dscout.com/study-basics/testing-prototypes/privacy-blur.md).
# Privacy blur
Study type
Availability
Usability tests
true
Intercept studies
true
AI moderated studies
true
Some studies let you record participant screens throughout an entire study. But in some cases, you may ask your participants to do something that exposes PII (personally identifiable information). You can still get the insights you need while maintaining their privacy by enabling privacy blur. With privacy blur enabled, you’ll still be able to hear participants’ audio but their screen will be blurred in their final response.
{% hint style="info" %}
**Note:** Heat maps and click data are not affected by the Privacy blur setting. This setting only blurs the participant's screen during analysis. Any task data that would normally be collected will still be collected.
{% endhint %}
Privacy blur is available on the following question types:
* Task.
* Checkpoint.
* Talk out loud.
Here’s how questions with privacy blur look when analyzing study responses:
{% hint style="info" %}
**Note:** If you’ve chosen to record a participant’s camera and their screen, you’ll still be able to see their camera in their response. Only the participant’s screen will be blurred.
{% endhint %}
**To enable privacy blur on a question:**
{% stepper %}
{% step %}
In your study, add or navigate to the question you want to blur. You can enable privacy blur on task, checkpoint, or talk out loud questions.
{% endstep %}
{% step %}
Under **Question settings**, toggle **Privacy blur** on.
{% endstep %}
{% endstepper %}
{% hint style="success" %}
**Tip:** Give your participants a heads up that a question will be blurred by including a note in the prompt. For example, *Note: The recording of your screen will be blurred for your privacy. Please navigate away from any sensitive information upon completing the task.* You can see this in the screenshot below.
{% endhint %}
Questions with privacy blur enabled will include a **Privacy blur** chip in the builder:
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.dscout.com/study-basics/testing-prototypes/privacy-blur.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 `automate deployments from our CI pipeline` 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.
