Video Conferencing
Google Meet
Rest of world Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Google LLC · workspace.google.com
Compare with Wire → Compare with Zoom → Report an error on this page Is this your product? →
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Google Meet's bench strength is pricing transparency and meeting core: the evidence publishes EUR per-user prices from €4.76 to €14.77 under a 16% annual-commitment discount, participant caps of 100/150/500/1000 by plan, 24-hour meetings on every tier, and pooled storage from 30 GB to 5 TB per user. Weakest are encryption and access and reach and accessibility — the captured pages document no meeting encryption, lobby or admission control, and nothing on dial-in, captions, guest joining or an accessibility statement. Recording governance credits recording from the Standard plan and Vault at Plus but finds attendance tracking with no documented off-switch; integrations cover Secure LDAP and Cloud Identity Premium with no stated calendar integration, API or self-hosted option. Sovereignty rests on Google Ireland Limited as controller for EEA/Switzerland users and Enterprise 'data regions', while data residency and subprocessor exposure are marked unknown. The 4-6 spread on meeting core reflects the IT administrator's 6 against the others' 4, crediting published scale; no criterion crossed the threshold for flagging a split.
Speaks for it
- Publishes per-user EUR prices for three tiers (€4.76–€14.77 discounted) with billing terms and a 16% annual-commitment discount
- States participant capacity per plan (100/150/500/1000), 24-hour maximum meetings on all plans, and pooled storage allowances of 30 GB to 5 TB per user
- Recording included from the Standard plan, with Vault retain/archive/search at Plus
- Identity and admin tooling on higher tiers — Secure LDAP at Plus, Cloud Identity Premium, DLP and context-aware access at Enterprise
- Names Google Ireland Limited as data controller for EEA/Switzerland users
Held against it
- No documented meeting encryption, key handling, lobby, passcode or admission control on any captured page
- Nothing on dial-in, live captions, guest or browser joining, or any accessibility statement
- Attendance tracking sold at Plus with no documented off-switch, and no statement of who may record, whether participants are notified, or where recordings are stored
- Sovereignty attributes — legal entity jurisdiction, ownership, data residency, subprocessor exposure — all marked unknown, with subprocessors named only as 'affiliates and other trusted businesses or persons'
- Enterprise priced only via 'Contact sales', add-ons sold separately without prices, and dial-in rates and VAT treatment absent
Best for
- You need published, plannable meeting capacity — up to 1000 participants and 24-hour meetings — at a computable EUR per-user price for up to 300 users
- You administer a Google-stack workspace and value built-in Secure LDAP, Vault and endpoint management over third-party integrations
- You need in-domain live streaming, available on the Enterprise tier
- You buy on published list prices with a stated billing model — monthly billing, a 16% annual-commitment discount, and a 14-day trial
Avoid if
- You need documented end-to-end or even TLS-level meeting encryption and admission controls — ask the vendor: the public pages we read do not show it
- Your participants include phone dial-in users, caption users or screen-reader users — ask the vendor: the public pages we read do not show it
- A works council will ask you to prove recording consent, participant notification, or an attendance-tracking off-switch — ask the vendor: the public pages we read do not show it
- You require confirmed EU data residency and named subprocessors — data residency and subprocessor exposure are marked unknown, and data regions sit behind the Contact-sales Enterprise tier
The scores
The meeting itself
Show reasoningHide reasoning
How this is scored
Whether the call works: participant capacity, video and audio quality under load, screen sharing, breakout rooms, moderation, and what happens on a bad connection.
0 — Small meetings only, no screen sharing worth the name, no moderation controls, and the call degrades without telling anyone.
3 — Standard meetings with screen sharing and mute-all, but low participant limits, no breakout rooms and no bandwidth adaptation stated.
5 — Meetings at the scale most teams need with screen sharing, breakout rooms, host moderation, and documented behaviour on constrained connections.
8 — Large meetings and webinars with published capacity limits, per-participant moderation and waiting rooms, layout control, simulcast or adaptive bitrate stated, and reliable behaviour on mobile networks.
10 — Scale and control are engineering claims the vendor stands behind: capacity published per plan and per region, selective forwarding with adaptive quality documented, live streaming, hardware-room support, and diagnostics an admin can read after a bad call.
The IT Administrator
Published capacity I can actually plan against — 100/150/500/1000 participants per plan, 24-hour meetings, in-domain streaming at Enterprise, and a hardware add-on for rooms. But the evidence is silent on moderation controls, waiting rooms, breakouts, behaviour on a bad connection, and any diagnostics an admin can read after a call fails — and I judge a product by its worst meeting, not the capacity slide. 2
The Security Officer
The evidence proves scale and nothing else: 100/150/500/1000 participants published per plan, 24-hour meetings, in-domain live streaming on Enterprise, a hardware add-on and noise cancellation. Not one word on screen sharing, breakout rooms, host moderation, or behaviour on a bad connection — capacity without documented controls doesn't clear the 5 anchor. 2
The Works Council Advocate
Participant capacity is published per plan (100/150/500/1000) with 24-hour meetings, in-domain live streaming and a hardware-room add-on, which is genuinely strong scale. But the evidence is silent on screen sharing, breakout rooms, host moderation, waiting rooms and what happens on a constrained connection — undocumentable mechanics cannot be relied on for a works assembly. 2
The Educator
Capacity is genuinely published — 100 to 1000 participants depending on plan, 24-hour meetings, noise cancellation from Standard, in-domain live streaming at Enterprise. But the evidence never mentions a screen share, a breakout room, a mute control or what happens when half my class joins on a weak mobile signal, and anchor five requires exactly those — so I stop just under it. 2
The Accessibility Advocate
Capacity is published per plan — 100 to 1,000 participants, 24-hour meetings, in-domain streaming and a hardware add-on — but the evidence says nothing about screen sharing, breakout rooms, host moderation, waiting rooms, or behaviour on a bad connection. I cannot credit meeting controls I cannot read, so this sits between the low-limit and most-teams anchors. 2
The Skeptic
The capacity ladder is the one thing the evidence commits to per plan — 100, 150, 500, 1000 participants, 24-hour meetings on every tier, in-domain live streaming on Enterprise. Beyond that, nothing: no screen sharing, no breakout rooms, no host moderation, no word on behaviour when the connection degrades — capacity is claimed, the meeting's workings are not. 2
Encryption & meeting access
Show reasoningHide reasoning
How this is scored
What is actually encrypted and against whom, plus who can get into a meeting. Judged on documented mechanism rather than on the word "encrypted".
0 — Transport encryption only, undocumented; meetings joinable by anyone with a link and no lobby.
3 — TLS in transit and encryption at rest, with the vendor holding all keys; access control is a passcode.
5 — The above plus a lobby or waiting room, host-controlled admission, per-meeting passcodes, and a clear statement that the vendor can technically access media.
8 — Optional end-to-end encryption for meetings with the trade-offs named (which features stop working), documented key handling, SSO-gated joining, and per-meeting access policies.
10 — End-to-end encryption available without surrendering the product — its cryptography documented or open source, key management explained, identity verification for participants, and the vendor stating plainly what it can and cannot see.
The IT Administrator
The vendor's own captured pages document no encryption mechanism for meetings whatsoever — not transport, not key handling, not E2E — while the privacy policy instead documents voice/audio collection and AI training on user interactions. The only access evidence is Enterprise context-aware access via Cloud Identity Premium; no lobby, no per-meeting policy, and no statement of who can technically see media. 3 2
The Security Officer
Nowhere does the evidence state what is encrypted, who holds the keys, or who can get into a meeting — no TLS statement, no E2EE, no lobby, no passcode, no admission control for Meet at all. The only security-adjacent facts are Google-wide privacy machinery (transparency report, deletion process, complaint handling), which say nothing about a meeting; undocumented is the 0-1 floor. 3
The Works Council Advocate
Nothing documents any encryption mechanism for Meet media, key handling, lobbies, passcodes or admission control; the only security language is that affiliates and trusted businesses process data under 'appropriate confidentiality and security measures', which is a promise, not a documented mechanism. Judged on documented mechanism, the evidence offers none. 3
The Educator
Judged on documented mechanism, and the evidence documents none: the privacy policy never states what is encrypted, against whom, or who holds keys. No fact names a lobby, a passcode or host-controlled admission either; the closest things are Enterprise DLP and context-aware access, which are directory rules, not meeting encryption — silence lands at the bottom. 3 2
The Accessibility Advocate
Neither the privacy policy nor the pricing page documents any encryption mechanism, key handling, lobby or host admission for meetings — not even a TLS statement. Undocumented is the anchor's own word for zero. 3 2
The Skeptic
I read every line for the sentence that says which meetings are end-to-end encrypted, on which plan, and what stops working — it does not exist, and neither does a plain TLS or encryption-at-rest claim for Meet media. DLP, context-aware access and endpoint management on Enterprise are admin security, not meeting encryption; on this sheet encryption is undocumented. 3 2
Reach & accessibility
Show reasoningHide reasoning
How this is scored
Whether everyone who needs to join can: browser without an install, dial-in, low bandwidth, guests without accounts, captions and keyboard operation.
0 — A desktop client is the only way in; guests must create an account.
3 — Browser joining exists but is degraded, guests can join by link, and there is no dial-in and no accessibility statement.
5 — Full-feature browser joining without an install, guest access by link, mobile apps, and a stated accessibility posture.
8 — Telephone dial-in with numbers listed, live captions, keyboard-navigable and screen-reader-tested interface, and documented low-bandwidth behaviour.
10 — Reach is designed for: browser parity with the client, dial-in across the regions the customer operates in, live captions and translation, a published accessibility conformance report, and a usable experience on a poor mobile connection.
The IT Administrator
For a product of this scale, the evidence says nothing about browser joining, guest access without an account, dial-in, captions, or any accessibility statement — the closest item is a separately sold Voice telephony add-on that is not meeting dial-in. When the question is whether everyone can get in, total silence is the answer; I cannot even confirm a guest joins without an account. 2
The Security Officer
Nothing evidences how a single participant joins: no browser joining, no guest access by link, no dial-in, no captions, no accessibility statement anywhere in the evidence. The one adjacent fact is that Google collects mobile network and carrier data — that implies devices exist, not that anyone can reach a meeting; total silence on every element of the anchor is the floor. 3
The Works Council Advocate
The Meet product pages were captured twice and yielded no evidence of browser joining, guest access by link, dial-in, captions or any accessibility statement — the only telephony in the evidence is a separately sold Voice add-on, which is not a way to phone into a meeting. Absence of any evidenced joining path beyond a signed-in client lands at the bottom anchor. 1 1 2
The Educator
Nothing on the evidence says a student can join from a browser without installing anything, join as a guest without an account, dial in by phone, or get live captions — the plan tables list participant counts and AI add-ons and stop there. The single reach-adjacent fact is 'real-time speech translation' sold as a paid add-on, which is not captions and not included. By the anchors, silence on all of this is the bottom, not the middle. 2
The Accessibility Advocate
No dial-in, no live captions, no keyboard or screen-reader testing, and no accessibility statement or conformance report anywhere; the only caption-adjacent fact is 'real-time speech translation' buried in an unpriced AI add-on. On this evidence a deaf colleague cannot run the meeting and a screen-reader user's experience is a guess. 2 3
The Skeptic
The evidence never says how a person actually joins a Meet: no browser joining, no guest links, no dial-in numbers, no captions, no accessibility statement — the entire reach question is silent. The only adjacent items are separately sold add-ons, a business telephony product and an AI add-on mentioning real-time speech translation, which is not dial-in or captions. 2
Recordings, retention & admin control
Show reasoningHide reasoning
How this is scored
A recording is personal data about everyone in the room. Who may record, who is told, where it is stored, how long it lives, and what the works council can switch off.
0 — Anyone can record, storage location unstated, no retention rule, no admin policy.
3 — Host-only recording with a notification, but storage region unstated, retention manual, and no organisation-wide policy control.
5 — Admin policy over who may record, participant notification and consent prompt, stated storage region, and manual deletion that works.
8 — Automatic retention and deletion per policy, recordings encrypted at rest with access logged, transcription handled with its own retention rule, and attendance or analytics features that can be switched off for co-determination.
10 — Built for a works agreement: every recording, transcript and analytics feature independently switchable and documented, retention executed and evidenced, an audit trail of who accessed which recording, and no participant-level behavioural scoring at all.
The IT Administrator
Recording arrives at Standard, Vault can retain and archive at Plus, and Enterprise names data regions plus an Assured Controls add-on — but nothing states who may record, whether participants are told, where Meet recordings are stored, or who accessed them. Attendance tracking appears at Plus with no documented off-switch, which is exactly what a works council will ask me to disable and I cannot evidence that I can. 3 2
The Security Officer
Recording appears from the Standard plan and attendance tracking on Plus, but the evidence never says who may record, whether participants are notified, or where recordings are stored; what exists is generic — domain admins can restrict deletion and privacy settings, and data can auto-delete after set periods — plus Vault retention tooling. Attendance tracking arrives with no evidenced off-switch, which is exactly what a works council will ask me about. 2 3
The Works Council Advocate
Recording appears from Standard onward and attendance tracking is sold as a Plus feature with no documented off-switch — co-determination over analytics, my central demand, is unmet. Generic per-service deletion, account auto-deletion, Vault retention at Plus and vague admin powers to 'restrict your ability to delete or edit' exist, but nothing on who is told a recording starts, consent, recording storage region, or access logs. 3 2
The Educator
Recording arrives at Standard and attendance tracking at Plus, Vault gives admins retain/archive/search, and domain admins can restrict some settings — real tooling. But no fact says who may record, whether the room is told, where the recording is stored, or for how long it lives, and nothing says attendance tracking can be switched off for a works council. That is anchor three's shape: the feature exists, the governance is manual and unstated. 2 3
The Accessibility Advocate
Recording arrives as a Standard-plan feature with pooled storage, but who may record, whether participants are told, where recordings sit and how long they live are all unstated, and attendance tracking is sold as an upsold feature with no documented off-switch for a works council. Account-level deletion tools exist, but nothing recording-specific. 2 3
The Skeptic
Recording exists from Standard upward and Plus adds attendance tracking, but the evidence never says who may record, whether participants are told, or where recordings are stored — pooled Drive allowances of 30 GB to 5 TB per user are stated and never tied to recordings. Retention appears only as Vault archival tooling and an Enterprise 'Assured Controls' add-on; no recording-specific retention rule, access log, or consent prompt, and no statement that attendance tracking can be switched off. 2 3
Integrations & deployment
Show reasoningHide reasoning
How this is scored
Calendar, identity and the wider stack — plus, in this category, whether the product can be run on the customer's own infrastructure at all.
0 — No calendar integration, no SSO, no API; cloud-only with no alternative.
3 — One calendar integration and basic SSO, no API worth building on, cloud-only.
5 — Calendar integration for the major suites, SAML or OIDC SSO, a documented API for scheduling, and room-system support.
8 — The above plus SCIM provisioning, embedding via SDK, webhooks for meeting events, and either a self-hosted option or a documented private-cloud deployment.
10 — Deployment is the customer's choice: a genuine on-premises or private-cloud option with the same features, open protocols or open source, embeddable SDKs, and identity integration that does not require the vendor's directory.
The IT Administrator
Identity plumbing is real — Secure LDAP at Plus, Cloud Identity Premium and context-aware access at Enterprise — and room hardware exists as a separately sold add-on. But there is no documented API, no SCIM, webhooks or SDK, and it is cloud-only with no deployment alternative at any price or tier. 2
The Security Officer
Identity plumbing exists — Secure LDAP on Plus, Cloud Identity Premium and DLP on Enterprise — and a Meet Hardware add-on covers room systems, but no calendar integration is named, no SAML/OIDC or documented API appears, and deployment is cloud-only with no alternative evidenced. 2
The Works Council Advocate
Identity tooling is real (Secure LDAP at Plus, Cloud Identity Premium and context-aware access at Enterprise) and the Meet hardware add-on gives room-system support, but no documented API, SCIM, webhooks or embedding appear anywhere. Cloud-only with no self-hosted or private-cloud option in the evidence caps it. 2
The Educator
Room hardware exists as a separately sold add-on, and Plus brings Secure LDAP, endpoint management and Vault — genuine stack presence. But the evidence documents no calendar integration, no SSO mechanism, no API, and no way to run the product anywhere but Google's cloud; anchor five needs the first three of those, so I sit just under it. 2
The Accessibility Advocate
The evidence evidences identity hooks (Secure LDAP, Cloud Identity Premium) and a Meet hardware add-on, but no calendar fact, no documented API, no SCIM or SDK, and no deployment option other than Google's cloud. 2
The Skeptic
Room-system support is real (the Meet Hardware add-on) and directory adjacency exists as Secure LDAP on Plus and Cloud Identity Premium on Enterprise. But for a meeting product sold inside a suite, no calendar integration is ever stated, there is no API, SCIM, webhook or SDK in evidence, and no self-hosted or private-cloud option of any kind — cloud-only. 2
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Where media and metadata are processed, who the contracting entity is, which subprocessors carry the traffic. Independently sourced by the sovereignty pipeline; scored here as this buyer weighs it — which in this category is heavily.
0 — Non-EU vendor and contracting entity, media routed through unstated regions, subprocessors unnamed.
3 — EU data residency for storage while media relays or metadata remain non-EU, or the contracting entity sits outside the EU.
5 — EU hosting and an EU contracting entity, but parts of the chain — relays, analytics, support tooling, transcription — are non-EU without an explained safeguard.
8 — Media and metadata processed in the EU on named infrastructure, EU contracting entity, complete subprocessor list published, any non-EU processing named with its legal basis.
10 — Sovereign end to end and evidenced: media never leaves the EU, every subprocessor European, certification published, and an on-premises option that removes the question entirely.
The IT Administrator
Provenance puts the vendor in Mountain View, and Google Ireland Limited appears only as the EEA controller — UK users get Google LLC in California. Subprocessors are named only as 'affiliates and other trusted businesses', media routing and data residency are unstated, and the pipeline scored this 0; nothing on these pages moves me far off that. 3
The Security Officer
The pipeline found jurisdiction, ownership, residency and subprocessor exposure all unknown; the vendor is Google LLC of Mountain View, media routing is unstated, and subprocessors are described only as unnamed 'affiliates and trusted businesses or persons' processing on Google's instructions. Google Ireland is the designated EEA controller and an 'enterprise data regions' feature is named, but neither says where meeting media actually flows — one point, no more. 3 2
The Works Council Advocate
The vendor is Google LLC of Mountain View, the UK controller is also Google LLC, subprocessors are unnamed 'affiliates and other trusted businesses', and data residency is unconfirmed on the vendor's own pages. Google Ireland as EEA controller and the Enterprise-only 'data regions' feature are the sole EU anchors, and where media and metadata travel is entirely undocumented. 3 2
The Educator
The pipeline computes 0/10 and I mostly agree: provenance is Google LLC in California, the UK controller is Google LLC in Mountain View, media routing and data residency are unknown, and the only named subprocessors are 'affiliates and other trusted businesses'. The slivers are Google Ireland Limited as controller for EEA users and 'enterprise data regions' locked behind the unpriced Enterprise tier — a crack of light, not a guarantee, and I weigh this heavily. 3 2
The Accessibility Advocate
The vendor is Google LLC of Mountain View; the policy names Google Ireland Ltd as EEA controller and only 'affiliates and trusted businesses' as subprocessors, while media routing and residency are unstated and data regions are an Enterprise upsell. Non-EU vendor, unstated regions, unnamed subprocessors is the zero anchor, softened one point for the Irish controller. 3 2
The Skeptic
The vendor is Google LLC of Mountain View; the evidence's own sovereignty attributes mark legal entity, data residency and subprocessor exposure as unknown on the vendor's pages, media routing is unstated, and the subprocessor list is 'affiliates and other trusted businesses' — unnamed. The single EU fact is a controller statement (Google Ireland Limited for EEA users, US entity for UK users), which does not amount to residency or a safeguard; this buyer weighs that heavily, so it sits near the floor. 3 2
Pricing transparency
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the annual invoice for their host count — including the capacity, dial-in and recording storage they actually need — from public pages alone.
0 — No public prices at all; every tier is a sales conversation.
3 — A per-host headline exists, but participant caps, dial-in minutes or recording storage are unpriced or unmentioned.
5 — Per-host prices public with billing period stated and capacity limits given, but at least one commonly needed piece (webinar capacity, dial-in, storage) sits in an unpriced add-on.
8 — Every tier and add-on priced publicly with per-host maths, capacity limits, dial-in rates, storage allowances, minimum term and VAT treatment stated.
10 — Complete price computability: a calculator producing the annual invoice for a given host count, meeting size and recording volume, including overage and per-region dial-in.
The IT Administrator
Per-user prices, billing period, the 16% annual-commitment maths, capacity per plan, meeting length, storage allowances and even promo limits are public — a small-tier invoice is computable. But Enterprise is 'Let's talk', add-ons are sold separately without prices, and dial-in rates and VAT treatment are absent, so the buyer at the size that matters most cannot compute their invoice. 2
The Security Officer
Three tiers are computable from the public page — EUR per user with monthly vs 16%-discount annual billing, participant caps of 100/150/500/1000, 24-hour meetings and pooled storage stated. But Enterprise is 'Contact sales', the Meet Hardware and Voice add-ons are 'sold separately' with no prices, and dial-in rates and VAT treatment are never mentioned — a solid 5 pushed to 6 on capacity disclosure. 2
The Works Council Advocate
Three of four tiers carry public EUR per-user prices with billing period, annual discount, seat caps (300 on lower tiers) and pooled storage allowances, so an invoice is computable for small host counts. But Enterprise — the only tier with 1000-participant meetings and data regions — is 'Contact sales', the Meet Hardware and Voice add-ons are sold separately with no prices, dial-in rates are absent entirely, and VAT treatment is unstated. 2
The Educator
Per-user euro prices, billing period, the 16% annual discount, participant caps and pooled storage allowances are public per plan — better than most. But Enterprise, the only tier with 1000 participants and streaming, is 'Let's talk', every add-on is 'sold separately' and unpriced, and dial-in and VAT treatment are unmentioned — a school with 301 teachers cannot compute its annual invoice from these pages. 2
The Accessibility Advocate
Three tiers carry public per-user prices with billing period, capacity limits and pooled storage allowances, so a buyer can compute much of the invoice for up to 300 users. But Enterprise is 'Let's talk', every add-on is 'sold separately' with no price, and dial-in rates and VAT treatment are absent — the anchors call that an unpriced hole, not a complete picture. 2
The Skeptic
Per-user prices, billing periods, discounts and participant caps are public — €4.76 to €14.77 per user with 100/150/500/1000 limits — but dial-in is not merely unpriced, it is unmentioned, and Enterprise is 'Let's talk', so every organisation above Plus's 300-user cap is pushed into a sales conversation. Storage allowances are stated per plan though never linked to recordings, add-ons carry no prices, and VAT treatment is nowhere; an invoice is computable only up to 300 users. 2
European sovereignty — proven facts
0 of 4 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined ⚠ unverified | — | uncited Report an error |
|---|---|---|---|
| Ownership | Not determined | — | uncited Report an error |
| Data residency | Not determined ⚠ unverified | — | uncited Report an error |
| Subprocessors | Not determined ⚠ unverified | — | uncited Report an error |
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 31 Aug 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Legal entity, Data residency, Subprocessors. Not confirmed on the vendor’s own pages as captured.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 146 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 35 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 21 legal facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 13 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 8 support facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 7 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 data fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 subprocessors fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 3 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown. Know more? Tell us
- 6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement. Know more? Tell us
Sources (8)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Product page workspace.google.com Checked 5 Oct 2026 +1 earlier capture: 11 Sep 2026 Details →
- 2 Pricing workspace.google.com Checked 5 Oct 2026 +3 earlier captures: 15 Sep 2026, 11 Sep 2026, 31 Aug 2026 Details →
- 3 Privacy policy policies.google.com Checked 5 Oct 2026 +1 earlier capture: 15 Sep 2026 Details →
- 4 Terms of service policies.google.com Checked 5 Oct 2026 Details →
- 5 Encryption & meeting access — found from sitemap workspace.google.com Checked 5 Oct 2026 Details →
- 6 Reach & accessibility — found from sitemap www.google.com Checked 5 Oct 2026 Details →
- 7 Recordings, retention & admin control — found from sitemap workspace.google.com Checked 5 Oct 2026 Details →
- 8 Integrations & deployment — found from sitemap workspace.google.com Checked 5 Oct 2026 Details →