# O3.23 Establish robust data delinking mechanisms

{% tabs %}
{% tab title="Principle" %}
[O3: Ensure data privacy by design](https://safedpi.gitbook.io/safeguards/universal-dpi-safeguards-framework/principles/operational-principles/o3-ensure-data-privacy-by-design)
{% endtab %}

{% tab title="Risk" %}
[RS1 Privacy vulnerability](https://safedpi.gitbook.io/safeguards/universal-dpi-safeguards-framework/risks/risks-to-safety)
{% endtab %}

{% tab title="Life Cycle Stage" %}
[L2: Strategy and Design](https://safedpi.gitbook.io/safeguards/universal-dpi-safeguards-framework/life-cycle-stages)
{% endtab %}
{% endtabs %}

## Practices

> * Use automated scripts that routinely delink identifiers from datasets after data processing is complete, as practiced in some Nordic countries’ privacy frameworks.
> * Implement temporary session identifiers in online services that expire after the session ends. Pairwise pseudonymous identifiers should be used wherever possible to prevent correlation of user data across interactions.

## Resources

<table data-view="cards"><thead><tr><th></th><th></th><th></th></tr></thead><tbody><tr><td>References</td><td></td><td></td></tr></tbody></table>


---

# Agent Instructions: 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 current page URL with the `ask` query parameter:

```
GET https://safedpi.gitbook.io/safeguards/universal-dpi-safeguards-framework/processes/o3.23-establish-robust-data-delinking-mechanisms.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.