> For the complete documentation index, see [llms.txt](https://docs.syntho.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.syntho.ai/overview/get-started/syntho-bootcamp/4.-pii-scan.md).

# 4. Sensitivity scan

Syntho provides a built-in sensitivity scanner to identify potentially sensitive columns. Review results to support privacy compliance and prevent accidental exposure.

You can run a [shallow scan](/configure-a-data-generation-job/privacy-dashboard/automatic-pii-discovery-with-pii-scanner.md#shallow-scan-uses-metadata) (faster, based on metadata) or a [deep scan](/configure-a-data-generation-job/privacy-dashboard/automatic-pii-discovery-with-pii-scanner.md#deep-scan-uses-metadata--data) (more accurate, inspects data contents using NLP).

{% hint style="warning" %}
**Important:** Review sensitivity scanner results manually. Some columns may be falsely flagged or missed.
{% endhint %}

***

### Interactive guide: Start the sensitivity scanner

Follow the interactive guide to run your first sensitivity scan.

{% embed url="<https://www.guidejar.com/guides/14115eb8-62b8-41a1-b382-43a0bd19bd05>" %}

***

### Scan modes explained

| Scan Type                                                                                                                                 | Description                                                             | Speed  | Accuracy                                   |
| ----------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------- | ------ | ------------------------------------------ |
| [Shallow Scan](/configure-a-data-generation-job/privacy-dashboard/automatic-pii-discovery-with-pii-scanner.md#shallow-scan-uses-metadata) | Uses column names and regex rules to infer sensitive entities           | Fast   | Medium                                     |
| [Deep Scan](/configure-a-data-generation-job/privacy-dashboard/automatic-pii-discovery-with-pii-scanner.md#deep-scan-uses-metadata--data) | Analyzes actual data content using NLP models (for string/text columns) | Slower | Higher (but possibly more false positives) |

#### What to watch for

* Red sensitive column headers: These columns are flagged but not yet handled.
* Exclamation mark (!) next to a table: At-risk sensitive columns remain in [Duplicate](/configure-a-data-generation-job/configure-column-settings/duplicate.md) mode.

#### To resolve

* Apply a [Mocker](/configure-a-data-generation-job/configure-column-settings/mockers.md)
* Or [exclude](/configure-a-data-generation-job/configure-column-settings/exclude.md) the column from data generation


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.syntho.ai/overview/get-started/syntho-bootcamp/4.-pii-scan.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
