# Data Restrictions

You can mask personal data, such as phone number and email address. If this setting is enabled, an error message will display when there is a masked value detected in a user's free-text response.

You can set data restrictions in the Pulse Insights Console by clicking on the <img src="/files/QCXJVDI5AOEdHuEOInsC" alt="" data-size="line"> menu and clicking “Data Restrictions”.  Then checking one or more of the following options:

* Masking enabled
* Phone number masked
* Email masked

Next, hit “Update” in the bottom right.

<figure><img src="/files/dJ4XE7T2GEYC0GYnwn4b" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Note: By default, personal data is allowed (masking is disabled) unless explicitly set in the Data Restrictions.
{% endhint %}

### Personal Information Detection & Error Messaging

Pulse Insights automatically monitors open-text responses in surveys to help prevent the collection of personally identifiable information (PII). If a response appears to include sensitive information, the user will see the following error message:

> **"Oops, looks like you are trying to submit personal information."**

This behavior is controlled at the account level via **Data Masking Settings**, and is enabled by default for all accounts with PII restrictions in place.

**Trigger Criteria**

The system triggers this error when open-text input contains patterns that match known PII formats. These include:

* **Email addresses**
* **Phone numbers**
* **Social Security Numbers (SSNs)** or similar government ID formats (U.S. or international)
* **Credit card numbers**
* **Driver’s license numbers**
* Any string containing a **large number of consecutive digits** (to detect structured numerical identifiers)

Detection is pattern-based and may vary slightly depending on regional formatting (e.g., U.S. vs EU identifiers), but it is primarily designed to catch sensitive data entry, not general personal information like names or dates.

**Customization**

The error message text can be customized for each free text question using the **Error Text** field in the Console. If no custom message is entered, the default system message will display.


---

# Agent Instructions: 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:

```
GET https://docs.pulseinsights.com/configuring-pulse-insights-console/account-level-settings/data-restrictions.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.