Read AI Buyer's Checklist: Is It Safe, HIPAA-Ready and Private?

Read AI is a legitimate product, and its security basics hold up. Read AI says it holds SOC 2 Type 2 certification, encrypts data with AES-256 at rest and TLS 1.2 or higher in transit, and does not train its models on your meetings unless you opt in.^[1] The real risk sits in the defaults. Once a calendar is connected, Read joins every event on it and sends the recap to everyone with access. HIPAA is the hard gate: it needs Enterprise+ billed annually, a signed BAA and at least 5 licenses. Fix the defaults before rollout.

The company behind it is Read AI, Inc., founded in Seattle in 2021 by David Shim, Rob Williams and Elliott Waldron, with seed, Series A and Series B rounds behind it. Read AI says it has more than 5 million monthly active users (May 2026). Its browser extension runs on Chromium browsers and installs without permission to read every site; Zoom and Teams detection needs extra permissions you grant yourself. Public complaints cluster around an uninvited assistant, spam-like invitations and hard account deletion, and each one traces back to a setting covered below.

Check how Read joins meetings and spreads

Most safety complaints start with one choice. During onboarding Read marks All calendar events as recommended, and that option, paired with Any participants, is the default for calendar auto-join. The 7-day Enterprise trial joins every meeting too. Recaps go to People with access unless you switch them to Only me or No one. Depending on the sender's settings, guests without an account get an invitation to sign up to view the summary, and Read AI's help says this is how accounts are often created.^[2] From the outside, that loop looks like spam.

• Auto-join scope: in Account Settings, Meeting Recording, Auto-Join Preferences, pick meetings you host, internal participants only, or off, before anyone connects a calendar.
• Recap delivery: set it to Only me for the pilot, then widen it on purpose.
• Unscheduled meetings: leave Auto-Join Unscheduled Meetings off unless you want Read in ad hoc Meet and Zoom calls.
• Editor rights: anyone who adds Read gets editor access and can share the report, unless the owner marks the meeting private.
• Other attendees: turning your Read off does not stop a guest from bringing their own. Our guide on how to remove Read AI walks through every stop path.
• Zoom rule: since November 2026 Read joins a Zoom meeting only if the user has connected a Zoom account and is in the call; on Teams and Meet it can join without the user.

Check consent and recording notices

In bot mode, the default on Zoom, Teams and Meet from a calendar, the assistant joins as a visible participant named read.ai meeting notes. It posts a chat message naming the person who invited it. Anyone in the call can type Read stop to end recording and keep a report up to that point, or Opt out to make Read leave and delete everything. Neither needs an account or host approval. Google Meet native recording works without a bot, but someone must approve a consent pop-up within 10 minutes of the start.

Local capture is a different story. The desktop app for Windows and macOS and the iPhone and Android apps record audio on the device. Read never appears in the participant list. Nothing is posted in chat, and the chat commands do not apply. The app reminds its user to get consent and offers a disclosure message with an opt-out link, but that link works only if the user shares it. Read AI's Terms put notice and consent on the user, not on Read.

• Local recording policy: decide whether desktop and mobile capture is allowed at all; Workspace admins can disable it.
• Advance Notice and Opt-Out: invitees outside your Workspace get an email with an opt-out button and a reminder 24 hours before. One opt-out stops Read for everyone. It needs a paid Workspace, not Free or a trial, and covers scheduled meetings only.
• A consent script: give staff one sentence to say aloud before in-person recordings.

Check admin controls, SSO and report access

A Workspace starts on Pro and gives owners roles, sharing rules and license management. Admins can restrict auto-join so members may pick only the admin's choice or a stricter one, disable report downloads, and switch Ask Read and its model modes on or off. Turning downloads off also blocks members from the API and the MCP server, both open beta and available on every plan, Free included. Global Report Access lets chosen admins open any member's report; Read AI recommends it only when truly necessary. The identity controls a security team usually asks for all sit on Enterprise+.

• SAML SSO with Google Workspace, Microsoft Entra, Okta or Duo. Two-factor login can be enforced at the SSO level, but not for username and password logins.
• SCIM with Entra, Okta or Google Workspace, syncing about every 40 minutes (30 for Google). Teams sync from Entra only. Deprovisioning frees a seat but never removes the license from your bill automatically.
• Domain capture, after DNS verification that can take up to 72 hours, stops people on your domain from creating stray accounts unless invited.
• Workspace audit logs, on annual Enterprise+ only, delivered by webhook and holding no user content.

Check HIPAA, SOC 2, GDPR and data location

Read AI says it holds SOC 2 Type 2 certification. The report and the subprocessor list both sit on its Trust Center, so request them instead of trusting a badge. Read AI participates in the EU-U.S. Data Privacy Framework, states GDPR compliance and signs a DPA when you create a Workspace. For EU and EEA Workspace customers it acts as an Article 28 processor. Data lives in AWS us-east-1 in Northern Virginia by default. EU and Canada hosting, including Ask Read processing, is Enterprise+ only and arranged through sales.

HIPAA is narrow. Read AI signs a BAA only on Enterprise+ billed annually with at least 5 licenses, and only after SAML and domain capture are set up and the settings are verified with its team.^[3] A HIPAA workspace auto-joins only meetings the user hosts and turns push integrations off by default. It disables downloads, participant access, public links and domain discovery, and Ada is unavailable. Read AI says these workspaces keep all data in the US and cannot contribute to training. No other plan qualifies.

Check model training, retention and deletion

Read AI says meeting content trains its models only if a user opts in to the Read Customer Experience Program, which is off by default. Workspaces are excluded from it. Read AI says about 10-15% of users opt in. The Privacy Policy (June 2026) adds detail the help center skips. Connected Google data may train personalized models, never generalized ones. Under US state privacy laws, Read AI says it shares and sells identifiers, activity and inference data with marketing partners, which you can stop through Cookie Settings or Global Privacy Control.

Retention depends on the plan. On Free, report text is kept at least a year and no longer than two, and recordings are deleted 180 days after the meeting. On paid plans reports stay until someone deletes them, unless an Enterprise+ retention policy removes reports and Ask Read history after a set number of days, past and future. Only a report's owner can delete it for everyone. A guest without an account has to ask that owner. Account deletion is permanent, though Read AI may keep information the law requires.

• Affective metrics: outside the EU and UK, engagement scores draw on facial expressions, gaze and speech; any user can turn affective metrics off.
• Transcript storage: it can be limited or disabled while summaries remain.
• Self-deletion: Workspace admins can block members from deleting their own accounts.

Check the plan and the real cost

Every person in a Workspace needs a license, and all licenses sit on the same plan.^[4] A team that needs SSO therefore buys Enterprise+ for everyone, and Read AI routes that plan through sales. Five licenses billed annually come to $1,785 a year by our arithmetic, against $1,350 for five Enterprise licenses billed annually. The step costs $87 a year per user. Ten such licenses total $3,570 a year. Volume discounts of 10%, 15% and 20% start at 100, 500 and 1,000 annual licenses.

The trial is 7 days of Enterprise. It starts at sign-up with no card, runs once per account and falls back to Free, which covers 5 meeting reports a month (shared reports count) and meetings up to an hour. It joins all your meetings by default, so set auto-join first. Read AI does not offer refunds; cancelling keeps access until the period ends, as our Read AI pricing guide explains. Cancelling never stops the assistant. Only auto-join settings, disconnecting calendars or deleting the account do that.

• Pilot safely: run the trial with auto-join set to hosted meetings only.
• Price the whole Workspace: one plan for every member, not only the admins.
• Read the Terms: binding individual arbitration under Washington law, with 30 days to opt out by emailing Read AI's legal team.

The bottom line

Read AI is safe enough for most business teams once two defaults change: auto-join scope and recap delivery. The core controls are documented, training is opt-in, and anyone in a bot-mode meeting can stop it from the chat. The gaps are about governance. Desktop and mobile capture leaves consent to the user, and SSO, SCIM, domain capture, retention and HIPAA all sit on Enterprise+, which needs at least 5 licenses. Regulated teams should budget for annual Enterprise+; everyone else can start on Pro or Enterprise with tight settings.