> For the complete documentation index, see [llms.txt](https://docs.nullify.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nullify.ai/capabilities/code-reviews/secrets-detection/confidential-data-detection.md). # Confidential Data Detection Nullify inspects every diff for sensitive personal information that should never live in source control. When detected, the finding appears in the secrets channel with the relevant PII category and rotation guidance. ## Categories We Classify * Personal information: surnames, email addresses, phone numbers, postal addresses, dates of birth. * Financial information: payment card numbers and bank identifiers. * Location and identity data sourced from structured dumps or seed files. All detections currently focus on English-language datasets. ## Example Workflow 1. A developer commits a seed file containing realistic user records (`create.sql`). 2. Nullify analyses the diff, labels the exposure as **Personal Information**, and posts the finding to the dashboard. 3. The reviewer can remediate, suppress with justification, or convert the event into a campaign task. > 💡 PII detection is available to enterprise tenants on request. Contact your Nullify representative to enable it for your environment. --- # 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://docs.nullify.ai/capabilities/code-reviews/secrets-detection/confidential-data-detection.md?ask=&goal= ``` `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.