> For the complete documentation index, see [llms.txt](https://docs.sdv.dev/rdt/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sdv.dev/rdt/transformers-glossary/deep-data-understanding/email.md).

# ＊ Email

{% hint style="info" %}
**＊SDV Enterprise Feature.** This feature is available to our licensed users and is not currently in our public library. For more information, visit our page to [Explore SDV](https://docs.sdv.dev/sdv/explore/sdv-enterprise/compare-features).
{% endhint %}

Email data represents email addresses associated with real users, businesses or other entities. Emails are a type of PII data. A key consideration is that **you do not want the real emails in your dataset to leak**. However, you may want to also **preserve key characteristics of emails** such as the top level or sub domain.

## Key Features

:earth\_americas: This sdtype **understands the domain** of email addresses. It can extract both the full and top domain in your data.

:unlock: This sdtype offers the novel [**Contextual Anonymization**](/rdt/resources/use-cases/contextual-anonymization.md) technique on emails that are Personal Identifiable Information (PII). 

## Browse Email Transformers

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td>＊ <a href="/rdt/transformers-glossary/deep-data-understanding/email/domainbasedanonymizer.md"><strong>DomainBasedAnonymizer</strong></a></td><td>Anonymize emails while preserving the domain.</td><td><a href="/rdt/transformers-glossary/deep-data-understanding/email/domainbasedanonymizer.md">＊ DomainBasedAnonymizer</a></td></tr><tr><td>＊ <a href="/rdt/transformers-glossary/deep-data-understanding/email/domainbasedmapper.md"><strong>DomainBasedMapper</strong></a></td><td>Psuedo-anonymize email data using a consistent mapping that preserves the domains.</td><td><a href="/rdt/transformers-glossary/deep-data-understanding/email/domainbasedmapper.md">＊ DomainBasedMapper</a></td></tr><tr><td>＊ <a href="/rdt/transformers-glossary/deep-data-understanding/email/domainextractor.md"><strong>DomainExtractor</strong></a></td><td>Extract domains from emails for data science use.</td><td><a href="/rdt/transformers-glossary/deep-data-understanding/email/domainextractor.md">＊ DomainExtractor</a></td></tr><tr><td><a href="/rdt/transformers-glossary/generic-pii-anonymization/anonymizedfaker.md"><strong>AnonymizedFaker</strong></a></td><td>Create fake, fully anonymous emails without considering the context.</td><td></td></tr><tr><td><a href="/rdt/transformers-glossary/generic-pii-anonymization/pseudoanonymizedfaker.md"><strong>PseudoAnonymizedFaker</strong></a></td><td>Create an use a reversible mapping without considering the context.</td><td></td></tr></tbody></table>


---

# 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.sdv.dev/rdt/transformers-glossary/deep-data-understanding/email.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.