> For the complete documentation index, see [llms.txt](https://docs.aquilax.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aquilax.ai/user-manual/scanners/pii-scanner.md).

# PII Scanner

PII Scanning refers to the automated identification of personally identifiable information (PII) within your code and data repositories. PII includes sensitive data such as names, addresses, phone numbers, Social Security numbers, and more. If exposed, this data can be exploited by attackers for identity theft, fraud, or phishing.\\

AquilaX AI’s PII Scanner is designed to identify potential leaks or exposure of such sensitive data, reducing the risk of compliance violations (e.g., GDPR, HIPAA) and protecting your customers. By using advanced ML-driven techniques, AquilaX ensures that organizations can proactively address PII exposure before it becomes a liability.

**Why PII Scanning Matters:**

• Ensure compliance with data privacy laws (GDPR, HIPAA).

• Prevent identity theft and fraud.

• Protect your brand from reputational damage.


---

# 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.aquilax.ai/user-manual/scanners/pii-scanner.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.