Google Meet Client-Side Encrypted Calls Made Available to Non-Google Users

Google Meet is enhancing its privacy features by extending client-side encryption capabilities to non-Google account holders. This upgrade allows participants from outside the Google ecosystem to join encrypted video calls, ensuring enhanced security for all users.

Understanding Client-Side Encryption in Google Meet

Client-side encryption ensures data privacy by allowing only meeting participants to access the information exchanged during a call. Previously, Google Meet had limited this feature to users within its own service. 

However, non-Google users will now be able to take advantage of encrypted calls. Google Meet, a part of the Google Workspace suite, is known for providing secure online video communication solutions and boasts over five billion downloads on Google Play alone.

Google’s Commitment to Data Security

According to Google’s recent announcement, “Meet already encrypts all of your data at rest and in transit between our facilities — client-side encryption gives users direct control of their encryption keys and the identity service that they choose to authenticate for those keys.” 

The introduction of external participant support is a game-changer for Google Meet users. It ensures that “customers can collaborate with any of their stakeholders safe in the knowledge that only the meeting participants can decrypt the call media.”

Rollout and Accessibility

Google has already started rolling out client-side encryption updates to Workspace customers with Enterprise Plus, Education Standard, and Education Plus licenses. To enable it, administrators must adjust their IdP/KACLS configurations, allowing access to external participants while selecting suitable third-party identity providers for joining the meetings.

External participants wishing to join an encrypted session via Google Meet are required to verify their identity using a method approved by the third-party Identity Provider (IdP) chosen by the meeting’s administrator. These methods may include existing Google or Microsoft accounts or a one-time password received through SMS or email.

Settings for admins to configure identity verification methods (Source: Google)

You can find more information about Meet client-side encryption here. Admins can refer to this guide to make client-side encryption available to external participants. 

Final Word

Google Meet’s expansion of client-side encrypted calls to include non-Google users significantly enhances privacy and security, making collaborative communication more inclusive and protected.