Kaspr
EU-Made Report an errorPanel 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 KASPR SAS · www.kaspr.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.
Kaspr at a glance
- Vendor
- KASPR SAS
- Headquarters
- Incorporated in France source, captured 16 Nov 2026
- Data hosting
- In the EU by default source, captured 16 Nov 2026
- Free plan
- Yes, per the vendor’s own page source, captured 16 Nov 2026
- Panel verdict
- The AI panel rates Kaspr 2/5, the mean of 6 judges. KASPR is a LinkedIn browser extension and contact database from KASPR SAS of Paris. how scores are made
- As of
- Vendor pages captured 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
KASPR is a LinkedIn browser extension and contact database from KASPR SAS of Paris. It scores 5 on CRM sync and export, with documented integrations spanning Salesforce, HubSpot, Pipedrive, Zoho, Aircall, Zapier, Lemlist and Ringover, plus an API and CSV enrichment. Pricing transparency splits between 6 and 7 on published tiers — Free at €0, Starter at €59, Business at €99 per user per month, with credits by data type and export limits — the lower scores citing the captured pages' different figures on credit roll-over and unpublished prices for extra export credits. Weakest is visitor identification at 1, its only public trace an unexplained 'Intent data' line on the Enterprise plan. Data coverage sits at 3-4 on headline counts of 200m+ profiles and 500m+ phone numbers and email addresses, with no country breakdown, verification method or refresh cadence shown. Sovereignty sits at 4-5 on published subprocessors and Standard Contractual Clauses, against an EU-processing promise qualified "as far as possible". Exit terms cut hardest: the workspace and its data are permanently deleted on termination, and transmitted data remains the vendor's property.
Speaks for it
- Per-user pricing published for every tier except custom-priced Enterprise: Free at €0, Starter at €59, Business at €99 per month, with credits by data type and export limits per tier
- The Free tier needs no credit card to start and includes 15 B2B email, 5 phone and 5 direct email credits per month
- Integrations documented with setup guides for Salesforce, HubSpot, Pipedrive, Zoho, Aircall, Zapier, Lemlist and Ringover, alongside a documented API and CSV enrichment
- Database sources are named — LinkedIn, Whois, GitHub and data partners — and people in the database get a self-service opt-out form against sharing with customers
- The contracting entity and data controller is named (KASPR SAS, Paris), subprocessors are published, and Standard Contractual Clauses cover third-country transfers
Held against it
- The captured pages give different figures for credit roll-over: the pricing page lists a 'Credits Roll Over' row while the terms state credits cannot be carried over
- On termination the workspace and all its contacts and credits are permanently deleted, and user-transmitted data remains the property of KASPR even after account deletion
- We found no public information on coverage by country or region, the verification method, a refresh cadence or a bounce guarantee
- The terms cap 'unlimited' credits at 10,000 credits per account per month
- We found no public information naming the GDPR legal basis for the database records, an Article 14 notification practice, or a data processing agreement
Best for
- You build prospect lists on LinkedIn — profiles, lists, groups and events — and want the contact data pushed straight into Salesforce, HubSpot, Pipedrive or Zoho
- You want to start free and evaluate at published per-seat prices (€0, €59, €99 per user per month) before any sales conversation
- Your stack already includes Aircall, Ringover, Lemlist or Zapier, each with a documented setup guide
- You enrich CSV files in bulk or auto-enrich LinkedIn lists into your CRM through workflows
Avoid if
- You need to identify companies visiting your website — the captured pages describe a LinkedIn extension and contact database, with 'Intent data' only an unexplained line on the Enterprise plan
- You need in-product guardrails around the automated LinkedIn outreach the product markets — we found no public information on a suppression or do-not-contact list or on cold-outreach guidance
- You cannot accept the exit terms: the workspace, contacts and credits are permanently deleted on termination, and data you transmit remains the vendor's property even after account deletion
- You must verify country-level coverage or a bounce guarantee before spending — the captured pages show only global totals of 200m+ profiles and 500m+ phone numbers and email addresses, and credits are neither refundable nor exchangeable
The scores
| Criterion | Panel median |
|---|---|
| Coverage, accuracy & freshness | 1.5 of 5 |
| Data sources & lawful basis | 2 of 5 |
| Visitor identification & intent signals | 0.5 of 5 |
| Prospecting workflow & outreach rules | 1.5 of 5 |
| CRM sync, enrichment & export | 2.5 of 5 |
| European sovereignty | 2 of 5 |
| Pricing transparency | 3.5 of 5 |
Coverage, accuracy & freshness
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 vendor publishes headline counts — over 200 million profiles and 500 million-plus verified phone numbers and email addresses — with profile fields covering employer, job title, skills and approximate workplace location. We found no public information on coverage by country or region, the verification method behind the word "verified", a refresh cadence, or a bounce guarantee — and I judge a database by connect rate, not the homepage counter. 1 7
The RevOps Manager
The homepage gives total counts — contact data for over 200m+ profiles and 500m+ verified and compliant phone numbers and email addresses — and the privacy policy names the fields carried, including employer, job title and approximate location. We found no public information on coverage by country or region, the verification method, a refresh cadence or a bounce and credit-back guarantee, so I can only credit the headline numbers with verification stated as a claim rather than a method. 1 5 7
The Data Protection Officer
The homepage puts totals on record — "500m+ verified and compliant phone numbers and email addresses" and over 200m profiles — with email, phone and direct-email as the data types, but the captured pages give no coverage by country or region, no verification method, no refresh cadence and no credit-back for bounced data. For a DACH rollout I found nothing telling me how many of those records are European, and the profile fields stop at name, contact details, employer, job title and approximate location. 1 5 7
The ABM Marketer
Headline scale is stated — contact data for over 200m+ profiles and 500m+ verified and compliant phone numbers and email addresses — with profile fields running to employer, job title and skills, so it clears the record-count bar. But coverage is never broken down by country or region, verification is asserted rather than described, and no refresh cadence or last-verified date appears anywhere, so I cannot tell how deep the file runs in Germany versus the US. 1 7
The DACH Sales Director
The homepage claims "500m+ verified and compliant phone numbers and email addresses" and "over 200m+ profiles", which gives total record counts with the data types and a verification claim, but coverage is not broken down by country and nothing is stated for Germany, Austria or Switzerland specifically. No verification method, refresh cadence or bounce guarantee appears on any captured page, so I cannot tell whether my Mittelstand targets are even in the database. 1 7
The Skeptic
The homepage carries the totals — 500m+ "verified and compliant" phone numbers and email addresses across 200m+ profiles — and the privacy notice lists the fields held per profile, but we found no public information on coverage by country or region, the verification method, a refresh cadence or any last-verified date. The terms state credits are "neither refundable nor exchangeable", so an inaccurate record stays the buyer's cost. 1 4 7
Data sources & lawful basis
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
Sources are named outright — LinkedIn, Whois, GitHub and data partners — with five-year retention from first capture, a self-service opt-out form for people in the database, and a German-language rights guide covering access, deletion and objection. We found no public information stating the legal basis for EU records in so many words, an Article 14 notification practice, or source and collection date per record. 3 7 8
The RevOps Manager
Source categories are named — social networks such as LinkedIn, directories such as Whois and GitHub, plus data partners — collected through a LinkedIn browser extension the terms make an integral part of the solution, and people in the database get a dedicated rights guide, a self-service opt-out form against sharing with customers, and deletion unless an overriding legitimate interest exists. We found no public information naming the GDPR legal basis for the records sold, an Art. 14 notification practice or a published balancing test. 3 5 7 8
The Data Protection Officer
Source categories are named — LinkedIn, Whois, GitHub and data partners — collection through a LinkedIn browser extension is disclosed as part of the product, and the people in the database get a privacy notice, objection and deletion rights and a self-service opt-out form against sharing with customers. What I cannot find is the legal basis for those records stated as such: legitimate interest appears only inside the deletion conditions, and no Art. 14 notification practice or balancing test is described, so the origin story of an exported record rests on inference rather than publication. 3 4 7 8
The ABM Marketer
Source categories are named — social networks like LinkedIn, directories like Whois and GitHub, and data partners — and the people inside the database get a Personal Data Charter, a rights guide and a self-service opt-out form against sharing with customers, which is more than most vendors offer. The pages never state the legal basis for EU records outright (legitimate interest surfaces only obliquely in the deletion conditions), and we found no public information on an Article 14 notification practice when someone is added. 3 7 8
The DACH Sales Director
Source categories are named openly — LinkedIn, Whois, GitHub and data partners, with collection through a LinkedIn browser extension disclosed as such — and the people in the database get a rights guide plus a self-service opt-out form. We found no public information naming the GDPR legal basis explicitly (legitimate interest under Art. 6(1)(f)), on an Art. 14 notification practice, or on per-record traceability; the deletion right is granted only "unless an overriding legitimate interest exists". 3 7 8
The Skeptic
Sources are named as LinkedIn, Whois, GitHub and data partners, and people in the database get a self-service opt-out form against sharing with customers plus access, deletion and objection rights, with five-year profile retention disclosed. We found no public information naming the GDPR legal basis for the database records, on notifying people when they are added, or on a published balancing test; deletion is promised only where no overriding legitimate interest exists. 3 7 8
Visitor identification & intent signals
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
The only public mention I can find is the words "Intent data" in the Enterprise plan's feature list. We found no public information on identifying companies behind website visits, any tracking script, or a position on consent under the German TDDDG — nothing a team buying on intent signals can weigh yet. 2
The RevOps Manager
The only fact bearing on this is Intent data listed among the Enterprise extras on the pricing page, with no description. We found no public information on any website-visit tracking, how intent is sourced, a consent-mode option or a stated position on the German TDDDG consent rule. 2
The Data Protection Officer
The captured pages describe a LinkedIn extension and a contact database, and we found no public information on reverse-IP identification of website visitors, a tracking script, its behaviour without consent, or any position under §25 TDDDG. The single trace of intent is an unexplained "Intent data" line in the Enterprise tier, with nothing on how such data is sourced. 1 2 5
The ABM Marketer
This is a different kind of tool for my purposes: the terms define it as an access tool to a database of professional contacts, synchronised to the user's LinkedIn account via a browser extension, and we found no public information on companies identified behind website visits, a named third-party intent source, or alerts routed to the account owner. The single nod is an 'Intent data' line on the Enterprise plan with no source, mechanics or delivery described behind it. 2 4 5
The DACH Sales Director
The only fact bearing on this is "Intent data" listed among the Enterprise plan's advanced features on the pricing page. We found no public information on how companies behind website visits are identified, how any tracking script works, whether it runs cookieless, or a position on consent for it. 2
The Skeptic
The captured pages describe a LinkedIn browser extension that extracts contact data from profiles, lists, groups and events, and we found no public information on identifying companies behind website visits, any tracking script, or any stated consent position for one. The only trace of intent is the word "Intent data" in the Enterprise feature list, with no description of its source or method. 2 4 5
Prospecting workflow & outreach rules
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
List building and outreach are real — lists, groups, tasks, automated LinkedIn outreach and export workflows, with export credits metered separately from phone and email credits. But the prospecting search effectively happens on LinkedIn profiles, lists, groups and events rather than through the vendor's own documented firmographic filters, and we found no public information on a suppression or do-not-contact list, country-aware flags for German contacts, or guidance on cold-outreach rules — "GDPR aligned" and "Enterprise-level compliance" read as badge text, not workflow. 2 4 5 10
The RevOps Manager
The documented workflow is a Chrome extension pulling contact data from LinkedIn profiles, lists, groups and events into a dashboard with lists, tasks, notes, automations, in-platform dialing and export to CRMs. That earns list building and export; we found no public information on firmographic search in a database, technographic or trigger filters, a suppression or do-not-contact list, or guidance on cold-outreach rules for EU contacts. 2 4 5 10
The Data Protection Officer
List building is well documented — extraction from LinkedIn profiles, lists, groups and events, saved leads with lists, tasks and automated workflows, and export to CRM — but I found no public information on a suppression or do-not-contact list, opt-outs from outreach synced back to the database, or any guidance keeping buyers within UWG §7; "GDPR aligned" on the homepage and "Enterprise-level compliance" as a feature label are the only compliance statements. 1 2 5 10
The ABM Marketer
The find-to-export loop is documented: the extension pulls contact data from LinkedIn profiles, lists, groups and events, leads land in a dashboard with lists, tasks and automated workflows including LinkedIn outreach scenarios, and export runs to CSV or a CRM. We found no public information on a suppression or do-not-contact list, country-aware flags for German cold-outreach rules, or outreach guidance beyond a 'GDPR aligned' badge on the homepage. 5 10 2
The DACH Sales Director
Lead lists, tasks, automated workflows, in-platform dialing and export are documented, with discovery running through the LinkedIn extension rather than a firmographic-filter search in the product itself. We found no public information on a suppression or do-not-contact list, country-aware handling for German contacts under UWG §7, or opt-outs synced back to the database — LinkedIn outreach automations are marketed with no compliance guardrails shown. 4 5 10
The Skeptic
Lists, tasks, automated workflows and export to CRM are documented, and LinkedIn outreach automation is marketed as a feature, but we found no public information on an in-product search with firmographic or job-title filters, a do-not-contact or suppression list, or any guidance for buyers on GDPR and cold-outreach rules for EU contacts. 4 5 10
CRM sync, enrichment & export
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
Salesforce, HubSpot, Pipedrive, Aircall, Zoho, Zapier, Lemlist and Ringover all have documented setup guides, alongside an API with a setup guide, CSV enrichment, and workflows that enrich LinkedIn lists and push straight to Salesforce. We found no public information on bidirectional sync, scheduled re-enrichment, deduplication or field mapping; and the exit terms are blunt — on termination the workspace and its contacts are permanently deleted, credits are neither refundable nor exchangeable, and data the user transmits becomes and remains the property of the vendor even after account deletion. 2 4 5 9 10
The RevOps Manager
Integrations with Salesforce, HubSpot, Pipedrive, Aircall, Ringover, Lemlist, Zoho and Zapier are documented with help-centre guides, enrichment workflows can auto-enrich a LinkedIn list and push it to Salesforce, CSV enrichment exists and there is an API with a setup guide — though API access is listed as upon request. I found no public information on field mapping, deduplication, bidirectional sync or scheduled re-enrichment, and the exit terms cut hard against the buyer: on termination the workspace and all its data and credits are permanently deleted, and everything a user transmits becomes and remains the property of Kaspr even after account deletion. 2 4 5 9 10
The Data Protection Officer
Integration documentation covers Salesforce, HubSpot, Pipedrive, Zoho, Zapier and dialers, exports run from the extension, the Leads tab or a workflow, CSV and workflow-based enrichment exist and an API is documented. The pages document no bidirectional sync, field mapping or propagation of objections into synced records, and exit is blunt: on termination the workspace and all contacts and credits are permanently deleted, while all data the user transmits "shall become and remain the property of KASPR, even after the account has been deleted". 4 5 9 10
The ABM Marketer
Native integrations with Salesforce, HubSpot, Pipedrive, Zoho, Aircall and Zapier each carry setup articles, exports run from the extension, the leads tab or an automated workflow, CSV and bulk enrichment are on the plan table, and the API is documented. We found no public information on field mapping, deduplication or bidirectional sync — and the terms state the workspace with all contacts and credits is permanently deleted on termination, with user-transmitted data remaining the vendor's property even after account deletion. 9 10 2 4
The DACH Sales Director
Native integrations with Salesforce, HubSpot, Pipedrive and more are documented with setup guides, CSV and bulk enrichment exist, and an API with a setup guide is offered, though plan pages describe API access as upon request or limited. We found no public information on bidirectional sync, propagation of deletions or objections into synced records, or API limits and credit costs; the terms state that on termination the workspace and all its professional contacts and credits are permanently deleted, and that data the user transmits becomes and remains the property of KASPR even after account deletion. 2 4 5 9 10
The Skeptic
Documented native integrations with Salesforce, HubSpot, Pipedrive and Zoho, a documented API, CSV enrichment, and workflows that auto-enrich LinkedIn lists into Salesforce put this at the integrations-and-API level. We found no public information on bidirectional sync, field mapping, deduplication, or propagation of objections into synced records; on exit the workspace and all its data are permanently deleted, and data a user transmits "become and remain the property of KASPR, even after the account has been deleted". 2 4 9 10
European sovereignty
panel opinion
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
The contracting entity and data controller are KASPR SAS in Paris, subprocessors including Google and HubSpot in the USA plus OVH, MongoDB, Stripe and others are named, and third-country transfers are covered by Standard Contractual Clauses. The EU-processing promise is qualified — "as far as possible" — and it concerns personal data generally rather than where the contact database itself is hosted; we found no public information on a data processing agreement. 3 4 7
The RevOps Manager
KASPR SAS in Paris is the named controller and contracting entity, and subprocessors are published — Google and HubSpot in the USA for analytics, Active Campaign and Sendinblue for email marketing, OVH Limited and MongoDB for storage, Stripe for payments — with Standard Contractual Clauses named for third-country transfers. EU processing is promised only as far as possible, the data partners feeding the contact database are not named, and we found no public information on a data processing agreement, which keeps this short of sovereign end to end. 3 4 7
The Data Protection Officer
KASPR SAS of Paris is the named controller and contracting entity, and the privacy policy publishes its processors — OVH and MongoDB for storage, but also Google and HubSpot in the USA for analytics, plus Stripe, Sendinblue, Active Campaign and Userback, with Standard Contractual Clauses as the stated safeguard. The EU-processing promise is qualified "as far as possible", the licence grants SaaS use only, the data partners are unnamed, and we found no public information on a data processing agreement. 3 4 7
The ABM Marketer
The controller and contracting entity are KASPR SAS in Paris, subprocessors including OVH Limited, MongoDB, Google, HubSpot, Active Campaign and Stripe are named in the privacy policy, and third-country transfers are covered by standard contractual clauses — a real foundation. It stops short of clean European processing: the residency promise is qualified 'as far as possible', US providers handle analytics, data partners remain unnamed, and we found no public information on a data processing agreement. 3 7 4
The DACH Sales Director
The contracting entity and declared controller are KASPR SAS in Paris, and the privacy policy publishes a subprocessor list including OVH Limited, MongoDB, Stripe, Active Campaign, Sendinblue, Google and HubSpot. But hosting is stated only as personal data processed within the UK/EU/EEA "as far as possible", with transfers to third countries permitted under Standard Contractual Clauses and Google and HubSpot processing analytics in the USA; we found no public information on a data processing agreement or on the hosting location of the customer database specifically. 3 4 7
The Skeptic
KASPR SAS of Paris is named as contracting entity and controller, and the privacy notice names its processors — including Google and HubSpot in the USA — with Standard Contractual Clauses covering third-country transfers. Processing within the UK/EU/EEA is stated only "as far as possible", we found no public information on a data processing agreement, and we found no public information on where the contact database itself is hosted. 3 4 7
Pricing transparency
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
Free, Starter at €59 per user per month and Business at €99 per user per month are public, with credits split by data type — B2B email, phone, direct email, export — export limits per tier, credit expiry at the end of each subscription period, notice periods, and prices in euros excluding VAT. Enterprise is custom-priced, API access is listed as upon request, and no per-credit overage rate is published; the captured pages also give different figures for credit roll-over, the pricing page carrying a roll-over row while the terms state credits cannot be carried over. 2 4 10
The RevOps Manager
Free at €0 / month per user, Starter at €59 / month per user and Business at €99 / month per user are public, with credits broken out per data type — B2B email, phone, direct email and annual export limits per tier — and the terms state credit expiry at period end, monthly or annual terms, notice periods, tacit renewal and prices in euros excluding VAT. Enterprise is custom-priced, API access is upon request, and we found no published price for the additional export credits the help centre says can be purchased, so a full annual invoice cannot be computed for every configuration. 2 4 10
The Data Protection Officer
Free (€0), Starter (€59/month per user) and Business (€99/month per user) are priced with email, phone and direct-email credits per tier, prices are stated excluding VAT, monthly and annual terms carry their notice periods, and the terms state credits expire each subscription period and are neither refundable nor exchangeable — while the pricing page carries a credits-roll-over row, so the captured pages give different figures for rollover. Enterprise is custom-priced, API access is on request, additional export credits are purchasable at no stated price, and the "unlimited" email tiers are capped at 10,000 credits per account per month in the terms — so the real annual invoice is close to computable but not fully. 2 4 10
The ABM Marketer
Almost everything is computable: Free at €0 / month per user with 15 B2B email, 5 phone and 5 direct email credits, Starter at €59 / month per user, Business at €99 / month per user with 200 phone and 200 direct email credits, export limits per tier, credits-per-type rows, expiry terms (credits expire at the end of the subscription period), per-user seat pricing, notice periods and prices shown excluding VAT. What blocks a full invoice calculation is the unpriced cost of additional export credits, API billing (access sits behind 'upon request'), and the custom-priced Enterprise tier. 2 4 10
The DACH Sales Director
Every tier except the custom Enterprise plan is priced publicly per user — Free at "€0 / month per user", Starter at "€59 / month per user", Business at "€99 / month per user" — with credits broken out by data type (B2B email, phone, direct email) plus export limits per plan, and the terms state credit expiry at the end of each subscription period, prices in euros excluding VAT, notice periods, and that credits are neither refundable nor exchangeable. Enterprise pricing is a sales conversation, API access is upon request, and the price of additional export credits and any overage rates are not published. 2 4 10
The Skeptic
Free, Starter at €59 and Business at €99 per user per month are published with credits per data type (B2B email, phone, direct email) and export limits per tier, and the terms add credit expiry, per-user billing, VAT excluded, auto-renewal and termination notice periods. Enterprise is custom-priced, additional export credits and API access are on request without published unit prices, and the captured pages give different signals on rollover: the pricing page lists a "Credits Roll Over" row while the terms state credits "cannot be carried over". 2 4 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 | 2/2 pts | 3 Report an error |
|---|---|---|---|
| Hosting location |
EU by default
unverified
Why unverified?The statement is qualified ("as far as possible") and expressly permits transfers to third countries via non-EU service providers, and it concerns personal data generally rather than the hosting location of customer data specifically. |
2/4 pts | 3 Report an error |
| Hosting options |
Cloud service only
unverified
Why unverified?Inferred from the licence definition in the terms, which grants only SaaS-mode use and prohibits copying, modification and decompilation; no page states explicitly that there is no self-hosted or on-premises option. |
0/1 pts | 4 Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Kaspr
Is Kaspr European?
Yes. whats-best.ai classifies Kaspr as EU-Made. Its vendor, KASPR SAS, is incorporated in France, per the vendor’s page captured 16 Nov 2026.
Where does Kaspr store data?
Kaspr stores customer data in the EU by default, though not exclusively, per the vendor’s page captured 16 Nov 2026.
Does Kaspr have a free plan?
Yes. Kaspr has a free plan, per the vendor’s page captured 16 Nov 2026.
What are the best alternatives to Kaspr?
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: Kaspr alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 16 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 — Hosting location. The statement is qualified ("as far as possible") and expressly permits transfers to third countries via non-EU service providers, and it concerns personal data generally rather than the hosting location of customer data specifically.
- Weak sourcing — Hosting options. Inferred from the licence definition in the terms, which grants only SaaS-mode use and prohibits copying, modification and decompilation; no page states explicitly that there is no self-hosted or on-premises option.
- 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.
- 9 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
- 4 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
- 3 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 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
- 3 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
- 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
- 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
Sources (10)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.kaspr.io Checked 16 Nov 2026 Details →
- 2 Pricing page www.kaspr.io Checked 16 Nov 2026 Details →
- 3 Privacy policy www.kaspr.io Checked 16 Nov 2026 Details →
- 4 Terms of service www.kaspr.io Checked 16 Nov 2026 Details →
- 5 Coverage, accuracy & freshness — found from sitemap www.kaspr.io Checked 16 Nov 2026 Details →
- 6 Coverage, accuracy & freshness — found from sitemap help.kaspr.io Checked 16 Nov 2026 Details →
- 7 Prospecting workflow & outreach rules — found from sitemap www.kaspr.io Checked 16 Nov 2026 Details →
- 8 Prospecting workflow & outreach rules — found from sitemap help.kaspr.io Checked 16 Nov 2026 Details →
- 9 CRM sync, enrichment & export — found from sitemap help.kaspr.io Checked 16 Nov 2026 Details →
- 10 CRM sync, enrichment & export — found from sitemap help.kaspr.io Checked 16 Nov 2026 Details →