> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cognigy.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Data Protection & Analytics
Updated in 4.92
The *Data Protection & Analytics* section includes Endpoint settings for analytics and system logging. Here you can toggle whether you want to create and store data about contacts, and whether you want to collect analytics data for the Endpoint. If you choose to collect data, you can also configure whether you're masking sensitive data.
| Setting | Description |
| ---------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Contact Profiles | Collects individual [Contact Profiles](/ai/agents/analyze/contact-profiles) data to store user data across sessions. |
| Collect Analytics | Collects Analytics data for the Endpoint. The [Voice Gateway Endpoint](/ai/agents/deploy/endpoint-reference/voice-gateway) has [additional settings for collecting analytics data](#store-extensive-data-payloads-in-analytics). |
| Mask IP Address | Masks the IP address from the user in the [Input object](/ai/agents/develop/ai-agent-memory/input), [Insights](/insights/overview), and [Analytics](/ai/agents/analyze/overview). When this setting is activated, IP addresses are replaced by asterisks and aren't available through the [OData Analytics Endpoint](/ai/agents/analyze/odata). |
| Mask Sensitive Analytics | Masks sensitive information in the [Input object](/ai/agents/develop/ai-agent-memory/input), [Insights](/insights/overview), and [Analytics](/ai/agents/analyze/overview). Specifically, the `inputText`, `inputData`, and `userLanguageText` properties, and the user IP address are replaced with asterisks and aren't available through [Cognigy OData Analytics Endpoint](/ai/agents/analyze/odata). If you activate this setting, you can't use the [Intent Trainer](/ai/platform-features/nlu/intents/intent-trainer) because Cognigy.AI doesn't store the user's input text.
Additionally, you can use the Code Node to [ignore specific analytics](#ignore-specific-analytics-data). |
| Mask Sensitive Logging | Masks potential sensitive information in system logs on the [Logs](/ai/agents/test/logs) page. If you activate this setting, Cognigy.AI replaces the following log entries with asterisks: |
| Collect Conversations | Stores the conversation history in Contact Profiles. |
| Enable Input Sanitization | Activates server-side input sanitization. If you activate this setting, Cognigy.AI removes potentially harmful HTML content from user inputs before processing them in other parts of the system.
If you use [Input Transformers](/ai/for-developers/transformers/input-transformer), the sanitization takes place after their execution. This process involves validating and cleaning the data on the server to make sure the data is safe and complies with the expected format.
For [Webchat](/webchat/index), client-side input [sanitization](https://github.com/Cognigy/WebchatWidget/blob/master/docs/embedding.md#endpoint-settings) (`disableHtmlContentSanitization: false`) works by default. In this case, activating server-side input sanitization provides an additional layer of security for your server. |
| Hide References to External Resources in Transcripts | This setting removes tags that reference third-party APIs, such as `` for links and `![]()
` for images, from user inputs in conversation transcripts to protect users from risks associated with third-party content. In the Transcript explorer and Message explorer in Insights, conversation transcripts keep references to the content instead of rendering the actual links or images. For example, `
` or ``.
For the Interaction Panel, set `DISABLE_SKIP_URI_TAGS_IP_CONVERSATIONS: "true"` in `values.yaml` to hide references to external resources. |
| Dashbot | Allows you to integrate Cognigy.AI with [Dashbot](https://www.dashbot.io) using a Dashbot API key. Refer to the [Help Center Dashbot article](https://support.cognigy.com/hc/en-us/articles/360016311379) for a detailed description of how to set up the Dashbot integration. |
## Endpoint-Specific Settings
### Voice Gateway Endpoint
#### Store Extensive Data Payloads in Analytics
If you activate **Store Extensive Data Payloads in Analytics** in the [Voice Gateway](/ai/agents/deploy/endpoint-reference/voice-gateway) Endpoint, all the information from [Voice Gateway event](/voice-gateway/references/events/overview) payloads is stored in the Analytics database. You can access this information via [OData](/ai/agents/analyze/odata) or the [Transcript explorer](/insights/explorers/transcript) in Insights. You can activate this setting after you toggle on **Collect Analytics**. By default, the setting is disabled.
This setting allows you to store the following information:
* `trace_id`
* `account_sid`
* `application_sid`
* `call_id`
* `sip_status`
* `sip_reason`
* `originating_sip_ip`
* `local_sip_address`
* `service_provider_sid`
* `fs_sip_address`
* `api_base_url`
* `originating_sip_trunk_name`
## Ignore Specific Analytics Data
You can deactivate the logging of specific analytics data fields with a [Code Node](/ai/for-developers/code/analytics-data) using the `analyticsdata` object. For example:
```js theme={null}
analyticsdata.text = "overwritten text";
delete analyticsdata.data.token;
```
In this example, the Code Node deletes `token` from the analytics data before it's written to the database.
## More Information
* [Endpoints](/ai/agents/deploy/endpoints/overview)