> For the complete documentation index, see [llms.txt](https://knowledge.whiteintel.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.whiteintel.io/basics/consumer-records.md).

# Consumer Records

Consumer Records represent credential exposures that **do not belong to the organization’s corporate domain**.\
For example, when monitoring **acme.com**, any leaked account that is **not** in the format **`<user>@acme.com`** is classified as a Consumer Record.

This includes:

* Personal email addresses (e.g., Gmail, Yahoo, Outlook) used by employees or third-party users
* Accounts identified **only by usernames** with no associated corporate email
* Credentials originating from infostealer infections or breached platforms where users signed up using non-corporate identities

By separating Consumer Records from corporate-domain leaks, Whiteintel enables organizations to clearly identify **direct corporate exposures** while still assessing potential risks such as password reuse, supply-chain access, and lateral movement.


---

# 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://knowledge.whiteintel.io/basics/consumer-records.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.