AI Meeting Assistants & Notetakers
Fellow
Rest of world Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 1 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Fellow Insights, Inc. · fellow.ai
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.
Fellow at a glance
- Vendor
- Fellow Insights, Inc.
- Headquarters
- Not stated on the vendor’s pages as of 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 Fellow 3.5/5, the mean of 6 judges. Fellow is an AI meeting assistant from Fellow Insights, Inc., a Canadian company. 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
Fellow is an AI meeting assistant from Fellow Insights, Inc., a Canadian company. Scores cluster tightly: integrations and workflow at 8, the rest between 6 and 8, sovereignty alone at 3 to 4. Judges credited a visible bot for Zoom, Google Meet and Teams, botless desktop capture reaching Slack Huddles, Webex and in-person meetings, native Salesforce, HubSpot, Pipedrive and Freshworks integrations with a REST API and MCP server, consent capture that swaps the join link for a consent page about an hour ahead, and retention governance with separate clocks, zero-day deletion and an exportable audit trail. Sovereignty is the low: Fellow Insights, Inc. contracts under Ontario law and hosts on AWS Canada Central, we found no public information on EU hosting or a European entity, and the 3-to-4 range reflects judges weighing Canadian processing against the published sub-processor list and Standard Contractual Clauses. Pricing transparency scores 6 to 7: all four tiers are public with a thirty-day trial and no credit card, but minutes, storage limits and seat definitions are unstated, with consent capture, auto-deletion and auto-record rules on Enterprise.
Speaks for it
- Records with a visible bot or botless desktop audio on Mac and Windows, covering Slack Huddles, Webex, in-person meetings and mobile capture.
- Native Salesforce, HubSpot, Pipedrive and Freshworks integrations sit beside a documented REST API with webhooks and an MCP server.
- Consent capture swaps the calendar join link for a consent page, logs declines with the attendee's email and warns the organizer in real time.
- Retention runs on separate clocks for recordings, transcripts and AI notes, with zero-day deletion that preserves summaries and permanent deletion within an hour, backups included.
- States its AI is never trained on customer data, and an admin toggle disables third-party AI providers entirely.
Held against it
- The contracting entity and hosting sit in Canada — Fellow Insights, Inc. under Ontario law on AWS Canada Central — and we found no public information on EU hosting or a European entity.
- The sub-processor list is published including the AI providers, but we found no public information naming them or their regions and retention terms.
- Consent capture is exclusive to the Enterprise plan and currently works with Microsoft 365 Calendar only, with Google Calendar planned.
- We found no public information on included transcription minutes or credits, storage limits, or what counts as a seat, so the full annual cost is not computable from public pages.
- We found no public information naming the AI models behind summaries or transcription accuracy per language, and the captured pages give different figures for the language count (99 versus 100).
Best for
- You run customer-facing meetings across Zoom, Google Meet and Teams and want recaps, decisions and action items synced natively into Salesforce, HubSpot, Pipedrive or Freshworks.
- Your compliance work needs documented retention governance: separate clocks for recordings, transcripts and AI notes, zero-day deletion, and an exportable audit trail over every deletion and access event.
- You need documented consent from external guests before recording starts and can run Microsoft 365 Calendar workspaces on the Enterprise plan.
- Your meetings include in-person rooms, Slack Huddles or Webex calls and you need botless capture from desktop or mobile apps.
Avoid if
- You need meeting recordings hosted in the EU or a European contracting entity — the documented chain runs through Canada, and we found no public information on either.
- You must name the transcription engine, the AI models or sub-processor locations in a DPIA before rollout — we found no public information on any of them.
- Your consent workflows run on Google Calendar today — consent capture is documented for Microsoft 365 Calendar workspaces only, with Google Calendar planned.
- You need the total cost computable before signing, or your team exceeds fifty seats — seat maximums are 5, 20, 50 and unlimited, minute and storage limits are unstated, and Enterprise purchase runs through Contact sales.
The scores
| Criterion | Panel median |
|---|---|
| Recording, transcription & languages | 3.5 of 5 |
| Summaries, action items & meeting knowledge | 3.5 of 5 |
| Integrations, API & workflow | 4 of 5 |
| Consent, participant rights & works council | 3.5 of 5 |
| Retention, AI training & administration | 3.5 of 5 |
| European sovereignty | 2 of 5 |
| Pricing transparency | 3 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
Both paths are documented: a visible bot for Zoom, Google Meet and Teams, and botless capture through the Mac and Windows desktop app recording system audio, explicitly including in-person meetings, Slack Huddles and Webex, plus mobile recording and Zoom native capture — that covers my workshops without a laptop on the table. Transcription is documented with automatic language detection, speaker labelling from workspace voice samples, and timestamps linking each recap section to the recording and transcript. The captured pages give different figures for the language count (99 versus 100), we found no public information naming German specifically, and none on custom vocabulary, phone-call capture or accuracy per language. 1 2 3 11 12 13 14
The Sales Team Lead
The bot covers Zoom, Teams and Google Meet, and botless desktop capture on Mac and Windows reaches Slack Huddles, Webex and in-person meetings, with mobile recording and a no-bot Zoom native capture alongside; a hundred languages with automatic detection and voice-based speaker labeling that learns names within a workspace are documented. Custom vocabulary, dialer or phone calls, and accuracy figures per language are not described, which keeps it below the top band. 1 2 3 12 13
The Works Council Chair
A visible bot covers Zoom, Google Meet and Teams, and next to it botless capture through the Mac and Windows desktop app, the mobile apps, Zoom's own native capture, and desktop audio for Slack Huddles and Webex, including in-person meetings. Automatic language detection covers a hundred languages, speaker labelling runs on voice samples with only four named exceptions, and recap timestamps link to the recording. We found no public information on published accuracy per language, dialer calls, or custom vocabulary for our plant jargon. 12 13 14 1 3
The Data Protection Officer
A visible bot covers Zoom, Google Meet and Teams, while botless capture from the Mac and Windows desktop apps extends to Slack Huddles, Webex and in-person meetings, with mobile recording and Zoom native capture as further channels. Automatic language detection covers a large language set (the captured pages give different figures for the exact count), and speaker identification runs on collected voice samples with four named exceptions. I found no public information on dialer or phone calls, custom vocabulary, transcript editing, or the transcription engine itself and its accuracy per language — that engine must be named before I can finish the DPIA. 1 2 3 12 13
The IT Lead
Bot, botless desktop capture on Mac and Windows, mobile recording without a bot, Zoom Native Capture, desktop audio for Webex and Slack Huddles, and in-person capture are all documented, with speaker identification via voice samples and timestamps that link recaps to the recording and transcript. Automatic language detection covers roughly a hundred languages, though the captured pages give different figures (99 and 100), and we found no public information on phone or dialer calls, custom vocabulary, or accuracy per language. 1 2 3 12 13 14
The Skeptic
Capture is flexible and well documented: a visible bot for Zoom, Google Meet and Teams, botless recording from Mac and Windows desktop audio across Slack Huddles, Webex and in-person rooms, mobile recording, Zoom native capture without a bot, one hundred languages with automatic detection, and speaker identification with its exceptions named. The captured pages give different figures for the language count (99 versus 100), accuracy is asserted as 'human-level' with nothing published per language, and we found no public information on phone or dialer capture, custom vocabulary, file upload, or editing the transcript. Timestamps linking recap sections to the recording and transcript are documented. 1 2 3 12 13 14
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
This is close to the minutes workflow I want: thirteen ready templates from project sync and one-on-one through MEDDIC and customer success, custom sections defined in plain language, multiple template formats per recording, and recaps that carry decisions plus AI-detected action items with assignees pushed to Asana, Jira or Linear and resurfaced before the next meeting. Search and questions over all past transcripts are documented through Ask Fellow, with sharing by email, Slack, Confluence or password-protected recap. We found no public information on the summary language being selectable, the AI models used, or answers that cite the exact transcript passage they rest on. 1 3 6 12 14 15
The Sales Team Lead
This is what my team lives on: thirteen ready templates including Sales discovery, Sales follow-up, BANT, MEDDIC and SPICED, custom sections written in plain language, action items with assignees that resurface before the next call, timestamps in every section linking into the recording, and Ask Fellow turning conversations into follow-up emails. Answers over the archive are documented without a shown link back to the transcript passage they rest on, and the AI models behind the summaries are not named. 1 3 12 14 15
The Works Council Chair
Thirteen ready templates from project sync to BANT and MEDDIC, custom sections defined in plain language, and multiple formats per recording; decisions and action items come out with multiple assignees, are tracked and resurfaced before the next meeting, and flow into Asana, Jira or Linear. Ask Fellow answers questions across all transcripts and summaries, and recaps go out by email or into team channels with restricted visibility. We found no public information on the AI models behind the summaries, on answers citing the transcript passage they rest on, or on choosing the summary language. 14 15 3 6 4
The Data Protection Officer
Meeting recaps are shaped by thirteen prebuilt templates plus custom sections defined in plain language, action items with multiple assignees flow to Jira, Asana and other task tools, and Ask Fellow answers questions across all transcripts and summaries, with recap sections carrying timestamps that link back to the recording and transcript. For an auditable archive the models behind the summaries are not named, and I found no public information on citations behind the question-answering, summary language selection, topic tracking, or export of minutes to Word or PDF. 3 6 12 14 15
The IT Lead
Recaps include decisions and AI-suggested action items with assignees, thirteen prebuilt templates plus custom templates and plain-language custom sections on Business and above, and timestamps link each section to the recording. Action items flow to Jira, Asana, Linear, Microsoft To Do and more; Ask Fellow answers questions across all transcripts and summaries; team-scoped channels have restricted visibility. We found no public information naming the AI models behind summaries, on selecting the summary language, or on whether answers cite the transcript passage they rest on. 3 4 6 14 15
The Skeptic
The recap pipeline is real: thirteen prebuilt templates from standups to MEDDIC with custom sections defined in plain language and multiple formats per meeting, action items detected and pushed to named task tools, and Ask Fellow answering questions across all transcripts and summaries with recap sections timestamped to the recording. Team channels with restricted visibility and resurfacing of open items are documented. We found no public information on which models write the summaries, whether answers cite the passage they rest on, or a selectable summary language, so the traceability I look for is not shown. 3 14 15 4
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
Google and Microsoft calendars with workspace auto-record rules by attendee domain, internal or external mix and title keywords; native Salesforce, HubSpot, Pipedrive and Freshworks CRM sync with AI-powered field updates; Slack and Teams; and a documented REST API with webhooks, request limits, pagination, a Super Admin endpoint and an MCP server for Claude and ChatGPT. Native apps on Mac, Windows, iOS and Android round out a layer a consultancy could genuinely build its week around. We found no public information on Microsoft Dynamics or on granular OAuth scopes. 1 5 6 7 8 11 16 17
The Sales Team Lead
HubSpot, Salesforce, Pipedrive and Freshworks are native, AI-powered CRM field updates exist on the Enterprise plan, and Slack delivers summaries, action items and decisions after every call — exactly the write-back my reps never get around to typing. A REST API with webhooks and request limits, an MCP server, Zapier, Confluence, calendar sync and native desktop and mobile apps are documented, with auto-record rules by internal or external attendees, domains and title keywords on Enterprise. We found no public information on Microsoft Dynamics or SharePoint connections. 5 6 7 8 14 16 17
The Works Council Chair
Google and Microsoft calendars, several CRMs including Salesforce, HubSpot and Pipedrive with AI-powered field updates on the Enterprise plan, Slack, Teams, Notion, Confluence, the task tools, Zapier, and native apps on every platform. The REST API comes with reference documentation covering webhooks, request limits and an MCP server, and admins can set recording rules by criteria such as external attendees, domains or keywords in the title. We found no public information on Microsoft Dynamics. 7 6 16 5 8
The Data Protection Officer
Fifty-plus integrations span Google and Office 365 calendars, the Salesforce, HubSpot, Pipedrive and Freshworks CRMs, Slack, Teams, Notion, Confluence and a dozen task tools, alongside Zapier and native Mac, Windows, iOS and Android apps. The developer documentation describes a REST API with webhooks, request limits and pagination plus an MCP server, with Claude, ChatGPT and Copilot connectors, and the Enterprise tier adds AI-powered CRM field updates and workspace auto-record rules by domain, keyword or attendee type. I found no public information on Microsoft Dynamics, granular OAuth scopes or API versioning. 5 6 7 8 16 17
The IT Lead
Google and Microsoft 365 calendars, Salesforce, HubSpot, Pipedrive and Freshworks with AI-powered CRM field updates on Enterprise, Slack and Teams, Notion and Confluence, Zapier, native apps and browser extensions are documented, alongside a REST API whose reference documentation covers webhooks, request limits, pagination and an MCP server. Enterprise auto-record rules can key on meeting ownership, internal versus external attendees, domains, title keywords and combinations. We found no public information on a SharePoint integration, or on API versioning and OAuth scopes. 5 6 7 8 16 17
The Skeptic
This is the strongest layer: Google and Microsoft calendars with Enterprise auto-record rules, native CRM integrations for Salesforce, HubSpot, Pipedrive and Freshworks with AI-powered field updates, Slack, Teams, Notion and Confluence, Zapier, a REST API with webhooks, request limits and a Super Admin API, an MCP server, connectors for Claude, ChatGPT and Copilot, browser extensions and native desktop and mobile apps. Administrators can control which integrations are available. We found no public information on API versioning, granular OAuth scopes, or whether residency holds as data flows through integrations. 5 6 7 11 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
Consent capture is unusually complete for external guests: about an hour before a meeting the calendar join link is swapped for a Fellow-hosted consent page, declines are logged with the attendee's email, the organizer gets a real-time warning naming who declined, and consent or refusal is visible in activity and disclosure logs that an admin can lock workspace-wide; pausing recording notifies everyone in the call and the pause is independently logged. For a German rollout under co-determination the picture thins out: we found no public information on a works-agreement template, DPIA support, the EU AI Act classification, or how per-person analytics are handled, and consent capture is documented only for Enterprise workspaces on Microsoft 365 calendars. 1 4 5 8 11 18
The Sales Team Lead
Consent is collected before the call starts: the calendar join link is swapped for a Fellow-hosted consent page about an hour ahead, declines are logged with the attendee's email, the organizer sees a real-time warning naming who declined, and disclosure emails plus pause notifications tell prospects politely. The machinery is Enterprise-only and currently works with Microsoft 365 Calendar only, with Google Calendar planned; we found no public information on a works-agreement template, DPIA support or an EU AI Act classification, which matters if I have to walk this past a Betriebsrat. 1 4 5 18
The Works Council Chair
This is what my council cares about most, and much of it is genuinely built: an hour before the meeting the calendar link is swapped for a consent page, every attendee agrees or declines with the decline logged, the organizer sees a live warning naming who declined, and activity logs record who consented; disclosure emails go to all participants, pause and resume informs the whole call, and recording permissions run always, never or at user discretion at organisation, team or individual level, with voice matching switchable off per user or for the whole workspace. But consent capture sits on the Enterprise plan and works with Microsoft 365 Calendar only, and the captured pages describe only an organisation-wide analytics dashboard; we found no public information on talk-time or engagement scores per person or an off-switch for them, nor on works-agreement material, DPIA support or EU AI Act classification. 18 4 5 11 1
The Data Protection Officer
Consent capture replaces the calendar join link with a Fellow-hosted consent page about an hour before the meeting, logs who agreed or declined, warns the organizer in real time when someone declines, and can be enforced or locked workspace-wide by admins; disclosure emails, pause-and-resume with in-call notifications, logged pause events and restriction rules by domain and keyword complete a strong picture. For my works agreement I found no public information on a works-council information pack, DPIA support, the EU AI Act classification, or per-person analytics such as talk time and sentiment and how to switch them off — only an admin usage dashboard is described. Consent capture also sits exclusively on the Enterprise plan and currently on Microsoft 365 Calendar only. 1 4 5 8 18
The IT Lead
Consent capture is unusually concrete: about an hour before a meeting the calendar join link is swapped for a consent page, attendees can agree or request not to be recorded, declines are logged with the attendee's email, the organizer gets a real-time warning naming who declined, and admins can lock the requirement workspace-wide. Disclosure emails, pause-and-resume with in-call notifications and logged pause events, and domain-based recording blocks are also documented. We found no public information on per-person analytics defaults, works-council or works-agreement material, DPIA support, or an EU AI Act classification — and consent capture currently works only for Microsoft 365 Calendar workspaces. 1 4 5 11 18
The Skeptic
Consent capture is built rather than promised: about an hour before the meeting the calendar join link is swapped for a Fellow-hosted consent page, attendees choose to agree or to request not to be recorded — declines are logged, an email address is required, and the organizer gets a real-time warning naming who declined — alongside disclosure emails, pause logging and organization-wide enforcement with an auditable disclosure log. The feature requires the Enterprise plan and Microsoft 365 Calendar today, with Google Calendar support only planned. We found no public information on a works-agreement template, DPIA support, EU AI Act classification, or how per-person analytics are defaulted. 4 5 18
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 promise I want in writing is stated plainly and repeatedly: the AI is never trained on customer data, and an administrator can switch off transfers to third-party AI providers altogether in workspace security settings. Governance matches it — separate retention periods for recordings, transcripts and AI notes down to zero days with the summary preserved, deletion that is permanent and removed from backups, every retention change logged with the admin's name, and an exportable, SEC and FINRA-ready audit trail over access and deletion events, with SOC 2 Type II scope and validity published. We found no public information on SCIM by that name, on legal hold, or on documented deletion of copies at the AI subprocessors. 1 2 5 10 11 19 20
The Sales Team Lead
Retention is genuinely governed: separate clocks for recordings, transcripts and AI notes, zero-day deletion that keeps the summary, permanent deletion within the hour and out of the backups, and every retention change logged with the admin's name on top of an exportable, exam-ready audit trail. Customer content is excluded from AI training, admins can switch third-party AI providers off entirely, and SOC 2 Type II is stated with its criteria and validity. We found no public information on SCIM provisioning or legal hold, and the sub-processor list is published without region or retention terms for the AI providers. 1 2 5 11 19 20
The Works Council Chair
Retention is governable: separate auto-deletion periods for recordings, transcripts and AI notes, zero-day deletion that preserves only summary and action items, deletion executed within an hour and stripped from backups, and every retention change logged with the admin's name beside an exportable audit trail. The subprocessor list is published including the AI providers, an admin toggle cuts the data flow to AI providers entirely, customer content stays out of model training, and SOC 2 Type II is stated with its scope. Auto-deletion is Enterprise-only, and we found no public information on SCIM or the regions and retention terms of the AI subprocessors. 20 5 11 19 1 2
The Data Protection Officer
Retention is governable end to end: separate admin-set periods for recordings, transcripts and AI notes, zero-day deletion that keeps only summary and action items, execution within an hour with removal from backups, and every retention change logged with the admin's name into an exportable, SEC Rule 17a-4 and FINRA-ready audit trail; no-training-on-customer-data is stated, SOC 2 Type II with its scope is published, and an admin toggle can sever the third-party AI providers entirely. Voice samples are addressed with an Art. 9(2)(a) explicit-consent basis, user-level access, correction and deletion, and a workspace-wide opt-out. What I cannot yet put in the DPIA: the privacy policy points to a sub-processor list including the AI providers, but no names, regions or retention terms appear in the pages I read, SCIM is evidenced only as Okta and directory provisioning, and I found no public information on legal hold. 1 2 11 19 20
The IT Lead
Enterprise admins can set separate retention for recordings, transcripts and AI notes, zero-day deletion preserves summaries, deletion is permanent including backups and executes within an hour, retention changes are logged with the admin's name, and an exportable audit trail covers every deletion and access event. SOC 2 Type II with its scope (Security and Confidentiality), AES-256 at rest, HTTPS in transit, a no-training commitment, and an admin toggle that disables third-party AI providers are stated. Single sign-on via Okta, OneLogin and Custom OIDC is documented on the Enterprise plan, but we found no public information naming SCIM or SAML, on legal hold or whole-archive export, or on the regions and retention of the AI and transcription subprocessors. 1 2 5 8 11 19 20
The Skeptic
Governance is unusually concrete for a notetaker: separate retention windows for recordings, transcripts and AI notes, zero-day retention that preserves only the summary, permanent deletion reaching backups, retention changes logged with the admin's name, an exportable audit trail pitched at SEC Rule 17a-4 and FINRA exams, a published subprocessor list including the AI providers, and an admin toggle that switches off third-party AI entirely. SOC 2 Type II is stated with its criteria and audit history, encryption is stated in transit and at rest, and no training on customer content is stated repeatedly and plainly. We found no public information on SCIM provisioning or subprocessor regions and retention terms, and the terms themselves state that data cannot be exported from the free trial. 1 5 10 11 19 20
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
The contracting entity is Fellow Insights, Inc. of Ottawa under Ontario law, hosting sits on AWS in the Canada Central region with backups on AWS for 30 days, and the subcontractor list including the AI providers is published — but every documented link in the chain is outside Europe. GDPR safeguards are documented in the form of Standard Contractual Clauses, GDPR-compliant data processing agreements and a Data Protection Officer on staff; we found no public information on EU hosting, a European contracting entity, or where the AI and transcription providers actually process the conversation. 10 11 17 19
The Sales Team Lead
Fellow Insights, Inc. is a Canadian company governed by Ontario law, hosting on AWS in the Canada Central region, so my call recordings would sit outside the EU. GDPR commitments do appear — Standard Contractual Clauses, an on-staff Data Protection Officer, GDPR-compliant data processing agreements — and a sub-processor list including the AI providers is published, but we found no public information on an EU hosting option, an EU entity or the locations of those sub-processors. 10 11 19
The Works Council Chair
The contracting entity is Fellow Insights, Inc. in Ottawa under Ontario law and the infrastructure runs on AWS in Canada Central; the privacy policy separately speaks of a primary data centre, which suggests further locations. Safeguards for Europe exist on paper — GDPR-compliant data processing agreements, an on-staff data protection officer, standard contractual clauses, and a published subprocessor list including the AI providers — but we found no public information on EU hosting or a European entity. 19 11 10 17
The Data Protection Officer
The contracting and operating entity is Fellow Insights, Inc. of Ottawa under Ontario law, hosting is AWS in the Canada Central region, and transfers rest on adequacy decisions or Standard Contractual Clauses with GDPR-compliant data processing agreements offered. Every recording, transcript and voice profile would sit outside the EU, no EU hosting option is documented, and although a sub-processor list including the AI providers is referenced, no names or locations appear in the captured pages. For a DORA institution I would need every one of those points resolved before the first recording. 10 11 17 19
The IT Lead
Fellow Insights, Inc. is the contracting entity in Ottawa, Ontario under Canadian governing law, hosting is AWS Canada Central, and we found no public information on EU hosting or a European entity or representative. A sub-processor list including the AI providers is published, GDPR-compliant data processing agreements and Standard Contractual Clauses are stated, and SOC 2 Type II and GDPR compliance are claimed. That sits above a bare privacy policy with no sub-processor list, but for us the conversations are processed in Canada under contractual safeguards rather than in Europe. 10 11 17 19
The Skeptic
The contracting entity is Fellow Insights, Inc. of Ottawa under Ontario law and venue, hosting is AWS Canada Central, standard contractual clauses and adequacy mechanisms are cited, and a subprocessor list including the AI providers is said to be published. No EU hosting option, EU entity or EU representative appears in the captured pages, and the locations of the AI and transcription providers that read the conversation are not stated, so a European buyer cannot see where their meetings are processed. 10 11 19
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
Every tier carries a public seat price — $0 on Free, $7 per user per month billed annually or $11 billed monthly on Team, $15 annual or $23 monthly on Business, $25 annual on Enterprise starting at ten users with unlimited seats — together with seat maximums, monthly versus annual billing, and a terms clause leaving VAT and similar taxes with the customer. What I still could not compute for a twelve-person firm: we found no public information on what counts as a seat, on included transcription minutes or storage limits, and consent capture, auto-deletion and redaction sit on Enterprise, where final terms run through sales. 8 10 18
The Sales Team Lead
Per-seat prices are public for every tier — $7 per user / month billed annually for Team, $15 for Business, $25 for Enterprise with contact sales, monthly figures shown alongside — plus a free tier capped at five seats, seat caps per plan, a thirty-day trial without a credit card, and customer responsibility for value-added and other taxes. What a seat counts as, transcription minutes or credits, storage limits and overage handling are not stated, and the governance my team would actually need — consent capture, auto-record rules, CRM field updates — sits on Enterprise, which pairs its price with a sales call. 8 10 18
The Works Council Chair
Four tiers are public down to the seat — free, seven dollars, fifteen dollars and twenty-five dollars per user per month billed annually with monthly prices alongside — plus seat caps per plan, a ten-user minimum on Enterprise, a thirty-day trial without credit card, auto-renewal with thirty days' notice, and taxes on the customer. What I could not compute: minute or storage limits are not described, custom storage time is marked as coming soon, and the governance features my council would insist on — consent capture, auto-deletion, auto-record rules — are Enterprise, where purchase goes through contact sales. 8 10 18 20 5
The Data Protection Officer
All four tiers carry public per-user prices in annual and monthly billing, seat maximums, an Enterprise minimum of ten users, and public plan gating for API access, single sign-on, redaction, consent capture and auto-deletion; taxes are the customer's, the trial runs thirty days without a credit card, and renewal needs thirty days' notice. I found no public information on transcription minutes or credits included, storage limits, what counts as a seat, or the price of tailored onboarding beyond "additional fee", so the real annual cost is not fully computable from public pages. 5 8 10 18 20
The IT Lead
All four tiers are public — Free at "$0 per user / month billed annually", Team at "$7 per user / month billed annually" / "$11 billed monthly", Business at "$15" / "$23", Enterprise at "$25 per user / month billed annually" with "Contact sales" — with seat maximums of 5, 20, 50 and unlimited, a ten-user Enterprise minimum, annual-versus-monthly billing, tax responsibility, and auto-renewal with 30 days' notice. The seat caps mean an organisation of our size can only buy the unlimited tier, where single sign-on, auto-record rules, consent capture, auto-deletion and the audit log sit. We found no public information on transcription minutes or credit limits, storage limits, what counts as a seat, or overage handling, so the real annual cost is not fully computable from public pages. 5 8 10 14 18 20
The Skeptic
Four tiers carry per-user prices with monthly and annual figures, seat caps per plan, a free tier, a thirty-day trial without credit card, tax responsibility and the thirty-day cancellation notice stated. Transcription minutes or credits, storage limits and the onboarding fee are not priced on the captured pages, the Enterprise monthly price is 'Contact sales', and consent capture, auto-deletion and transcript redaction sit behind the Enterprise plan. What counts as a seat beyond per-user billing is not stated. 8 10 18 20
European sovereignty — proven facts
1 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 | Not determined ⚠ unverified | — | uncited Report an error |
|---|---|---|---|
| Hosting location | Outside the EU ⚠ unverified | 0/4 pts | 19 Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined ⚠ unverified | — | uncited Report an error |
| Data processing agreement | Not determined | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Fellow
Is Fellow European?
No. whats-best.ai classifies Fellow as Rest of world.
Where does Fellow store data?
Fellow stores customer data outside the EU by default, per the vendor’s page captured 5 Nov 2026.
Does Fellow have a free plan?
Yes. Fellow has a free plan, per the vendor’s page captured 5 Nov 2026.
What are the best alternatives to Fellow?
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: Fellow 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, Open source. Not confirmed on the vendor’s own pages as captured.
- Weak sourcing — Hosting location. The statement covers server infrastructure generally rather than explicitly customer data, and the privacy policy separately refers to a 'primary data center', suggesting other locations may exist.
- 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.
- 23 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
- 13 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
- 11 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
- 6 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
- 2 data 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 hosting 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
- 2 sovereignty dimensions could not be confirmed on the vendor’s own pages and are 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 fellow.ai Checked 5 Nov 2026 Details →
- 2 Features page (AI meeting notes) fellow.ai Checked 5 Nov 2026 Details →
- 3 Features page (recording and transcription) fellow.ai Checked 5 Nov 2026 Details →
- 4 Features page (privacy controls) fellow.ai Checked 5 Nov 2026 Details →
- 5 Features page (compliance) fellow.ai Checked 5 Nov 2026 Details →
- 6 Integrations page fellow.ai Checked 5 Nov 2026 Details →
- 7 API documentation developers.fellow.ai Checked 5 Nov 2026 Details →
- 8 Pricing page fellow.ai Checked 5 Nov 2026 Details →
- 9 Trust center trust.fellow.ai Checked 5 Nov 2026 Details →
- 10 Terms of service fellow.ai Checked 5 Nov 2026 Details →
- 11 Privacy policy fellow.ai Checked 5 Nov 2026 Details →
- 12 Recording, transcription & languages — found from sitemap help.fellow.ai Checked 5 Nov 2026 Details →
- 13 Recording, transcription & languages — found from sitemap help.fellow.ai Checked 5 Nov 2026 Details →
- 14 Summaries, action items & meeting knowledge — found from sitemap help.fellow.ai Checked 5 Nov 2026 Details →
- 15 Summaries, action items & meeting knowledge — found from sitemap fellow.ai Checked 5 Nov 2026 Details →
- 16 Integrations, API & workflow — found from sitemap fellow.ai Checked 5 Nov 2026 Details →
- 17 Integrations, API & workflow — found from sitemap fellow.ai Checked 5 Nov 2026 Details →
- 18 Consent, participant rights & works council — found from sitemap help.fellow.ai Checked 5 Nov 2026 Details →
- 19 Retention, AI training & administration — found from sitemap help.fellow.ai Checked 5 Nov 2026 Details →
- 20 Retention, AI training & administration — found from sitemap help.fellow.ai Checked 5 Nov 2026 Details →