# Security and Privacy Settings

This section provides an overview of AI Companion’s Security and Privacy settings.

### Redact Personal Data for Meeting Summary

Account admins can redact certain personal data from a meeting summary using Zoom’s pre-defined entity types. Zoom's Personal Data Redaction Service automatically identifies and redacts sensitive personal information within meeting summaries to help maintain privacy and compliance. When applying these settings, these changes are applicable only for future recordings/transcripts and historical data (i.e., past meeting summaries) will not be updated.

| **Entity Type**                                                      | **Description**                                                                     |
| -------------------------------------------------------------------- | ----------------------------------------------------------------------------------- |
| **DATE\_TIME**                                                       | Universal date and time information.                                                |
| **DRIVER\_ID**                                                       | Driver's license numbers, consisting of alphanumeric characters.                    |
| **EMAIL**                                                            | Email addresses (e.g., <user@example.com>).                                         |
| **INTERNATIONAL\_BANK\_ACCOUNT\_NUMBER**                             | IBAN numbers, with country-specific formats.                                        |
| **IP\_ADDRESS**                                                      | IPv4 addresses (e.g., 198.51.100.0).                                                |
| **LICENSE\_PLATE**                                                   | Vehicle license plates, typically 5–8 uppercase letters/numbers.                    |
| **MAC\_ADDRESS**                                                     | Unique identifier for network interfaces (NIC).                                     |
| **NAME**                                                             | Individual's names, excluding titles or organization/address names.                 |
| **PASSWORD**                                                         | Alphanumeric passwords (e.g., *special#pass*).                                      |
| **PHONE**                                                            | Phone, fax, or pager numbers.                                                       |
| **PIN**                                                              | Four-digit personal identification numbers.                                         |
| **SWIFT\_CODE**                                                      | Standard bank identifier code used for international transfers.                     |
| **URL**                                                              | Web addresses (e.g., [www.example.com](http://www.example.com/)).                   |
| **USERNAME**                                                         | Account login names, screen names, nicknames, or handles.                           |
| **VEHICLE\_IDENTIFICATION\_NUMBER (VIN)**                            | Unique vehicle identifier numbers (ISO 3779 specification).                         |
| **BANK\_ACCOUNT\_NUMBER** *(Country-specific)*                       | US bank account numbers (typically 10–12 digits). Also recognizes last four digits. |
| **BANK\_ROUTING** *(Country-specific)*                               | US bank routing numbers (typically 9 digits). Also recognizes last four digits.     |
| **PASSPORT\_NUMBER** *(Country-specific)*                            | US passport numbers (6–9 alphanumeric characters).                                  |
| **US\_INDIVIDUAL\_TAX\_IDENTIFICATION\_NUMBER** *(Country-specific)* | US ITIN numbers (9 digits, starts with "9," fourth digit "7" or "8").               |
| **SSN** *(Country-specific)*                                         | US Social Security Numbers (9 digits). Also recognizes last four digits.            |

<figure><img src="https://1175968039-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FctBXUMeBy4rtLMmMkKRG%2Fuploads%2Fgit-blob-43c185e284c0c7f8e3d24225e070560c23bd814e%2Fimage133.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

{% hint style="info" %}
**Note**

This feature requires a support ticket to enable.
{% endhint %}

### Block Sensitive Information for Meeting Summary

Account administrators can help prevent sensitive information from appearing in meeting summaries by configuring custom regular expressions. These regular expressions must follow Java's regex syntax and conventions. By defining specific patterns, admins can precisely control and automatically block the inclusion of sensitive phrases, numbers, or any other data types within meeting summaries.

For example,

* To block credit card numbers, a Java regex like **\b(?:\d\[ -]\*?){13,16}\b** could be used.
* To block a specific phrase such as "internal use only," a Java regex like **(?i)internal use only**(case-insensitive) could be applied.

Admins should ensure that regular expressions are thoroughly tested and validated to avoid inadvertently blocking non-sensitive or relevant meeting content.

<figure><img src="https://1175968039-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FctBXUMeBy4rtLMmMkKRG%2Fuploads%2Fgit-blob-7c98da199cd7092cabbe5e3a680e068359b3a10a%2Fimage21.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

{% hint style="danger" %}
**Warning**

Sensitive information may not be fully blocked by this setting. When sensitive information is blocked, the original, unredacted meeting summary can no longer be retrieved and accuracy may be impacted.
{% endhint %}

{% hint style="info" %}
**Note**

This feature requires a support ticket to enable.
{% endhint %}

### Custom Disclaimer

Account administrators can configure a Custom Disclaimer prompt to display custom messages to users before they access certain content or features. Disclaimers can be tailored separately for internal and external audiences, allowing admins to present different messages based on the user's audience type. Additionally, admins can require explicit user consent before proceeding.

The Custom Disclaimer prompt supports multiple languages, allowing organizations to cater to diverse, multilingual audiences. Supported languages include:

| <p>- English<br>- Español<br>- Deutsch<br>- 简体中文<br>- 繁體中文<br>- Français</p> | <p>- Português<br>- 日本語<br>- Русский<br>- 한국어<br>- Italiano<br>- Tiếng Việt</p> | <p>- Polski<br>- Türkçe<br>- Bahasa Indonesia<br>- Nederlands<br>- Svenska</p> |
| ---------------------------------------------------------------------------- | ------------------------------------------------------------------------------- | ------------------------------------------------------------------------------ |

When creating the disclaimer(s), administrators must manually provide translated versions of the disclaimer messages for each desired language and audience (internal/external). The Zoom web portal does not provide an automated translation mechanism, so translations must be completed externally before being configured in the Custom Disclaimer’s settings.

<figure><img src="https://1175968039-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FctBXUMeBy4rtLMmMkKRG%2Fuploads%2Fgit-blob-e0339af845676370c7b7d02a249fee2d5c00c1d7%2Fimage38.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>


---

# 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://library.zoom.com/zoom-workplace/artificial-intelligence/artificial-intelligence-bluepaper/ai-companion/security-and-privacy-settings.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.
