> For the complete documentation index, see [llms.txt](https://docs.material.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.material.security/email-protections/email-redaction.md).

# Email Redaction

Email Redaction identifies and redacts sensitive content (PII, financial data, legal documents, etc.) archived in user mailboxes. Users can still access messages on-demand in their mailbox after an authentication step.

### About Email Redaction <a href="#h-about-data-protection" id="h-about-data-protection"></a>

Email Redaction automatically identifies and redacts sensitive messages in mailboxes and allows them to be accessed on-demand, when needed by users after they verify their identity via an authentication step. Time to redact and the type of content protected is flexible and can be specified based on your company’s security policies. Message retrieval is immediate after a user completes a simple verification step (e.g., Okta Verify Request).

Material logs every message retrieval. To review them, from the left navigation expand **Email Redaction**, then click **Message Access Log**. To see where redaction stands and how it's changing over time, including an estimate of how many messages are currently redacted and how often users request access, from the left navigation expand **Email Redaction**, then click **Report**.

Other solutions, like DLP filters, block emails in transit but ignore the thousands of sensitive messages in your users’ mailbox archives. If an attacker (or malicious insider) gains access to an inbox, this at rest sensitive content is at risk of being exfiltrated. This forces an impractical trade-off between the security risk of retention and the productivity hit of deletion.

With Email Redaction, you can add a layer of protection to sensitive content while still keeping it accessible when needed. This protection can be enabled wall-to-wall or for a subset of accounts or groups.

### Deployment <a href="#h-deployment" id="h-deployment"></a>

See the [Deployment Guide](/getting-started/deployment-guides/your-first-30-days/6-enable-email-remediation.md).

### FAQ <a href="#h-faq" id="h-faq"></a>

#### Where does sensitive content go after being redacted? <a href="#h-where-does-sensitive-content-go-after-being-redacted" id="h-where-does-sensitive-content-go-after-being-redacted"></a>

Messages are stored in a storage bucket inside your private, dedicated Material cloud instance. When a user retrieves a message or if Email Redaction is disabled for a user, messages are returned to the mailbox in their original form (including attachments, message metadata, etc.).

#### Can Email Redaction be disabled after-the-fact? <a href="#h-can-data-protection-be-disabled-after-the-fact" id="h-can-data-protection-be-disabled-after-the-fact"></a>

Yes, you can disable Email Redaction at any time, which restores all redacted messages.

#### What messages are considered sensitive? <a href="#h-what-messages-are-considered-sensitive" id="h-what-messages-are-considered-sensitive"></a>

Material has built-in [Sensitive Content Categories](/detections/sensitive-categories.md) that are automatically identified and protected. Admins can enable or disable built-in categories and define their own categories.

#### Can users still search for redacted messages in their email? <a href="#h-can-users-still-search-for-redacted-messages-in-their-email" id="h-can-users-still-search-for-redacted-messages-in-their-email"></a>

Users can search for messages by subject, recipients, date and other message metadata that is preserved post-redaction.

### Additional Resources <a href="#h-additional-resources" id="h-additional-resources"></a>

* [Deployment Guide](/getting-started/deployment-guides/your-first-30-days/6-enable-email-remediation.md)
* [Sensitive Content Categories](/detections/sensitive-categories.md)
* [Grace Periods](/email-protections/email-redaction/grace-periods.md)


---

# 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://docs.material.security/email-protections/email-redaction.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.