Is Google Meet HIPAA compliant? BAA by plan, covered services and exclusions

Google Meet can be used with PHI only under a signed Business Associate Agreement (BAA), which paid Google Workspace and Cloud Identity accounts can accept and personal Google accounts cannot. The BAA is the first step; configuration and staff policies come after it.

Conditional A BAA is available on paid Google Workspace and Cloud Identity accounts for Google Meet (verified 2026-10-20). Consumer accounts and the legacy free edition are excluded, as are third-party apps and add-ons.

Short answer

Google lists Google Meet as HIPAA Included Functionality. A super administrator accepts the BAA in the Admin console. Without that acceptance, Meet should not carry PHI. This applies equally to telehealth visits, therapy sessions and internal case discussions.

Consumer Google accounts and the legacy free edition of Google Workspace cannot accept the BAA. Third-party applications and add-ons are not covered by it. For "how to make Google Meet HIPAA compliant," the sequence is: confirm the account type, accept the BAA, configure Meet and the surrounding apps, then set staff policies. See the HIPAA glossary (BAA, PHI) for term definitions.

Which plans include a BAA

Plan BAA How it is obtained Extra cost
Google Workspace (paid editions) Available A super administrator reviews and electronically accepts the BAA in the Admin console under Account settings > Legal and compliance, before any PHI is used None
Cloud Identity Available Same acceptance path as above None
Consumer Google accounts (personal Meet) Not available None Not applicable
Legacy free edition of Google Workspace Not available None Not applicable

Minimum seat count: Not published by the vendor.

Entry price for paid Workspace: from €6.80 per user/month (Business Starter, annual commitment, EUR as shown on Google's pricing page, checked 2026-10-20).

What the BAA covers and what it excludes

Covered

  • Google Meet

Excluded

  • Third-party applications and add-ons
  • Gemini in Chrome

Other Workspace services, such as Gmail, Drive and Docs, are covered on their own check pages. Start with Is Google Workspace HIPAA compliant?.

Security controls the vendor publishes

Control Published status
Encryption in transit Not published by the vendor
Encryption at rest Not published by the vendor
Audit log Not published by the vendor
Access controls Yes
SSO Not published by the vendor
Data residency Not published by the vendor
SOC 2 Not published by the vendor
HITRUST Not published by the vendor
ISO 27001 Not published by the vendor

For access controls, Google's Meet documentation describes controlling whether external guests may participate.

"Not published by the vendor" refers to Meet-specific statements in the sources checked. It does not mean the control is absent.

How to use Google Meet with PHI

  1. Confirm the account is a paid Google Workspace or Cloud Identity account. A therapist running sessions from a personal Gmail address does not qualify.
  2. Have a super administrator accept the BAA in the Admin console before any PHI is used in Meet.
  3. Control external guest participation per meeting. A patient joining from outside the organization is an external guest, so decide who may admit them.
  4. Keep third-party apps and add-ons away from sessions that involve PHI. A recording or transcription add-on is outside the BAA.
  5. Keep Gemini in Chrome out of PHI use.
  6. Set written policies for staff: which meetings may include PHI, who may join, and what happens to any recordings or notes.
  7. Train staff and manage access, including removing accounts at offboarding.

Compliance depends on the signed BAA, configuration and policies, not on the product alone. This page is a reference, not legal advice.

Alternatives with a BAA

Each verdict reflects the vendor's published BAA terms.

Browse the full category at HIPAA-compliant video conferencing tools.

Sources

Changes

No changes recorded since first verification on 2026-10-20. See recent changes in vendor HIPAA status.

Changes and FAQ

Changes: No changes recorded since first verification on 2026-10-20. See recent changes for other vendors.

Is Google Meet HIPAA compliant for telehealth?

Conditionally. A BAA is available for Google Meet on paid Google Workspace and Cloud Identity accounts. A super administrator must accept it before PHI is used. Signing the BAA alone does not make a practice HIPAA compliant; configuration and policies still apply.

Can I use a personal Google account for Meet with patients?

No. Consumer Google accounts cannot accept the BAA, and neither can the legacy free edition of Google Workspace.

How do I sign the Google BAA for Meet?

A super administrator reviews and electronically accepts it in the Admin console under Account settings > Legal and compliance, before any PHI is used.

Does the BAA for Google Meet cost extra?

No. The BAA has no extra cost. Paid Workspace starts from €6.80 per user/month (Business Starter, annual commitment, EUR as shown on the pricing page, checked 2026-10-20).

Are third-party add-ons and Gemini in Chrome covered by the BAA?

No. Third-party applications and add-ons are excluded, and so is Gemini in Chrome. Keep both away from PHI.