# Is Read AI Safe? Opt-In AI Training, but a Bot That Spreads > Is Read AI safe? I read its policy and terms. AI training is opt-in, but its bot spreads, others' copies can't be deleted and six universities block it. - URL: https://www.getvoibe.com/resources/is-read-ai-safe/ - Author: Ayush - Published: 2026-10-26 ## Is Read AI Safe? The Short Answer In October 2024, the University of Memphis told staff to deny Read AI's requests to join their Teams meetings. Its IT office [explained why](https://blogs.memphis.edu/cio/2024/10) in one line: Read AI "is able to quickly propagate throughout an organization." So I read Read AI's privacy policy, terms and privacy center line by line. The first surprise was a good one. Read AI's AI training is opt-in. Contributing to model improvement is off by default. Otter, Fathom and Granola all train on de-identified or anonymised meeting data unless you act. **Short answer: Read AI is safer than its reputation on training, but risky for confidential calls.** The risk isn't what Read does with your meeting. It's how many copies exist, and who controls them. ### Where the risk sits - **It spreads.** Read can join when any invited participant has it connected, "even if they don't actually attend the meeting", per its own Account & Privacy Center. - **You can't delete someone else's copy.** Non-owners can only request deletion. Read says it can't delete reports "at the request of a third party", corporate IT included. - **Reports live in its cloud.** They sit in AWS us-east-1 in Northern Virginia. Paid accounts are kept until you stop paying or ask. Audio and video are kept no longer than 2 years. - **The policy reaches past meetings.** It describes inferring demographic traits "to improve our models". Google Workspace data may feed personalized models "either now or in the future". - **HIPAA needs Enterprise+.** That plan requires at least 5 licences. ### What Read AI gets right - Training on your meetings is off unless you opt in. - Anyone on the call can type "opt out" in the chat. Read leaves and deletes the meeting data for everyone. - The bot announces itself and asks to be let in. - Read states SOC 2 Type II and says "We never sell your data". - I found no lawsuit naming Read AI as of October 26, 2026. ### How I checked - On October 26, 2026, I read Read AI's privacy policy (last updated June 29, 2026) and terms (last updated February 26, 2026). - I also read its privacy center, pricing page and help center, plus six university IT notices. - I haven't used Read AI hands-on. How it behaves comes from its own documentation. - Its trust center loads only with JavaScript. I couldn't read its SOC 2 report or subprocessor list. ### What it costs, and the no-bot option Price isn't the safety problem. Every plan and limit is in our [Read AI pricing breakdown](https://www.getvoibe.com/resources/read-ai-pricing/). Notetakers that keep no vendor copy are in our [Read AI alternatives guide](https://www.getvoibe.com/resources/read-ai-alternatives/). If the number of copies is the deal-breaker, look at [Voibe Work](https://www.getvoibe.com/resources/voibe-work-meeting-notes-no-bot/) (the app we build). No bot joins, on Mac or Windows, so there's nothing to spread. The audio is deleted as soon as processing completes. The notes are saved on your computer, never trained on. It costs $149 a year. The math: - **vs Read AI Pro annual ($180):** $31 (17.2%) less. - **vs Enterprise annual ($270):** $121 (44.8%) less. - **vs Enterprise+ ($357 a seat, 5-seat minimum)**, the HIPAA plan: $208 (58.3%) less per seat. - **vs Read AI Free ($0):** Free wins for five short meetings a month. Voibe reminds you to tell everyone you're taking notes when recording starts. The recording-consent rules are yours to follow. > **Key takeaway:** Read AI's AI training is opt-in and off by default, which beats Otter, Fathom and Granola. The risks are elsewhere: the bot joins whenever any invited user has Read connected, reports sit in its cloud while you pay, you can't delete a copy someone else owns, and HIPAA needs Enterprise+ with 5 licences. No lawsuit naming Read AI was found as of October 26, 2026. ## Key Takeaways: Read AI Safety at a Glance (October 2026) Every row comes from Read AI's own pages, university notices and rating pages. I checked them on October 26, 2026. | Question | Read AI's answer (October 2026) | Source | | --- | --- | --- | | **Does a bot join?** | Yes, the Read Assistant joins Zoom, Teams and Meet once a user connects a calendar. Read says this "may happen automatically for eligible meetings". The desktop app (Windows 10+, macOS 14+) and a Google Meet integration capture without a bot. | Read AI privacy center; help center | | **Why does it keep joining?** | "If someone else invited to the meeting has Read connected, it may still join—even if they don't actually attend the meeting." | Read AI Account & Privacy Center | | **Can a guest remove it?** | Yes. Type "opt out" in chat (removes Read and deletes all meeting data) or "Read stop" (removes Read, keeps the report so far). | Read AI help center | | **Where is it stored?** | Encrypted at rest in AWS us-east-1, Northern Virginia. The policy says "servers located in the United States and other countries". | Read AI help center; privacy policy | | **How long?** | Audio and video "in no case for longer than 2 years". Paid accounts kept until you stop paying or ask. Custom retention is Enterprise+ only. | Read AI privacy policy (June 29, 2026); pricing page | | **Trained on?** | Opt-in. "AI training is opt-in. Contributing to model improvement is off by default." | Read AI privacy center | | **Other data uses** | Infers demographic characteristics from audio and visual data "to improve our models". Google Workspace data may train personalized models "either now or in the future". | Read AI privacy policy | | **Who can delete a report?** | Only its owner. Others request deletion; Read is "not able to delete accounts or meeting reports at the request of a third party". | Read AI help center | | **Attestations** | Read states SOC 2 Type II, GDPR (DPA and SCCs), AES-256 at rest and in transit; Data Privacy Framework participant. | Read AI privacy center | | **HIPAA** | Pricing page: "HIPAA compliance" on Enterprise+ (5+ licences). Privacy center: "BAA available on request". | Read AI pricing page; privacy center | | **Lawsuits** | None naming Read AI found as of October 26, 2026. | Web search, October 26, 2026 | | **Institutional blocks** | University of Memphis (2024), Case Western Reserve (2025), CUNY (2025), UC Riverside (2025), Morgan State (2026) and Eastern Washington University block it. | [Memphis ITS](https://blogs.memphis.edu/cio/2024/10); [EWU IT](https://support.ewu.edu/support/solutions/articles/10000099209-Availability-of-Read-ai-and-Otter-ai) | | **Ratings** | App Store 4.88 (1,034 ratings); Chrome Web Store 4.4 (30 ratings, 400,000 users). | [App Store](https://apps.apple.com/us/app/id6575345796); [Chrome Web Store](https://chromewebstore.google.com/detail/read-ai/aiamjjeggglngiggkmmbnpnpeejjejaf) | | **Price** | Free $0 (5 meetings a month); Pro $15/mo annual ($180) or $19.75 monthly; Enterprise $22.50 or $29.75; Enterprise+ $29.75 or $39.75, 5-licence minimum. | Read AI pricing page; [our Read AI pricing breakdown](https://www.getvoibe.com/resources/read-ai-pricing/) | ## What Is Read AI, and How Does It Join a Meeting? [Read AI](https://www.read.ai/) is a US meeting-intelligence platform. Its homepage headline reads "Meetings In, Decisions Out". It's more than a notetaker. Beyond transcripts and summaries, it offers a "Personalized meeting coach" and engagement and sentiment metrics. Its privacy policy says it notifies people "that the meeting is being measured". ### Three ways Read AI captures a call - **The bot (Read Assistant).** It joins Zoom, Microsoft Teams and Google Meet after a user connects a calendar. Read says it joins "only when a user has set it up or initiated it". It adds: "this may happen automatically for eligible meetings". - **The desktop app, no bot.** "Capture meetings anywhere, no bot necessary", including in-person discussions, 1:1s and Slack Huddles. It's "Available on Windows 10+ and MacOS 14+". - **Google Meet without a bot.** The help center lists a "Read Native Integration for Google Meet (bot-less)". Mobile apps capture in-person meetings too. ### It reaches past meetings That matters for a privacy review. Read AI isn't only holding your calls. - **Search.** Ask Read searches "meetings, emails, messages, and more". - **Connections.** A Gmail Chrome extension, plus Slack, Outlook, Salesforce, HubSpot, Jira and Notion. - **AI tools.** A Claude Connector, a ChatGPT App and an MCP Server. Paid plans give "Direct access to native LLMs from Anthropic Claude and OpenAI GPT" in its Search Copilot. Each connection widens what Read can see. Connect only what you'll use. ### What users say - **4.88 out of 5 from 1,034 ratings** on the [App Store](https://apps.apple.com/us/app/id6575345796) - **4.4 out of 5 from 30 ratings** on the [Chrome Web Store](https://chromewebstore.google.com/detail/read-ai/aiamjjeggglngiggkmmbnpnpeejjejaf), where it lists 400,000 users Both checked October 26, 2026. High ratings say the reports are useful. They don't say where the meeting goes. ## Why Does Read AI Keep Joining My Meetings? Because someone else invited to the meeting has Read connected. You don't need an account for it to show up. Read's Account & Privacy Center says so plainly. "If someone else invited to the meeting has Read connected, it may still join—even if they don't actually attend the meeting." That's also its answer if Read still joins after you've deleted your account. Another participant is using it. ### How it spreads, in Memphis's words The University of Memphis [described the loop](https://blogs.memphis.edu/cio/2024/10) on October 29, 2024. Read AI had spread among its Teams users. The notice reads: > "The service joins Teams meetings, records all content and emails summaries to the participants. In order to access the full notes, users must create their own Read AI account. Read AI then attempts to join all Teams meetings of the new user." Its conclusion: "Through this method, Read AI is able to quickly propagate throughout an organization." Memphis said Read AI's terms violate its data security and data privacy policies. It blocked Read from November 1, 2024. ### What Read's docs say today That's Memphis's description, from 2024. Read's current help center puts more in the owner's hands: - Report access is a "requirement … set by the meeting report owner". - Owners choose whether reports are auto-shared with participants. So the loop depends on settings. But you don't control another user's settings. ### How to see who invited Read Check the meeting chat. Read says it "will attempt to notify users via chat" and "will also list the name(s) of who invited Read". The help center adds that "multiple people can invite Read to meetings". The chat message names them. ### How to remove Read from a meeting - **Type "opt out" in the chat.** Read leaves and deletes all the meeting data. - **Type "Read stop".** Read leaves, but keeps the report up to that point. - **Ask the host.** A host can remove Read like any other participant. Then ask the person who invited it to change their join settings. Otherwise it may turn up at the next meeting too. ### The platforms are adding gates - **Google Meet:** since March 24, 2026, a "safeguarded guest admit flow" sends guests such as bots to a second queue. That queue defaults to deny. - **Microsoft Teams:** began tagging third-party bots in the lobby in May 2026. They're admitted separately. A bot now has to be let in on purpose. Read's desktop app and Meet integration don't add a bot at all. ## Where Does a Read AI Meeting Go? Bot, Desktop App and Cloud To Read's cloud, whichever way you capture it. The bot, the desktop app and the Meet integration all produce a report Read stores. ### What Read's documents say - **Location.** The help center: "stored encrypted at rest within the AWS us-east-1 datacenter in Northern Virginia USA". Large customers can ask sales about other locations. - **The policy's wording is wider.** It says "servers located in the United States and other countries". - **Encryption.** "AES-256 Encryption — At rest and in transit", per the privacy center. - **What's collected.** Meeting audio and video, the subject, location and access details. Also the names and emails "of invitees and participants without a Read account". - **Playback.** Audio and video playback comes on Enterprise and up. Read says if you don't keep it, "no audio or visual data is retained by Read beyond the duration needed to reliably produce the meeting report". ### Every participant's report is its own copy This is the part most people miss. When three colleagues each have Read connected, each can own a report of the same meeting. Deleting yours doesn't touch theirs. Read calls itself "a service provider, and the data belongs to them as a user of Read". For a team that wants every call searchable, that's the product working. For a client call about a lawsuit or a diagnosis, it's copies you can't manage. ### What I couldn't verify Read's SOC 2 report, subprocessor list and DPA sit on its trust center. It loads only with JavaScript, and I couldn't read it on October 26, 2026. So I haven't named a transcription vendor. ### Where Your Meetings Go: Read AI vs Otter vs Fathom vs Granola vs Fireflies vs Voibe Work Same five questions, six notetakers. Deep dives: [Is Otter Safe?](https://www.getvoibe.com/resources/is-otter-safe/), [Is Fathom Safe?](https://www.getvoibe.com/resources/is-fathom-safe/), [Is Granola Safe?](https://www.getvoibe.com/resources/is-granola-safe/) and [Is Fireflies Safe?](https://www.getvoibe.com/resources/is-fireflies-safe/) | Tool | Bot in the call? | What's kept, and where | Retention | Training default | Attestations | | --- | --- | --- | --- | --- | --- | | **Read AI** | Yes by default; desktop app (Windows, Mac) and Google Meet integration without one | Reports and transcripts, plus audio and video with playback; AWS us-east-1 | Paid: until you stop paying or ask; audio and video at most 2 years; custom retention Enterprise+ | Off (opt-in) | Read states SOC 2 Type II, GDPR; HIPAA on Enterprise+; BAA on request | | **Otter** | Yes by default; desktop app records without a bot (Mac, Windows) | Audio and transcript; Otter cloud | Until you delete; custom retention through an account manager | On (de-identified); no opt-out found | SOC 2 Type II; HIPAA as an Enterprise add-on | | **Fathom** | Yes by default; bot-free in the Mac app | Video, audio, transcript, summary; Fathom cloud, US | Until you delete; auto-delete Enterprise only | On (de-identified); opt-out | Fathom states SOC 2 Type II, GDPR, HIPAA; signed BAA Enterprise | | **Granola** | No | Audio deleted after transcription; notes in a US-hosted AWS cloud | Indefinitely unless a retention policy is set | On for Free and Business (anonymised); opt-out; off on Enterprise | SOC 2 Type II; HIPAA and BAA Enterprise only | | **Fireflies** | Yes by default; Take Notes in the desktop app without one | Transcript and summary, plus audio and video in bot mode; Fireflies cloud | While the account is active; custom retention Enterprise only | Never (policy) | Fireflies states SOC 2 Type II, ISO 42001, GDPR; BAA on Enterprise with Private Storage | | **Voibe Work** | No (Mac and Windows) | Audio deleted as soon as processing completes; transcript and summary saved on your computer | Your files, your choice | Never trained on | None claimed; BAA available on request | > **Key takeaway:** Every Read AI capture path ends in its cloud, in AWS us-east-1. Paid accounts keep reports until you stop paying or ask; audio and video stay no longer than 2 years. Each participant who owns a report owns a separate copy, and only they can delete it. ## Does Read AI Train on Your Data? Opt-In, With Fine Print **Not on your meetings, unless you opt in.** Read's privacy center: "AI training is opt-in. Contributing to model improvement is off by default." That's a stronger default than most. Otter, Fathom and Granola all train on de-identified or anonymised meeting data unless you act ([Otter](https://www.getvoibe.com/resources/is-otter-safe/), [Fathom](https://www.getvoibe.com/resources/is-fathom-safe/), [Granola](https://www.getvoibe.com/resources/is-granola-safe/)). Only Fireflies goes further, with a flat no-training policy. ### The opt-in has a name It's the Customer Experience Program, a setting you switch on. The policy says it "allows Meeting Information and connected data (email, messages) to be used for the purpose of improving the features of our Service." The privacy policy says model training happens "consistent with your account settings". The terms say the same, subject to "any applicable opt-in or opt-out mechanisms". ### Four lines in the policy worth reading twice The opt-in covers your meetings. The policy also describes other uses. To be fair, none of these says your meetings train a general model. - **Demographic inference.** "We also use 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." - **Roles and companies.** Read infers "users' role during a meeting". It uses names and emails "to infer company affiliation". - **Google Workspace.** Read "may, either now or in the future" collect Google user data for "developing, improving, or training personalized AI and/or ML models". That includes Gmail, Google Drive and Google Chat. It "may be transferred to third party AI tools". The policy says it isn't used for generalized models. - **Data brokers.** Read lists a source "from third-party data brokers who provide us with audio and visual data sets". ### Advertising and "we never sell" The privacy center says "We never sell your data". The policy is more careful. - Identifiers such as hashed emails and phone numbers go to advertising partners. That "may constitute 'sharing' or 'selling'" under US state laws. - Meeting information isn't shared for targeted ads "unless you provide your consent". So your meeting content stays out of ads by default. Your identifiers don't. ### My read On training, Read AI deserves credit. The opt-in is real and clearly worded. But the policy gives Read room to analyze you, not only transcribe you. If you connect Google Workspace, read that section before you click allow. Voibe doesn't train on audio or text, from dictation or meetings. So the gap with Voibe Work isn't only training. It's what else the tool can read, and where the notes live. > **Tip:** Save a dated copy of Read AI's privacy policy (last updated June 29, 2026) and terms (February 26, 2026) with your vendor records. If the opt-in wording ever changes, you'll be able to show what you agreed to. ## How Long Does Read AI Keep Your Meetings, and Who Can Delete Them? For paid accounts, until you stop paying or ask Read to delete it. Audio and video have a hard cap. The policy: "We store your audio and video information … in accordance with our internal policies, but in no case for longer than 2 years." It continues: "For paid accounts, we will store your data until you (i) stop paying, or (ii) request that we delete some or all of your data." ### The controls that exist - **Custom retention is Enterprise+ only.** It can "automatically delete meeting reports after a specified number of days", per the pricing page. - **Owners delete their own reports.** There's also an account-deletion button in Account Settings. Support can't do it for you. - **Playback is a choice.** Don't keep audio and video, and Read keeps none beyond producing the report. ### The part that catches IT teams out Non-owners can't delete a report. They can request deletion through the Account and Privacy Center form. The request goes to the report's owner. Read's help center is blunt: "we are not able to delete accounts or meeting reports at the request of a third party". That includes corporate IT. So if a colleague recorded a client call with Read, the client can't delete it. Neither can your IT team. Only the colleague can. ### Free accounts Read Free covers 5 meetings a month, each up to 1 hour. The paid-account retention line doesn't name Free. The 2-year cap on audio and video applies to everyone. Plan-by-plan detail is in our [Read AI pricing guide](https://www.getvoibe.com/resources/read-ai-pricing/). ## Is Read AI HIPAA Compliant? SOC 2, GDPR and the BAA Only on Enterprise+, and Read's two pages word it differently. - **Pricing page:** "HIPAA compliance" appears on Enterprise+ only, described as "Support for enabling HIPAA compliance in your Read workspace". - **Privacy center:** "HIPAA — BAA available on request". It adds that Read "meets HIPAA's technical safeguard requirements". Read both together. The HIPAA workspace setting is an Enterprise+ feature. Enterprise+ "REQUIRES 5+ LICENSES". ### What the HIPAA plan costs - Enterprise+ is $29.75 per seat a month billed annually ($357 a year), or $39.75 monthly. - Five licences make the floor $1,785 a year on annual billing. - Read's terms say "Read AI does not offer refunds for Services." ### What each claim covers, and what it doesn't - **SOC 2 Type II**, "Independently audited annually", per Read. It's an audit of security controls. It doesn't change where reports are stored or for how long. - **GDPR:** "DPA & SCCs available". Read also participates in the Data Privacy Framework. - **A BAA is a contract**, not a certification. Read what it covers before you sign. - **Other Enterprise+ controls:** SAML and SCIM, domain capture and custom data retention. ### The question certificates don't answer None of this stops a colleague's personal Read account from joining a patient call. A BAA covers your workspace, not the copies other people own. Handle protected health information below Enterprise+? Keep it out of Read. Our [HIPAA dictation guide](https://www.getvoibe.com/resources/hipaa-dictation/) starts with data flow for the same reason. > **Key takeaway:** Read AI's pricing page puts "HIPAA compliance" on Enterprise+ only, which needs 5 or more licences ($1,785 a year minimum on annual billing). Its privacy center says a BAA is available on request. Read states SOC 2 Type II and GDPR. Below Enterprise+, keep health information out of Read. ## Has Read AI Been Sued? And Which Universities Block It? **I found no lawsuit naming Read AI as of October 26, 2026.** That's a search result, not a guarantee. Re-check before relying on it. ### Your own claims go to arbitration Read's terms require binding individual arbitration, through NAM with AAA as a fallback. There's a class-action waiver. There's also an opt-out, so read the procedure soon after you sign up. ### Other notetakers are in court - **Otter** faces a consolidated privacy class action in California ([details on Otter](https://www.getvoibe.com/resources/is-otter-safe/)). - **Granola** faces a wiretap class action aimed at bot-free capture ([the Granola lawsuit explained](https://www.getvoibe.com/resources/granola-lawsuit/)). - **Fireflies** faces a pending BIPA voiceprint class action ([details on Fireflies](https://www.getvoibe.com/resources/is-fireflies-safe/)). Bot or no bot, the common thread is whether everyone on the call agreed. ### Six universities that block Read AI Read AI has no lawsuit, but it has a long block list. These six named it: - **University of Memphis** blocked it from November 1, 2024, after its [October 2024 notice](https://blogs.memphis.edu/cio/2024/10) on how Read spreads. - **Case Western Reserve University** [announced on September 3, 2025](https://case.edu/utech/about/utech-news/learn-about-upcoming-third-party-ai-note-taker-application-block) that "Starting Sept. 12" it would block notetakers "such as Fireflies.ai, Read.ai and Fanthom.video". One reason: "CWRU does not have enterprise contracts with these vendors". - **CUNY** blocked Read.AI and Otter.AI from September 11, 2025, per a [York College IT notice](https://mailings.york.cuny.edu/cgi-bin/dada/mail.cgi/archive/faculty_ft/20250905090020/). - **UC Riverside**'s [October 2025 tech bulletin](https://lists.ucr.edu/pipermail/tech-bulletin/2025-October/000244.html) blocked "Fireflies AI, Spinach AI, and Read AI" from UCR-based Zoom meetings from October 10, 2025. - **Morgan State University** listed "Read.ai" and "Read.ai Notetaker" among blocked tools in June 2026 ([Morgan State IT](https://www.morgan.edu/information-technology/security/ai-meeting-note-taking-tools)). - **Eastern Washington University** blocked Read AI's and Otter's Zoom and Teams integrations ([EWU IT](https://support.ewu.edu/support/solutions/articles/10000099209-Availability-of-Read-ai-and-Otter-ai)). ### Why they did it Two reasons recur. EWU cited "several complaints regarding read.ai and otter.ai tools appearing in Zoom and Teams meetings without the consent of all participants". It had no data sharing agreements with either vendor. CUNY's reason was storage: "To prevent the inappropriate disclosure and storage of CUNY online meeting content on unapproved cloud storage servers." Consent and storage. Those are the two questions this page keeps coming back to. None of these blocks touch the desktop app, because no bot joins. That doesn't make it allowed. An employer's or school's approved-tools list overrides anything here. > **Key takeaway:** No lawsuit naming Read AI was found as of October 26, 2026. Six universities block it: Memphis (2024), Case Western Reserve, CUNY and UC Riverside (2025), Morgan State (2026) and Eastern Washington University, citing spread, consent complaints and unapproved cloud storage. ## Recording Consent: Read AI's "Opt Out" Command Is a Real Strength Read AI gives the people on your call more control than most notetakers. Credit where it's due. ### What Read tells the people on your call - "Read announces itself at the start of every meeting and requires host approval before joining", per the privacy center. - It shows a participant tile or a Read logo. - Where it can, it posts a chat message naming who invited it. - Anyone can type "opt out". "The meeting data is immediately and permanently deleted." That last one is rare. A guest who never accepted Read's terms can wipe the meeting for everyone. ### Where the notices stop The policy has an exception. Read notifies users "except where meeting chat and notices have been disabled or are unsupported". And those notices describe the bot. With the desktop app or an in-person meeting, say it out loud yourself. ### The states where everyone has to agree All-party-consent states, and the ones with important nuances, per [Justia's 50-state survey](https://www.justia.com/50-state-surveys/recording-phone-calls-and-conversations/): - **California**: California Invasion of Privacy Act (CIPA), statutory damages of $5,000 per violation. - **Connecticut**: civil liability for recording phone calls without all-party consent. - **Delaware**: arguably all-party; the law is ambiguous. - **Florida**, **Maryland**, **Massachusetts**, **New Hampshire** and **Pennsylvania**. - **Illinois**: Eavesdropping Act; generally all-party. - **Michigan**: technically all-party, though courts have held participants can record. - **Montana**: an all-party "knowledge" state. - **Nevada**: all-party for phone calls, one-party in person. - **Oregon**: all-party in person, one-party for phone calls. - **Washington**: generally all-party. ### Recaps are a disclosure too Owners choose whether reports are auto-shared with participants. A summary in a client's inbox is a disclosure, even if the recording was consented to. ### A one-line script that covers most calls Say: "I'm taking AI notes on this call. Is everyone OK with that?" Then wait for a yes from each person. Voibe Work has no participant-side opt-out, because it has no bot in the call. Read AI wins on that one. Voibe reminds you to tell everyone you're taking notes when recording starts. The recording-consent rules are yours to follow. ## The Read AI Safety Decision Tree Five questions, from the easiest case to the hardest. Stop at the first one where you can't accept Read's answer. 1. **Is it an internal, non-confidential meeting?** Stand-ups, planning, your own team. If yes, Read AI is a reasonable choice. Turn off auto-share and set who can open reports. 2. **Will people outside your company join?** Clients, patients, candidates and partners never saw Read's terms. Each needs notice and, in the states above, consent. 3. **Will health information come up?** HIPAA support is on Enterprise+ only, with a 5-licence minimum. On any other plan, keep those calls out of Read. 4. **Is a copy you can't delete acceptable?** Every colleague with Read connected may own a report. You can only request deletion of theirs. 5. **Can the meeting sit in Read's cloud while you pay?** Below Enterprise+ there's no custom retention. If the answer is no, use a tool that keeps no copy on its side. Most internal and sales calls stop at question 1 or 2, and Read handles them well. Legal, medical and financial client calls usually reach question 4 or 5. Our [notetaker guide for lawyers](https://www.getvoibe.com/resources/best-ai-meeting-note-taker-for-lawyers/) and [notetaker guide for financial advisors](https://www.getvoibe.com/resources/best-ai-meeting-note-taker-for-financial-advisors/) cover those rules. ## The 5-Step Read AI Safety Audit: Settings to Check Today Keeping Read AI? These five checks cover most of the risk. 1. **Set your join preferences.** Decide which meetings Read joins on its own. Keep it out of client, HR and legal calls. 2. **Turn off auto-share.** Owners choose whether reports go to participants. Switch it off, and limit who can open a report. 3. **Skip audio and video playback.** On Enterprise and up, don't keep playback unless you need it. Without it, Read keeps no audio or video beyond producing the report. 4. **Check the Customer Experience Program is off.** It's opt-in. If someone switched it on, meetings, email and messages can be used to improve features. 5. **Narrow the Google Workspace connection.** The policy covers Gmail, Drive and Chat for personalized models. Connect only what you use. ### Then talk to your colleagues Your settings cover your account only. Ask colleagues who have Read connected to do the same five steps. Ask them to keep it out of meetings with your clients. ### Which steps matter most Steps 1 and 2. They decide where Read goes and who sees what it writes. Read already handles training for you, as long as nobody opts in. > **Warning:** You can't delete a report someone else owns. Read says it is "not able to delete accounts or meeting reports at the request of a third party", so a colleague's copy of your meeting outlives anything you change here. ## A Setup With No Bot to Spread: Voibe Work Read AI solved training with an opt-in. What it can't change without changing the product is the spread, and the cloud copy. [Voibe Work](https://www.getvoibe.com/resources/voibe-work-meeting-notes-no-bot/) (ours) is built the other way round. ### What Voibe Work does differently - **No bot in the call, on Mac or Windows.** It captures Zoom, Microsoft Teams, Google Meet, Webex, Slack huddles or any other meeting app from your computer. It also records in-person meetings through your Mac or PC's mic. - **Nothing to spread.** There's no bot to invite itself into your colleagues' meetings. The notes stay on your computer unless you copy or export them. - **Speaker labels without a bot.** Each speaker is labelled, with a time next to every line. Click a name to rename them and the summary updates. Names aren't pulled from a calendar. - **Audio deleted after processing.** Open-source models on zero-retention cloud providers process the audio. It's deleted as soon as processing completes ([what zero data retention means](https://www.getvoibe.com/resources/zero-data-retention/)). - **Notes saved on your computer**, not on Voibe's servers, and never trained on. Retention is your call, no Enterprise+ plan needed. - **The rest.** Up to 4 hours per meeting, unlimited meetings. Templates for each type of meeting, chat with your meetings, one-click copy and PDF export. Dictation on Mac and Windows is included. - **BAA available on request**, for practices that need one. **Consent doesn't change.** Voibe reminds you to tell everyone you're taking notes when recording starts. The recording-consent rules are yours to follow. ### Where Read AI wins - **The "opt out" command.** Any guest can remove Read and delete the meeting. Voibe Work has no participant-side opt-out. - **A free plan for light use.** Read Free covers 5 meetings a month, up to 1 hour each. - **Longer meetings at the top.** Enterprise+ allows 8 hours. Pro and Enterprise match Voibe Work at 4. - **Reach.** Read has iPhone and Android apps, video playback, a meeting coach, CRM integrations and email search. Voibe Work has no phone app and no audio or video playback. It doesn't list calendar auto-join, CRM, email or Slack integrations. - **Internet.** Voibe Work's meeting notes need a connection. On-device processing is a Voibe dictation feature on Apple Silicon Macs, not a meeting-notes feature. ### What It Costs: Read AI vs Voibe Work Prices from Read AI's pricing page (checked October 26, 2026) and getvoibe.com/pricing. Read plans are per seat. Full detail: [Read AI pricing](https://www.getvoibe.com/resources/read-ai-pricing/). | Plan | Monthly | Per year (annual billing) | 3 years | Longest meeting | | --- | --- | --- | --- | --- | | Read AI Free | $0 | $0 | $0 | 1 hour | | Read AI Pro (per seat) | $19.75 | $180 | $540 | 4 hours | | Read AI Enterprise (per seat) | $29.75 | $270 | $810 | 4 hours | | Read AI Enterprise+ (per seat, 5+ licences) | $39.75 | $357 | $1,071 | 8 hours | | **Voibe Work** | **$19** | **$149** | **$399 lifetime** ($447 on annual) | 4 hours | - **Against Pro:** $31 (17.2%) less a year ($180 − $149 = $31; $31 ÷ $180). Month to month, $0.75 (3.8%) less ($19 vs $19.75). - **Against Enterprise:** $121 (44.8%) less a year ($270 − $149 = $121; $121 ÷ $270). - **Against Enterprise+**, the HIPAA plan: $208 (58.3%) less per seat. Five seats of Voibe Work cost $745, against Read's $1,785 minimum. That's $1,040 (58.3%) less. - **Over three years:** the $399 lifetime plan is $141 (26.1%) less than three years of Pro annual ($540). - **With dictation:** Read AI has no dictation app. Read AI Pro plus [Wispr Flow Pro](https://www.getvoibe.com/resources/wispr-flow-pricing/) is $324 a year ($180 + $144). Voibe Work covers both for $175 (54.0%) less. **My take:** for five short meetings a month, Read Free is the better deal. If copies you can't control are the risk, Voibe Work costs less than every Read plan that addresses it. Voibe Work starts with a 7-day free trial of every feature, no credit card and no automatic charge. Then it moves to Voibe Free unless you buy. Paid plans carry a 30-day money-back guarantee. [See Voibe Work pricing](https://www.getvoibe.com/pricing), read the [October update on Windows meeting notes and 4-hour meetings](https://www.getvoibe.com/resources/voibe-free-plan-meeting-notes-windows/), or compare the [best no-bot meeting note takers](https://www.getvoibe.com/resources/best-no-bot-meeting-note-takers/). > **Key takeaway:** Voibe Work has no bot, so there's nothing to spread: audio is deleted as soon as processing completes and the notes are saved on your computer, never trained on, for $149 a year. That's $31 (17.2%) less than Read AI Pro annual and $208 (58.3%) less per seat than Enterprise+. Read AI Free is cheaper for light use, and its "opt out" command has no Voibe equivalent. Consent is your job with both. ## Who Read AI Is Safe For, and Who Should Pick Something Else Read AI is safe for most internal and sales calls. Turn off auto-share first, and make sure everyone knows the call is recorded. It's a weaker fit where copies of the meeting are the risk. Find your situation: | Your situation | Read AI verdict | What to do | | --- | --- | --- | | Internal stand-ups and planning | Safe | Turn off auto-share; delete old reports periodically | | Sales and recruiting calls | Safe with notice | Say it out loud; tell guests they can type "opt out" | | Participants in California, Illinois or another all-party state | Safe only with everyone's consent | Ask each person and wait for a yes | | Read keeps joining meetings you host | Fixable | Check the chat for who invited it; ask them to change join settings | | You want no bot | Workable | Use the desktop app (Windows 10+, macOS 14+) or the Google Meet integration | | Patient conversations with health information | Enterprise+ only | Five licences minimum; get the BAA and read what it covers | | Privileged legal calls | Risky | Read the [lawyers guide](https://www.getvoibe.com/resources/best-ai-meeting-note-taker-for-lawyers/); prefer no vendor-side copy | | Client reviews at an advisory firm | Check recordkeeping rules first | See the [financial advisors guide](https://www.getvoibe.com/resources/best-ai-meeting-note-taker-for-financial-advisors/) | | Your university or employer blocks third-party notetakers | Not allowed | Follow the policy (Memphis, Case Western, CUNY, UC Riverside, Morgan State and EWU block Read) | | You need meetings auto-deleted on a schedule | Enterprise+ only | Buy Enterprise+ for custom retention, or use a tool that keeps no copy | Weighing a different notetaker altogether? Our [Read AI alternatives](https://www.getvoibe.com/resources/read-ai-alternatives/) compare where each one keeps your meetings. Not sure which category you need? The [dictation vs notetaker breakdown](https://www.getvoibe.com/resources/dictation-vs-notetaker-vs-meeting-assistant-vs-transcription/) explains how they differ. Our [AI privacy guide](https://www.getvoibe.com/resources/privacy/) covers the wider picture. ## Is Read AI Safe? FAQ Straight answers on Read AI's privacy, joining, compliance and alternatives, grouped by theme. ### Privacy and Your Data **Is Read AI safe to use?** Yes, for most internal and sales calls. - Its AI training is opt-in and off by default, it states SOC 2 Type II and GDPR, and any guest can type "opt out" to delete the meeting. - The catches: it joins when any invited user has it connected, reports stay in its cloud while you pay, and you can't delete a copy someone else owns. HIPAA needs Enterprise+ with 5 licences. **Does Read AI train AI on my meetings?** Not unless you opt in. Its privacy center says "AI training is opt-in. Contributing to model improvement is off by default." - The opt-in is the Customer Experience Program setting. - The privacy policy also describes inferring demographic characteristics "to improve our models", and possible personalized models on Google Workspace data "either now or in the future". **Where does Read AI store my meetings, and for how long?** Encrypted at rest in AWS us-east-1 in Northern Virginia, per its help center. - Paid accounts are kept until you stop paying or ask for deletion. Audio and video are kept "in no case for longer than 2 years". - Custom retention is Enterprise+ only. Without playback, Read keeps no audio or video beyond producing the report. ### Joining, Removing and Deleting **Why does Read AI keep joining my meetings?** Because someone else invited has Read connected. - Read's own wording: "it may still join—even if they don't actually attend the meeting." - Check the meeting chat: Read lists "the name(s) of who invited Read". Ask that person to change their join settings. **How do I remove Read AI from a meeting?** Type "opt out" in the meeting chat. Read leaves and deletes all the meeting data. - Typing "Read stop" removes Read but keeps the report up to that point. - A host can also remove Read like any other participant. **Can I delete a Read AI report someone else made?** No. Only the report's owner can delete it. - Non-owners can request deletion through Read's Account and Privacy Center form, which goes to the owner. - Read says it is "not able to delete accounts or meeting reports at the request of a third party", corporate IT included. ### Compliance, Lawsuits and Alternatives **Is Read AI HIPAA compliant?** Only on Enterprise+, which requires 5 or more licences. - The pricing page lists "HIPAA compliance" on Enterprise+; the privacy center says "BAA available on request". - Enterprise+ is $29.75 per seat a month billed annually, so at least $1,785 a year. Below it, keep health information out of Read. **Is Read AI SOC 2 certified?** Read states SOC 2 Type II, "Independently audited annually". - It also lists GDPR (DPA and SCCs), AES-256 encryption at rest and in transit, and Data Privacy Framework participation. - I couldn't read the SOC 2 report, because its trust center loads only with JavaScript. **Has Read AI been sued, and who blocks it?** I found no lawsuit naming Read AI as of October 26, 2026. - Six universities block it: Memphis (2024), Case Western Reserve, CUNY and UC Riverside (2025), Morgan State (2026) and Eastern Washington University. - Their reasons include spread across staff accounts, consent complaints and unapproved cloud storage. **What is a safer alternative to Read AI for confidential meetings?** A notetaker with no bot and no vendor-side copy. - Voibe Work (ours) has no bot, labels speakers, deletes the audio after processing and saves notes on your computer, never trained on. BAA available on request. - At $149 a year, it's $31 (17.2%) less than Read AI Pro annual and $208 (58.3%) less per seat than Enterprise+. - Voibe reminds you to tell everyone you're taking notes; recording-consent rules are yours to follow. ## The Bottom Line: Is Read AI Safe in 2026? **Read AI is safer than its reputation on training, and riskier than it looks on spread.** Its opt-in training and "opt out" command are better than most notetakers ship. Its weak points are about who holds a copy: - a bot that joins when any invited user has Read connected - reports in Read's cloud while you pay, audio and video up to 2 years - copies you can't delete when someone else owns them - a policy that allows demographic inference and Google Workspace personalization - HIPAA only on Enterprise+, with 5 licences ### If you're keeping Read AI I'd keep it for internal and sales calls. Do the five-step audit today: join preferences, auto-share, playback, the Customer Experience Program, Google Workspace. Re-check when the privacy policy date moves past June 29, 2026. ### If the meeting shouldn't spread [Voibe Work](https://www.getvoibe.com/resources/voibe-work-meeting-notes-no-bot/) captures it from your Mac or Windows PC with no bot and labels speakers. The audio is deleted as soon as processing completes. The notes are saved on your computer, never trained on. Dictation's included, for $149 a year. Voibe reminds you to tell everyone you're taking notes when recording starts. The recording-consent rules are yours to follow. [Start the 7-day free trial](https://www.getvoibe.com) (no credit card). ### Related reading - [Read AI pricing](https://www.getvoibe.com/resources/read-ai-pricing/) - [Read AI alternatives](https://www.getvoibe.com/resources/read-ai-alternatives/) - [Is Fireflies Safe?](https://www.getvoibe.com/resources/is-fireflies-safe/), [Is Otter Safe?](https://www.getvoibe.com/resources/is-otter-safe/), [Is Fathom Safe?](https://www.getvoibe.com/resources/is-fathom-safe/) and [Is Granola Safe?](https://www.getvoibe.com/resources/is-granola-safe/) - [Wispr Flow Notetaker vs Voibe Work](https://www.getvoibe.com/resources/wispr-flow-notetaker-vs-voibe-work/) - Our [AI Tool Privacy Tracker](https://www.getvoibe.com/resources/ai-privacy-tracker/), which scores notetakers side by side > **Info:** I checked Read AI's privacy policy, terms, privacy center, pricing page and help center, plus six university IT notices, on October 26, 2026. If Read AI's privacy policy shows a date newer than June 29, 2026, re-check before relying on these facts. ## Frequently asked questions ### Is Read AI safe to use? Yes, for most internal and sales calls. Its AI training is opt-in and off by default, it states SOC 2 Type II and GDPR, and any guest can type "opt out" to delete the meeting. The catches: it joins when any invited user has it connected, reports stay in its cloud while you pay, and you can't delete a copy someone else owns. HIPAA needs Enterprise+ with 5 licences. ### Does Read AI train AI on my meetings? Not unless you opt in. Its privacy center says "AI training is opt-in. Contributing to model improvement is off by default." The opt-in is the Customer Experience Program setting. The privacy policy also describes inferring demographic characteristics "to improve our models", and possible personalized models on Google Workspace data "either now or in the future". ### Where does Read AI store my meetings, and for how long? Encrypted at rest in AWS us-east-1 in Northern Virginia, per its help center. Paid accounts are kept until you stop paying or ask for deletion. Audio and video are kept "in no case for longer than 2 years". Custom retention is Enterprise+ only. Without playback, Read keeps no audio or video beyond producing the report. ### Why does Read AI keep joining my meetings? Because someone else invited has Read connected. Read's own wording: "it may still join—even if they don't actually attend the meeting." Check the meeting chat: Read lists "the name(s) of who invited Read". Ask that person to change their join settings. ### How do I remove Read AI from a meeting? Type "opt out" in the meeting chat. Read leaves and deletes all the meeting data. Typing "Read stop" removes Read but keeps the report up to that point. A host can also remove Read like any other participant. ### Can I delete a Read AI report someone else made? No. Only the report's owner can delete it. Non-owners can request deletion through Read's Account and Privacy Center form, which goes to the owner. Read says it is "not able to delete accounts or meeting reports at the request of a third party", corporate IT included. ### Is Read AI HIPAA compliant? Only on Enterprise+, which requires 5 or more licences. The pricing page lists "HIPAA compliance" on Enterprise+; the privacy center says "BAA available on request". Enterprise+ is $29.75 per seat a month billed annually, so at least $1,785 a year. Below it, keep health information out of Read. ### Is Read AI SOC 2 certified? Read states SOC 2 Type II, "Independently audited annually". It also lists GDPR (DPA and SCCs), AES-256 encryption at rest and in transit, and Data Privacy Framework participation. I couldn't read the SOC 2 report, because its trust center loads only with JavaScript. ### Has Read AI been sued, and who blocks it? I found no lawsuit naming Read AI as of October 26, 2026. Six universities block it: Memphis (2024), Case Western Reserve, CUNY and UC Riverside (2025), Morgan State (2026) and Eastern Washington University. Their reasons include spread across staff accounts, consent complaints and unapproved cloud storage. ### What is a safer alternative to Read AI for confidential meetings? A notetaker with no bot and no vendor-side copy. Voibe Work (ours) has no bot, labels speakers, deletes the audio after processing and saves notes on your computer, never trained on. BAA available on request. At $149 a year, it's $31 (17.2%) less than Read AI Pro annual and $208 (58.3%) less per seat than Enterprise+. Voibe reminds you to tell everyone you're taking notes; recording-consent rules are yours to follow. ## Related - [Read AI Pricing](https://www.getvoibe.com/resources/read-ai-pricing/): Every Read AI plan, the 5-licence Enterprise+ minimum, the no-refund rule and what a year costs. - [Read AI Alternatives](https://www.getvoibe.com/resources/read-ai-alternatives/): Notetakers that skip the bot, don't spread across a company, or keep no vendor copy. - [Is Fireflies Safe?](https://www.getvoibe.com/resources/is-fireflies-safe/): Fireflies' no-training terms, where its meetings live and the BIPA suit.