> ## Documentation Index
> Fetch the complete documentation index at: https://docs.blackmountain.io/llms.txt
> Use this file to discover all available pages before exploring further.

# PII Protection

> How personal data is masked in your chats before it reaches the AI model

PII protection keeps personal data, such as names, email addresses and phone numbers, away from the AI providers. Before a message is sent, 48° finds personal data in it and in its attachments, and replaces each item with an encrypted token. The model only ever sees the tokens. You can still read the original values in your own chats.

PII protection is turned on for the whole organization by an administrator. You can't turn it on or off yourself. When it is on, you see **Personal Information Encryption activated** above the composer.

## What gets masked

48° detects these types of personal data in English and German text:

| Type | Example |
| - | - |
| **Person** | Names of people |
| **Email** | Email addresses |
| **Phone number** | Phone numbers |
| **Location** | Addresses, cities, places |
| **IBAN** | Bank account numbers |
| **Credit card** | Card numbers |
| **US SSN** | US social security numbers |
| **IP address** | IP addresses |
| **Custom** | Anything you mark yourself |

Detection works on your message text and on the text of attached documents. Chat titles are protected too.

## Review before sending

Every time you send a message, 48° shows **Confirm personal information before sending**. The dialog appears even when nothing was detected, so nothing is ever sent without your review.

1. Check the highlighted text in the **Message** tab and in a tab for each attached file.
2. To change a highlight, right-click it. Choose **Change type** or **Remove mask**.
3. To mask something that was missed, select the text, right-click it and choose **Mark selection as personal information**.
4. To remove all highlights in a tab, click **Clear all**.
5. Click **Confirm & send**.

The dialog shows how many items will be masked. If you close it, the message is not sent.

## How masked text looks

In the chat, every masked item appears as a green highlight. By default it shows the encrypted token, a long string of random characters, shortened to keep the chat readable. Hover over it to see the full token.

The model works with these tokens. It can refer to them, but it never sees the original values.

## Show the original values

To read the original values in a chat you own:

1. Click the eye icon next to **Personal Information Encryption activated** above the composer (**Show original personal information**).
2. The highlights now show the original text.
3. Click the icon again (**Hide original personal information**) to switch back.

Revealing only changes what you see in your browser. The stored chat stays masked, and nothing is sent to the model. Only the owner of a chat can reveal its original values.

## What changes when PII protection is on

* **Chat sharing** is unavailable. See [Sharing chats](https://docs.blackmountain.io/chat/sharing.md).
* **Voice input** is not available.
* If the protection service can't be reached, your message is not sent. 48° never falls back to sending unmasked data.

> [!WARNING]
>
> Scheduled tasks are not covered by PII protection. Their prompts and files are sent to the model as they are. See [Scheduled tasks](https://docs.blackmountain.io/scheduled-tasks/introduction.md).

> [!TIP]
>
> Detection is automatic but not perfect. Take a moment in the review dialog to check names, numbers and addresses that are specific to your business.

## Related

> [card] [Why is my text masked?](https://docs.blackmountain.io/faq/masked-text.md)
>
> Quick answers about masked text.

> [card] [PII enforcement (admin)](https://docs.blackmountain.io/admin/security/pii-enforcement.md)
>
> How administrators turn it on.

> [card] [Attachments](https://docs.blackmountain.io/chat/attachments.md)
>
> How files are processed.

> [card] [Data residency](https://docs.blackmountain.io/admin/security/data-residency.md)
>
> Where your data is processed.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.