> For the complete documentation index, see [llms.txt](https://help.nightfall.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.nightfall.ai/faqs/nightfall_data_types_classification.md).

# What types of data does Nightfall classify?

Nightfall classifies over 100+ types of sensitive data, including forms of personally identifiable data (PII), protected health information (PHI), payment card information (PCI), credentials & secrets, and more. For example, email addresses, credit card numbers, social security numbers, API keys, passwords, and many more. These data types support compliance regimes like HIPAA, GDPR, HIPAA, PCI-DSS. Likewise, Nightfall’s detectors apply to a broad variety of industries and geographies (countries in US, EMEA, APAC, etc.).

Nightfall also supports custom detectors, as well as features such as context rules & exclusion rules that enable you to further tune detectors to your specific business needs and increase accuracy. Contact us at <sales@nightfall.ai> to determine if Nightfall supports detectors that meet your needs.


---

# 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://help.nightfall.ai/faqs/nightfall_data_types_classification.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.