AI Meeting Assistants & Notetakers
Read AI
Rest of world Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 2 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Read AI, Inc. · www.read.ai
Compare with Noota → Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
Read AI at a glance
- Vendor
- Read AI, Inc.
- Headquarters
- Incorporated in United States source, captured 5 Nov 2026
- Data hosting
- Outside the EU by default source, captured 5 Nov 2026
- Free plan
- Yes, per the vendor’s own page source, captured 5 Nov 2026
- Panel verdict
- The AI panel rates Read AI 3/5, the mean of 6 judges. Read AI, Inc. how scores are made
- As of
- Vendor pages captured 5 Nov 2026; evaluated by the panel 6 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Read AI, Inc. of Seattle is an AI meeting assistant offering bot, botless and app capture across Zoom, Teams and Google Meet, plus audio and video upload. Its strongest score came for integrations and workflow at 7, covering an MCP server with developer documentation, a REST interface, webhooks and auto-push to HubSpot and Salesforce. Summaries and knowledge scored 6-7, with Ask Read answers carrying citations and direct links to sources. Weakest were pricing transparency at 3-4 and sovereignty at 4: the privacy policy states processing and storage 'in the United States and other countries', EU and Canada hosting appears only as a paid Enterprise+ plan feature, and we found no public information on seat prices for any paid tier. Scores sit within a point on every criterion; no disagreement was flagged. The captured pages give different framings on training — no training on customer data by default, beside a broad terms licence over user content. Recurring gaps: German is not named among the '20+ languages supported', and we found no public information on subprocessors, audit logs or works-council material.
Speaks for it
- Capture covers a bot on Zoom, Teams and Google Meet, botless Google Meet capture, desktop and mobile apps, and audio and video upload
- Integrations and workflow scored 7, with an MCP server, REST interface, webhooks, Zapier, Make and n8n and HubSpot/Salesforce auto-push
- Summaries and knowledge scored 6-7, with Ask Read answers citing sources with direct links
- The free tier is $0, always free, no credit card required, with 5 meeting transcripts per month
- Consent machinery is documented: notice before recording, a visible bot announcing who added it, and chat commands that remove it and delete all meeting data
Held against it
- The privacy policy states processing and storage in the United States and other countries, with EU and Canada hosting only as an Enterprise+ plan feature
- We found no public information on seat prices for any paid tier, on what counts as a seat, or on monthly versus annual billing
- German is not named among the '20+ languages supported', and we found no public information on transcription accuracy, speaker identification or transcript editing
- We found no public information on a subprocessor list, audit logs, or switching per-person analytics off at organisation level
- Audio and video are kept up to 2 years, with a custom retention policy only in the Enterprise+ plan
Best for
- You need capture across every channel — bot, botless and one-tap in-person recording — pushed automatically into HubSpot, Salesforce, Slack and automation tools
- You build custom workflows and value an MCP server, REST endpoints and webhooks with documented payloads
- You want cited answers over meetings, emails and documents and can start on the free tier of 5 meeting transcripts per month
- Your team weighs SOC 2 Type II certification and Data Privacy Framework commitments more heavily than EU-hosted processing
Avoid if
- You must budget precisely before signing — we found no public information on seat prices, what counts as a seat, or monthly versus annual rates
- You need German transcripts or summaries — ask the vendor: the public pages we read do not show it
- EU processing by default is a hard requirement — the privacy policy names the United States and other countries, EU and Canada hosting sits in the Enterprise+ plan, and we found no public information on subprocessors or the hosting infrastructure
- Your rollout runs through a works council — per-participant talk time, bias and charisma metrics and a Read Score analysing facial and verbal elements are documented, with no public information on an organisation-wide opt-out or on works-agreement and DPIA material
The scores
| Criterion | Panel median |
|---|---|
| Recording, transcription & languages | 3 of 5 |
| Summaries, action items & meeting knowledge | 3.5 of 5 |
| Integrations, API & workflow | 3.5 of 5 |
| Consent, participant rights & works council | 3 of 5 |
| Retention, AI training & administration | 3 of 5 |
| European sovereignty | 2 of 5 |
| Pricing transparency | 2 of 5 |
Recording, transcription & languages
Show reasoningHide reasoning
How this is scored
How the conversation gets in and how faithfully it is written down: a bot that joins Zoom, Microsoft Teams, Google Meet and Webex, botless capture from a desktop or mobile app, in-person meetings and phone calls, file upload, live transcription, speaker identification and names, the languages supported with German stated, meetings that switch language, custom vocabulary for names and jargon, timestamps linked to the recording, and editing of the transcript.
0 — Does not record or transcribe meetings; a note template or agenda tool without capture.
3 — A bot that joins one or two conferencing tools and produces a transcript; languages, speaker names, in-person capture and accuracy are basic or not described.
5 — A bot for Zoom, Teams and Google Meet, a desktop or mobile app for in-person meetings, file upload, speaker identification, German among the supported languages, timestamps linked to the recording, and an editable transcript.
8 — Botless capture documented next to the bot, Webex and phone or dialer calls, live transcription, mixed-language meetings handled, custom vocabulary, speaker names learned across meetings, and the transcription engine or its accuracy per language stated.
10 — Capture a regulated team relies on: every channel above with accuracy published per language and method, dialects and specialist vocabulary documented, on-device or customer-hosted transcription as an option, and how errors are corrected and fed back stated.
The Management Consultant
The bot covers Zoom, Teams and Google Meet, a botless Google Meet integration plus desktop and mobile apps record in-person conversations with one tap, and audio or video files can be uploaded — every channel a client workshop needs. We found no public information naming German among the twenty-plus supported languages, nor on speaker identification, custom vocabulary for names, timestamps linked to the recording, editable transcripts or accuracy per language. 1 2 5 11 12
The Sales Team Lead
The bot works on Zoom, Teams and Google Meet, and capture goes further than most: a botless Google Meet integration, desktop and mobile apps that record without a bot, one-tap recording of face-to-face meetings on iOS and Android, and audio or video file upload. It stays short of the top band because German is not named among the '20+ languages supported', and we found no public information on Webex, dialler calls, custom vocabulary, speaker naming, timestamps or transcript editing. 1 2 5 11 12
The Works Council Chair
A bot joins Zoom, Microsoft Teams and Google Meet, and next to it the vendor documents botless capture through the Google Meet Media API plus desktop and mobile apps that record in-person conversations with one tap, audio and video file upload, and real-time meeting notes. German is not named among the "20+ languages supported", and we found no public information on Webex, phone calls, custom vocabulary or transcription accuracy, so the breadth of channels clearly exceeds the solid level without reaching the advanced one. 5 11 12 2
The Data Protection Officer
Bot, botless and app capture are all documented: a Google Meet integration built on the Meet Media API, desktop and mobile apps for local or cloud recording without a bot, one-tap in-person recording, file upload and real-time meeting notes across Zoom, Teams and Google Meet. For a German-language client conversation I cannot verify the essentials: the "20+" supported languages are not itemised so German is not named, and speaker identification, timestamps, transcript editing and per-language accuracy are not described. 1 2 5 11 12
The IT Lead
A bot covering Zoom, Microsoft Teams and Google Meet is documented alongside botless capture built on the Google Meet Media API and desktop and mobile apps that record in-person meetings with one tap, plus audio and video file upload and real-time meeting notes. '20+ languages supported' is stated, but we found no public information on German specifically, Webex, phone or dialer calls, custom vocabulary, or transcription accuracy per language. That is strong capture breadth for my Teams users, with the detail my compliance colleagues would ask for missing. 1 2 5 11 12
The Skeptic
The capture breadth is real: a bot for Zoom, Teams and Google Meet, a botless Google Meet integration built on the Meet Media API, desktop and mobile apps that record in-person meetings without a bot, and audio and video upload. What I cannot verify is the writing down: the pages say '20+ languages supported' without naming them — I cannot confirm German — and they are silent on speaker identification, timestamps tied to the recording, an editable transcript, the transcription engine and any accuracy figure. A language count without a list has turned a German meeting into English nonsense before my eyes, so a count alone buys no confidence from me. 1 2 5 11 12
Summaries, action items & meeting knowledge
Show reasoningHide reasoning
How this is scored
What the tool makes of the transcript: summaries and minutes by meeting type with editable templates, decisions and action items with owners and due dates, summaries in the meeting's language or a chosen one, follow-up emails, clips and highlights, search across all meetings, questions answered over the archive with citations back to the transcript passage, shared team folders or channels, and the minutes exported to Word, PDF or a wiki.
0 — No summaries of any kind; only the raw transcript or recording.
3 — One generic summary per meeting; templates, action items, search across meetings and citations are basic or not described.
5 — Summaries with templates per meeting type, action items and decisions extracted, the summary language selectable with German available, search across meetings, questions answered over one or several meetings, and sharing or export of the minutes.
8 — Custom templates per team, action items with owners pushed to task tools, answers that cite and link the transcript passage they rest on, topic or keyword tracking across meetings, team libraries with permissions, and the AI models used for summaries named.
10 — Meeting knowledge a company can audit: every generated statement traceable to its source passage, hallucination handling and human review documented, summary quality by language stated, and the archive queryable through an API or MCP server with the same permissions as in the app.
The Management Consultant
Summaries with decisions, action items and key questions, custom templates that can be applied as a shared view for all viewers, automatic pushes into HubSpot and Salesforce, and answers over meetings, email and documents that cite and link their sources — this covers my minutes workload, and the models are named with ChatGPT and Claude on paid plans. We found no public information on summaries written in German or a chosen language, nor on how hallucinated output is handled. 1 2 3 5 14 16
The Sales Team Lead
Every call ends with a summary of decisions and takeaways, auto-generated action items and key questions, and templates I can build per team — including ones tailored for sales — and apply to what goes out to connected tools; Ask Read then answers questions over meetings, emails and documents with citations and direct links to the source, and themes and tags run across meetings. We found no public information on action item owners and due dates, a selectable summary language with German, or a drafted follow-up email, and export runs through Google Docs or documents generated via MCP clients. 1 2 3 11 14 16
The Works Council Chair
Summaries with decisions and action items, custom templates with personal and shared views, answers over meetings with citations and direct links to the source passage, filtered search across meetings, playback with highlight reels, and reports stored automatically as Google Docs; the models behind the answers (GPT, Claude) are named. We found no public information on selecting the summary language or on action items carrying owners and due dates, which holds this below the top of the level. 2 3 14 11 16
The Data Protection Officer
Summaries with decisions and action items, custom templates with personal and shared views, cross-meeting search, and Ask Read answers with citations and direct links back to the source give me much of the traceability I need. I found no public information on choosing the summary language, and action items are not described with owners and due dates. 1 2 3 14 15
The IT Lead
Summaries with decisions and key questions, action items routed to the tools teams work in, custom templates with personal and shared views, and topics and chapters per meeting are all documented, and Ask Read answers questions over meetings, emails, chats and documents with citations and direct links to sources. The premium model options (GPT and Claude on paid plans) are named, though we found no public information on the default summary model or on choosing the summary language. Sharing runs through email, calendar updates, links, Google Docs, webhooks and Slack, which covers most of where my people work. 1 2 3 14 15 16
The Skeptic
Summaries with decisions and takeaways, custom templates with personal and shared views, action items, topics and key questions, cross-meeting search, and Ask Read answers with citations and direct links to sources are documented — traceability back to the source is stated, which is the first thing I ask for. Two questions stay open: the pages name ChatGPT and Claude only as paid options for broader research while the model that writes the summary by default goes unnamed, and I found no public information on a selectable summary language or German output. The pages are also silent on owners and due dates for action items. 1 2 3 14 15
Integrations, API & workflow
Show reasoningHide reasoning
How this is scored
How the notes reach the place where work happens: calendar connection with rules for which meetings are recorded, CRM fields filled from the call (HubSpot, Salesforce, Pipedrive, Microsoft Dynamics), project and task tools, Slack and Microsoft Teams channels, Notion, Confluence and SharePoint, Zapier, Make or n8n, a documented REST API and webhooks, an MCP server for AI assistants, and browser extensions and native apps.
0 — No integrations and no export; the notes stay in the app.
3 — A calendar connection and an email or Slack summary; CRM, API and task tools are basic or not described.
5 — Google and Microsoft calendars, a native CRM integration (HubSpot or Salesforce), Slack or Teams, a task or wiki tool, Zapier or Make, and a documented API or webhooks.
8 — CRM field mapping per meeting type, several CRMs including Microsoft Dynamics or Pipedrive, a full REST API with webhooks and reference documentation, an MCP server, SharePoint or Confluence export, and recording rules per calendar or meeting type.
10 — An integration layer a company builds on: every object reachable by API with rate limits and versioning stated, granular OAuth scopes, data residency kept across integrations, and the integrations administered centrally with logs.
The Management Consultant
Webhooks with documented payload contents, a REST API and an MCP server with developer documentation, Zapier, Make and n8n, Slack with notes posting and real-time search, plus Notion, Jira and Confluence — a genuinely broad layer, with CRM auto-push into HubSpot and Salesforce using selectable templates. We found no public information on Microsoft Dynamics or Pipedrive, or on recording rules per calendar or meeting type beyond an automatic-versus-manual join preference, and MCP OAuth is stated as coming soon. 5 8 13 14 15 16
The Sales Team Lead
This is the part I care about most and it holds up: meeting notes auto-push into HubSpot and Salesforce with a selected template, webhooks carry summary, chapters, topics, action items and key questions into CRM, project, wiki or database tools, Zapier, Make and n8n are supported, and there is a REST interface plus an MCP server with developer documentation. Only HubSpot and Salesforce are named as CRM targets — we found no public information on a Microsoft Dynamics or Pipedrive connection — the join setting is a user-level automatic-versus-manual toggle rather than per-calendar rules, and MCP OAuth is described as coming soon. 5 6 14 15 16
The Works Council Chair
Beyond Slack, Zapier, Make and n8n, the vendor documents a full REST interface, webhooks carrying summaries, chapters, topics, action items and key questions into CRM, project and wiki tools, an MCP server with developer documentation plus a ChatGPT app and Claude connector, a Chrome extension and native mobile apps. Salesforce and HubSpot note-push runs per template at workspace level; we found no public information on Microsoft Dynamics or Pipedrive, or on recording rules per calendar or meeting type. 16 15 14 5 2
The Data Protection Officer
An MCP server with developer documentation, a REST interface, webhooks carrying summary, topics, action items and key questions, Zapier, Make and n8n, auto-push to HubSpot and Salesforce, Confluence, Notion and Jira, plus a Chrome extension and Google Docs export. Webex, Microsoft Dynamics or Pipedrive connections, recording rules per calendar, and anything beyond username-and-password authentication at the MCP endpoint (OAuth is stated as coming) are not documented. 5 11 14 15 16
The IT Lead
The MCP server is documented with its endpoint and Streamable HTTP transport, the same FastAPI server exposes everything as REST endpoints, and webhooks carry summary, chapters, topics, action items and key questions to project management, CRM, wiki or database targets. Slack notes with real-time search, Zapier, Make and n8n, HubSpot and Salesforce auto-push with push templates, and Notion, Jira and Confluence as premium integrations give us most of the wiring we need. We found no public information on Microsoft Dynamics, Pipedrive or SharePoint, or on admin-level recording rules per calendar (the documented auto-join setting is per user), and MCP OAuth is 'coming soon' with username and password at launch. 5 6 14 15 16
The Skeptic
This is a layer a company can wire into: HubSpot and Salesforce auto-push with selectable push templates, webhooks carrying Meeting Summary, Chapters, Topics, Action Items and Key Questions, Zapier, Make and n8n, Slack, Notion, Jira and Confluence, plus an MCP server over Streamable HTTP that doubles as a full REST interface with developer documentation. My reservations: the MCP endpoint launched with username-and-password authentication with OAuth 'coming soon', and I found no public information on rate limits, versioning, or whether residency holds once transcripts flow into Slack, Claude and ChatGPT. I found no public information on Microsoft Dynamics or Pipedrive support either. 2 5 14 15 16
Consent, participant rights & works council
Show reasoningHide reasoning
How this is scored
Whether every person in the meeting knows and can decide, and whether the tool can be introduced under German co-determination: a recording notice to all participants including external guests, consent or opt-out before the recording starts, a visible bot or a stated notice for botless capture, rules for when the assistant joins automatically, stopping and deleting a recording on request, per-person analytics (talk time, sentiment, engagement scores) off by default or switchable per organisation, material or a template for a works agreement (Betriebsvereinbarung, § 87 (1) no. 6 BetrVG), and support for a data protection impact assessment.
0 — Built to record people without their knowledge, or sells covert recording or individual performance scoring as a feature.
3 — A general privacy statement and a bot that appears in the participant list; notices to guests, opt-out, per-person analytics and works councils are basic or not described.
5 — A recording notice to participants by chat message, email or the bot's name, a way for a participant to stop the recording or opt out, admin rules for when the assistant joins, recordings deletable on request, and per-person analytics described with how to switch them off.
8 — Consent collected before recording starts for external participants, per-person analytics off by default or switchable per organisation, botless capture with its notice method documented, a works-council information pack or works-agreement template published, DPIA support, and the EU AI Act classification stated.
10 — Co-determination built into the product: every analytic and its granularity documented for the works council, consent and opt-out logged per participant, configuration changes logged, minimum group sizes for any team statistics, and references of works-council-approved rollouts published.
The Management Consultant
Participant-facing consent is documented thoroughly: notification before recording begins, a visible bot that announces who invited it, consent reminders by default in the botless modes, and chat commands that remove the assistant instantly and delete all meeting data. For German co-determination the evidence stops: participant-level talk-time, bias and charisma metrics and a Read Score that analyses facial elements of all attendees are described as features, and we found no public information on switching per-person analytics off per organisation, on a works-agreement template, on DPIA support or on an EU AI Act classification. 2 6 10 11 17 20
The Sales Team Lead
Notice and opt-out are handled seriously: the measurement notification goes out before recording begins, the bot is visible and announces in the chat who invited it, the botless modes pop up consent language by default, and any participant can type 'opt out' to make it leave and delete the data. For a rollout under a works council the picture thins out: participant-level talk time, bias and charisma metrics plus the Read Score are flagship features, and we found no public information on switching per-person analytics off at organisation level, on a works-agreement template, DPIA support or an EU AI Act classification. 2 6 10 11 20
The Works Council Chair
The consent chain is genuinely documented: measurement is notified before recording begins, the bot is visible and announces in the chat who added it, botless modes show consent language and reminders by default, anyone can type "Read stop" or "opt out" to remove it and delete all meeting data, and joining can be switched to manual mode. For our co-determination file the open point is the analytics: talk time, bias and charisma are measured per participant and a Read Score analyses facial and verbal elements — for EU and UK users only the facial elements are excluded — and we found no public information on switching per-person analytics off for the whole organisation, nor any works-agreement template or DPIA support material. 10 6 20 2 17
The Data Protection Officer
The pieces I would put in the DPIA exist: notification before recording begins to solicit consent, a visible bot in the participant list, chat commands that remove the assistant instantly and delete all meeting data, consent pop-ups by default in the botless modes, and a manual join setting. Participant-level metrics such as talk time, bias and charisma, and a Read Score built on facial analysis for non-EU users, are described, but I found no statement that per-person analytics are off by default, and no works-council pack, works-agreement template, DPIA support or EU AI Act classification. 2 6 10 11 17 20
The IT Lead
The bot is a visible participant, the measurement notification goes out before recording begins to solicit consent, botless modes show consent language and reminders by default, and typing 'Read stop' or 'opt out' removes it instantly, with the opt-out deleting all meeting data. What worries me for our works council is that the Read Score analyzes facial and verbal elements of all attendees and participant metrics include talk time, bias and charisma, and we found no public information on switching per-person analytics off per organisation, on a works-agreement template, DPIA support or the EU AI Act classification — the only documented mitigation is that EU and UK scores exclude video and facial elements. 2 6 10 11 17 20
The Skeptic
The notice machinery is genuinely documented: a visible bot that announces in chat who added it, a notification before recording begins to solicit consent, consent reminders popping up by default in the botless modes, 'Read stop' and an 'opt out' that removes Read and deletes all meeting data, and a switch from automatic to manual joining. Then I read that Read may still join a meeting even if the person who invited it does not show up, and the help pages include troubleshooting for Read still joining meetings after account deletion. Participant-level talk time, bias and charisma metrics and a Read Score analyzing facial and verbal elements of all attendees — facial elements excluded only for EU and UK users — are documented, but I found no public information on whether these analytics are off by default or switchable per organisation, nor on works-council material, a works-agreement template, DPIA support or an EU AI Act classification. 2 6 10 11 20
Retention, AI training & administration
Show reasoningHide reasoning
How this is scored
What the employer can govern: retention periods and automatic deletion of recordings, transcripts and summaries, whether audio and video can be discarded after transcription, sharing defaults and link permissions, customer content excluded from model training by contract, the AI and transcription providers named with their region and their own retention, encryption, single sign-on (SAML), SCIM, roles and workspaces, admin policies on auto-recording and sharing, audit logs, export of the whole archive, and security certifications such as ISO 27001 and SOC 2.
0 — No administration and no deletion; every user decides alone and recordings are kept indefinitely.
3 — Users can delete their own recordings and a security page exists; retention policies, model training, SSO and audit logs are basic or not described.
5 — Retention settings per workspace, customer content excluded from model training, team workspaces with roles, single sign-on, admin control over sharing and auto-recording, encryption at rest and in transit, and ISO 27001 or SOC 2 stated.
8 — Automatic deletion by policy with audio discardable after transcription, the AI and transcription subprocessors named with region and zero retention, SAML with SCIM, granular roles, audit logs, legal hold or export of the full archive, and certifications with their scope published.
10 — Governance an auditor accepts: every retention, sharing and recording policy enforceable centrally and logged, models run on the vendor's own or the customer's infrastructure as an option, audit logs exportable to a SIEM, and the deletion of every copy, including at subprocessors, documented.
The Management Consultant
The written promise I want exists — meeting content is never used for training unless a user explicitly, knowingly opts in — alongside encryption, SOC 2 Type II, SAML and SCIM on the top plan, admin settings over recordings, transcriptions, access and downloads, and audio and video capped at two years. The terms of service, however, grant a broad licence to user content for providing and improving the services and permit training on it subject to opt-in and opt-out mechanisms, and paid-account data is kept until payment stops or deletion is requested. We found no public information on audit logs, on named subprocessors and their regions, on discarding audio after transcription, or on exporting the whole archive. 1 5 9 10 17 18 20
The Sales Team Lead
Employers can manage settings for recordings, transcriptions, access and downloads, SAML with SCIM comes with the top tier, encryption in transit and at rest plus SOC 2 Type II are stated, a data processing addendum applies to enterprise customers, and a custom retention policy is offered at the highest tier, with audio and video otherwise kept up to two years. The captured pages give different framings on training — meeting content is described as never used unless you explicitly opt in, while the terms grant a broad licence over user content and describe its use for improving AI models subject to opt-in and opt-out — and we found no public information on audit logs, named subprocessors or export of the full archive. 1 5 9 10 17 18
The Works Council Chair
Audio and video are kept no longer than 2 years and paid-account data until payment stops or deletion is requested, with a custom retention policy available only in the top plan; no training on customer data by default is stated repeatedly, while the terms simultaneously grant a broad licence to user content for improving the services — the captured pages give different figures on training use, and I will not pick one. SAML and SCIM, encryption at rest and in transit, admin settings over recordings, transcriptions, access and downloads, and SOC 2 Type II are stated; we found no public information on audit logs, discarding audio after transcription, or a named subprocessor list with regions. 10 5 17 18 9
The Data Protection Officer
SOC 2 Type II, encryption in transit and at rest, training on meeting content only after explicit opt-in, SAML and SCIM, and admin settings over recordings, transcriptions, access and downloads cover most of the governance scaffolding. Custom retention is an Enterprise+ feature while paid accounts are stored until payment stops or deletion is requested, with audio and video kept up to two years, and I found no public information on audit logs, a subprocessor list, archive export or legal hold. 1 5 10 17 18
The IT Lead
SAML and SCIM are in the Enterprise+ plan along with a custom data retention policy, employers can manage settings around recordings, transcriptions, access and downloads, content is not used for training by default, and SOC 2 Type II, HIPAA and GDPR compliance plus encryption in transit and at rest are stated. We found no public information on audit logs, named AI and transcription subprocessors, discarding audio after transcription, legal hold or export of the full archive; the retention statements captured are an audio and video maximum of two years and storage until payment stops or deletion is requested, and the terms grant a broad licence over user content for providing and improving the services. I would get single sign-on and provisioning, but not the logging and subprocessor transparency my auditors expect. 1 5 9 10 17 18
The Skeptic
No training on customer data by default with an explicit opt-in Customer Experience Program, SOC 2 Type II, encryption in transit and at rest, SAML and SCIM on the top tier, HIPAA-locked workspaces, and admin settings over recordings, transcriptions, access and downloads are all stated. What an auditor will not find: audio and video are kept up to 2 years, paid-account data until payment stops or deletion is requested, and a custom retention policy exists only on the top tier — I found no public information on discarding audio after transcription, on subprocessors with their regions, on audit logs, or on export of the full archive. The terms grant a broad, sublicensable license to user content for creating, providing and improving the Services, which sits alongside the no-training-by-default statements; the data processing addendum the terms say applies to enterprise customers is where a buyer must draw that line. 1 5 9 10 18
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Who the contracting entity and the parent company are, where recordings, transcripts, summaries, voice profiles and account data are stored and processed, which language model and transcription providers read them and where, and who the other subprocessors are (hosting, email, support, analytics and payment tools). Independently sourced by the sovereignty pipeline. A conferencing platform outside Europe that the customer already uses is part of the meeting, not counted against the notetaker; where the notetaker stores and processes the conversation is.
0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and no data processing agreement offered.
3 — A privacy policy and a data processing agreement exist, but hosting location is unstated or non-EU and the subprocessors are not listed.
5 — EU hosting available and an EU contracting entity or EU representative, but parts of the chain (language models, transcription, email, support, payment) run through non-EU providers without a stated safeguard.
8 — EU hosting on named infrastructure, EU contracting entity, subprocessors including the AI providers listed with their locations, a data processing agreement published, and security certifications (ISO 27001, SOC 2) stated.
10 — Sovereign end to end and evidenced: European ownership, entity, hosting and every subprocessor, with transcription and language models run in Europe by European operators, data export and deletion documented, and certifications published with their scope rather than implied.
The Management Consultant
Read AI, Inc. of Seattle is the contracting entity and processes by default in the United States and other countries; EU and Canada hosting appears only as a paid Enterprise+ plan feature. An Article 27 GDPR representative, Data Privacy Framework commitments and a data processing addendum for entity and enterprise customers are documented. We found no public information on the hosting infrastructure, on where the language models or transcription run, or on any subprocessor list — a chain I could not demonstrate to a German client. 3 5 9 10
The Sales Team Lead
The contract and the processing sit with Read AI, Inc. of Seattle, with information stored on servers in the United States and other countries; EU and Canadian hosting exists only as a feature of the paid top plan. An Article 27 EU representative is named and a data processing addendum applies to enterprise customers, but we found no list of the hosting, language model or support providers with their locations, so the chain cannot be assessed end to end. 5 9 10
The Works Council Chair
The contracting entity is Read AI, Inc. of Seattle, and personal information is processed and stored in the United States and other countries, with EU and Canadian hosting available only as a paid Enterprise+ plan feature. An Article 27 EU/UK representative and an enterprise data processing addendum exist and Data Privacy Framework certification is stated, but the captured pages name no subprocessors and no hosting infrastructure, so the chain a works council and data protection officer must assess remains opaque. 10 9 5
The Data Protection Officer
The contracting entity is Read AI, Inc. of Seattle, processing and storing on servers in the United States and other countries, with an Article 27 EU and UK representative, Data Privacy Framework certification, a data processing addendum for enterprise customers, and EU hosting available only as a paid top-tier plan feature. The language models offered for reading and answering over transcripts (GPT, Claude) are named but without region or retention terms, and no subprocessor list with locations appears on the captured pages, which is what I read before the feature page. 5 9 10
The IT Lead
Read AI, Inc. of Seattle states that it and its service providers process and store personal information on servers in the United States and other countries, and EU and Canada hosting appears only as a paid Enterprise+ plan feature. There is an Article 27 EU and UK representative, Data Privacy Framework certification, and a data processing addendum that applies to entity and enterprise customers, but we found no public information on the subprocessors, so the chain stays unnamed. For a German engineering firm, the default is American processing with a European option behind the top tier. 5 9 10
The Skeptic
Read AI, Inc., Seattle, states that it and its service providers process and store personal information 'in the United States and other countries'; EU hosting appears only as a feature of the paid top tier, and I found no public information on the hosting infrastructure behind it. The transfer paperwork is done — an Article 27 EU and UK representative, Data Privacy Framework certifications, contractual-clause safeguards, and a data processing addendum said to apply to enterprise customers — but I found no public information on the subprocessor list or on where transcription and the language models run; ChatGPT and Claude appear as paid model options and both are non-European. A US chain with an EU option gated behind the top tier is an upgrade, not sovereignty. 3 5 9 10
Pricing transparency
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the real annual cost from public pages alone: price per seat and tier, what counts as a seat (every invited user, only recording users), transcription minutes or credits included, storage limits, which features (CRM integrations, API access, SSO, custom retention, EU hosting, AI credits) cost extra, the free tier and its limits, monthly versus annual billing, minimum seats and VAT.
0 — No public prices at all; every customer is a sales call.
3 — A starting price or a free tier exists, but how cost scales with seats, minutes or features is unclear.
5 — Tiers are public with their seat price and main inclusions, but at least one commonly needed piece (SSO, CRM integration, API, custom retention, EU hosting, minute or credit limits) is unpriced or "on request".
8 — Every tier priced publicly with its scaling rule (seats, minutes, credits, storage), add-ons priced, what counts as a seat stated, overage handling stated, minimum term and VAT treatment stated.
10 — Complete price computability: annual cost derivable for a given team size and meeting volume, with every add-on, overage and support fee and the cancellation and data-return terms published.
The Management Consultant
The free tier is concrete — five meetings a month, one-hour meeting limit, no credit card — and upload minutes, meeting-length caps and which features sit in which plan are published in detail. But we found no public information on prices per seat for the paid plans, on monthly versus annual billing, or on what counts as a seat, so an annual cost for my twelve-person firm cannot be computed; taxes are excluded from shown prices and itemized at checkout, and cancelling brings no refund. 1 5 9
The Sales Team Lead
The free tier is unusually well documented — five transcripts a month, no credit card, botless use free, all Google integrations included — and the plans page maps limits per tier such as upload minutes and maximum meeting length, while the terms state that prices exclude taxes and paid fees are not refunded on cancellation. A buyer still cannot compute the real annual cost: we found no public information on the paid seat prices, what counts as a seat, monthly versus annual rates, minimum seats or VAT treatment. 1 5 9 11
The Works Council Chair
The free plan is published precisely — "$0 Always free, no credit card required" with 5 meetings per month — and upload minutes of 100, 200 and 300 per month and meeting lengths of 1, 4, 4 and 8 hours per tier are stated. We found no public information on seat prices for the paid tiers, what counts as a seat, or monthly versus annual billing; taxes are excluded from shown prices and itemised at checkout, so a buyer cannot compute the annual cost from these pages. 5 9 1
The Data Protection Officer
The free tier is fully specified — $0, "5 meeting transcripts per month", no credit card — and upload minutes, maximum meeting length and inclusions per tier are listed, with taxes itemised at checkout, automatic renewal, a one-day notice for price changes and a no-refund policy stated. I found no public seat price for the paid tiers in the captured pages, so the annual cost for a given team cannot be computed from what I read. 5 9
The IT Lead
The free tier is concrete — $0, always free, no credit card, five meeting transcripts per month with a one-hour meeting limit — and the tiers differ in upload minutes (100, 200 and 300 mins/mo), maximum meeting length and included features such as SAML and SCIM, while prices shown exclude taxes that are itemized at checkout. However, we found no public information on the seat price of any paid tier, what counts as a seat, minimum seats, or monthly versus annual billing, so I cannot compute what four hundred users would cost. The cancellation terms are published — no refunds, access until the period ends — but that does not help me budget. 1 5 9
The Skeptic
The free tier is computable: $0, five meeting transcripts per month, a one-hour meeting cap, no credit card required, and per-tier limits are public — 100, 200 and 300 mins/mo of uploads by tier, meeting lengths of 1, 4, 4 and 8 hours — with taxes stated as excluded from shown prices and itemized at checkout. What I cannot compute is a paid annual cost: I found no public information on seat prices for any paid tier, on what counts as a seat, or on the price of the tier where EU and Canada hosting, HIPAA, SAML and custom retention live. Refunds are stated not to be offered, cancellation keeps access to period end, and price changes require cancelling at least one day before they take effect. 1 5 9
European sovereignty — proven facts
2 of 6 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 | Incorporated in US ⚠ unverified | 0/2 pts | 10 Report an error |
|---|---|---|---|
| Hosting location | Outside the EU ⚠ unverified | 0/4 pts | 10 Report an error |
| Hosting options | Not determined ⚠ unverified | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Read AI
Is Read AI European?
No. whats-best.ai classifies Read AI as Rest of world. Its vendor, Read AI, Inc., is incorporated in United States, per the vendor’s page captured 5 Nov 2026.
Where does Read AI store data?
Read AI stores customer data outside the EU by default, per the vendor’s page captured 5 Nov 2026.
Does Read AI have a free plan?
Yes. Read AI has a free plan, per the vendor’s page captured 5 Nov 2026.
What are the best alternatives to Read AI?
As of 6 Nov 2026, the panel rates MeetGeek (3.5/5), Noota (3.5/5) and Jamie (3.5/5) highest among the other 14 AI Meeting Assistants & Notetakers products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is MeetGeek (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Read AI alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 5 Nov 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. No imprint or commercial-register excerpt is provided; jurisdiction is derived from 'based in the United States' and a US street address (999 Third Ave, Suite 3300) in the privacy policy rather than a registration statement.
- Weak sourcing — Hosting location. The privacy policy states no EU default; an EU option exists only as a paid Enterprise+ plan feature ('EU & CA hosting' on the pricing page).
- Weak sourcing — Hosting options. 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.
- 18 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
- 8 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
- 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
- 4 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
- 2 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
- 2 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
- 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 sovereignty dimension could not be confirmed on the vendor’s own pages and is shown as unknown. Know more? Tell us
Sources (20)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.read.ai Checked 5 Nov 2026 Details →
- 2 Features page (meeting reports) www.read.ai Checked 5 Nov 2026 Details →
- 3 Features page (Ask Read) www.read.ai Checked 5 Nov 2026 Details →
- 4 Integrations page www.read.ai Checked 5 Nov 2026 Details →
- 5 Pricing page www.read.ai Checked 5 Nov 2026 Details →
- 6 Account and privacy centre www.read.ai Checked 5 Nov 2026 Details →
- 7 Trust center trust.read.ai Checked 5 Nov 2026 Details →
- 8 About page www.read.ai Checked 5 Nov 2026 Details →
- 9 Terms of service www.read.ai Checked 5 Nov 2026 Details →
- 10 Privacy policy www.read.ai Checked 5 Nov 2026 Details →
- 11 Recording, transcription & languages — found from sitemap www.read.ai Checked 5 Nov 2026 Details →
- 12 Recording, transcription & languages — found from sitemap www.read.ai Checked 5 Nov 2026 Details →
- 13 Summaries, action items & meeting knowledge — found from sitemap www.read.ai Checked 5 Nov 2026 Details →
- 14 Summaries, action items & meeting knowledge — found from sitemap www.read.ai Checked 5 Nov 2026 Details →
- 15 Integrations, API & workflow — found from sitemap www.read.ai Checked 5 Nov 2026 Details →
- 16 Integrations, API & workflow — found from sitemap www.read.ai Checked 5 Nov 2026 Details →
- 17 Consent, participant rights & works council — found from sitemap www.read.ai Checked 5 Nov 2026 Details →
- 18 Consent, participant rights & works council — found from sitemap www.read.ai Checked 5 Nov 2026 Details →
- 19 Retention, AI training & administration — found from sitemap www.read.ai Checked 5 Nov 2026 Details →
- 20 Retention, AI training & administration — found from sitemap www.read.ai Checked 5 Nov 2026 Details →