> For the complete documentation index, see [llms.txt](https://library.zoom.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://library.zoom.com/business-services/zoom-revenue-accelerator/zoom-revenue-accelerator-explainer/data-privacy-and-security-in-zra.md).
# Data Privacy and Security in ZRA
### Participants will see in-product notifications in Zoom Meetings when Zoom Revenue Accelerator is on
Currently, users will see certain in-product notifications when recording with Zoom Revenue Accelerator is on. These notifications may be updated over time.
Audio participants will also hear a notification when joining a meeting by phone when Zoom Revenue Accelerator is enabled.
### Accounts with greater than 100 licenses can customize the Zoom Revenue Accelerator consent disclaimer
Similar to standard [recording disclaimers](https://support.zoom.us/hc/en-us/articles/360026909191-Customizing-the-recording-consent-disclaimer), Enterprise, API, Education, or Business accounts with 100+ licenses can [customize the Zoom Revenue Accelerator disclaimer](https://support.zoom.us/hc/en-us/articles/7977115380749-Managing-Zoom-IQ-recording-access-and-disclaimers-#h_01G923TYAVGSWDW5K4V8T8T55F) with additional text.
### Recording consent prompts are configurable to be triggered automatically before meetings launch
Account owners and admins can configure consent profiles that define the language and content of consent prompts displayed to participants before a meeting is recorded. Each consent profile may support multiple languages and be assigned to specific team members for granular management. Consent responses are logged and associated with participant records for auditing purposes.
When meetings are launched from integrated calendar applications including Outlook Calendar and Google Calendar, automated consent prompts can be presented to participants before the meeting begins.
### Admins can configure an account to prevent Zoom Revenue Accelerator from processing meetings or calls with specific contacts
Zoom Revenue Accelerator users may have conversations with certain contacts or accounts that do not wish their meetings or calls to be analyzed. In these cases, admins can configure recording access in [Account Settings](https://zoom.us/account/setting) under the **Zoom Revenue Accelerator** tab and list the domains of external meeting participants for which they want Revenue Accelerator to be blocked. Admins can also prevent Zoom Revenue Accelerator from automatically analyzing calls with specific phone numbers or number prefixes. Zoom Revenue Accelerator will then recognize those domains or phone numbers and prevent meetings attended by those users from being recorded for viewing and analysis.
### Users can set clips of recordings to expire, limit their visibility, or protect them with a password
Zoom Revenue Accelerator offers optional security features for recorded meeting and call clips. Specifically, users may [configure clips](https://support.zoom.us/hc/en-us/articles/10439780974861-Sharing-Zoom-IQ-clip-and-conversation) to expire after a set time period, restrict visibility to internal users only, or protect the clip behind a password.
### Zoom Revenue Accelerator data handling aligns with Zoom’s Privacy Statement
Zoom Revenue Accelerator analyzes data from cloud-recorded meetings and calls, and any data Zoom collects or processes aligns with [Zoom’s Privacy Statement](https://explore.zoom.us/en/privacy/).
### Conversations analyzed by Zoom Revenue Accelerator are not used to train Zoom’s or its third-party AI models
Zoom does not use any of your audio, video, chat, screen sharing, attachments, or other communications-like Customer Content (such as poll results, whiteboard and reactions) to train Zoom’s or its third-party artificial intelligence models.
### Data collected by Zoom Revenue Accelerator may be processed by its third party AI models, but will not be used to train or improve those AI models.
Zoom Revenue Accelerator data is stored by Zoom in Amazon Web Services (AWS), with analysis for most features performed by Zoom’s in-house services. Some Zoom Revenue Accelerator features, for example Email Compose, Generate a New Summary, Generate New Next Steps, and Generate New Good Questions currently use Zoom’s third-party AI models. For such features, data will be shared with third-party models (e.g., OpenAI) to provide the service once the admin enables the feature on the account and the user engages with the feature. The data is sent to the third-party model to generate the requested outputs (e.g., email copy, summaries, etc.), but the third-party model is not permitted to use this data to improve or train. Data may be temporarily retained by the third-party models for Trust and Safety purposes or to comply with legal obligations.
#### **Third-party analysis with Zoom Revenue Accelerator is disabled by default, and requires administrator opt-in to utilize third-party features**
By default, Zoom Revenue Accelerator does not utilize third-party models for analysis or processing. However, account administrators may opt in to third-party processing and analysis for additional features, such as Zoom AI message composition, and generating or regenerating new summaries, next steps, and good questions.
### Zoom Revenue Accelerator is globally available, across five regions
Zoom Revenue Accelerator currently supports operations in five global clusters, including: the United States (US01, US02, US03, US04, US06), Australia (AU01), Canada (CA01), Europe (EU01), and India (IN01). For customers with a region-specific account, Zoom Revenue Accelerator data storage and processing will persist in that region.
### User data stored in AWS is encrypted at rest
Zoom Revenue Accelerator customer data is encrypted at rest with a 256-bit AES-GCM algorithm, using encryption keys stored in AWS Key Management Service (AWS KMS).
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## 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, and the optional `goal` query parameter:
```
GET https://library.zoom.com/business-services/zoom-revenue-accelerator/zoom-revenue-accelerator-explainer/data-privacy-and-security-in-zra.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.