Inside this story Context & sources

This article links to 2 sources. Source links are provided below so you can inspect the evidence yourself.

  • Google’s rollout began on 12 October, with up to 15 days allowed.
  • Web and room hardware come first; mobile follows later.
  • NIST’s standards explain the background, not Meet’s implementation.

A quiet change beneath the call

Google Meet is extending post-quantum cryptography to laptop browsers and meeting-room hardware. Google’s 12 October announcement gives the rollout up to 15 days and says mobile support will follow. The company describes an automatic change, without a new setting or anything for participants to switch on. [1]

For readers following the announcement this week, the important detail is its staged timing. A release headline describes a direction of travel; it does not establish that a particular call has already received the change. We have not inspected a Meet session or measured its encryption.

What the future threat means

Google frames the change around the possibility of someone collecting encrypted traffic now and decrypting it with a sufficiently capable future quantum computer. It says no such computer exists today. Meet already used quantum-safe encryption for client-side-encrypted calls; this announcement broadens its use. [1]

There is an established standards effort behind the terminology. On 13 August 2024, the US National Institute of Standards and Technology finalised its first three post-quantum standards. Its explanation describes mathematical approaches designed to resist attacks from both conventional and quantum computers. That is historical background from a separate organisation, not an audit of Meet’s rollout. [2]

Read the scope before the promise

Google lists Workspace customers, Individual subscribers and personal accounts as eligible. The announced starting point remains web clients and room hardware. Mobile is a later step, rather than something this release date confirms is available. [1]

Our reading is that the scope deserves more attention than the futuristic label. A team can keep the original announcement alongside its ordinary service notes, with the date and device limits intact. That gives colleagues a specific reference when they ask what changed, without turning a vendor update into a blanket assurance about every meeting.

An update worth describing precisely

For a South African organisation using Meet, that distinction is useful when explaining the change internally. We would describe it as an announced encryption rollout and retain the provider’s timetable. We have not verified adoption in any local organisation, and the announcement supplies no evidence about a particular reader’s device.

The practical news is a protective technology moving further into an everyday service. Its significance will be easier to judge through precise descriptions of where it is deployed and what has been checked. Our explanation stops at the published scope; it is not a security assessment of the service or a claim that a meeting is immune to attack.

Sources & further reading

1. Google Meet now uses post-quantum cryptography — 12 October

Google’s dated announcement and rollout limits, not independent implementation testing.

2. NIST releases its first three finalised post-quantum standards — August 2024

Independent standards-body background, updated 29 August 2025; historical context, not verification of Meet’s particular implementation.

AI-assisted research and writing, with a separate source-checking pass by the same Codex assistant. Google supplies rollout details; NIST supplies independently authored historical standards context, not an implementation audit. Practical interpretation is ours. No hands-on, local adoption, specific algorithm or completed per-account rollout verified.

THE OPEN TABStay curious. Keep reading.