> 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/risks.md).

# Risks

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXclDlqhCLPktrffjprb7tMmstbJGu-awQkHO78-4vAeWU90QfnBCTG0EmJnmcVJefNyIO79BJJY6ntr0hYiESWtiqBw6IOiMvbI1zPSAaYEjNRjnFxy8L6WRvAgu_HzCLArnvv_BVI3db1mo93Jmw3EEpYVEIV69oh7JLtZkYImN15Ax2P7cyo?key=X5_tqiPrckjKLwzeEqNY4A" alt=""><figcaption></figcaption></figure>

DPI systems comprise standards (including protocols), technological systems and services that operate at the intersection of individuals on the one hand, and public and private entities that hold institutionalized political and economic power, on the other. Risks therefore derive from failures and inadequacies in the overarching legal, regulatory and ethical (normative) frameworks in which they operate, encompassing all organizations and stakeholders that have a role related to DPI service delivery. Risks also lie within the technological systems themselves.&#x20;

RS1. Privacy vulnerability

RS2. Digital insecurity

RS3. Physical insecurity

RS4. Lack of recourse

RI1. Discrimination

RI2. Unequal access

RI3. Exclusion

RI4. Disempowerment

SV1. Digital distrust

SV2. Weak rule of law

SV3. Weak institutions

SV4. Technical shortcomings

SV5. Unsustainability


---

# 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/risks.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.