> For the complete documentation index, see [llms.txt](https://safedpi.gitbook.io/safeguards/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://safedpi.gitbook.io/safeguards/universal-dpi-safeguards-framework/processes/f6.4-design-user-interfaces-that-empower-subjects-with-clear-and-continuous-control-over-their-data.md).

# F6.4 Design user interfaces that empower subjects with clear and continuous control over their data

{% tabs %}
{% tab title="Principle" %}
[F6 Promote autonomy and agency](/safeguards/universal-dpi-safeguards-framework/principles/foundational-principles/f6-promote-autonomy-and-agency.md)
{% endtab %}

{% tab title="Risk" %}
[RI4 Disempowerment](/safeguards/universal-dpi-safeguards-framework/risks/risks-to-inclusion.md)
{% endtab %}

{% tab title="Life Cycle Stage" %}
[L2 Strategy and Design](/safeguards/universal-dpi-safeguards-framework/responsible-authorities/r3-donor/l2-strategy-and-design-old.md)
{% endtab %}
{% endtabs %}

## Practices

> * Implement human-centred design techniques to create interfaces that offer explicit and ongoing consent options, ensuring that users can easily manage their data preferences.
> * Conduct A/B design testing with focus groups to determine which UX choices enable the most autonomy and agency.
> * Monitor UX designs to prevent the use of dark patterns.

## Resources

<table data-view="cards"><thead><tr><th></th><th></th><th></th></tr></thead><tbody><tr><td></td><td><mark style="color:yellow;"><strong>Case Study</strong></mark></td><td>( to come soon..)</td></tr><tr><td></td><td><mark style="color:yellow;"><strong>References</strong></mark></td><td></td></tr></tbody></table>


---

# 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://safedpi.gitbook.io/safeguards/universal-dpi-safeguards-framework/processes/f6.4-design-user-interfaces-that-empower-subjects-with-clear-and-continuous-control-over-their-data.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 `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.