Cognism
UK / wider Europe Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 2 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Cognism Limited · www.cognism.com
Compare with Lusha → 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.
Cognism at a glance
- Vendor
- Cognism Limited
- Headquarters
- Incorporated in the United Kingdom source, captured 16 Nov 2026
- Data hosting
- In the EU by default; pages mention Ireland source, captured 16 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 16 Nov 2026
- Panel verdict
- The AI panel rates Cognism 2.5/5, the mean of 6 judges. Cognism, a B2B contact database with a European focus, is strongest where its compliance machinery is visible: prospecting compliance runs 6-7, with records screened against 16 global Do Not Call lists before they are returned and failures withheld rather than charged. how scores are made
- As of
- Vendor pages captured 22 Sep 2026 to 16 Nov 2026; evaluated by the panel 17 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Cognism, a B2B contact database with a European focus, is strongest where its compliance machinery is visible: prospecting compliance runs 6-7, with records screened against 16 global Do Not Call lists before they are returned and failures withheld rather than charged. Data coverage, data provenance and CRM sync and export cluster at 6, on quantified regional figures — 55 million European profiles, over 90% coverage for European decision-makers — named source categories, and native Salesforce, HubSpot and Pipedrive export. Visitor identification is the weakest product area, at 2-4: documented intent is licensed from Bombora, and the judges found no public information on identifying companies behind website visits. Sovereignty is the genuine split, 4-8: the high score of 8 credits named joint controllers and cited certifications, while the low score of 4 weighs the England and Wales contracting entity and SCC-permitted transfers. The widest split is unexplained: one judge's registered scores are 0 across the board, the written rationale describing strengths. The pricing pages show no figures; Standard and Pro, five licences each, end in a sales conversation.
Speaks for it
- Records are screened against 16 global Do Not Call lists before they are returned, with failed records withheld rather than charged.
- European coverage is quantified — 55 million European profiles, over 90% coverage for European decision-makers, 20 million direct-dial numbers across Europe and the USA — with daily updates in the millions and a research team manually validating mobile numbers.
- Business contacts are notified of their inclusion in the database within the GDPR timeframe, can opt out via the Cognism Privacy Centre, and platform business contact data carries a stated five-year removal aim.
- Salesforce, HubSpot and Pipedrive export natively, a separately purchasable add-on refreshes CRM records automatically, and a documented API plus read-only MCP connector run under existing permissions and credit controls.
- Sovereignty documentation names joint controllers — Cognism Limited (England and Wales) and Cognism d.o.o. (Croatia) — the Croatian AZOP as EU supervisory authority, hosting on Amazon Web Services in Ireland, with ISO 27001, ISO 27701 and SOC 2 Type II certifications cited.
Held against it
- Documented intent data is licensed from third-party Bombora, and we found no public information on identifying the companies behind website visits or on any tracking script.
- Coverage figures are stated at region level, and we found no public information on per-country or per-industry breakdowns, per-record verification dates, or a bounce or credit-back guarantee.
- The compliance FAQ raises the legal-basis question, and we found no public answer text naming a legal basis or a published legitimate-interest assessment.
- Personal data is stated as stored inside the EU, while the same policy permits onward transfers outside the UK and EU under SCCs and the contracting entity is Cognism Limited under England and Wales law.
- We found no public information on CRM field mapping or deduplication, API rate limits, or the customer's data and access after cancellation.
Best for
- You run phone-led prospecting into Europe and want do-not-call screening handled by the vendor before numbers reach your reps.
- Your team sells across Europe and can plan against region-level figures such as 55 million European profiles and over 90% coverage for European decision-makers.
- You want prospecting, CRM enrichment and API use billed as one pooled credit per contact, with reuse free.
- Your procurement requires named joint controllers, a named EU supervisory authority and cited certifications before signing.
Avoid if
- You need to identify the companies visiting your own website — the documented intent data is third-party, licensed from Bombora, and visitor identification scored 2-4, the bench's weakest product area.
- Your compliance requirement is EU-only processing end to end — the policy permits transfers outside the UK and EU under SCCs to named affiliates including in North Macedonia and the UK, and the contracting entity is Cognism Limited under England and Wales law.
- You need per-country or per-industry coverage numbers to plan — the published figures are stated at region level.
The scores
| Criterion | Panel median |
|---|---|
| Coverage, accuracy & freshness | 3 of 5 |
| Data sources & lawful basis | 3 of 5 |
| Visitor identification & intent signals | 1.5 of 5 |
| Prospecting workflow & outreach rules | 3.5 of 5 |
| CRM sync, enrichment & export | 3 of 5 |
| European sovereignty | 3 of 5 |
Coverage, accuracy & freshness
panel disagrees
Show reasoningHide reasoning
How this is scored
How much of the target market the database actually covers — judged on DACH and EU coverage as much as North American — and what the vendor documents about verification and refresh, because accuracy claims cannot be checked from outside.
0 — Not a data product: the tool supplies no contact or company data and only manages leads the customer brings.
3 — Total record counts for the database with the data types offered (email, phone, company data) and email verification mentioned.
5 — Coverage stated by country or region with Europe or DACH included, email verification described, firmographics beyond name and domain (industry, size, revenue), and a refresh cadence or last-verified date stated.
8 — Coverage broken down by country, industry and data type (email, direct dial, mobile), verification method and refresh cadence documented, company data drawn from official registers where available, and a bounce or credit-back guarantee with stated terms.
10 — The vendor is accountable for its data: per-country coverage and accuracy methodology published, every field carrying a last-verified date visible to the user, register-sourced company data, and credit-back terms that make inaccuracy the vendor's cost rather than the buyer's.
The SDR Team Lead
The database is Europe-first with numbers I can plan around: 55 million European profiles, 20 million direct dials across Europe and the USA, a claim of over 90% coverage for European decision-makers, firmographics like revenue, headcount and technologies, millions of daily updates, a research team manually verifying mobile numbers, and company registries among the monitored sources. What holds it back is that no country-by-country or industry breakdown is published, and we found no bounce guarantee or credit-back terms — the 9-in-10 connect claim is a vendor-cited study, not terms I can hold them to. 6 7 8 9 10 11
The RevOps Manager
European coverage is quantified: 55 million European profiles, 20 million direct dial numbers across Europe and the USA, a claim of over 90 percent coverage for European decision-makers, plus 400 million company profiles worldwide, daily updates in the millions, phone verification, a research team manually validating mobile numbers, and company data confirmed against registries. Coverage is stated at region level rather than broken down by country and industry, and we found no public information on a bounce or credit-back guarantee for inaccurate data. Strong European dataset with documented refresh and manual verification, short of per-country accountability. 6 7 8 10
The Data Protection Officer
The captured pages show a database deliberately built for Europe — 55 million European profiles, over 90 per cent coverage of European decision-makers, 20 million direct-dial numbers across Europe and the USA — with firmographics such as revenue, headcount and industry, company data confirmed against company registries, daily refresh in the millions, and a research team manually validating mobile numbers. We found no public information on per-country or per-industry breakdowns, on email verification, or on a bounce or credit-back guarantee, so the vendor is not yet accountable for inaccuracy in the way the top level requires. 6 7 8 9 10
The ABM Marketer
For a DACH-heavy target list this is the right shape: 55 million European profiles with a stated 90-plus percent coverage of European decision-makers, 20 million direct dials across Europe and the USA, daily refresh running into millions of updates, a research team manually validating mobile numbers, and company registries among the monitored sources. What holds it back from the top: no per-country or per-industry breakdown, no per-field verification dates, and we found no public information on bounce guarantees or credit-back terms — only that records failing Do Not Call screening are withheld and not charged. 7 6 8 10
The DACH Sales Director
The European numbers carry weight: 55 million European profiles, over 90% coverage of European decision-makers, 20 million direct-dial numbers for Europe and the USA, 800,000 data points updated daily, and a research team that manually verifies the most-demanded profiles and mobile numbers, with company registries among the monitored sources. We found no public information on coverage figures for Germany, Austria or Switzerland, on any per-country or per-industry breakdown, or on bounce and credit-back terms making accuracy the vendor's cost — the only withheld-charge rule covers records failing do-not-call screening. 6 7 8 9 10
The Skeptic
Coverage is stated at region level with Europe front and centre — over 90% coverage for European decision-makers, 55 million European profiles, 20 million direct-dial numbers across Europe and the USA, and 400 million company profiles worldwide — with verification described concretely (a research team manually validating mobiles, phone verification, machine-learning monitoring of company sites and registers) and daily refresh claimed in millions of updates. The counts are regional totals, though: we found no public information on per-country or per-industry breakdowns, per-record last-verified dates, or an email-bounce credit-back, and the only stated not-charged rule covers records failing do-not-call screening. 6 7 8 9 10
Data sources & lawful basis
panel disagrees
Show reasoningHide reasoning
How this is scored
Where the personal data in the database comes from and on what legal basis it is processed — as evidenced on the vendor's own pages. Covers Art. 6(1)(f) legitimate interest, the Art. 14 notice to the people in the database, and whether they can find, object to and remove their record.
0 — The vendor states that it leaves the legal basis for the personal data it sells entirely to the buyer, or that records are collected without the people in them being able to object.
3 — Sources described in general terms (public sources, partners), a GDPR legal basis named, and an opt-out or removal route for people in the database.
5 — Source categories named (registers, company websites, contributory networks, licensed partners), legitimate interest under Art. 6(1)(f) stated as the basis for EU records, a privacy notice addressed to the people in the database, and a self-service opt-out or removal process.
8 — The above plus an Art. 14 notification practice described (people informed when added), contributory or browser-extension collection disclosed as such, a legitimate-interest assessment summarised publicly, and EU records handled differently from US records where the law differs.
10 — Provenance is traceable per record: the source and collection date available for each contact, Art. 14 notices sent and documented, the balancing test published, objections honoured across the whole dataset and suppressed permanently, and no data sourced by scraping behind logins or from contributors' address books without their contacts' knowledge.
The SDR Team Lead
Source categories are named — company websites, job postings, news feeds, company registries, community-contributed contacts matched to business profiles, and licensed external providers — and the privacy policy gives people in the database a self-service Privacy Centre opt-out, a five-year retention limit, notification of their inclusion within the GDPR timeframe, and named UK and Croatian joint controllers. We found no public information naming legitimate interest under Art. 6(1)(f) as the stated basis for EU records (the legal-basis question appears in an FAQ with no answer text captured), and no published legitimate-interest assessment. 3 8 9 3
The RevOps Manager
Source categories are named — a community layer where members allow contact information to be matched to business profiles, plus company websites, job postings, news feeds and company registries — and the vendor states it notifies business contacts of inclusion in the database within the GDPR timeframe and runs a self-service Privacy Centre opt-out. We found no public statement naming the legal basis for EU records (the FAQ raises the question without showing an answer on the captured page) and no published balancing test, which is what I would want before defending this data to a DPO. 3 8 3
The Data Protection Officer
Source categories are named — company websites, job ads, newsfeeds, company registries, community-sourced contacts matched to business profiles, and external providers — and, to the vendor's credit, business contacts are notified of their inclusion in the database within the GDPR timeframe, with a Privacy Centre form and privacy@ contact as a removal route and a stated aim of removing platform data after five years. The compliance pages raise the question of Cognism's legal basis but the answer text was not captured, no legitimate-interest assessment is published, and provenance is not traceable per record, so I cannot verify the Art. 6 basis the way this review requires. 3 8 9 3
The ABM Marketer
Source categories are named openly — community-contributed contacts as the first data layer, company websites, job postings, newsfeeds, company registries and vetted external providers — and there is a documented practice of notifying business contacts of their inclusion in the database within the GDPR timeframe, with removal via the Cognism Privacy Centre. The captured pages pose the legal-basis question in the FAQ but show no answer text, and we found no public legitimate-interest assessment or per-record source and collection date. 8 3 3
The DACH Sales Director
Sources are named by category — company websites, job ads, news feeds, company registries, community-contributed contacts and vetted partners — and the practice is unusually serious: business contacts are notified of their inclusion in the database within the GDPR timeframe and can remove themselves through the Cognism Privacy Centre. The FAQ raises the legal-basis question while the captured pages show no stated answer naming legitimate interest for EU records, and we found no public information on a published balancing test or per-record source and collection dates. 3 8 9 3
The Skeptic
Source layers are named plainly — community-sourced contacts as the first layer, the public web and company registries, external providers, and Bombora for intent — and business contacts are said to be notified of inclusion in the database within the GDPR timeframe, with a self-service opt-out via the Privacy Centre. The legal basis itself is the thin part: the compliance FAQ names the question of which legal basis applies, and we found no public answer text naming legitimate interest or any other basis, nor a published legitimate-interest assessment. 3 8 9 3
Visitor identification & intent signals
panel disagrees
Show reasoningHide reasoning
How this is scored
Identifying companies behind website visits and surfacing buying intent — scored on what is identified (company or person), how the tracking works, and whether the vendor states that its script needs consent under §25 TDDDG and how it behaves without it.
0 — No visitor identification or intent data; the product does not look at website visits.
3 — Reverse-IP identification of the companies behind website visits through a tracking script, with visits listed per company.
5 — Company-level identification with filters and visit history per company, alerts or CRM handover of identified companies, and a stated position on consent for the script or a consent-mode option.
8 — Company-level only for EU traffic by design, cookieless operation documented, integration with common consent management platforms and the §25 TDDDG position stated, intent topics or page-level signals with the source of third-party intent data named, and alerts routed to owners.
10 — Identification that survives a DPO review: no personal data of visitors stored, the TDDDG and GDPR position published and specific, third-party intent data sourced from a named co-op or panel with its consent basis stated, and scoring on intent that the user can trace back to the underlying visits.
The SDR Team Lead
Third-party intent is real and named — Bombora supplies the intent data, and intent topics and strength are API fields — which is the half of this criterion my team would actually use for prioritisation. But we found no public information on identifying the companies behind website visits, on any tracking script, or on a consent position for one, so the visitor-identification side is undocumented. 6 7 8 10
The RevOps Manager
The documented intent piece is third-party: intent topics and intent strength flow through the API, and the Bombora partnership is named as the intent source. We found no public information on identifying the companies behind website visits, how any tracking script works, or the vendor's position on consent for such a script, so this rests almost entirely on resold intent data. 6 7 10
The Data Protection Officer
The captured pages evidence buying intent as a licensed third-party data product — intent topics and strength fields sourced from Bombora, plus intent filters — but we found no public information on identifying companies behind website visits, on any tracking script, or on a position on consent under §25 TDDDG. Because the intent data comes from a named external partner rather than from the customer's own site traffic, only a fragment of what this picture assesses is documented. 6 8 10
The ABM Marketer
The intent half of my wish list is genuinely covered: third-party intent data comes from a named partner, Bombora, exposed as intent topics and strength through the API and usable as a filter to prioritise accounts, alongside signals like new hires, job changes and funding rounds. The visitor-identification half is undocumented — we found no public information on identifying companies behind website visits, on any tracking script or its consent position under the German TDDDG, on visit history per company, or on alerts reaching account owners while a signal is still warm. 8 10 7
The DACH Sales Director
Intent signals are documented and sourced by name: Bombora supplies the intent data, buying intent is a filter in the search, and intent topics and strength come back through the API. We found no public information on identifying the companies behind website visits, on any tracking script, or on a stated position on consent under §25 TDDDG or consent-mode behaviour. 6 7 8 10
The Skeptic
Intent signals are documented and their third-party source is named — Bombora — with intent filters in search and intent topics and strength returned through the API. We found no public information on identifying the companies behind website visits, any tracking script or consent mode, or a stated position on consent for such a script. 6 7 8 10
Prospecting workflow & outreach rules
panel disagrees
Show reasoningHide reasoning
How this is scored
Search, list building and outreach — and whether the product helps the buyer stay within UWG §7 and the GDPR once the list exists, rather than leaving the legal risk entirely with the customer.
0 — No search, list building or outreach; the product only stores leads entered or captured elsewhere.
3 — Search with filters on firmographics and job title, saved lists, and export of the contacts found.
5 — Advanced filters (technographics, hiring or funding triggers), saved searches with alerts, a suppression or do-not-contact list, and guidance on GDPR or cold-outreach rules for EU contacts.
8 — Country-aware handling (for example German contacts flagged where cold calls and emails require consent under UWG §7), phone numbers checked against national do-not-call registers where they exist, and opt-outs from outreach synced back to the database.
10 — Compliance is part of the workflow: outreach channels restricted or flagged per country and contact type by default, suppression shared across the whole account and every export, the Art. 14 notice supported at first contact, and a documented record of how each contact entered the buyer's pipeline.
The SDR Team Lead
Search and list building run on firmographic, technographic and signal filters (new hires, funding and M&A, job changes, intent) with CSV and CRM export, and the compliance lives in the data rather than in a PDF: every record is screened against 16 global Do Not Call lists before it is returned, failures are withheld and not charged, and DNC and opt-out checks run before restricted phone data is shown or exported. We found no public information on country-aware flagging such as German contacts under UWG §7, or on a documented trail of how each contact entered the buyer's pipeline. 2 8 9 10 2
The RevOps Manager
Search runs on firmographic, technographic and signal filters (new hires, funding and M&A, job changes, intent) with export and CSV enrichment, and the compliance workflow is real: records screened against 16 global do-not-call lists before being returned, failures withheld and not charged, and do-not-call and opt-out checks applied before restricted phone data is shown or exported. We found no public information on country-aware flagging such as German contacts under UWG §7, or on a customer-managed do-not-contact list carried across every export. 2 8 10 2
The Data Protection Officer
Search with firmographic, technographic and signal filters, list building and export to the major CRMs sit on top of a genuinely vendor-side compliance layer: records are screened against 16 global Do Not Call lists before they are returned, failing records are withheld and not charged, opt-out checks apply before restricted phone data is shown or exported, and the compliance pages set out the GDPR and CCPA posture with data-subject notification. We found no public information on country-aware flagging of German contacts under UWG §7 or on saved searches with alerts, so the buyer still carries that part of the outreach risk alone. 2 8 9 10 2
The ABM Marketer
The vendor carries compliance weight I would otherwise carry myself: every restricted phone record is screened against 16 global Do Not Call lists before it is shown or exported, failed records are withheld and not charged, and business contacts receive their GDPR notification of inclusion. Search runs on firmographic, technographic and signal-based filters with verified-mobile filters and on-demand verification; we found no public information on saved-search alerts, customer-managed suppression lists, or country-specific flagging of contacts such as German ones requiring consent under UWG §7. 10 8 2
The DACH Sales Director
For a phone-led team this is the strongest part: records are screened against 16 global Do Not Call lists before being returned, records failing screening are withheld and not charged, do-not-call and opt-out checks run before restricted phone data is shown or exported, and business contacts are notified of inclusion within the GDPR timeframe. We found no public information on country-aware flags for German contacts where cold calls and emails require consent under UWG §7, or on saved searches with alerts. 2 8 9 10
The Skeptic
Search runs on firmographic, technographic and signal filters (new hires, funding and M&A, job changes, intent) with export to CSV and named CRMs, and the phone workflow is the strongest part: records are screened against 16 global do-not-call lists before they are returned, and failed records are withheld rather than charged. We found no public information on saved searches with alerts, per-country flagging of German contacts where cold-outreach rules differ, or outreach opt-outs syncing back into the database. 2 8 9 10 2
CRM sync, enrichment & export
panel disagrees
Show reasoningHide reasoning
How this is scored
Getting the data into the systems where sales works — CRM sync, enrichment of existing records, API — and what happens to exported data, and to the buyer's access to it, when the subscription ends.
0 — Data can only be viewed inside the product; the vendor states no export and no integration.
3 — CSV export and a push of contacts to at least one named CRM.
5 — Native integrations with the major CRMs (Salesforce, HubSpot or similar) with field mapping or deduplication, enrichment of existing CRM records, and a documented API.
8 — Bidirectional sync with scheduled re-enrichment, update and deletion propagated when a record changes or a person objects, webhook or API access with stated limits and credit costs per call published, and data retention rights after cancellation stated plainly.
10 — The vendor treats the buyer's CRM as the system of record: objections and corrections propagated into synced records automatically, full change history per field, a versioned API with a deprecation policy, and exit terms that say exactly which data the customer may keep and for how long.
The SDR Team Lead
Two-way CRM integration with Salesforce, HubSpot and Pipedrive, an enrichment add-on that automatically refreshes historical CRM records, CSV export and enrichment, and a documented search/enrich/retrieve API with field selection cover what my SDRs need day to day. We found no public information on API rate limits or per-call credit costs, on propagating deletions when a person objects, or on the buyer's data rights after cancellation. 6 10 11 1 2
The RevOps Manager
Export goes directly to Salesforce, HubSpot and Pipedrive, two-way integration and automatic CRM refresh are claimed, and the API documents search, enrichment and retrieval with per-request field selection, with credit reuse free across prospecting, CRM enrichment and API. But the things that decide whether my CRM stays clean are undocumented: we found no public information on field mapping, deduplication, propagation of deletions when a person objects, API rate limits, or what data the customer may keep after cancelling. 6 10 11 2
The Data Protection Officer
Direct export to Salesforce, HubSpot and Pipedrive, CSV export and enrichment, automatic CRM enrichment that refreshes historical records, two-way integration, and a documented search-and-enrich API with field selection and an MCP connector take this past the basics, with do-not-call and opt-out checks applied before restricted data is exported. We found no public information on field mapping or deduplication, stated API limits, credit costs per call, or retention and access after cancellation — and because the customer becomes controller the moment a list leaves the platform, exit terms stated plainly are exactly what I need to see. 2 6 10 11 2
The ABM Marketer
Salesforce, HubSpot and Pipedrive connect natively, a separately purchasable enrichment add-on keeps CRM records current automatically, the API documents search and enrich endpoints with field-level control, and a read-only MCP connector pulls Cognism data into Claude and ChatGPT under the existing roles and credit controls — with one unlocked contact reusable across prospecting, enrichment and API at no extra cost. We found no public information on field mapping or deduplication, on whether deletions or objections propagate back into synced records, or on what data a customer may keep after cancelling. 11 10 2 6
The DACH Sales Director
Salesforce, HubSpot, Pipedrive and the sales-engagement tools integrate natively, the CRM integration is described as two-way, an add-on enriches CRM records automatically and keeps them current, and the API with field selection plus the MCP connector run under account-wide credit governance — one credit covers the same contact for prospecting, enrichment and API use. We found no public information on propagating deletions or objections into synced CRM records, on API rate limits and credit costs per call, or on data retention rights after cancellation. 2 6 10 11
The Skeptic
Salesforce, HubSpot and Pipedrive integrations are named, CRM enrichment exists as its own add-on that refreshes existing records, two-way integration and APIs are claimed, and the API is documented down to a search endpoint, field selection and read-only MCP access governed by existing permissions and credit controls. We found no public information on field mapping or deduplication during sync, API rate limits, or the buyer's data and access after cancellation. 2 6 10 11 2
European sovereignty
panel opinion
panel disagrees
Show reasoningHide reasoning
How this is scored
Where a database of EU residents' personal data is held, who the contracting entity and controller are, and which subprocessors see it. Independently sourced by the sovereignty pipeline; weighted heavily here, because the product itself is personal data about people who never chose the vendor.
0 — Vendor, contracting entity and processing of EU residents' contact data all shown to be outside the EU, with no transfer basis stated.
3 — A named contracting entity and a privacy policy or data processing agreement; a non-EU entity with an EU representative under Art. 27, or EU hosting offered while the hosting location of the database is not stated.
5 — EU hosting stated as standard, together with an EU contracting entity or a published subprocessor list, and a data processing agreement offered.
8 — EU contracting entity and controller, EU hosting on named infrastructure, subprocessor and data-partner list published, and any non-EU transfer named with its legal basis.
10 — Sovereign end to end and evidenced: vendor, controller, hosting, data partners and every subprocessor European, certification published, and a DPA covering both the customer's data and the database records the customer exports.
The SDR Team Lead
EU hosting is stated as standard on named infrastructure — Amazon Web Services in Ireland, with personal data stored inside the EU — a data processing agreement is in place where Cognism acts as processor, and a Croatian joint controller plus a German entity on the imprint sit alongside Cognism Limited, the UK contracting entity. The policy permits onward transfers outside the EU under Standard Contractual Clauses, affiliates including one in North Macedonia can receive data, and we found no public information on a transfer impact assessment. 3 5 3
The RevOps Manager
Hosting is EU on named infrastructure (Amazon Web Services in Ireland) with a statement that personal data is stored inside the EU, a data processing agreement is in place where Cognism acts as processor, supervisory authorities are named (the ICO and Croatia's AZOP), and onward transfers outside the EEA are covered by standard contractual clauses after a country-level assessment. The lead contracting entity is the UK company acting as joint controller with the Croatian entity, and named data recipients include non-EU affiliates in Macedonia and the UK, which keeps this short of full European sovereignty. 3 3
The Data Protection Officer
Cognism Limited (England and Wales) and Cognism d.o.o. (Croatia) are named as joint controllers with the Croatian AZOP given as the EU supervisory authority, hosting is on Amazon Web Services in Ireland with EU storage stated, non-EU transfers are named with Standard Contractual Clauses after a third-country assessment, recipients including affiliates in North Macedonia, the UK and France and the sales-engagement providers are listed, and a processing agreement is in place where Cognism acts as processor, with ISO 27001, ISO 27701 and SOC 2 Type II certification cited. The joint-controller arrangement covering the database itself is available only on request rather than published, and the primary entity is British with US transfers permitted under SCCs, which keeps it short of sovereign end to end. 3 9 3
The ABM Marketer
Hosting is Amazon Web Services in Ireland with a policy statement that personal data is stored in the EU, a data processing agreement applies when Cognism acts as processor, and a Croatian entity acts alongside the UK company as joint controller with the Croatian authority as EU lead supervisor. The contracting entity is Cognism Limited under the law of England and Wales, and the same policy permits onward transfers outside the EU under Standard Contractual Clauses, including to affiliates in North Macedonia and the UK — an EU default rather than EU-only. 3 3 4 5
The DACH Sales Director
Hosting is stated as inside the EU on named infrastructure — Amazon Web Services in Ireland — with a Croatian joint controller, the Croatian authority named as the EU supervisory authority, a data processing agreement where Cognism acts as processor, and non-EU transfers named with standard contractual clauses. The contracting entity and governing law are Cognism Limited under England and Wales, and the recipient list includes a North Macedonian affiliate alongside the UK and French ones, so this reads as EU-hosted rather than European end to end. 3 4 3
The Skeptic
Cognism Limited (England and Wales) and Cognism d.o.o. (Croatia) are named as joint controllers, the platform runs on Amazon Web Services in Ireland with personal data stated as stored inside the EU, a processing agreement is in place where Cognism acts as processor, and transfers outside the EU are named with standard contractual clauses after an assessment of third-country law. The contracting and governing law sit with the UK entity, though, affiliates in North Macedonia and the UK can receive data, and we found no public information on hosting options beyond the stated default. 3 4 5 3
Pricing transparency
not rated — the vendor publishes no price
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the real annual cost from public pages alone — including credits per email, phone number and mobile, credit expiry, seat pricing, visitor-identification tiers and the API — in a category where the unit of billing is often invented by the vendor.
0 — No public prices at all; every tier is a sales conversation.
3 — A public "from" price, a free tier or one priced tier, while what a credit buys or the other tiers are not stated.
5 — Prices public per tier with the billing period and the credits or contacts included per tier; extras such as mobile numbers, additional seats or API access may still be on request.
8 — Every tier priced publicly with credits per data type, credit expiry and rollover, per-seat costs, overage rates, minimum term and VAT treatment stated.
10 — Complete price computability: the annual invoice derivable for a given number of seats, exported contacts by data type, identified companies and API calls, with every credit cost and the refund rule for inaccurate data published.
The SDR Team Lead
The pricing page names a Standard and a Pro package (five licenses each, Pro adding verified mobiles, on-demand verification and intent data) and explains the billing unit well — one credit per unlocked contact regardless of fields, free browsing, free reuse across prospecting, CRM enrichment and API, pooled account-wide — but shows no figures. Every path ends in an individual quote or a conversation with the sales team, so I cannot compute an annual cost from public pages. 2 10 2
The RevOps Manager
Both captured pricing pages present Standard and Pro plans — five licenses included in each — and route pricing to a sales conversation; we found no public price figures on either page. Unusually, the billing unit itself is documented: one credit equals one unlocked contact, browsing and already-unlocked contacts are free, credits are pooled account-wide, and reuse across prospecting, CRM enrichment and API costs nothing. Useful semantics, but they still do not let me compute an annual cost. 2 10 2
The Data Protection Officer
No prices are published anywhere on the captured pricing pages: a Standard and a Pro package with five licences each are described and the buyer is directed to the sales team for a quote. The billing unit itself is explained publicly — one credit unlocks one contact regardless of the number of fields, browsing and already-unlocked contacts cost nothing, credits pool across the account, and reuse across prospecting, CRM enrichment and the API is free — but without a single per-tier or per-credit figure, the annual cost cannot be computed from public pages. 2 10 2
The ABM Marketer
The captured pricing pages show no figures: Standard and Pro (five licenses each) both route to a sales conversation, and Data-as-a-Service pricing and standalone CRM enrichment are quote-only. Unusually, the credit unit itself is explained precisely — one credit per unlocked contact regardless of fields, pooled account-wide, free to reuse, no charge for browsing — but without a single figure I cannot begin to compute an annual cost for my team. 2 2 10
The DACH Sales Director
The pricing pages show no published prices: Standard and Pro are described with their included seats and features, but both point to a conversation with the sales team for an individual quote, and even Data-as-a-Service and standalone CRM-enrichment pricing sit behind FAQ questions. The credit unit is unusually well defined — one credit unlocks one contact regardless of fields, browsing and already-unlocked contacts cost nothing, and reuse across prospecting, enrichment and API is free — but without a single figure a buyer can compute no annual cost at all. 2 10 2
The Skeptic
The pricing pages name a Standard and a Pro package, each including five seats, and explain the credit unit more clearly than most — one credit per unlocked contact, pooled across the account, browsing and already-unlocked contacts free, reuse across prospecting, enrichment and API at no extra cost. No figures appear on the captured pricing pages, which defer price structure to a conversation with the sales team and push Data-as-a-Service and standalone enrichment pricing into FAQs and individual quotes, so an annual cost cannot be computed from public pages. 2 7 2
European sovereignty — proven facts
2 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity |
Incorporated in GB
unverified
Why unverified?Cognism Limited is named as joint controller rather than explicitly as parent, and regional entities (Cognism GmbH on the German imprint, Cognism d.o.o. in Croatia) appear alongside it, but the copyright line on every page names Cognism Ltd and nothing marks it as a subsidiary. |
1/2 pts | 3 Report an error |
|---|---|---|---|
| Hosting location |
EU by default
unverified
Why unverified?The statement covers personal data generally rather than customer data specifically, and the same policy permits onward transfers outside the UK and EU including to the US under SCCs, so EU storage is the default rather than exclusive. |
2/4 pts | 3 Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined | — | uncited Report an error |
| Transfer impact assessment |
Not determined
unverified
Why unverified?Not confirmed on the vendor’s own pages as captured. |
— | uncited Report an error |
Questions about Cognism
Is Cognism European?
Yes, though not from the EU. whats-best.ai classifies Cognism as UK / wider Europe. Its vendor, Cognism Limited, is incorporated in the United Kingdom, per the vendor’s page captured 16 Nov 2026.
Where does Cognism store data?
Cognism stores customer data in the EU by default, though not exclusively, per the vendor’s page captured 16 Nov 2026. The vendor’s pages mention Ireland as hosting location, per the vendor’s page captured 16 Nov 2026.
Does Cognism have a free plan?
Not stated on the vendor’s pages as of 16 Nov 2026.
What are the best alternatives to Cognism?
As of 18 Nov 2026, the panel rates Dealfront (3/5), Lusha (2.5/5) and Vainu (2.5/5) highest among the other 48 Lead Generation 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 Dealfront (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Cognism alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 22 Sep 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Transfer impact assessment. Not confirmed on the vendor’s own pages as captured.
- Weak sourcing — Legal entity. Cognism Limited is named as joint controller rather than explicitly as parent, and regional entities (Cognism GmbH on the German imprint, Cognism d.o.o. in Croatia) appear alongside it, but the copyright line on every page names Cognism Ltd and nothing marks it as a subsidiary.
- Weak sourcing — Hosting location. The statement covers personal data generally rather than customer data specifically, and the same policy permits onward transfers outside the UK and EU including to the US under SCCs, so EU storage is the default rather than exclusive.
- 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.
- 7 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
- 2 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 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
- 1 data fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 legal fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 pricing fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 sovereignty dimension could not be confirmed on the vendor’s own pages and is shown as unknown. Know more? Tell us
- The pricing here was last read more than 30 days ago. Vendors change prices without notice; the capture date is shown with every figure. Know more? Tell us
Sources (11)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.cognism.com Checked 16 Nov 2026 +1 earlier capture: 22 Sep 2026 Details →
- 2 Pricing page www.cognism.com Checked 16 Nov 2026 +1 earlier capture: 22 Sep 2026 Details →
- 3 Privacy policy www.cognism.com Checked 16 Nov 2026 +1 earlier capture: 22 Sep 2026 Details →
- 4 Terms of service www.cognism.com Checked 16 Nov 2026 Details →
- 5 Imprint — found from the homepage www.cognism.com Checked 16 Nov 2026 Details →
- 6 Coverage, accuracy & freshness — found from sitemap www.cognism.com Checked 16 Nov 2026 Details →
- 7 Coverage, accuracy & freshness — found from sitemap www.cognism.com Checked 16 Nov 2026 Details →
- 8 Prospecting workflow & outreach rules — found from sitemap www.cognism.com Checked 16 Nov 2026 Details →
- 9 Prospecting workflow & outreach rules — found from sitemap www.cognism.com Checked 16 Nov 2026 Details →
- 10 CRM sync, enrichment & export — found from sitemap www.cognism.com Checked 16 Nov 2026 Details →
- 11 CRM sync, enrichment & export — found from sitemap www.cognism.com Checked 16 Nov 2026 Details →