> For the complete documentation index, see [llms.txt](https://doc.dastra.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.dastra.eu/en/features/gerer-les-exercices-des-droits/document-redaction.md).

# Document redaction

When processing a data subject right request, it is common to have to share documents with the requester — identity copies, contracts, account histories, client files. These documents almost always contain confidential information that should not be disclosed: data relating to third parties, internal contractual data, or personal references.

Dastra includes a redaction tool directly inside the request processing workflow, without leaving the platform.

***

## How to access redaction

The redaction tool is available from the **Communication / Transmission** step of a request in progress, when an attachment is present or added.

1. Open a data subject request in progress
2. Go to the **Communication / Transmission** step
3. Select or add the document to be shared
4. Click **Redact document**

<figure><img src="/files/PyTTVZdpRSjxh2OEjNgA" alt="Request processing step with the original document to redact"><figcaption><p>Original attachment in the request processing step — ready to redact</p></figcaption></figure>

***

## AI-assisted redaction

When you launch redaction, the AI assistant analyses the document and **automatically detects zones likely to contain third-party personal identifiers**: names, addresses, contact details, identification numbers.

These zones are pre-selected and displayed on the document. Your team:

* **Removes false positives** with a click (incorrectly detected zones)
* **Manually adds** any zone the AI may have missed

<figure><img src="/files/XJnwG255hq41bkncnvSC" alt="AI analysis of a document, automatically detecting zones containing third-party identifiers"><figcaption><p>The AI analyses the document and automatically places the redaction zones to validate</p></figcaption></figure>

{% hint style="warning" %}
The AI result is a starting proposal, not a final decision. Every redaction zone must be reviewed and validated by a qualified person before the document is sent.
{% endhint %}

***

## Manual redaction

For teams that prefer to keep full control without AI assistance, **fully manual redaction** is available in the same interface. Select the zones to mask directly on the document.

<figure><img src="/files/DvGvJy1vywnR2p3U8EpO" alt="Manually selecting the zones to mask on a document"><figcaption><p>Draw the zones to redact yourself, directly on the document</p></figcaption></figure>

***

## Generating the redacted document

Once the review is complete, click **Generate redacted document**. The output document is:

* **Rasterised** — the underlying text is not simply hidden visually but made definitively inaccessible. It is not possible to extract redacted content from the final file.
* **Saved to the request** — the redacted document is attached to the request and available for sending.

The original can be kept or deleted based on your organisation's policy.

{% hint style="info" %}
Rasterisation-based redaction is the method recommended by data protection authorities. A simple visual mask (an opaque rectangle on a non-flattened PDF) can be circumvented and does not constitute compliant redaction.
{% endhint %}

***

## Best practices

* Always review the redacted document before sending to verify that no confidential information is visible.
* Keep the original in Dastra for your compliance file, unless your internal policy requires deletion.
* For large or complex documents (multi-page contracts, account statements), combine AI detection with a manual page-by-page review.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://doc.dastra.eu/en/features/gerer-les-exercices-des-droits/document-redaction.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.