Lead Generation
Leadinfo
EU-Made Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Leadinfo B.V. · www.leadinfo.com
Compare with Dealfront → Compare with Albacross → 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.
No written verdict for this product
The panel scored Leadinfo, but the summary our synthesizer wrote did not survive our own contradiction check — twice. Rather than print a paragraph we cannot stand behind, we print none. Every score, rationale and source below is unaffected; read them and draw the conclusion yourself.
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
The headlines are big — 220 million companies, 300 million decision makers, 45 datapoints, 195 countries — but there is no country-level breakdown for DACH or anywhere else, and we found no public information on how records are verified, how often they are refreshed, or any credit-back when an email bounces. A count without a guarantee is just a count when my team is measured on connect rate. 1 2
The RevOps Manager
The marketing pages give headline counts — 220 million companies, more than 300 million decision makers, 195 countries, 45 datapoints — but I found no public information on per-country or DACH coverage, on verification, or on how often records are refreshed. Counts without a refresh cadence or accuracy terms are numbers I cannot stand behind once they land in my CRM. 1 2
The Data Protection Officer
The vendor publishes headline counts — 220 million companies, more than 300 million decision makers, 195 countries, 45 datapoints — with no breakdown by country or region and no verification method or refresh cadence behind them. I found no public information on accuracy guarantees or any credit-back for inaccurate records, so the accuracy claims rest on assertion. 1 2
The ABM Marketer
Headline counts — 220 million companies across 195 countries, 45 datapoints, over 300 million decision makers — but I work DACH accounts and the pages never break coverage down by country, let alone Germany, Austria or Switzerland. I found no public information on how records are verified or refreshed, and the "typically around 30% of your traffic" identification figure is claimed with no method behind it. 1 2
The DACH Sales Director
Headline counts of 220 million companies, 300 million decision makers and 195 countries, with European coverage undifferentiated and no figures for Germany, Austria or Switzerland. We found no public information on a refresh cadence, a verification method or credit-back terms, and the only accuracy-adjacent figure is the trial claim that around 30% of traffic is identified, given without method. 1 2
The Skeptic
Everything here is a homepage counter — 220M companies, a database with +300M decision makers, 195 countries, 45 datapoints — with no per-country or DACH breakdown, no verification method and no refresh cadence; the only method statement on the pages is an own database built on IP addresses for profiling visitors. We found no public information on how often records are re-verified, or any guarantee that makes inaccurate contact data the vendor's cost rather than the buyer's. 1 2 3
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
The privacy policy names the basis — own legitimate interest under Article 6(1)(f) — says only publicly accessible corporate data built from IP addresses is shared with users, and promises that an objection leads to deletion with no recollection. Sources stay in general terms though, and we found no public information on a balancing test, on notifying people when they are added, or on a self-service removal route. 2 3
The RevOps Manager
Legitimate interest under Article 6(1)(f) is named as the basis, the privacy notice lists data-subject rights including objection, and it states that an objecting person's data is deleted and not collected again — deletion with stopped recollection is the right behaviour. I found no public information on source categories beyond publicly accessible corporate data compiled from IP addresses, on any balancing test, or on informing people when they are added. 2 3
The Data Protection Officer
Legitimate interest under Article 6(1)(f) is named, the controller and processor roles are stated, and an objection leads to deletion with no further collection — a real route for people in the profiles, though only via a request answered within one month. The balancing behind the legitimate interest is not published, I found no public information on any Article 14 notification practice, and where the contact records come from is described only in general terms as publicly accessible corporate data. 2 3
The ABM Marketer
Legitimate interest under Article 6(1)(f) is named as the basis, IP addresses are not saved, only publicly accessible corporate data is shared, consumer IPs are dropped, and an objection leads to deletion with no recollection — a genuine story for data subjects. But sources are described only as "publicly accessible corporate data" in general terms, I found no published balancing test and no practice of informing people when they are added, and the opt-out runs through a privacy email address rather than a self-service route. 2 3
The DACH Sales Director
Legitimate interest under Article 6(1)(f) is named as the basis and the privacy policy is written to the people in the profiles, with an objection leading to deletion and no recollection. But the source picture stays at the level of an own IP-based database and publicly accessible corporate data, with no balancing test summarised and a request route answered within one month rather than self-service removal. 2 3
The Skeptic
The privacy notice names its basis — 'own legitimate interest' under Article 6(1)(f) GDPR — and admits only to an own IP-address database and 'publicly accessible corporate data', with no balancing test, no notification practice for the people added, and no word on where the +300M decision-maker records came from. Data subjects get the full rights catalogue, a one-month response window, and an objection that triggers deletion with no recollection — a real commitment, but request-based rather than self-service. 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
This is the core product and it is company-level by design: real-time identification with visited pages, LinkedIn profiles and financials, IP addresses not saved, and consumer IPs filtered out. The gap is the script's own legal footing — we found no public information on whether the tracking code needs consent under German rules or on a consent-mode or cookieless option, and recordings can run on cookies or browser/device fingerprinting. 1 2 3
The RevOps Manager
Identification is company-level by reverse IP with consumer-IP filtering, bot detection and per-company visit history, and the pages state that IP addresses are not saved. I found no public information on a consent position for the tracking script — the options described are cookies or browser/device fingerprinting — and the roughly 30% identification rate quoted for the trial is claimed without method. 2 3
The Data Protection Officer
Identification is company-level by design: consumer IP addresses are filtered out and not profiled, IP addresses are not saved, and profiles come from the vendor's own IP-based database. But the tool works with cookies or browser/device fingerprinting, and I found no public information on a stated consent position for the tracking script or a cookieless mode — exactly what I need to see before a tracker goes live on a site. 2 3
The ABM Marketer
Company-level identification in real time from their own IP-based database, with consumer IPs filtered out and the pages visited shown per company — exactly the shape I need for a named-account list, and IP addresses are not stored. But the captured pages take no position on consent where the script sets cookies or uses browser/device fingerprinting, the identification share is claimed without method, and I found no public information on a named third-party intent source. 1 2 3
The DACH Sales Director
Company-level reverse-IP identification with an own database, consumer IPs filtered out and IP addresses stated as not saved — good instincts. But the captured pages offer recordings via cookies or browser/device fingerprinting with no stated position on consent for the tracking script, and the 30% identification share is claimed without method, leaving the consent question to the customer, who is merely told to declare the processing in their own privacy statement. 1 2 3
The Skeptic
The core product is built the right way round: company profiles from an own IP database, suspected-consumer IPs removed without a profile being built, IP addresses not saved, and users see company details plus the pages visited in real time. What a DPO will ask for next is absent — no stated position that the tracking script requires consent, no consent-mode or cookieless option (recording via cookies or browser/device fingerprinting is offered as a plain choice), and the 'typically around 30% of your total traffic' match claim comes with no method. 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
There are persona filters by job title, automated lead scoring, bulk import tagging and automated LinkedIn and email outreach via Autopilot, but the legal risk lands on the customer: the terms only say use must not violate Dutch or other laws. We found no public information on a suppression or do-not-contact list, country-aware flags, or guidance on cold outreach rules in the main EU markets. 1 2 4
The RevOps Manager
There are persona filters by job title, automated lead scoring, and automated LinkedIn and email outreach in the Autopilot add-on, but the terms leave the law with the customer: no use violating Dutch or other applicable laws. I found no public information on a global suppression or do-not-contact list, on do-not-call register checks, or on country-specific cold outreach guidance. 1 2 4
The Data Protection Officer
Job-title filters and automated outreach across email and LinkedIn are offered, and the terms place the duty on the customer by prohibiting any use that violates Dutch or other applicable laws. I found no public information on a do-not-contact list, do-not-call register checks, or guidance on cold outreach rules in the main EU markets, so the legal risk of the list sits entirely with the buyer. 2 4
The ABM Marketer
The outreach tooling is there — automated LinkedIn requests, email, persona filters by job title — and the terms put the legal burden on me: use must not violate Dutch or other applicable laws and I must disclose Leadinfo in my own privacy statement and processing register. I found no public information on a do-not-contact or suppression list, on country-aware flagging of German contacts, or on guidance for cold outreach in the main EU markets. 2 4
The DACH Sales Director
The outreach machinery is there — persona filters on job title, automated LinkedIn requests and email via Autopilot, multichannel campaigns — while the terms simply forbid use that violates Dutch or other applicable laws, which leaves cold-call and cold-email consent under UWG §7 squarely on the customer's desk. We found no public information on suppression lists, country-aware flags or do-not-call checks, nor outreach guidance for the main EU markets. 1 2 4
The Skeptic
The outreach machinery is sold plainly — automated LinkedIn requests and email in the Autopilot add-on, persona filters on job title, multi-channel campaigns — while the only compliance text is a prohibition on uses that violate Dutch or other applicable laws and a duty on users to disclose the processing in their own privacy statements and processing register. We found no public information on a suppression or do-not-contact list, country-aware flagging of German or other contacts, or guidance on consent requirements for cold email and cold calls. 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
Sixty-seven free CRM integrations including HubSpot, Dynamics, Salesforce and Marketo with real-time sync, export through the service interface at any time, and terms that keep the customer's data their property — the basics of getting leads into the pipeline are covered. But the Starter plan is manual-only, and we found no public information on an API, field mapping, deduplication, enrichment of existing records, or what a customer may keep after cancelling beyond account data being deleted a month after the service ends. 2 3 4
The RevOps Manager
Sixty-seven CRM integrations with real-time sync covering HubSpot, Dynamics and Salesforce, export at any time through the service interface, and terms stating my data remains my property — the right skeleton, though the Starter plan sends insights to the CRM only manually. I found no public information on field mapping, deduplication, a documented API, re-enrichment behaviour, or which exported records I may keep after cancellation; account data is retained only one month past the end of the service. 2 3 4
The Data Protection Officer
Real-time sync with 67 CRM integrations and export through the service interface are documented, and the terms state that customer data remains the customer's property. I found no public information on field mapping, deduplication, a documented API, or how an objection to a record propagates after export — the moment my company becomes the controller over those people. 2 4
The ABM Marketer
Sixty-seven free CRM integrations including HubSpot, Salesforce, Dynamics and Marketo with real-time sync, bulk import for tagging, and the terms state my data remains my property with export available at any time through the service interface. I found no public information on an API, field mapping or deduplication, and the Starter plan only sends insights to the CRM manually. 2 4
The DACH Sales Director
Sixty-seven free CRM integrations with real-time sync, HubSpot, Dynamics, Salesforce and Marketo named, plus export through the service interface at any time — respectable breadth, though the Starter package is manual-only. We found no public information on an API, field mapping, deduplication or what the buyer may keep of exported contacts after cancellation; the terms say only that stored information remains the customer's property. 2 4
The Skeptic
The pipe exists: 67 free CRM integrations including HubSpot, Microsoft Dynamics, Salesforce and Marketo with real-time sync, bulk import for automatic tagging, an export right through the service interface at any time, and terms stating that stored information remains the customer's property. We found no public information on a documented API with rate limits, field mapping, deduplication, or how an objection to a contact propagates into already-synced records; Starter-plan users send insights to their CRM by hand. 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
Leadinfo is a Dutch company with a Chamber of Commerce registration, Dutch law, Dutch courts and a stated controller role — the right starting point for EU data. We found no public information on where the data is hosted, the subprocessor list, or the ownership chain beyond sharing with team.blue Group companies, and the policy confirms transfers outside the EEA on a generic "appropriate safeguards" basis. 3 4
The RevOps Manager
The contracting entity is Leadinfo B.V. in the Netherlands with a Chamber of Commerce number, Dutch governing law and Dutch courts, and group sharing sits within team.blue — a real European foundation. I found no public information on hosting location, on subprocessors or data partners, and while the privacy statement says data may be shared with parties outside the EEA only if appropriate safeguards are in place, I found no public information naming those safeguards or the recipients; the independently sourced sovereignty data could not confirm residency or subprocessors either. 3 4
The Data Protection Officer
The contracting entity is a Dutch company with a published Chamber of Commerce number, Dutch law and courts, and the Dutch supervisory authority named, so the entity and controller questions are answered. But the privacy policy itself says data may be shared with parties outside the EEA under safeguards that are asserted rather than named, and I found no public information on hosting location or a published subprocessor list, including the scope of the team.blue group sharing. 3 4
The ABM Marketer
Leadinfo B.V. is the contracting entity in the Netherlands with a Chamber of Commerce number, Dutch law and the Dutch courts — but the captured pages say nothing about where the data is hosted and name no subprocessors, while acknowledging transfers outside the EEA under "appropriate safeguards" that are never specified. Personal data is also shared with team.blue Group companies for marketing statistics and reporting. 3 4
The DACH Sales Director
A Dutch B.V. with a Chamber of Commerce number, Dutch law, Dutch courts and the Dutch Personal Data Authority as complaint route — the contracting side is genuinely European. But hosting location is unstated, no subprocessor list is published, personal data is shared among team.blue Group companies, and transfers outside the EEA are confirmed with safeguards asserted only in general terms; the independently sourced attributes could not confirm residency or subprocessor exposure. 3 4
The Skeptic
The contracting entity is verifiably European — Leadinfo B.V. in Capelle aan den IJssel with its Chamber of Commerce number, Dutch governing law, Dutch courts and the Dutch Personal Data Authority for complaints — but the trail ends there: hosting location unstated, no subprocessor list, and a privacy policy that shares personal data with parties outside the EEA 'if appropriate safeguards are in place' without naming a single recipient or instrument. Group-wide sharing with team.blue Group companies and Google Ads conversion tracking round out the disclosed chain; we found no public information on where the visitor database itself is hosted. 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
The Starter price is public in annual and monthly form, seat counts per plan are stated, add-ons carry explicit prices, and the billing unit is honest — identified unique companies, repeat visits counted once, ISPs excluded, extra leads hidden rather than billed. The captured pages show only one tier's price, and we found no public information on extra-seat costs or VAT treatment, so the full-year invoice for a growing team is still a sales conversation. 2 4
The RevOps Manager
The Starter tier is public at € 69 billed annually and € 99 monthly for the smallest lead range, add-ons carry public starting prices (Autopilot from € 39/seat, Leadbot Business from € 59 /seat, Liquid content from € 39 /mo), and seat counts per plan are stated. What I still cannot compute is the invoice: higher lead-volume pricing, the cost of additional seats and VAT treatment, and the terms say a payment cannot be refunded. 2 4
The Data Protection Officer
A public package price exists — 'Starter € 69 € 99' — with add-ons priced per seat, seat counts per package, and billing, refund and termination terms stated plainly. I found no public information on the cost of an additional seat or VAT treatment, and the published material shows one package price, so a full annual invoice for a given team cannot be computed from it. 2 4
The ABM Marketer
The Starter tier is public at € 99 monthly or € 69 on annual billing for a 0–50 identified-company band, with seat counts per package, per-seat add-ons priced (Autopilot at € 39 per seat, Leadbot Business at € 59 per seat), repeat visits from one company counted once, ISPs excluded, and stated over-limit behaviour. The captured pages show only the Starter price — I found no public information there on the higher tiers' prices or on VAT treatment. 2 4
The DACH Sales Director
The Starter package is priced publicly at € 69 annually and € 99 monthly with a lead allowance, seats per package and add-ons like Autopilot at € 39/seat and Leadbot Business at € 59/seat, and billing by identified companies with ISPs and repeat visits excluded is a unit a Mittelstand buyer can grasp. But the captured pages give no price for the higher packages, no overage rate once the lead limit is hit (leads are still collected but not visible), and nothing on rollover or VAT treatment, so the full invoice is not computable from what is public. 2 4
The Skeptic
The billing unit is unusually legible for this category — unique companies per month, repeat visits from the same company counted once, ISP traffic excluded, leads past the limit still collected but hidden — and the Starter tier is published as '€ 69' billed annual against '€ 99' monthly for the 0–50 tier, with seats per tier (3, 10, unlimited), per-seat add-ons ('€ 39/seat', '€ 59 /seat') and termination terms stated. We found no public information on the prices of the Pro and Scale tiers, the cost of extra seats beyond the bundle, or VAT treatment, so a growing team's annual invoice cannot be computed from the public pages. 2 4
European sovereignty — proven facts
0 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 | Not determined | — | uncited 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 — 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.
- 18 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
- 5 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 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 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
- The panel’s written verdict is withheld: our own re-read found claims in it that the evidence does not carry, and a second synthesis did not fix them. The scores and the material below are unaffected. Know more? Tell us
Sources (12)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.leadinfo.com Checked 22 Sep 2026 Details →
- 2 Pricing page www.leadinfo.com Checked 22 Sep 2026 Details →
- 3 Privacy policy www.leadinfo.com Checked 22 Sep 2026 Details →
- 4 Terms of service www.leadinfo.com Checked 22 Sep 2026 Details →
- 5 Security / trust page www.leadinfo.com Checked 30 Sep 2026 Details →
- 6 Legal notice www.leadinfo.com Checked 30 Sep 2026 Details →
- 7 Visitor identification & intent signals — found from sitemap help.leadinfo.com Checked 1 Oct 2026 Details →
- 8 Visitor identification & intent signals — found from sitemap help.leadinfo.com Checked 1 Oct 2026 Details →
- 9 Prospecting workflow & outreach rules — found from sitemap help.leadinfo.com Checked 1 Oct 2026 Details →
- 10 Prospecting workflow & outreach rules — found from sitemap www.leadinfo.com Checked 1 Oct 2026 Details →
- 11 CRM sync, enrichment & export — found from sitemap help.leadinfo.com Checked 1 Oct 2026 Details →
- 12 CRM sync, enrichment & export — found from sitemap help.leadinfo.com Checked 1 Oct 2026 Details →