> 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/o3.3-analyse-stakeholder-interests-and-implement-appropriate-safeguards.md).

# O3.3 Analyse stakeholder interests and implement appropriate safeguards

{% tabs %}
{% tab title="Principle" %}
[F3 Do not Exclude ](/safeguards/universal-dpi-safeguards-framework/principles/foundational-principles/f3-do-not-exclude.md)
{% endtab %}

{% tab title="Risk" %}
[SV2 Weak rule of law, ](/safeguards/universal-dpi-safeguards-framework/risks.md)

[RI3 Exclusion](/safeguards/universal-dpi-safeguards-framework/risks.md)
{% endtab %}

{% tab title="Life Cycle Stage" %}
[L1 Conception and scoping ](/safeguards/universal-dpi-safeguards-framework/life-cycle-stages.md)

[L5- Operations and Maintenance ](/safeguards/universal-dpi-safeguards-framework/responsible-authorities/r3-donor/l5-operations-and-maintenance.md)
{% endtab %}
{% endtabs %}

## Practices

> * Consider wider scenarios for data leakage, including potential vulnerabilities in data sharing and storage practices.
> * Analyse stakeholder interests and concerns to ensure safeguards align with their needs and expectations, particularly regarding data privacy and security.
> * Establish liability regimes for data leakage scenarios, clearly defining accountability and responsibilities to protect stakeholder interests.

##


---

# 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/o3.3-analyse-stakeholder-interests-and-implement-appropriate-safeguards.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.