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 addresses (e.g., [email protected]).
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).
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.
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.
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.
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:
- English - Español - Deutsch - 简体中文 - 繁體中文 - Français
- Português - 日本語 - Русский - 한국어 - Italiano - Tiếng Việt
- Polski - Türkçe - Bahasa Indonesia - Nederlands - Svenska
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.
Last updated
Was this helpful?