Leexi on iOSLeexi on Android

Zoom and GDPR: Rules and Settings to Verify for Your Meetings

  • Where Zoom processes your data, who accesses recordings, and what to verify before enabling AI: sources and settings for your organization.
Try for free
Where Zoom processes your data, who accesses recordings, and what to verify before enabling AI: sources and settings for your organization.

Zoom offers settings and commitments to govern your meeting data. Their scope depends on your plan, your account infrastructure, and the features enabled. To review your use under the GDPR, verify the applicable contract, processing locations, participant notices, and access to recordings. Storage region. Global DPA, November 2024.

Selecting a storage region applies to certain recorded data. Live streams and AI features have their own scope. A summary sent to guests or a file downloaded to a computer must also be included in your tracking. Your verification must cover this entire lifecycle, from collection to the deletion of copies. Live streaming data centers. AI summary settings.

This page is published by Leexi and concerns Zoom Meetings, its recordings, and AI features used in meetings. It is based on official sources consulted on 5 November 2026. It describes the applicable framework and does not constitute legal advice. Public documents should be reviewed alongside your contract and settings.

Where Zoom Stores and Processes Your Meeting Data

Local Recording and Cloud Recording

A local recording creates files on the computer used. Cloud recording stores files in the Zoom account, where they can be viewed or downloaded according to granted permissions. Plans and permissions govern these capabilities. Local recording. Cloud recording.

Identify the mode used in your organization. For a local file, include the destination folder and its backups in your inventory. For a cloud file, identify the owning account and the access rights granted. A download creates an additional copy whose lifecycle must be tracked separately.

Storage Region Selection and Affected Plans

Zoom documents a choice of storage region for certain data belonging to paid accounts, including cloud recordings. This selection does not apply uniformly to all service data. Account provisioning may also alter the options available in the portal. Storage region.

Ask your administrator to determine the effective region and covered categories. Retain proof of the setting and verify its scope for the accounts organizing your meetings. The location of your company address alone is not sufficient to determine where files are stored.

Data Centers Used During Meetings

The data centers selected for meetings govern the processing of live streams when your account hosts the meeting. The provisioning region remains included in the selection. This setting is distinct from the storage location of recordings. Live streaming data centers.

Identify the authorized regions for live streams and identify the organization hosting the meeting. For a meeting hosted by a third party, request clarification on the applicable settings. A screenshot of your own settings does not reflect the configuration of that host's account.

Data and Transfers Outside the Selected Scope

Certain data categories remain outside the scope of the storage selection described in general documentation. Zoom also offers a European infrastructure dedicated to eligible Education and Enterprise accounts. The April 2026 datasheet describes exceptions relating to global services, including support, security, and platform operations. Storage region. European infrastructure, April 2026 datasheet.

Obtain confirmation of the infrastructure used by your account. Then review the documented exceptions and connected applications. Any conclusion regarding localization must specify the data and features it covers.

To prepare participant notices and capture methods, consult obligations related to recording a meeting. This guide complements Zoom's technical settings.

Participant Information and Recording Settings

Purpose, Legal Basis, and Privacy Notice

Define why you are recording the meeting and how you will use the file. The notice must explain this processing to participants, specifying the recipients, retention period, and procedures for exercising rights. GDPR, Article 13.

GDPR, Article 13(1)(c): "the purposes of the processing for which the personal data are intended as well as the legal basis for the processing" (unofficial translation).

Your notice must therefore link the recording to an identified purpose and legal basis. Have this basis reviewed according to the context of the meeting; using the software does not determine it. GDPR, Articles 5 and 6.

GDPR, Article 6(1): "at least one of the following applies" (unofficial translation).

Document the selected condition before deploying recording for this purpose.

Consent Prompts in Zoom and Opt-Out Options

Zoom displays a consent prompt when recording starts or when an individual joins an already recorded meeting. The workflow depends on the device and account settings. The documentation notes that participants who are already active on audio or video may remain so while this prompt is displayed. Recording consent prompt.

Test the workflow on the devices used by your team. Verify the message displayed, the options offered, and what occurs when an individual leaves the meeting. This technical check complements the notice and the review of the legal basis described above.

Host, Co-host, and Participant Rights

Permissions differ between local recording and cloud recording. For cloud recording, host and co-host roles determine who can initiate recording. Permissions granted to participants must be reviewed separately for local capture. Local recording. Cloud recording.

Assign permissions based on the individuals required to record. Also verify the settings enforced by the administrator: a user may see an option without being able to modify it. Run a test with the roles actually used during your meetings.

Retention and Sharing of Zoom Recordings

Retention Periods and Deletion Rules

Zoom allows cloud recording deletion to be scheduled after a specified number of days. Exceptions may preserve certain files. Verify these exceptions when applying your retention policy. Deletion and trash.

GDPR, Article 5(1)(e): "kept in a form which permits identification of data subjects for no longer than is necessary for the purposes" (unofficial translation). GDPR, Articles 5 and 6.

The duration must correspond to the documented use of the recording. Define who can authorize an exception and for what operational need. The deletion setting must be monitored alongside the other stages of the file lifecycle, including the trash and exported copies.

The Trash Folder and Local Copies

When the trash feature is enabled, a deleted recording remains recoverable for 30 days. When disabled, the file bypasses this step. Zoom also describes a grace period in the operation of automatic deletion. Deletion and trash.

Test the deletion workflow within your account. Downloaded files, local recordings, and their backups require separate tracking. Include these locations in your policy to prevent a file deleted from the portal from remaining available in a shared folder.

Share Links, Downloads, and Guest Access

Zoom provides several audience options for recordings, including account users, specific domains, or designated individuals. Also verify download permissions, access passcodes, and link expiration. Link expiration applies to shared access; it does not constitute deletion of the file. Sharing recordings.

A recording added to a Zoom Video Management channel may be subject to additional access through that channel. Check where it is published, then test permissions using an external account. Also consider copies already distributed to recipients.

How Zoom AI Features Use Your Meeting Data

Data Used for Summaries and In-Meeting Questions

AI features do not all process the same data. Zoom documentation associates summaries with speech transcripts, and in-meeting questions with transcripts and submitted prompts. Additional content may be involved depending on the feature and enabled options. AI feature data processing.

Compile an inventory of the features used by your team. For each feature, record the input data, generated output, and individuals authorized to view it. This distinction allows a post-meeting summary to be assessed separately from a response generated during the exchange.

Model Providers and Processing Options

Zoom describes several options: Zoom-hosted models only, the ZM+ option, and a federated approach. The ZM+ option combines models hosted in Zoom infrastructure and models accessed through Amazon Bedrock according to documented scope. Available features may be limited depending on the chosen option. AI data residency options.

Confirm which option applies to your account. Request processing locations and the providers associated with the features you intend to enable. A page presenting an available option does not prove that it is already configured for your organization.

Non-Training Commitments and Documented Retention Limits

Zoom states that it does not use covered communication content to train its models or third-party models. Its documentation also describes zero retention with model providers, subject to limited trust and safety exceptions. AI feature data processing.

This commitment regarding training does not, on its own, determine how long a summary is stored. Verify Zoom data retention, processing by providers, and output retention separately. Compare public statements with the documents governing your contract.

Summary Recipients and Enabled Integrations

Automated summary sharing can be set to the host only, co-hosts, internal invitees, or all invitees, including external participants. Zoom offers a setting to restrict external sharing. The notification may contain the summary directly or a link requiring authentication. AI summary settings.

Designate the recipients before enabling the feature for a team. Also check what connected applications receive. A summary contains information derived from the meeting: its distribution must form part of your access review, even when the recording remains private.

Zoom Contractual Commitments and Certifications

The DPA and Contracting Entity

The public DPA consulted is dated November 2024 and names Zoom Communications, Inc. It forms an integral part of the service agreement. Verify the version and documents applicable to your organization, as well as the entity identified in your contract. Global DPA, November 2024.

GDPR, Article 28(3): "Processing by a processor shall be governed by a contract" (unofficial translation). GDPR, Articles 28, 32, and 35.

Retain the DPA alongside the service agreement and subscription documents. Your analysis must focus on the commitments actually applicable to the services used.

Subprocessors and Transfer Safeguards

Zoom publishes a list of subprocessors. Review it alongside the DPA according to the active services and features. Identify the relevant vendors, destinations, and the mechanism established for transfers applicable to your data. Subprocessors. Global DPA, November 2024.

GDPR, Article 46(1): "appropriate safeguards" (unofficial translation). GDPR, Articles 46 and 48.

This article governs relevant transfers subject to the conditions it sets out. Document the chosen mechanism and any supplementary measures. A vendor list provides one element of the assessment; it does not, on its own, describe all data flows for your account.

Certifications and Services Actually Covered

The Zoom Trust Center presents its certifications and compliance documentation. The HDS page refers to the ISO 27001 scope for covered services. Before relying on a certification in your compliance records, request the certificate, its validity period, and its scope appendix. Certifications and compliance. Announced HDS scope.

Verify that the services used appear in the documentation received. Private audit reports and detailed certificates were not reviewed for this page. The public information cited therefore does not confirm coverage for every feature of your account.

Framework for Government Access Requests

Zoom publishes a guide on handling government access requests. Review the commitments applicable to notification and response protocols alongside the other documents in your file. Government requests.

GDPR, Article 48: "on condition that it is based on an international agreement" (unofficial translation). GDPR, Articles 46 and 48.

This provision concerns the recognition or enforcement of foreign decisions requiring transfer or disclosure, without prejudice to other grounds for transfer under this chapter. Have government access requests examined within this framework. Storage location alone does not determine all potential access pathways.

Checks to Perform Before Using Zoom in Your Organization

Documents and Settings to Gather With Your DPO

Assemble documents and configuration records into a shared file for the DPO and the IT department. The following table summarizes the points documented on this page. Complete it for accounts that host your meetings and update it when changing plans or features.

Checkpoint Document or setting Decision to record
Contract and services Applicable agreement and DPA Uses covered by your approval
Localization Storage, live streams, and account infrastructure Accepted regions and exceptions
Participants Notice and recording workflow Planned disclosure and procedures
Retention Deletion, exceptions, trash, and copies Retention period and owner
Distribution Audience, downloads, and channels Authorized file recipients
AI features Data, models, and summary sharing Authorized features by meeting type

Support each line item with corresponding documentation, then verify the configuration through a representative test. Storage region. Sharing recordings. AI summary settings. Global DPA, November 2024.

Requirements Specific to Sensitive Meetings

Classify the data exchanged before authorizing recording or summary generation. For HR meetings, medical discussions, or executive board meetings, review access levels, export options, and necessary features with the relevant stakeholders.

GDPR, Article 32(1): "a level of security appropriate to the risk" (unofficial translation). GDPR, Articles 28, 32, and 35.

Security measures must correspond to the risks identified for the processing activity. Also evaluate the need for a data protection impact assessment in situations covered by Article 35.

GDPR, Article 35(1): "high risk" (unofficial translation). GDPR, Articles 28, 32, and 35.

This assessment focuses on the planned processing and its consequences for individuals. It requires more than a simple check of the storage location.

Additional Checks Before Adding Leexi to Zoom

Leexi introduces its own processing to meeting data. Review its DPA, vendors, processing locations, and access controls for meeting notes. Also verify retention schedules and data shared with active integrations. The DPA documents non-training commitments; its appendix lists several European hosting locations. Leexi DPA and vendor appendix.

Compare these documents with your Leexi configuration. Clarify the scope of AI providers applicable to your account. You can consult the Leexi security dossier to gather the documentation required for review.

To transcribe your meetings and generate notes, consult the Zoom integration documentation. It details calendar connection and recording authorization by the host. Verify these permissions before your first meeting with the assistant. Zoom integration documentation.

To complete your assessment of Leexi, review the terms of its data processing agreement and the scope of the non-training commitment. These materials complement the verification of your Zoom configuration.

Try Leexi for free

Frequently Asked Questions About Zoom and GDPR

What conditions must be verified before authorizing Zoom in a European company?

Have the applicable contract, processed data categories, and intended uses evaluated by your DPO and IT department. Compare the Zoom DPA with your plan and configuration: regions utilized, data transfers, enabled features, and authorized personnel. Authorization must address these specific uses and parameters. Zoom DPA, GDPR, Article 28.

Verify the commitments actually applicable to your organization.

Does selecting a European region cover all processing for my meeting?

Selecting a storage region covers the data categories specified by Zoom. Data centers for live streams are governed by a separate setting. Zoom also offers a European infrastructure dedicated to certain accounts, with documented exceptions for global services. Identify your account infrastructure and verify storage, live streams, and active features independently. Storage region, live streams, European infrastructure.

Is Zoom's consent prompt sufficient for recording participants?

The prompt displayed by Zoom must be accompanied by appropriate privacy information tailored to your processing. Define its purpose and legal basis, then specify recipients, retention periods, and procedures for exercising data subject rights. Also test the participant workflow: Zoom notes that individuals already active on audio or video may remain active while the prompt is displayed. Zoom consent prompt, GDPR, Articles 5 and 6, Article 13.

The software prompt alone does not demonstrate that the chosen legal basis is valid.

How can I prevent a Zoom recording from being shared outside my organization?

Restrict the link audience to authorized users within your organization and verify download options. Also monitor access permissions granted through Zoom Video Management: a channel can provide additional access to the recording. Test permissions using an external account. These settings restrict access options provided by Zoom; they do not guarantee that an authorized recipient will not make a copy. Managing recording sharing.

What should be checked before enabling AI summaries for a confidential meeting?

Verify the data used, the model option applicable to your account, and the retention conditions. Next, check automatic summary sharing: it may include external guests depending on the selected setting. Zoom offers a setting to restrict external sharing and deliver a link requiring authentication. Ensure these parameters are validated for the meeting data. AI data processing, model options, summary settings.

How do I set a retention period for Zoom recordings?

Define a retention period justified by the intended use of the recording, configure automatic deletion, and verify any exceptions. When the trash feature is enabled, deleted files remain recoverable for 30 days. Incorporate this step into your policy and provide for the deletion of downloaded or locally backed-up copies. Zoom recording deletion, GDPR, Article 5.

The configured duration must correspond to the documented operational need of your organization.

What safeguards should be reviewed before connecting Leexi to Zoom?

Review the Leexi DPA, its vendor list, and applicable processing locations. Verify non-training commitments, retention periods, users with access to meeting notes, and data transmitted to active integrations. Document this processing alongside Zoom's processing with your DPO. Leexi DPA, Articles 5 and 7, and Appendix 2.

Try Leexi for free

Sources and Verification Date

Public sources consulted on 5 November 2026. Specific document dates are indicated in their respective citations. No customer Zoom accounts or private certification audit reports were reviewed for this page.

Recommended Articles

Ready to boost your productivity with Leexi?

Leexi AI Notetaker takes notes for you

Discover here