Is Read AI safe? Who can send it to your meetings, who gets recaps, and how to remove it

The Morse teamPublished November 8, 20269 min read

As of November 2026, Read AI is safe by the usual security measures, with a SOC 2 Type 2 audit, AES-256 encryption, and a HIPAA business associate agreement on its top plan, but how private a meeting stays depends on whoever invited it. On most platforms, any Read user invited to your meeting can send Read without attending, its recap emails go by default to everyone with access to the report, and its desktop and mobile apps record with no bot and no notice in the meeting (Read AI). Training on meeting content is opt-in, though Read's privacy policy also describes inferring "certain demographic characteristics" from meeting audio and video "to improve our models."

We read Read AI's privacy policy (last updated June 29, 2026), its terms of service (February 26, 2026), its trust center's subprocessor list, its pricing page, and 10 of its help center articles on November 8, 2026, plus Caltech's IT page on removing Read. Read deserves credit for its opt-out. Any participant can type "Opt out" in the meeting chat and Read leaves and deletes everything it captured, with no approval needed from the host or the person who invited it (Read AI).

Read AI privacy settings at a glance

Read's defaults and where to change them, from its own pages, read November 8, 2026.

How does Read AI end up in your meetings?

Someone invited to the meeting connected it to their calendar. Read's help center says "In no instance does Read join random meetings" and that a user has to create an account and either set it to join or add it by hand (Read AI). That user needn't be in the room. Read's own explanation for why it keeps appearing is that "Someone else invited to your meeting uses Read," and "On most platforms, they don't need to attend the meeting to add Read; they only need to be invited" (Read AI). Zoom is the exception: Read joins only if its user is in the meeting, signed in to the Zoom account they connected.

Blocking it centrally doesn't always stop it. Caltech's IT office says "Read.AI is blocked from our Caltech environment, but you may find that it still joins your meetings," which it puts down to permissions granted before the block, and its fix is to sign in to Read and delete the account (Caltech). Deleting your own account doesn't stop anyone else's. Turning off Add Read? for a meeting in your Read calendar works only "at least 15 minutes before the meeting starts" (Read AI).

How do you remove Read AI from a meeting?

Type "Opt out" in the chat, or click the opt-out link if Read posted one. The command you pick decides what's left afterwards (Read AI):

Removing Read from the participant list can leave a report behind. Only "Opt out" deletes what was captured, and Read says that when anyone opts out, "recording stops for everyone in the meeting and the data from that meeting is deleted" (Read AI). If you joined late, you may not see Read's chat message unless the host pinned it, but the commands still work.

Two ways of recording leave nothing in the participant list. With Google Meet's native recording, someone sees a pop-up asking them to confirm that everyone agreed to be recorded, and closing it keeps Read out (Read AI). With the desktop or mobile app, Read "doesn't join the meeting as a participant or post a message in the chat, so other people in the meeting won't see that Read is recording." Read's advice for that case is to "ask them or the host directly."

Does Read AI train on your data?

Not on your meetings by default. Read's help center says "The default is to opt-out" and that contributing to its models "is completely optional" (Read AI). The privacy policy calls this the Customer Experience Program, which "allows Meeting Information and connected data (email, messages) to be used for the purpose of improving the features of our Service" once you opt in (Read AI).

The same policy describes other uses that aren't tied to that setting in its text. Read uses "audio and visual information to score user's affect and behavior during meetings" for its Read Score, and uses "audio and visual information, as well as other information like language, to infer certain demographic characteristics about users, which we use to improve our models." If you connect a Google account, Read "may, either now or in the future," collect Gmail messages, Drive files, Calendar events, and Google Chat messages "that we may use for developing, improving, or training personalized AI and/or ML models," and says it doesn't use that data for "generalized/non-personalized" models. The policy doesn't say whether the demographic modeling stops when the program is off. Read's terms grant it a license to "exploit and analyze your User Content," and say it may train on that content "subject to the terms and limitations described in our Privacy Policy and any applicable opt-in or opt-out mechanisms" (Read AI).

Two AI companies process meetings for Read. Its subprocessor list names OpenAI and Anthropic for "Augmentation of Meeting Data," both bound by an agreement "that includes zero re-use and zero retention" (Read AI). We compare training rules across apps in which AI companies train on your data.

Who gets your Read AI meeting reports?

Everyone with access to the report, unless you change it. The default for recap emails is People with access, decided by your internal and external participant settings; set both to No access and recaps go only to you (Read AI). Meeting Pre-Reads can send the last meeting's recap to the next meeting's invitees about an hour before it starts, and Update Calendar Event can put the report link in the shared calendar invite.

People who never signed up are in the data too. The privacy policy says Read collects "the names and email addresses of invitees and participants without a Read account" (Read AI). For its own marketing, the policy says Read "may disclose your identifiers, such as your email address(es) and phone number(s), to some of our advertising partners," and that under some state laws it shares and sells cookie IDs or "a hashed version of your email address" to "Marketing and advertising partners." Read's help center says it "does not share or sell this information for profit" in the context of customer metadata, so read both pages if this matters to you.

How do you delete Read AI recordings?

Delete the report, or the whole account, yourself. Read says deleting either "will permanently remove all of your associated data from our servers, and this cannot be undone" (Read AI). The account button is under Account Settings > Advanced, and "Read's support team can't delete an account for you from a support request" (Read AI). A workspace admin can gray that button out.

A report someone else owns is harder. You can request deletion through Read's Account and Privacy Center, but Read won't delete accounts or reports "at the request of a third party," corporate IT included, because "the data belongs to them as a user of Read." The privacy policy caps audio and video, and anything derived from it, at 2 years, and keeps paid accounts' data until the user stops paying or asks for deletion (Read AI).

Is Read AI HIPAA compliant and SOC 2 certified?

It has a SOC 2 Type 2 report, and HIPAA only on its top plan. Read offers a BAA "only" on an annual Enterprise+ plan, and only after a workspace has set up SAML sign-in and domain capture (Read AI). Enterprise+ needs at least 5 licenses and costs $29.75 per user a month billed annually, or $39.75 monthly, as of November 8, 2026 (Read AI). Two-factor sign-in "is not enforced via username/password," so a password account is only as strong as its password.

The terms make consent your job: you're "solely responsible for any User Content provided by you, including providing adequate notice and consent to individuals in the User Content." Disputes go to individual arbitration, and you can opt out by emailing legal@read.ai within 30 days of first accepting the terms (Read AI). This isn't legal advice. We found no lawsuit naming Read AI in news and legal press as of November 8, 2026. Our page on Otter AI covers the 2025 class action against a competitor.

How Morse keeps what you ask about a meeting off Read's servers

Every risk above starts with a meeting turned into a report that lives on Read's servers, shared by the defaults of whoever invited the bot, and processed by two outside AI companies. Morse doesn't join or record meetings. It's for the questions you have afterwards, like whether a contract term someone raised is normal or how to answer a hard email, and it stores those chats in your browser, encrypted, not on Morse's servers.

• E2EE, for pasting notes with a client's or patient's words in them. Your browser checks the secure enclave's proof that it's genuine, then encrypts the message on your device so only that enclave can read it. Morse's servers relay text they can't read, and only your browser decrypts the reply. E2EE runs open-weight models like GLM, Kimi, and DeepSeek on enclaves run by third-party providers, not by Morse, and depends on the enclave hardware and attestation working as designed. It comes with Pro, at $19 a month.
• Private, every new chat's starting mode, for working through what the meeting decided. Morse has zero data retention agreements with its inference, search, and other providers, so they keep nothing. Where a provider confirms zero retention on each reply, Morse checks it and refuses a reply that doesn't.
• Anonymous, to ask GPT, Claude, or Gemini without your account behind it. Our proxy strips your account, email, and IP address and sends the question under Morse's own account. The provider sees the message without knowing it's you, and may keep it for a limited time to check for abuse, under its own policy. Morse removes who you are, not what you paste, so take attendees' names out first.

There's no recap to switch off and no training program to opt out of: Morse doesn't train AI on your content, sell your data, or show ads (privacy policy). Clearing your browser or deleting your account removes your chats, and Morse can't recover them, so keep a copy of anything you'll need.

So is Read AI safe enough for you?

• If you use Read: set Send to to Only me, set outside participant access to No access, leave the Live Meeting Dashboard link off, and say you're recording before you start.
• If someone else's Read joins: type "Opt out", not "Read stop", if you want nothing kept.
• If you can't see it: ask whether anyone is recording with the desktop or mobile app.
• Training: leave the Customer Experience Program off, and don't connect Gmail or Drive unless you need to.
• Asking AI about the meeting afterwards: use an E2EE chat on Morse, where only a verified enclave reads the message and the history stays in your browser.

Try a chat from the Morse home page without an account, or start free with no card needed.