Panel rating · 6 judges · How to read the stars
Category median
Sovereignty: 3 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Claap SAS · claap.io
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.
Claap at a glance
- Vendor
- Claap SAS
- Headquarters
- Incorporated in France source, captured 17 Nov 2026
- Data hosting
- In the EU by default source, captured 17 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 17 Nov 2026
- Panel verdict
- The AI panel rates Claap 3/5, the mean of 6 judges. Claap, an AI meeting assistant from French vendor Claap SAS, is strongest at the infrastructure layer: sovereignty is a flat 8 — recordings and transcripts on AWS in an EU region, a published data processing agreement naming each subprocessor's location, with Sendgrid and Intercom in the US under standard contractual clauses — and integrations and workflow follows at 7-8, with an MCP server on every plan, free included, and four CRMs with mapped fields filled from the call. how scores are made
- As of
- Vendor pages captured 17 Nov 2026; evaluated by the panel 18 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Claap, an AI meeting assistant from French vendor Claap SAS, is strongest at the infrastructure layer: sovereignty is a flat 8 — recordings and transcripts on AWS in an EU region, a published data processing agreement naming each subprocessor's location, with Sendgrid and Intercom in the US under standard contractual clauses — and integrations and workflow follows at 7-8, with an MCP server on every plan, free included, and four CRMs with mapped fields filled from the call. The meeting layer lags: capture and transcription and summaries and knowledge score 4-5, Zoom-centred, with no public information on bots for Teams, Google Meet or Webex, or on action items with owners and due dates. Consent and codetermination scores 4-5 and data control and administration 6-7, with no public information on a participant opt-out, single sign-on, SCIM or audit logs. Pricing transparency has the widest spread, 5-7: tiers are published — Pro $32 per seat per month on annual billing — but Enterprise is unpriced and the captured pages give different figures for the top price.
Speaks for it
- An MCP server on every plan including the free one, answering plain-language questions over the archive under the user's own permissions
- Four CRMs — HubSpot, Salesforce, Pipedrive and Attio — log calls on Business and Enterprise with mapped fields filled from what was said
- Admin-governed retention from 6 months to 3 years with permanent deletion on expiry, and deleting a recording deletes its transcript and summary
- Customer data is excluded from AI training by stated policy, with zero retention stated at the AI providers and SOC 2 Type II on file
- A French contracting entity hosts recordings and transcripts on AWS in an EU region, with a published data processing agreement listing every subprocessor's location, including Sendgrid and Intercom in the US under standard contractual clauses
Held against it
- Capture is documented around Zoom, with no public information on bots for Microsoft Teams, Google Meet or Webex nor on German among the 99+ languages
- We found no public information on a participant opt-out, on consent collected from external guests before recording starts, or on works-council material, DPIA support or an EU AI Act classification
- Per-person conversation analysis and performance feedback are named as features with no public information on how to switch them off
- We found no public information on single sign-on, SCIM or audit logs
- Enterprise carries no public price, AI credits are mentioned without a price, and the captured pages give different figures for the top price, $60 for Business in the pricing text against a high price of 48 EUR in the site's structured offer data
Best for
- You run sales calls on Zoom and want them logged to HubSpot, Salesforce, Pipedrive or Attio with mapped fields filled from what was said
- You want an AI client such as Claude or ChatGPT to answer questions over your recording archive, starting from the free plan
- You are a European buyer weighing a French vendor that hosts recordings and transcripts in an EU region with a published subprocessor list
- You want to try before committing, as Basic is free with 10 recordings per user, 300 total transcription minutes and 3-month retention, and signing up needs no credit card
Avoid if
- Your meetings run on Microsoft Teams or Google Meet, since the documented bot, Chrome extension and desktop-app coverage is Zoom-centred and capture and transcription scored 4-5
- You need a documented participant opt-out or a default-off switch for per-person conversation analysis before works-council sign-off
- You need one clean figure at the top of the price range, as the captured pages give different figures for the top price and Enterprise is unpriced
- You need structured minutes with templates per meeting type, decisions and action items with owners and due dates, when the documented knowledge features centre on sales workflows such as CRM enrichment and conversation analysis
The scores
| Criterion | Panel median |
|---|---|
| Recording, transcription & languages | 2 of 5 |
| Summaries, action items & meeting knowledge | 2 of 5 |
| Integrations, API & workflow | 4 of 5 |
| Consent, participant rights & works council | 2.5 of 5 |
| Retention, AI training & administration | 3.5 of 5 |
| European sovereignty | 4 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
Capture is flexible: a visible bot for Zoom, botless recording from the Mac and Windows desktop app and the Chrome extension, file upload, a two-sided transcript from microphone and system audio, and transcript matches that jump to the exact moment in the recording. Everything documented centres on Zoom, though, and the 99+ languages from Pro come with German never named, no accuracy figures, no custom vocabulary and no speaker-name handling — the transcription provider (Gladia, France) is named in the subprocessor list but not its accuracy per language. We found no public information on Microsoft Teams, Google Meet, Webex, phone calls or in-person rooms. 3 4 5 7 10
The Sales Team Lead
The captured pages document a Zoom meeting bot alongside a botless route from a Mac and Windows desktop app and a Chrome extension, file upload with per-plan caps, a two-sided transcript in 99+ languages, and search hits that jump to the exact moment in the recording. I found no public information on Teams or Google Meet bots, on German being named among the languages, on speaker identification or on editing the transcript — and as a shop running Teams next to Zoom, that coverage is the first thing I would probe. The recording lands five to ten minutes after the call, which fits our pace. 4 5 7 10
The Works Council Chair
A bot joins Zoom, shows up in the participant list and returns the recording within five to ten minutes, and next to it there is documented botless capture from a Mac and Windows desktop app and a Chrome extension, plus upload of saved video files; transcripts cover more than 99 languages and a search hit jumps to the exact moment in the recording. The evidence is Zoom-centred: we found no public information on Microsoft Teams, Google Meet or Webex, phone or dialer calls, live transcription, custom vocabulary, editable transcripts, or German being named among the languages. For a workforce that holds its daily meetings in Teams, that alone keeps me from a works agreement on this tool today. 4 5 7
The Data Protection Officer
Capture is documented on two tracks: a meeting bot that appears in the Zoom participant list, and botless recording from a Chrome extension and Mac or Windows desktop apps using microphone and system audio for a two-sided transcript, plus video upload and 99+ languages from the Pro plan. We found no public information on bots for Teams, Google Meet or Webex, on phone calls, on speaker names, custom vocabulary or transcript editing, and German is not named among the languages; transcript search does jump to the exact moment in the recording. 4 5 7 10
The IT Lead
Everything documented publicly about the bot and extensions is Zoom-specific: the bot joins Zoom calls and appears in the participant list, the Chrome extension records the Zoom tab, and the Mac desktop app records the Zoom desktop app, with botless capture from Mac and Windows and file upload also documented, transcription in 99+ languages, and search results that jump to the exact moment in the recording. We found no public information on a bot or extension for Microsoft Teams, Google Meet or Webex, on German being named among the languages, on phone or in-person capture, or on speaker names and transcript editing. As a Microsoft 365 house, this documentation would not get Claap past our pilot. 4 5 7
The Skeptic
The bot joins Zoom calls and appears in the participant list, a botless desktop app captures any meeting from Mac or Windows using microphone and system audio, files can be uploaded and past Zoom cloud recordings imported, and transcript search jumps to the exact moment in the recording. But the pages are Zoom-centred: we found no public information on a bot for Teams, Meet or Webex, on phone calls, live transcription, speaker names, an editable transcript, or accuracy for the claimed 99+ languages — German is never named, and the transcription engine (Gladia, France) surfaces only in the data processing agreement, not with any accuracy figures. 4 5 7 3
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, notes and chapters are documented, and search is strong: keyword search across transcripts with a jump to the exact moment, saved views and AI fields shared with the team, and plain-language questions over the archive through the MCP connection on any plan. For minutes by meeting type, though, we found no public information on templates, on decisions and action items with owners and due dates, on choosing the summary language, or on export to Word or PDF — the documented use is sales (SPICED scores, CRM enrichment) rather than client minutes. 2 4 7 8
The Sales Team Lead
Summaries, notes, chapters and conversation analysis are named, search spans recordings, folders, CRM objects and transcript keywords, and the notes go out to Slack or Notion. What I actually need after every discovery call — action items with owners and dates, a follow-up email draft, a summary language I can set to German — I found no public information on any of those, nor on templates per meeting type or minutes exported to Word or PDF. Saved views and AI fields like a SPICED score filled on chosen calls are real workflow value, but that is analysis, not minutes. 2 4 7 8
The Works Council Chair
Summaries, notes and chapters are generated automatically, global search covers recordings, folders, connected CRM entities and transcript keywords, notes go to Slack or Notion, and the MCP endpoint answers plain-language questions over the archive under the user's own permissions. We found no public information on templates per meeting type, action items with owners and due dates, or the summary language being selectable, and nothing shows an answer citing the transcript passage it rests on. 2 4 7 8
The Data Protection Officer
Summaries, notes, chapters and conversation analysis are documented, keyword search spans recordings, folders, CRM entities and transcript text and jumps to the exact moment, notes go to Slack or Notion, and an MCP server on every plan lets AI clients read the archive under the user's own permissions, with the summarisation model named in the subprocessor list. We found no public information on templates per meeting type, on action items with owners and due dates, or on choosing the summary language with German available. 2 3 4 7 8
The IT Lead
Summaries, notes and chapters are documented, search spans recordings, folders, CRM entities and transcript keywords, and the MCP layer answers plain-language questions over the archive under each user's own permissions, with AI fields like a SPICED score and saved views shared with the team. But we found no public information on templates per meeting type, on action items with owners and due dates, on decisions being extracted, or on choosing the summary language with German available. That leaves the meeting knowledge generic where our engineering reviews need structured minutes. 2 4 7 8
The Skeptic
Summaries, notes and chapters are generated, search covers recordings, folders, CRM entities and transcript keywords, and an MCP server answers questions over the archive under the user's own permissions — the strongest part of the story, with AI fields and saved views adding team-level tracking. We found no public information on action items with owners and due dates, templates per meeting type, choosing the summary language, or whether answers cite the transcript passage they rest on; the summary model appears only in the subprocessor list (Google Gemini, EU), not as a documented, named engine with quality statements. 2 7 8 3
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
Calendars (Google and Outlook), four CRMs including HubSpot, Salesforce, Pipedrive and Attio with mapped fields filled from what was said, Slack and Notion for notes, Zapier, Make, n8n, documented webhooks with headers and retry policy, an API with reference documentation on Enterprise, and an MCP server on every plan including free that inherits the user's permissions. Recording rules per team and enforced workspace policies such as 'never record Legal' govern when it joins. We found no public information on SharePoint or Confluence export or Microsoft Dynamics. 4 8 9 10
The Sales Team Lead
This is the closest to what I ask for: each recorded call is logged on the matching contact and deal in HubSpot or Salesforce with the CRM fields I map filled from what was said, on Business and Enterprise. Attio, HubSpot, Pipedrive and Salesforce are covered, Slack and Notion take the notes, Zapier, Make, n8n and webhooks come with Business and Enterprise, the API with Enterprise, and an MCP server runs on every plan under the user's own permissions — deal updates through it work with HubSpot today. I found no public information on a Microsoft Teams destination or SharePoint and Confluence export on the captured pages. 4 8 9
The Works Council Chair
Google and Outlook calendars drive per-team recording rules — every meeting, external only, internal only, or none — enforceable workspace-wide including never recording named departments; mapped calls land in HubSpot, Salesforce, Pipedrive or Attio on Business and Enterprise, and there are Zapier, Make and n8n automations, webhooks documented with events, signatures and retry behaviour, an API on Enterprise and an MCP server on every plan including the free one. We found no public information on Microsoft Teams channels, SharePoint or Confluence export, or API rate limits and versioning. 4 8 9
The Data Protection Officer
MCP ships on every plan with OAuth or a workspace API key and works with Claude, ChatGPT and other clients; a documented API arrives with Enterprise, webhooks cover recording events with signing headers and a retry policy, and Zapier, Make and n8n are on Business and Enterprise. Four CRMs (HubSpot, Salesforce, Pipedrive, Attio) log calls and fill mapped fields from what was said, and per-team recording rules govern which meetings capture. We found no public information on API rate limits and versioning or on residency guarantees across integrations. 4 8 9
The IT Lead
Google and Outlook calendars, per-team recording rules, HubSpot, Salesforce, Pipedrive and Attio with mapped CRM fields filled from what was said, notes to Slack and Notion, Zapier, Make and n8n, a documented webhook reference with retry policy, and an MCP server on every plan — this is a genuinely strong layer. Two things hold it back for us: the API sits on the Enterprise plan, and we found no public information on Microsoft Teams channels or SharePoint, exactly where our 450 people work. 4 8 9
The Skeptic
Calendar connections with per-team recording rules, four CRMs (HubSpot, Salesforce, Pipedrive, Attio) with mapped fields filled from the call, notes to Slack and Notion, Zapier, Make, n8n and webhooks on Business and Enterprise, a REST API with reference documentation on Enterprise, and an MCP server on every plan including the free one — webhooks even document retry behaviour and verification headers. We found no public information on Confluence or SharePoint export, granular OAuth scopes, rate limits or versioning, so this stops short of a layer a company builds on blindly. 4 8 9
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
The notice machinery is documented: the bot appears in the participant list with customisable name, image and chat message, botless capture comes with the instruction to announce the recording yourself, the bot must be admitted by the host, and admins enforce per-team and per-workspace recording rules that even MCP agents cannot bypass. We found no public information on a participant opt-out, on consent collected from external participants before recording starts, on works-council or DPIA material, or on how to switch off the conversation analysis and performance feedback that the service description names as a feature. 3 4 10 11
The Sales Team Lead
The GDPR page speaks to exactly my worry: a visible bot in the participant list so everyone knows the call is recorded, bot branding with name, image and chat message, and a botless mode where you announce the recording yourself. Admins enforce per-team and workspace-wide recording rules — "never record Legal" is the example — the capture mode per workspace follows the notice each market expects, and recordings are deleted on request under the data processing agreement. I found no public information on a participant opt-out before recording starts, on switching off per-person conversation analysis, or on works-council material, DPIA support or an EU AI Act classification. 3 4 10 11
The Works Council Chair
The bot is visible in the participant list with a customizable name, image and chat message, for botless capture users are told to announce the recording themselves at the start, and admins can enforce recording rules per team and workspace — including never recording a named department, which a works agreement could build on. But we found no public information on a participant, let alone an external guest, being able to refuse or stop a recording; the data processing agreement advertises sales coaching through conversation analysis and performance feedback, and we found no public information on how such per-person analytics could be switched off; nor on any works-agreement template, DPIA support or EU AI Act classification — the vendor instead argues legitimate interest for recording sales calls as long as participants are informed. 3 4 10 11
The Data Protection Officer
The visible bot with a customisable name, image and chat message, botless capture where the user announces the recording, and admin-enforced per-team and per-workspace rules such as "never record Legal" are documented, as is deletion on request under the data processing agreement. We found no public information on a participant opt-out or a way for a participant to stop a recording, on defaults and switch-off for the conversation-analysis and sales-coaching feedback, or on works-council material, a works-agreement template, DPIA support or the EU AI Act classification. 2 3 4 10 11
The IT Lead
The visible bot with customisable name, image and chat message, botless capture where you announce the recording yourself and pick the capture mode per workspace, admin-enforced rules for which meetings record including never recording Legal, and deletion of the recording together with its AI outputs cover much of what a works council will ask about. We found no public information on participants opting out or on consent collected before recording starts, and conversation analysis is marketed as sales coaching with no documented default-off or minimum group sizes. That makes it introducible here only with a negotiated works agreement of our own. 3 4 10 11
The Skeptic
The GDPR page argues legitimate interest for recording sales calls as long as participants are informed, the bot is visible with customisable name, image and chat message, botless users are told to announce the recording themselves, and each team picks its capture mode to follow the notice its market expects — real notice discipline. But we found no public information on a way for a participant to stop or opt out of a recording — once admins enforce the rule, a member's own preference cannot switch it off — nor on consent collected from external guests before recording starts, works-council material, DPIA support or the EU AI Act classification, and per-person conversation analysis and performance feedback are described without any way to switch them off. 10 4 11 3
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 there more than once: calls are never used to train AI models, ours or anyone else's, and deleting a recording deletes the transcript and summaries generated from it. Governance is real too — retention policies with fixed periods and permanent deletion, admin-only security settings for public links, default privacy and retention, subprocessors named with regions and zero retention by default at the AI layer, whole-archive export in JSON or CSV within thirty days of termination, and SOC 2 Type II. We found no public information on single sign-on or SAML, SCIM, audit logs, legal hold, or discarding audio after transcription. 2 3 8 12
The Sales Team Lead
Workspace admins get real policy: retention of 6 months to 3 years against an indefinite default, then permanent deletion; public-link sharing blockable for recordings and folders; private links by default; and a firm, repeated commitment that no customer data trains models, with AI outputs deleted alongside the recording. The subprocessors are listed with their locations and SOC 2 Type II is stated. I found no public information on single sign-on, SCIM, audit logs, or discarding the audio once transcription is done on the captured pages. 2 3 8 10 11 12
The Works Council Chair
Retention defaults to indefinite but admins can set automatic deletion after 6 months, 1, 2 or 3 years with permanent deletion, security settings are admin-only and cover public link access, default link privacy and retention, sharing is private by default, customer content is excluded from AI training, deletion reaches subprocessors and backups, the archive exports in JSON or CSV, encryption and SOC 2 Type II are stated. We found no public information on single sign-on, SCIM, audit logs, audio being discardable after transcription, or the scope of the SOC 2 report — exactly the items our co-determination file would need. 2 3 8 12
The Data Protection Officer
Workspace admins set recording retention (indefinite by default, custom from six months to three years, permanent deletion at expiry), recordings and the AI data derived from them are deleted together, training on customer data is excluded at Claap and at the AI providers with zero data retention stated, and SOC 2 Type II, encryption in transit and at rest, admin-only security settings with public-link toggles and JSON/CSV export are documented. We found no public information on single sign-on, SAML or SCIM, on audit logs, or on discarding audio after transcription. 2 3 8 10 12
The IT Lead
Admins set retention centrally — indefinite by default or 6 months to 3 years, permanently deleted on expiry — and can block public links workspace-wide, set the default privacy of new recordings, and restrict security settings to admin and owner licences; customer data is excluded from model training by stated policy, the AI and transcription subprocessors are named with regions and zero retention, and SOC 2 Type II is stated. But we found no public information on single sign-on, SCIM or audit logs — the three controls I need before one tool goes to four hundred users — and the retention menu is a fixed list rather than free-form policy. 2 3 8 12
The Skeptic
Retention is admin-governed with custom periods from 6 months to 3 years and permanent deletion on expiry, deleting a recording deletes its transcript and summary, the archive exports as JSON or CSV, public links can be blocked workspace-wide, and the no-training promise is contractual and repeated down to provider models with zero retention — SOC 2 Type II is stated. We found no public information on single sign-on, SAML or SCIM, audit logs, legal hold, or discarding audio after transcription, and the SOC 2 scope is not detailed, which is what an auditor would ask for next. 12 2 3 8
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
A French contracting entity (Claap SAS, Saint-Mandé, lempire group), hosting on AWS in an EU region with recordings and transcripts stated to be hosted in the EU, a published data processing agreement, SOC 2 Type II, and a subprocessor list with locations: Gladia in France for transcription, Google Gemini in the EU as an option, OpenRouter EU by default, Recall AI in the EU. The caveats sit on the same page — Sendgrid in the US, Intercom US-based with EU-hosted data, and OpenRouter warning that a US hosting provider might be used depending on model evolution, with SCCs and the Data Privacy Framework as safeguards — so the model chain is not European-operated end to end. 2 3 8 10
The Sales Team Lead
Claap SAS in Saint-Mandé, part of the French lempire group, hosts recordings and transcripts on Amazon Web Services in an EU region, with Gladia in France for transcription and the AI chain named with locations — Google Gemini in the EU as an option, OpenRouter EU by default. Every non-EU subprocessor such as Sendgrid and Intercom carries standard contractual clauses or the Data Privacy Framework, the data processing agreement is published with the full list, and SOC 2 Type II is stated. The privacy policy itself notes some providers may process outside the EU, in particular in the United States, and a US hosting option for model routing is named, so the chain is documented rather than uniformly European. 2 3 10
The Works Council Chair
Claap SAS sits in Saint-Mandé under the French parent lempire, recordings and transcripts run on Amazon Web Services in an EU region, the data processing agreement is published, and the subprocessor list names locations: Gladia in France, Recall AI and OpenRouter in the EU, optional Google Gemini in the EU, Sendgrid in the US and Intercom with data hosted in the EU, each under standard contractual clauses or the Data Privacy Framework. Two caveats for the council: the privacy policy lists Vercel Inc. in the United States as a hosting provider and says some AI providers may process data in the US, and OpenRouter notes a US hosting provider might be used depending on the evolution of models. 2 3 10
The Data Protection Officer
The contracting entity Claap SAS and its parent lempire are French, recordings and transcripts are hosted on Amazon Web Services in an EU region, and the published data processing agreement lists every subprocessor with its location and transfer safeguard: Gladia in France for transcription, Google Gemini in the EU for summarisation, OpenRouter EU by default, Recall AI EU, Sendgrid in the US and Intercom with a US entity but EU-hosted data, under SCCs and the Data Privacy Framework, with a SOC 2 Type II report stated. The note that a US hosting provider might be used for the OpenRouter models, and the US companies elsewhere in the chain, keep this short of a fully European setup. 2 3 10
The IT Lead
Claap SAS is a French company in the lempire group, recordings and transcripts sit on Amazon Web Services in an EU region, and the subprocessor list names the whole chain with locations: Gladia in France for transcription, Gemini in the EU as an option, OpenRouter EU by default with a note that a US hosting provider might be used as models evolve, and Sendgrid and Intercom in the US under SCCs. A published data processing agreement and SOC 2 Type II are on file; the privacy policy also notes some providers may process data in the United States. Solid enough for our data protection reviews, with the OpenRouter caveat worth watching. 2 3 8 10
The Skeptic
Claap SAS is a French company in the French lempire group, recordings and transcripts sit on AWS in an EU region, and the published DPA lists every subprocessor with its location: Gladia in France for transcription, Recall AI in the EU for the bot, Gemini in the EU for summaries, Sendgrid and Intercom in the US under SCCs. Not sovereign end to end: by the vendor's own words a US hosting provider might be used for the AI function as models evolve, a US host (Vercel) appears in the privacy policy, and the summarization model is Google's rather than a European operator. 2 3 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
Unusually public on inclusions: a free plan capped at 10 recordings per user kept 3 months, Pro at $32 per seat per month on annual billing ($40 monthly), Business at $60 ($75 monthly), with transcription minutes (300 total, 1,000 monthly, then unlimited), upload counts, guest seats and storage per tier all stated. But the Enterprise tier that carries the API is unpriced, AI credits are mentioned without a price, what counts as a seat, minimum term and VAT treatment are not stated, and the captured pages give different figures — dollars on the pricing page against a euro range in the site's structured data — so I cannot compute one clean annual number for my twelve-person firm. 4 8 10
The Sales Team Lead
Seat prices are public — Pro at $32 per seat per month on annual billing ($40 monthly), Business at $60 ($75 monthly), and a free Basic with 10 recordings, 3 months retention and 300 total transcription minutes — with per-plan minutes, upload caps, guest counts and storage spelled out. Enterprise is not priced on the captured pages, the captured pages give different figures for the top of the range (the USD plan prices against a published EUR range topping at 48), and I found no public information on what counts as a seat, VAT treatment, minimum terms or overage handling. Good enough for a first budget conversation, not yet for a signed number. 4 8 10
The Works Council Chair
The tiers are public: a free Basic plan capped at 10 recordings per user, kept 3 months, with 300 transcription minutes in total; Pro at $32 per seat per month on annual billing ($40 monthly) with 1,000 minutes a month and 2-year storage; Business at $60 ($75 monthly) with unlimited minutes and 3-year storage. The captured pages give different figures for the top price — one page's structured data shows four offers from 0 to 48 EUR — and we found no public information on what counts as a seat, overage handling, minimum term, VAT or an Enterprise price, so the real annual cost for our workforce is not derivable from the public pages. 4 8 10
The Data Protection Officer
Tiers are public with their scaling: a free Basic plan capped at 10 recordings and 300 transcription minutes kept 3 months, Pro at $32 per seat per month on annual billing ($40 monthly) with 1,000 minutes a month, and Business at $60 ($75 monthly) with unlimited minutes; upload limits, guest seats, storage per tier and plan gating for the API and automations are documented. We found no public information on what counts as a seat, VAT treatment, minimum term or overage handling, and the captured pages give different figures for the top price, per-seat US dollars on one page and an aggregate euro range from 0 to 48 on another. 4 8 10
The IT Lead
The public pages state Pro at $32 per seat per month on annual billing ($40 monthly), Business at $60 ($75 monthly), and Basic free with 10 recordings kept 3 months and 300 total transcription minutes, with per-plan minutes, upload limits, guest counts and storage all stated. Enterprise, where the API lives, carries no public price, we found no public information on what counts as a seat, VAT or minimum seats, and the captured pages give different figures for the top of the range, one showing 0 to 48 in EUR across four offers. I could budget roughly for 400 seats on Pro or Business, but not to the last euro. 4 8 10
The Skeptic
Three tiers are priced publicly with concrete quotas — Basic free with 10 recordings per user, 300 total minutes and 3-month retention; Pro $32 per seat per month on annual billing ($40 monthly) with 1,000 minutes a month; Business $60 ($75 monthly) with unlimited minutes — and the free tier needs no credit card. Enterprise is unpriced, AI credits are mentioned but never priced, and we found no public information on what counts as a seat, VAT treatment, minimum term or overage; the captured pages also give different figures for the top price, $60 for Business in the pricing text versus a high price of 48 EUR in the structured offer data. 4 8 10
European sovereignty — proven facts
3 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 FR
unverified
Why unverified?The privacy policy names Claap SAS as the publisher and calls lempire SAS its parent company, but the parent's seat is stated only in the DPA's party list; both entities are French anyway. |
2/2 pts | 3 Report an error |
|---|---|---|---|
| Hosting location |
EU by default
unverified
Why unverified?The same page states that some service providers and sub-processors (e.g. AI providers) may process personal data outside the EU, in particular in the United States. |
2/4 pts | 2 Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement |
Published, self-serve
unverified
Why unverified?The GDPR product page describes the DPA as 'available on request', but the full agreement text is published at claap.io/legal/dpa. |
1/1 pts | 3 Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Claap
Is Claap European?
Not determined: the vendor’s pages as captured do not say where Claap is based. Its vendor, Claap SAS, is incorporated in France, per the vendor’s page captured 17 Nov 2026.
Where does Claap store data?
Claap stores customer data in the EU by default, though not exclusively, per the vendor’s page captured 17 Nov 2026.
Does Claap have a free plan?
Not stated on the vendor’s pages as of 17 Nov 2026.
What are the best alternatives to Claap?
As of 18 Nov 2026, the panel rates MeetGeek (3.5/5), Noota (3.5/5) and Jamie (3.5/5) highest among the other 23 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, Romania). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Claap alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 17 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 — Data processing agreement. The GDPR product page describes the DPA as 'available on request', but the full agreement text is published at claap.io/legal/dpa.
- Weak sourcing — Legal entity. The privacy policy names Claap SAS as the publisher and calls lempire SAS its parent company, but the parent's seat is stated only in the DPA's party list; both entities are French anyway.
- Weak sourcing — Hosting location. The same page states that some service providers and sub-processors (e.g. AI providers) may process personal data outside the EU, in particular in the United States.
- 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.
- 20 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
- 9 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
- 8 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
- 5 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
- 3 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
- 2 subprocessors 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 support 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
Sources (12)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page claap.io Checked 17 Nov 2026 Details →
- 2 Legal notice — found from the homepage www.claap.io Checked 17 Nov 2026 Details →
- 3 Data processing agreement (dpa) — found from the homepage www.claap.io Checked 17 Nov 2026 Details →
- 4 Recording, transcription & languages — found from sitemap www.claap.io Checked 17 Nov 2026 Details →
- 5 Recording, transcription & languages — found from sitemap help.claap.io Checked 17 Nov 2026 Details →
- 6 Summaries, action items & meeting knowledge — found from sitemap www.claap.io Checked 17 Nov 2026 Details →
- 7 Summaries, action items & meeting knowledge — found from sitemap help.claap.io Checked 17 Nov 2026 Details →
- 8 Integrations, API & workflow — found from sitemap www.claap.io Checked 17 Nov 2026 Details →
- 9 Integrations, API & workflow — found from sitemap docs.claap.io Checked 17 Nov 2026 Details →
- 10 Consent, participant rights & works council — found from sitemap www.claap.io Checked 17 Nov 2026 Details →
- 11 Retention, AI training & administration — found from sitemap help.claap.io Checked 17 Nov 2026 Details →
- 12 Retention, AI training & administration — found from sitemap help.claap.io Checked 17 Nov 2026 Details →