Lead Generation
Snitcher
EU-Made Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 1 of 4 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Snitcher B.V. · www.snitcher.com
Report an error on this page Is this your product? →
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Snitcher, a B2B lead generation tool from Snitcher B.V. of Hilversum, shows which companies visit your site and feeds verified contacts and intent into your CRM. Pricing transparency leads the scoring at 6-7: published monthly EUR tiers run from €49 for 0-50 unique companies identified per month to €529 for 4,001-5,000, with all features in every plan, unlimited team members and a 14-day free trial with no credit card required. CRM sync and export and sovereignty both hold at 4 — HubSpot, Salesforce and Pipedrive sync with REST API access; a Dutch contracting entity and controller under Dutch law, though the privacy policy itself lists Stripe, Intercom and other parties as established outside the EU. The weaknesses are just as concentrated: data coverage scores 0-2, data provenance 1-2 and prospecting compliance 1-3, because we found no public information on record counts, verification method, where revealed contacts originate, suppression lists or cold-outreach guidance. The split is visitor identification at 2-4 — judges crediting the documented company-level engine against those weighing the unstated consent position, legal basis and unexplained asterisk on contact-level identification.
Speaks for it
- Published monthly EUR tiers from €49 for 0-50 to €529 for 4,001-5,000 unique companies identified per month, with all features in every plan and unlimited team members
- A 14-day free trial with no credit card required
- CRM sync and export scores hold at 4, with documented sync to HubSpot, Salesforce and Pipedrive plus REST API access
- Sovereignty scores hold at 4, with Snitcher B.V. of Hilversum as contracting entity and declared controller under Dutch law and Dutch courts
- Company-level visitor identification is documented — which companies visited, what they viewed and how often they return — with real-time Slack and email alerts
Held against it
- Data coverage scores fall to 0-2; we found no public information on record counts, verification method or refresh cadence behind the 'verified contacts' claim
- Data provenance scores sit at 1-2; we found no public information on where revealed contacts originate or on what legal basis the people in that database are processed
- Visitor identification scores span 2-4; we found no public information on a consent position or cookieless option for the tracking script, or on the legal basis for the asterisked contact-level identification
- Prospecting compliance scores span 1-3; we found no public information on suppression or do-not-contact lists, do-not-call register checks or cold-outreach guidance for EU markets
- The terms state 'All sales are final' with no refunds, and allow termination without cause or notice, which may result in the forfeiture and destruction of all information associated with you
Best for
- You want to see which companies visit your site, what they viewed and how often they return, with real-time Slack and email alerts
- You run HubSpot, Salesforce or Pipedrive and want identified companies and contacts syncing automatically, with REST API access included
- You want computable self-serve pricing with all features in every plan and unlimited team members, at up to 5,000 unique companies identified per month
- You want a European contracting counterparty in Snitcher B.V., the declared controller, under Dutch law and Dutch courts
Avoid if
- You cannot accept no-refund terms; the terms state 'All sales are final' and that termination without cause may result in the forfeiture and destruction of all information associated with you
- You expect to identify more than 5,000 unique companies per month, where the published tiers end at €529 for 4,001-5,000
- You plan to keep costs down by deleting identifications; the terms state that manually removing more than 50% of identifications per month results in charges or adjustments based on the applicable billing tier
- Your procurement excludes vendors whose privacy policy lists Stripe, Intercom and other parties as established outside the EU
The scores
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 — No stated coverage, no refresh cadence, no verification method; accuracy asserted as a percentage with nothing behind it.
3 — Headline record counts for the whole database, thin or unstated European coverage, and no description of how often records are re-verified.
5 — Coverage stated per country or region including DACH, email verification described, a stated refresh cadence, and firmographics beyond name and domain.
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
I measure a database by whether my SDRs can trust the records, and we found no public information on record counts, on how contacts are verified, or on any refresh cadence — "verified contacts" is asserted with nothing behind it. The feature list does promise contact enrichment, technographic data reveal and industry segmentation, which is the only firmographic substance on the pages. 1 2
The RevOps Manager
The pages advertise contact enrichment, technographic reveal and "verified contacts" with no coverage figures, no verification method and no refresh cadence behind the word verified — nothing a buyer can check from outside. We found no public information on record counts, DACH or EU coverage, or a bounce and credit-back guarantee. 1 2
The Data Protection Officer
The pages describe finding "verified contacts behind every visit" but give no database size, no coverage by country or region, and we found no public information on a verification method or refresh cadence for the contact data, nor on any credit-back rule when a contact proves wrong. Accuracy is asserted with nothing behind it. 1 2
The ABM Marketer
For someone who needs to know how many of my three hundred target accounts this would resolve, we found no public information on database coverage, verification method or refresh cadence — no record counts, no country or industry breakdown, no match rates. 'Verified contacts' appears in the marketing copy but the captured pages describe no methodology behind the word. 1 2
The DACH Sales Director
Plans are billed on unique companies identified per month and the feature list promises contact enrichment and technographic data, but I found no public information on coverage for Germany, Austria or Switzerland, on database size, on any verification method or on a refresh cadence. For a Mittelstand pipeline that runs on register-grade firmographics, I cannot tell from these pages how deep the company data actually goes. 1 2
The Skeptic
The marketing claims 'verified contacts', contact enrichment and technographic data, but I found no public information on how many records stand behind those words, how they are verified, or how often they are refreshed — no coverage figures, no per-country or per-data-type breakdown, and no bounce or credit-back guarantee. 'Verified' is asserted and left there. 1 2
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 — No statement of where contact data comes from or on what legal basis; "GDPR-compliant" asserted without explanation, and no way for a listed person to object.
3 — Sources described in general terms ("public sources", "partners"), legitimate interest named without any balancing, and an opt-out request form as the only route for data subjects.
5 — Source categories named (registers, company websites, contributory networks, licensed partners), legitimate interest stated as the basis for EU records, a dedicated privacy notice for 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
We found no public information on where the contact and enrichment data comes from or on what legal basis the people in it are processed; the privacy policy governs the vendor's own site and customer data, not the records my team would export. The only GDPR signals are a Dutch controller and a bare "GDPR compliance tools" feature line, with no legitimate-interest statement, no notice to listed people and no self-service removal route for them. 1 2 3
The RevOps Manager
The privacy policy governs people who visit Snitcher's own site — retention for contact forms, newsletter and statistics — and is silent on where the revealed contacts come from or on what legal basis. "GDPR compliance tools" appears as a feature name with no explanation, and we found no public information on a notice, an objection route or a removal process for the people in the identification database. 2 3
The Data Protection Officer
We found no public information on where the contact and enrichment data comes from or on what legal basis it is processed, and the "GDPR native" claim appears without explanation. The privacy policy does list data subject rights including objection, correction and deletion, but there is no notification practice for the people added to the database and no dedicated removal route for a listed person. 1 2 3
The ABM Marketer
We found no public information on where the revealed contacts and enrichment data come from or on what legal basis the people in the database are processed — no source categories, no legitimate-interest balancing, no notice to identified individuals. The privacy policy grants generic subject rights including objection, and the site claims GDPR-native operation, but neither documents the provenance of the contacts the product reveals. 1 3
The DACH Sales Director
The privacy policy describes retention for Snitcher's own newsletter, registration and contact-form data, but I found no public information on where the contacts behind the verified-contacts and contact-reveal promises come from, no legitimate-interest statement for those people, and no Art. 14 notice or self-service removal route for anyone in that database. The only opt-out documented on the pages is for the vendor's own newsletter. 2 3
The Skeptic
The privacy notice is written for Snitcher's own customers and website visitors — it names statistics and profiling partners like Mixpanel, Heap and Segment — but says nothing about where the contact data used for identification and enrichment originates or on what legal basis it is processed. 'GDPR compliance tools' appears as a feature label with no explanation, and I found no public information on an opt-out or objection route for the people whose companies and contacts get identified. 1 2 3
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, or person-level identification of EU visitors with no statement of legal basis.
3 — Reverse-IP company identification with a cookie-setting script, no statement about consent, and match rates claimed without method.
5 — Company-level identification with filters, visit history per company, a stated position that the script requires consent where it sets cookies, and a consent-mode or cookieless option.
8 — Company-level only for EU traffic by design, cookieless operation documented, integration with common consent management platforms, 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
Company-level identification is genuinely the core — tiers are billed on unique companies identified per month, with page views, visit frequency and live intent signals — but we found no public information on cookie or consent handling under the German telemedia rules and no consent-mode or cookieless option. Contact-level identification and the Identity Layer are sold as features with an asterisk the captured pages do not explain, and no legal basis for identifying persons is stated anywhere, which is exactly what my DPO would flag. 1 2
The RevOps Manager
Company identification is clearly the core: which companies visited, what they viewed and how often they return, with first-party intent signals and real-time Slack and email alerts. But "contact-level identification" carries an unexplained asterisk, and we found no public information on a consent position under the TDDDG, a consent mode or a cookieless option — for EU traffic that silence is the whole risk. 1 2
The Data Protection Officer
Company-level identification with visit history, intent signals and real-time Slack and email alerts is well documented, and contact-level identification is advertised. But we found no public information on consent under §25 TDDDG for the tracking script, on a consent-mode or cookieless option, or on the legal basis for identifying EU visitors at person level — for a controller-side review, that silence is the deciding fact. 1 2
The ABM Marketer
The core of my job is covered in the evidence: which companies are on my site, what they viewed, how often they return, plus real-time Slack and email alerts so the account owner hears about it while the signal is warm. But we found no public information on whether the tracking script requires consent, on cookieless or consent-mode operation, or on identification match rates — and contact-level identification is advertised with no stated legal basis. 1 2
The DACH Sales Director
As an engine this is the real thing: company identification, visit history and returning-visitor alerts, intent signals, and real-time Slack and email alerts. But the pricing page advertises contact-level identification and a user-identification Identity Layer while I found no public information on the legal basis for identifying persons, on whether the tracking script requires consent under §25 TDDDG, or on a cookieless or consent-mode option — exactly what my customers' DPOs ask first. 1 2 3
The Skeptic
Company-level identification, visit history, intent signals and real-time Slack and email alerts are documented, but the same pages advertise contact-level identification and user identification in an 'Identity Layer' while I found no public statement of the legal basis, no position on whether the tracking script needs consent, and no cookieless or consent-mode option. I found no public information on match rates or identification method either. 1 2 3
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 — A search box and an export button; nothing on the pages about what the buyer may lawfully do with the contacts.
3 — Filters on firmographics and job title, saved lists, and a terms clause making the customer solely responsible for compliance.
5 — Advanced filters including technographics and triggers, company-level lists and alerts, a global suppression or do-not-contact list, and guidance on cold outreach rules in the main EU markets.
8 — The above plus country-aware handling (for example flagging German contacts where cold calls and emails require consent), 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
Buyer persona filters, industry segmentation and a feed into outreach sequences exist, but we found no public information on suppression or do-not-contact lists, on country-aware flags for German contacts, or on any guidance for lawful cold outreach. The pages leave the legal risk entirely with the customer, with only an unexplained "GDPR compliance tools" line as cover. 1 2 4
The RevOps Manager
The path runs from persona filters and industry segmentation straight into sequences for "perfectly timed outreach", with nothing in between about what a buyer may lawfully send. We found no public information on a suppression or do-not-contact list, do-not-call register checks, country-aware flags, or guidance on cold outreach rules in any market. 1 2
The Data Protection Officer
Persona filters, industry segmentation, lead scoring and outreach integrations are described, but we found no public information on a global suppression or do-not-contact list, checks against national do-not-call registers, or guidance on cold outreach rules in the main EU markets. Once a list is exported, the buyer carries the entire legal risk alone. 1 2
The ABM Marketer
Persona filters, industry segmentation, technographics, trigger-based notifications and automated feeding of contacts into outreach sequences are all evidenced. But we found no public information on suppression or do-not-contact lists, do-not-call register checks, or guidance on cold outreach rules in the main EU markets — the legal risk of what I may do with a revealed contact stays entirely with me. 1 2 4
The DACH Sales Director
The homepage pitch feeds contacts straight into your sequences for perfectly timed outreach, yet I found no public information on a suppression or do-not-contact list, do-not-call register screening, or any country-aware guidance on German consent rules for cold calls and emails. Every gram of UWG §7 risk lands on my reps' desks with nothing on the captured pages to help them carry it. 1 2 4
The Skeptic
Contacts are fed 'straight into your sequences' with outreach integrations attached, yet I found no public information on suppression or do-not-contact lists, no guidance on cold outreach rules in any EU market, and no country-aware flags for German contacts. The captured terms govern payment and liability; I found no public information on the lawful use of revealed contacts on any of the pages. 1 2 4
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 — Manual CSV export only; no CRM integration and no API.
3 — A one-way push to one CRM, CSV export, and no statement on whether exported data may be kept after cancellation.
5 — Native sync with the major CRMs including field mapping and deduplication, enrichment of existing CRM records, and a documented API with stated limits.
8 — Bidirectional sync with scheduled re-enrichment, update and deletion propagated when a record changes or a person objects, webhook or API access with 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
CRM sync with HubSpot, Salesforce and Pipedrive plus REST API and SDK access are claimed, which is what my team needs, but we found no public information on field mapping, deduplication or API limits. On exit the terms let you run out the billing period with no refunds, we found no statement on keeping exported contacts after cancellation, and the vendor may terminate without cause with forfeiture and destruction of all information associated with you. 1 2 4
The RevOps Manager
Named sync to HubSpot, Salesforce and Pipedrive plus a REST API and marketing automation sync is more than a CSV push, but we found no public information on field mapping, deduplication, bidirectional updates or re-enrichment of existing records — I cannot tell whether a re-identified account creates a duplicate. The terms allow termination without cause or notice "which may result in the forfeiture and destruction of all information", with no statement on whether exported data may be kept after cancellation. 1 2 4
The Data Protection Officer
Sync with HubSpot, Salesforce and Pipedrive, a REST API and a data-only IP-to-company option are documented, and the terms state that what you store remains your property. We found no public information on field mapping, deduplication, or update and objection propagation; the terms also allow termination without cause "which may result in the forfeiture and destruction of all information associated with you", with nothing on what exported data may be kept after cancellation. 1 2 4
The ABM Marketer
HubSpot, Salesforce and Pipedrive sync plus REST API access and a data-only mode are evidenced, with contacts and intent feeding straight into the CRM. But we found no public information on field mapping, deduplication, re-enrichment or API limits, and the terms say termination without cause or notice 'may result in the forfeiture and destruction of all information associated with you' — no plain statement of what I keep after cancellation. 1 2 4
The DACH Sales Director
HubSpot, Salesforce and Pipedrive sync, a REST API with SDKs, GA4 enrichment and automatic lead routing are all evidenced, which is comfortably beyond a one-way CSV push. But I found no public information on field mapping, deduplication or API limits, and the terms say termination without cause "may result in the forfeiture and destruction of all information associated with you", with no statement of what a customer may keep once the subscription ends. 1 2 4
The Skeptic
Sync with HubSpot, Salesforce and Pipedrive, REST API access, and developer-first APIs and SDKs with a data-only embed are documented, but I found no public information on field mapping, deduplication, bidirectional updates or API limits. Exit terms cut against the buyer: no refunds with access only to the end of the billing period, and Snitcher may terminate 'without cause or notice, which may result in the forfeiture and destruction of all information associated with you'. 1 2 4
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 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and EU residents' contact data processed outside the EU with no stated transfer basis.
3 — Non-EU contracting entity with an EU representative under Art. 27, or EU hosting offered while enrichment, support or AI processing stay non-EU.
5 — EU contracting entity and EU hosting as standard, but parts of the chain — data partners, enrichment sources, tracking infrastructure — are non-EU without an explained safeguard.
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 controller is Snitcher B.V. in Hilversum under Dutch law and Dutch courts, and the privacy policy names its processors, which gives a real European footing. But we found no public information on where the data is hosted, several named processors — Stripe and Intercom among them — are established outside the EU with no transfer safeguard stated, and no data-processing agreement covering the records a customer exports is visible. 3 4
The RevOps Manager
Snitcher B.V. of Hilversum is the contracting entity, the declared controller and the Dutch-law counterparty, which is the right starting point. But hosting location is unstated, and the published subprocessor list names Stripe, Intercom, Facebook, Adroll, Mixpanel, Heap, Segment and others as established outside the EU with no named transfer safeguard. 3 4
The Data Protection Officer
The contracting entity, controller and Dutch address are Snitcher B.V., under Dutch law and Dutch courts, and the privacy policy names its subprocessors and flags that Stripe, Intercom, Facebook, Mixpanel, Heap and others are established outside the EU. We found no public information on where the service is hosted or on the legal basis for those non-EU transfers, so the location and safeguarding of the identified EU contacts' data remains open. 3 4
The ABM Marketer
Snitcher B.V. is the controller with a Hilversum address, Dutch law and Dutch courts, so the contracting chain starts European. But we found no public information on where data is hosted, and the privacy policy names US-headquartered processors — Stripe, Intercom, Facebook, Mixpanel, Segment and others — with no stated transfer safeguard or legal basis. 3 4
The DACH Sales Director
Snitcher B.V. of Hilversum, contracting under Dutch law before Dutch courts and named as controller, is the right shape for a dataset about EU residents. But I found no public information on where the data is hosted, and the privacy policy itself flags a list of non-EU parties including Stripe, Intercom and several US analytics and advertising tools, with no stated transfer safeguard or DPA terms on the captured pages. 3 4
The Skeptic
The contracting entity and controller are Snitcher B.V. of Hilversum under Dutch law and Dutch courts — genuinely European — but I found no public information on where the service or its visitor data is hosted, and the privacy notice itself states that Stripe and Intercom, used for payment and support, are established outside the EU. I found no public information on a data processing agreement, a transfer mechanism, or safeguards covering those parties. 3 4
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 monthly headline exists, but what a credit buys, whether credits expire, or the cost of an additional seat is unstated — the invoice is unknowable.
5 — Tier prices public with credit allowances given, but at least one commonly needed piece (mobile numbers, extra seats, API access, CRM sync) is unpriced or behind a sales call.
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
Best-evidenced part of the product: a full public tier table in euros from €49 for 0-50 identified companies to €529 for 4,001-5,000, billing clearly on unique companies identified per month, with all features in every plan, unlimited team members, REST API access and CRM sync included, a 14-day trial with no credit card, and stated no-refund and annual price-adjustment terms. The gaps: the annual option is given only as approximately 30% off monthly, we found no statement of VAT treatment or of the cost above 5,000 identified companies, and the terms state that manually removing more than 50% of identifications per month results in charges or tier adjustments. 2 4
The RevOps Manager
Ten published monthly tiers from €49 to €529 based on unique companies identified, all features in every plan, unlimited team members and API access included, and a 14-day trial without a card — more of the invoice is computable than in most of this category. What stops it short: no published tier above 5,000 identifications, VAT treatment unstated, all sales final with no refunds, and annual pricing given only as "Annual ~ 30% off Monthly", so the exact annual figure cannot be derived. 2 4
The Data Protection Officer
Ten monthly EUR tiers are published against one clear metric — unique companies identified per month — with all features in every plan, unlimited team members and API access included, a 14-day trial without credit card, and the annual saving given only as "Annual ~ 30% off Monthly". We found no public information on VAT treatment, the price beyond 5,000 identified companies a month, or what the asterisk on contact-level identification covers, and the terms say removals beyond half of monthly identifications can result in charges at the applicable billing tier. 2 4
The ABM Marketer
The core invoice is computable: ten public monthly EUR tiers from €49 to €529 by unique companies identified per month, all features in every plan including the API, CRM sync and unlimited team members, roughly 30% off billed annually, and a published no-refunds rule with a fourteen-day trial that needs no card. Still unpriced on the captured pages: anything above 5,000 identified companies, contact-reveal costs if separate, and VAT treatment. 2 4
The DACH Sales Director
This is genuinely computable pricing: euro tiers from €49 for 0-50 identified companies to €529 for 4,001-5,000, the billing unit spelled out as unique companies identified per month, all features in every plan, unlimited team members, REST API included, an annual discount stated at roughly 30 percent, and a 14-day trial with no credit card. What I still cannot compute: the cost above 5,000 identified companies and VAT treatment — and the terms rule out refunds outright, "All sales are final". 2 4
The Skeptic
The billing unit is unusually legible for this category: plans run from €49 for 0-50 unique companies identified per month to €529 for 4,001-5,000, with all features in every plan, unlimited team members, a 14-day free trial without credit card, and 'Annual ~ 30% off Monthly'. What a buyer still cannot compute: the price above 5,000 companies, any credit cost for contact reveals and enrichment, VAT treatment, and the meaning of the asterisk on contact-level identification — though the rule that manually removing more than 50% of identifications per month triggers charges is at least published. 2 4
European sovereignty — proven facts
1 of 4 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 NL ⚠ unverified | 3/3 pts | 3 Report an error |
|---|---|---|---|
| Ownership | Not determined | — | uncited Report an error |
| Data residency | Not determined ⚠ unverified | — | uncited Report an error |
| Subprocessors | Not determined ⚠ unverified | — | uncited Report an error |
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 — Legal entity. No commercial register is cited; NL is derived from the named Dutch supervisory authority together with the Dutch B.V. legal form and the Hilversum contact address, rather than an explicit incorporation statement.
- Weak sourcing — Data residency, Subprocessors. Not confirmed on the vendor’s own pages as captured.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 13 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 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
- 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 subprocessors fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 2 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown. Know more? Tell us
- 6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement. 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.snitcher.com Checked 22 Sep 2026 Details →
- 2 Pricing page www.snitcher.com Checked 22 Sep 2026 Details →
- 3 Privacy policy www.snitcher.com Checked 22 Sep 2026 Details →
- 4 Terms of service www.snitcher.com Checked 22 Sep 2026 Details →
- 5 Visitor identification & intent signals — found from sitemap www.snitcher.com Checked 1 Oct 2026 Details →
- 6 Visitor identification & intent signals — found from sitemap help.snitcher.com Checked 1 Oct 2026 Details →
- 7 Prospecting workflow & outreach rules — found from sitemap help.snitcher.com Checked 1 Oct 2026 Details →
- 8 Prospecting workflow & outreach rules — found from sitemap help.snitcher.com Checked 1 Oct 2026 Details →
- 9 CRM sync, enrichment & export — found from sitemap help.snitcher.com Checked 1 Oct 2026 Details →
- 10 CRM sync, enrichment & export — found from sitemap docs.snitcher.com Checked 1 Oct 2026 Details →