Meeting recording consent: How Avoma helps you stay compliant

Recording consent requirements vary by country, state, and region. Regulations such as the General Data Protection Regulation (GDPR) in Europe, along with other privacy laws, may require participants to be informed about or consent to meeting recordings before personal data is collected.

Avoma helps organizations implement their preferred recording consent workflow with configurable organization-wide policies, automated participant notifications, and multiple enforcement levels.

Why recording consent matters

Meeting recordings and transcripts often contain personal data. Privacy regulations such as GDPR, along with many regional recording laws, may require organizations to notify participants or obtain consent before recording begins.

Avoma provides configurable recording consent controls that help organizations implement these requirements consistently across meetings. Organizations remain responsible for determining the legal obligations that apply to their use case.

Configure GDPR-friendly recording consent policies

Avoma offers four recording consent enforcement levels, allowing organizations to configure the approach that best aligns with their internal policies and applicable privacy regulations, including the GDPR where appropriate.

1. Disabled: No automated notifications.

2. Notified only: Participants are informed via pre-meeting or in-meeting notifications. This satisfies "informed consent" where remaining in the meeting constitutes agreement.

3. Acknowledgment required: Participants see a consent notice before joining and must acknowledge it to enter. (Available on select Avoma plans. Check pricing page for details).

4. Permission required: The highest compliance standard. Participants must explicitly accept or decline to be recorded. If they decline, Avoma automatically disables recording for that session. (Available on select Avoma plans

5. Check Avoma pricing page for details).

Automated notification touchpoints in Avoma

To support recording consent workflows required by regulations such as GDPR and other privacy laws, Avoma provides multiple notification touchpoints before and during meetings.

1. Pre-meeting transparency

• Automatically add recording notices to calendar invites: Avoma can automatically append a recording disclaimer to meeting descriptions, so participants know before the meeting that the session will be recorded. (e.g., "This meeting will be recorded for note-taking purposes").

• Send automated recording reminder emails: Avoma can send recording reminder emails before meetings, notifying participants that the upcoming session will be recorded. Reminders can be sent 15 minutes before internal meetings and 24 hours before external meetings.

   

2. In-meeting awareness

• Automated voice announcement: When the Avoma Bot joins a meeting, it can automatically play a voice announcement informing participants that the meeting is being recorded for note-taking purposes. This is especially useful on platforms like Google Meet and Microsoft Teams, which do not always provide native audio recording notifications. 

   

• Notify participants in the meeting chat: As soon as recording begins, the Avoma Bot automatically posts a recording notice in the meeting chat, providing an additional notification that the session is being recorded.

• Display native recording indicators: Avoma respects native platform indicators (like the blinking red icon in Zoom) to provide a constant visual reminder.

How Avoma handles recording consent with Zoom, Google Meet, and Microsoft Teams

If you record natively through your conferencing tool rather than using the Avoma Bot, Avoma integrates with their built-in compliance features:

• Zoom: Uses native voice announcements and recording indicators.

• Google Meet: Shows a recording indicator (Note: Google does not provide a native voice announcement, so we recommend using the Avoma Bot Voice Announcement for full compliance).

• Microsoft Teams: Displays an in-meeting recording banner to all participants.

Best practices for outbound calls

For cold outbound calls made via a dialer, we recommend that SDRs and BDRs standardize a verbal announcement at the start of every call:

“Hi, this is [Name] from [Company], and I’m calling from a recorded line.”

If the party continues the conversation, they have provided passive consent. Standardizing this "recorded line" disclosure is the safest way to maintain compliance across different state laws.

FAQs

What happens if a participant declines recording consent in Avoma?

If the organization uses the Permission required enforcement level, participants can explicitly accept or decline to be recorded. When a participant declines, Avoma automatically disables recording for that meeting session. This prevents the recording, transcript, and AI-generated notes from being created through Avoma. Organizations should confirm how declined consent affects their internal meeting process and whether an alternative note-taking method is required.

Can Avoma record a meeting if someone joins after the consent announcement?

Participants who join late may miss a voice announcement made when recording begins. Avoma can provide additional notification touchpoints, such as calendar disclaimers, reminder emails, chat messages, and visible recording indicators. Using multiple notifications reduces the likelihood that a participant is unaware of the recording. Organizations with stricter consent requirements may prefer acknowledgment or permission-based controls rather than relying only on an initial announcement.

Does Avoma support GDPR recording consent requirements?

Avoma provides configurable recording consent policies, participant notifications, acknowledgment prompts, and permission-based recording controls that help organizations implement GDPR-aligned recording workflows. Because GDPR obligations depend on your organization's legal basis for processing personal data and how meetings are conducted, customers are responsible for configuring the policy that best meets their compliance requirements.

Need more help?

If you have additional questions regarding your organization's specific setup, please reach out to our team at help@avoma.com.