> For the complete documentation index, see [llms.txt](https://wiki.privai.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.privai.cloud/ecosystem-components/identity-defense.md).

# Identity Defense

Identity Defense modules help users understand off-chain exposure that can create Web3 risk. The goal is to reduce doxxing, phishing, SIM-swap, and account-takeover risk without turning the product into a credential dumping tool.

## What It Helps Answer

* Is an email, username, domain, or phone number exposed in public or breach-derived sources?
* Are usernames reused across accounts that should stay separate?
* Does public identity data connect back to Web3 activity?
* What practical steps should the user take to reduce exposure?

## Active Modules

| Module                       | Purpose                                                                                                       | Status     |
| ---------------------------- | ------------------------------------------------------------------------------------------------------------- | ---------- |
| **breach\_intel.lookup**     | Checks breach and credential exposure for emails, usernames, domains, and phone numbers with redacted output. | MVP active |
| **phone\_privacy.lookup**    | Reviews phone metadata without displaying the raw number.                                                     | MVP active |
| **social\_exposure.inspect** | Reviews public profile, domain, reputation, and linkage signals without running breach/password lookups.      | MVP active |
| **privacy\_plan.aic**        | Generates practical privacy hygiene steps from saved scan results.                                            | MVP active |

## Redaction Policy

Credential values must be sanitized before display. PRIVAI should help users understand exposure and rotate affected accounts without exposing passwords, secrets, or sensitive raw records.

| Data Type                 | Display Approach                                                                 |
| ------------------------- | -------------------------------------------------------------------------------- |
| **Passwords and secrets** | Never display raw values.                                                        |
| **Phone numbers**         | Redact or partially mask where possible.                                         |
| **Emails and usernames**  | Show enough context for user recognition, while avoiding unnecessary disclosure. |
| **Breach details**        | Summarize source, category, and recommended action.                              |


---

# 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://wiki.privai.cloud/ecosystem-components/identity-defense.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.