Vainu
EU-Made Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 2 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Vainu.io Software Oy · www.vainu.com
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.
Vainu at a glance
- Vendor
- Vainu.io Software Oy
- Headquarters
- Not stated on the vendor’s pages as of 16 Nov 2026
- Data hosting
- In the EU source, captured 16 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 16 Nov 2026
- Panel verdict
- The AI panel rates Vainu 2.5/5, the mean of 6 judges. Vainu is a Nordic company-data platform from Vainu.io Software Oy of Helsinki. how scores are made
- As of
- Vendor pages captured 22 Sep 2026 to 16 Nov 2026; evaluated by the panel 18 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Vainu is a Nordic company-data platform from Vainu.io Software Oy of Helsinki. The judges score it highest on data coverage and CRM sync and export, both 6–7: per-country counts are published for Denmark, Finland, Norway and Sweden, data comes from named national registers and is re-checked daily, and native connectors to HubSpot, Salesforce, Pipedrive, Dynamics 365 Sales and Superoffice offer per-field update rules with an hourly recheck of CRM records. Weakest is visitor identification at 0–2, where we found no public information on identifying companies behind website visits; the closest documented capability is 72 company-change event types delivered as CRM tasks or Slack notifications. Prospecting compliance is level at 4: customers become data controllers on export. Scores spread on pricing transparency, 4–6: starting prices are public ('Starting at 3,500€/ year +200€ / one-time onboarding fee' for Prospecting), yet extra countries, seats and connectors are priced on a call, so the real annual invoice is not computable from the public pages. The captured pages also give different statements on where data is held.
Speaks for it
- Per-country coverage is published — Denmark 862k, Finland 1.3m, Norway 1.1m and Sweden 1.9m companies — refreshed daily and drawn first-hand from the national registers PRH, Bolagsverket, Brønnøysundregistrene and Erhvervsstyrelsen.
- Decision-makers in Finland and Sweden are manually reviewed on roughly a six-month cycle, with derived email addresses verified before storage.
- Every personal-data record is linked to the source it was acquired from and updated or removed when the source changes, with erasure and objection rights for people in the database.
- Native connectors to HubSpot, Salesforce, Pipedrive, Dynamics 365 Sales and Superoffice offer per-field update rules, reversible updates and an hourly recheck of every CRM record.
- A documented REST API provides change tracking, JSONL streaming, SFTP export and webhooks alongside file export.
Held against it
- We found no public information on identifying the companies behind website visits — the documented signals are 72 company-change event types, not visit identification.
- Customers become data controllers on export, and we found no public information on suppression lists, do-not-call register checks or guidance on EU cold-outreach rules.
- Extra countries, seats and connectors are priced on the same 30-minute demo call and the Data product carries customized pricing, so the real annual invoice is not computable from public pages.
- The captured pages give different statements on where data is held — one page says the data never leaves the EU while both privacy statements say it may be transferred to and stored outside the EEA — and we found no public information on a subprocessor list beyond the named AWS and MongoDB.
- Documented coverage is Nordic-only with no public information on Germany, Austria or Switzerland, and the captured pages give different figures for total contacts (9M+ and 10.5M+).
Best for
- You sell into Nordic markets and want register-sourced company data with published per-country counts and a daily refresh.
- Your team runs HubSpot, Salesforce, Pipedrive, Dynamics 365 Sales or Superoffice and wants enrichment that updates existing records hourly under per-field rules.
- You want change-based timing signals — 72 event types such as funding rounds and key hires — arriving as CRM tasks or Slack notifications.
- You want a Finnish controller with a named Data Privacy Officer and hosting stated as AWS in Ireland and MongoDB in Ireland.
Avoid if
- You need to know which companies visited your website — the documented signals are company-change events rather than website-visit identification.
- Your pipeline depends on coverage of Germany, Austria or Switzerland — documented coverage is Nordic-only.
- You need a fully computable annual price before a sales conversation — extra countries, seats and connectors are priced on the call, the Data product is customized, and the subscription auto-renews for 12 months with 60 days' notice.
- You expect the vendor to carry outreach compliance — customers become data controllers the moment they export, and we found no public information on suppression or do-not-call checks.
The scores
| Criterion | Panel median |
|---|---|
| Coverage, accuracy & freshness | 3.5 of 5 |
| Data sources & lawful basis | 3 of 5 |
| Visitor identification & intent signals | 1 of 5 |
| Prospecting workflow & outreach rules | 2 of 5 |
| CRM sync, enrichment & export | 3.5 of 5 |
| European sovereignty | 3 of 5 |
| Pricing transparency | 2.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
Counts are published per country — Denmark 862k, Finland 1.3m, Norway 1.1m, Sweden 1.9m — with a daily refresh and the official registers behind the data named, which is exactly the documentation I want under a headline number. Contact quality gets real treatment: decision-makers in Finland and Sweden are manually reviewed on a roughly six-month cycle and inferred emails are verified before storage, though the contact fields documented are work phone and work email, with no split by direct dial or mobile, no industry breakdown and no bounce or credit-back guarantee. The captured pages also give different figures for total contacts — 9+ million on one homepage capture, 10.5+ million on another. 2 7 4 1 1
The RevOps Manager
The Nordic database is documented at 5.1M+ companies with per-country counts for Denmark, Finland, Norway and Sweden, drawn first-hand from official registers such as PRH, Bolagsverket, Brønnøysundregistrene and Erhvervsstyrelsen, refreshed daily, with 550+ firmographic and financial fields and a manual review cycle for decision-makers in Finland and Sweden. The captured pages give different figures for contacts — 9M+ on the homepage, 10.5M+ on the data pages — and derived email addresses are verified before they are stored. We found no public information on coverage of Germany, Austria or Switzerland, on any bounce or credit-back guarantee, or on a last-verified date per field visible to the user. 1 2 7 4
The Data Protection Officer
Coverage is published per country for the Nordics — Denmark 862k, Finland 1.3m, Norway 1.1m and Sweden 1.9m companies, with 5.1M+ companies and 10.5M+ contacts overall — drawn first-hand from the named national registers (PRH, Bolagsverket, Brønnøysundregistrene, Erhvervsstyrelsen) and re-checked every day. A research team manually reviews decision-makers in Finland and Sweden on roughly a six-month cycle, and derived email addresses are verified before storage, with every field value traceable back to its register. We found no public information on coverage broken down by industry or data type, or on a bounce or credit-back guarantee, which is what holds this below the top of the scale. 2 7 4 1
The ABM Marketer
Coverage is stated per Nordic country — Denmark 862k, Finland 1.3m, Norway 1.1m and Sweden 1.9m companies, 10.5M+ contacts — drawn first-hand from the national registers (PRH, Bolagsverket, Brønnøysundregistrene, Erhvervsstyrelsen) and re-checked every day, with a research team manually reviewing decision-makers in Finland and Sweden on roughly a six-month cycle and verification applied to derived email addresses. That register sourcing and refresh discipline is real, but we found no public information on coverage broken down by industry or by data type (email versus direct dial versus mobile), on per-country accuracy methodology, or on any bounce or credit-back guarantee — and the documented scope is Nordic, so my DACH accounts sit outside it. 2 1 7 4
The DACH Sales Director
Coverage is documented per country — Denmark 862k, Finland 1.3m, Norway 1.1m, Sweden 1.9m companies, refreshed every day and drawn first-hand from PRH, Bolagsverket, Brønnøysundregistrene and Erhvervsstyrelsen, with a research team manually reviewing decision-makers in Finland and Sweden on a roughly six-month cycle, which is the register-based approach I want to see. The covered market is Nordic only — I found no public information on Germany, Austria or Switzerland, and the Global option for the data product carries no breakdown — and there is no industry or data-type split (email versus direct dial versus mobile) and no bounce or credit-back guarantee stated. 2 7 1
The Skeptic
The bones here are real: per-country counts for four Nordic markets, 5.1M+ companies and 10.5M+ contacts, registry changes re-checked every day, decision-makers in Finland and Sweden manually reviewed on roughly a six-month cycle, and company data drawn from named national registers with every value pointing back to the register it came from. What I could not find: a coverage split by industry or by data type such as direct dial versus mobile, a last-verified date visible to the user, or any bounce or credit-back rule that makes inaccuracy the vendor's cost. 2 1 7 4
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
Source categories are named — patent and registration offices, public officials, company websites, press releases — legitimate interest is stated as the legal basis, and every personal data record is linked to the source it came from, updating or disappearing shortly after the source does. A database privacy statement spells out rights for the people in it, including erasure and objection to direct marketing, with a named email route for requests. I found no public information on an Art. 14 notification practice, a published balancing test, or a self-service removal tool — requests go to privacy@vainu.io. 4 4 3
The RevOps Manager
Sources are named concretely — national patent and registration offices, public officials, company websites and press releases — and every personal data record is linked to the source it was acquired from, with records updated or removed when that source changes. Legitimate interest is stated as the basis, a database privacy statement addresses the people in the records with access, rectification, erasure and objection rights, and even the derivation of work emails from name and domain is disclosed with verification before storage. We found no public information on an Article 14 notification practice, a published balancing test, or a per-record collection date. 4 4 7 4
The Data Protection Officer
The database privacy statement names legitimate interest as the legal basis, lists registers, public officials, company websites and press releases as sources, links every personal-data record to the source it was acquired from, and gives people in the database a named Data Privacy Officer plus rights of access, rectification, erasure, objection and portability via privacy@vainu.io. The scope is tight — only publicly available data tied to a person's role in the company, date of birth only for registered representatives, and no automated decision-making or profiling. We found no public information on an Article 14 notification practice for people added to the database, a published balancing test for the legitimate interest, or a self-service removal route, since requests run by email. 4 4 4 7
The ABM Marketer
Source categories are named — national patent and registration offices, public officials, company websites, press releases — every personal-data record is linked to the source it came from and removed when the source removes it, the stated basis is legitimate interest in accordance with EU law, and a dedicated database privacy statement gives people access, rectification, erasure and objection rights via privacy@vainu.io. We found no public information on an Article 14 notification practice for people added to the database, a published legitimate-interest assessment, or a self-service removal process beyond email requests, which keeps this below the higher marks. 3 4 4 4
The DACH Sales Director
Sources are named as patent and registration offices, public officials, company websites and press releases, legitimate interest is stated as the basis for the processing, every personal-data record is linked to the source it came from, and a database privacy statement addressed to the people in the register grants erasure and objection rights. I found no public information on an Art. 14 notification practice or a published legitimate-interest assessment, and the documented removal route is a request to privacy@vainu.io rather than a self-service process. 4 4 4 3
The Skeptic
The database privacy statement names its source categories — patent and registration offices, public officials, company websites, press releases — links every record to the source it was acquired from, states legitimate interest as the basis, limits itself to publicly available data tied to a company role, and gives people access, rectification, erasure and objection rights plus a public search engine to find themselves. We found no public information on an Art. 14 notification practice, a published balancing test, or EU records being handled differently from US records, and removal runs by email request rather than a self-service process. 3 4 7 4
Visitor identification & intent signals
n/r
n/r
n/r
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 not rated — no public information
I found no public information on identifying the companies behind website visits or on a tracking script for buyer intent in the pages I read — homepage, pricing, the data page and both privacy statements. What those pages do describe is company-change event data, such as funding rounds and key hires, which is a different kind of signal. 1 6 7
The RevOps Manager
We found no public information on identifying companies behind website visits, a tracking script, or a consent position for one — Vainu's own cookie notice covers its website's cookies, and nothing on the pages describes reading customer site traffic. What the pages do show are buying signals from public company changes — a funding round, a key hire, one of 72 event types — delivered as CRM tasks or Slack notifications rather than as website-visit identification. 1 3 6
The Data Protection Officer not rated — no public information
We found no public information on identifying the companies behind website visits, on intent topics, or on any stated consent position for a tracking script. The pages we read — the homepage, pricing and the data page — describe register-based company data and event triggers such as funding rounds and key hires, not website-visit tracking, so this dimension stays open rather than credited. 1 2 7
The ABM Marketer
This is the gap for my use case: we found no public information on identifying the companies behind my website visits — no reverse-IP capability, no consent-mode option or TDDDG position for a tracking script, and no third-party intent source named anywhere on the captured pages. The closest capability is trigger-based alerting — 72 event types such as funding rounds and key hires landing as a CRM task or a Slack notification on a schedule I set — which warms accounts but never tells me who actually visited. 1 3 6
The DACH Sales Director
The captured pages document change-based timing signals — event data with 72 event types such as funding rounds and key hires, delivered as CRM tasks or Slack notifications — but I found no public information on identifying the companies behind website visits, on any tracking script, or on the vendor's position on consent for one. 1 6
The Skeptic not rated — no public information
We found no public information on identifying the companies behind website visits, a tracking script, consent-mode behaviour under §25 TDDDG, or third-party intent data — the captured pages describe register- and crawl-based company data, change-event alerts and CRM connectors, and the cookie notice covers only anonymous statistics on visits to Vainu's own website. 1 2 3 7
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
Search and triggers are the strong part: financial, group-structure, social-media and event filters, alerts when a new company matches your criteria, 72 event types like funding rounds and key hires delivered as CRM tasks or Slack notifications, and export by file, SFTP or API. What I miss as the person whose team sends the emails: I found no public information on a suppression or do-not-contact list, on country-aware flagging of contacts where cold outreach requires consent, or on guidance for EU cold-outreach rules — and the pages do say customers become data controllers of what they export, so the legal risk lands with the buyer. 2 6 1 5
The RevOps Manager
Search carries deep filters — financials, group structures, technologies, events — plus alerts when a new company matches your criteria and export of companies to Excel, SFTP or the API. We found no public information on a suppression or do-not-contact list, on country-aware flags for German contacts or do-not-call register checks, or on cold-outreach guidance for EU contacts. The database privacy statement instead hands controller status to the customer the moment data is exported, so the legal risk sits entirely on the buyer. 1 2 6 4
The Data Protection Officer
Search and list building are real and strong: advanced financial, group-structure, social-media and event filtering, alerts when a new company matches saved criteria, 72 event types delivered as CRM tasks or Slack notifications, and export of companies and contacts. But the legal weight is squarely on the buyer — the privacy statements say customers become data controllers the moment they export, with the customer's own privacy notice then applying. We found no public information on a do-not-contact or suppression list, checks against national do-not-call registers, or guidance on cold-outreach rules for EU contacts. 2 6 4 4
The ABM Marketer
Search and list building are deep — financial, group-structure, social-media and event-data filters across 550+ data points, alerts whenever a new company matches my criteria, and export to Excel or download of companies. But we found no public information on a suppression or do-not-contact list, on per-country flags for contacts whose outreach requires consent, or on do-not-call register checks — and on export the customer becomes the data controller, so the outreach compliance risk lands squarely with me. 1 2 4
The DACH Sales Director
The filters go deep — financials, group structures, technologies, vehicle and event triggers — with alerts when a new company matches the criteria, and contacts and companies export cleanly, but the only compliance statement I found is that the customer becomes the data controller on export, which shifts the legal risk to the buyer. I found no public information on a suppression or do-not-contact list or on any guidance for consent rules in cold outreach, so my team would carry the UWG §7 question entirely alone. 2 1 4 6
The Skeptic
Search with financial, group-structure, social media, technographic and event-data filters, alerts when a new company matches, and export of companies and contacts are all documented. We found no public information on a suppression or do-not-contact list, checks against national do-not-call registers, or guidance on GDPR and cold-outreach rules — and on export the customer is expressly told they become the controller for the data, which puts the outreach risk squarely on the buyer. 1 2 4 6
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
Native connectors to HubSpot, Salesforce, Pipedrive, Dynamics and Superoffice, per-field update rules that are reversible on request, and an hourly recheck of every CRM record is strong data hygiene, and the API is documented with search, enrichment, change tracking, streaming and webhooks alongside SFTP and file export. Customers become controllers of the data they export. I found no public information on access and exported data after cancellation, on propagating an objection or deletion into synced records, or on stated API limits and per-call costs. 6 6 5 2 4
The RevOps Manager
Native connectors for HubSpot, Salesforce, Pipedrive, Dynamics and Superoffice map straight into existing fields, company and contact records are re-enriched with per-field rules (fill only when empty, always overwrite, only on a new account), updates are reversible on request, and every CRM record is rechecked hourly — this is enrichment that updates rather than duplicates, exactly what I want to see. Change webhooks and a REST API with change tracking, JSONL streaming and async jobs round it out. We found no public information on API rate limits and per-call costs, on objections or deletions propagating into synced CRM records, or on what data a customer may keep after cancellation — and with a 12-month auto-renewing subscription needing 60 days' notice, exit terms matter. 2 6 6 5
The Data Protection Officer
Native connectors to HubSpot, Salesforce, Pipedrive, Dynamics 365 Sales and Superoffice with per-field update rules (fill only when empty, always overwrite, only on new account), hourly re-checks of matched records, reversible updates, webhooks, SFTP export and a documented REST API with streaming and change tracking. We found no public information on stated API limits or per-call costs, on propagation of deletions or objections into synced records, or on what data the customer may keep after cancellation — only a twelve-month auto-renewing subscription with sixty days' notice. 6 6 2 5
The ABM Marketer
The sync story fits my workflow well: native connectors to HubSpot, Salesforce, Pipedrive, Dynamics 365 Sales and Superoffice, per-field rules (fill only when empty, always overwrite, only on a new account) with updates reversible on request, hourly rechecks of my CRM accounts, change webhooks, and a REST API that streams the whole matching set as JSONL alongside SFTP export. We found no public information on deletion propagating into the CRM when a person objects, on stated API limits, or on what happens to my data and access when the subscription ends. 2 5 6 6
The DACH Sales Director
Native connectors to HubSpot, Salesforce, Pipedrive, Dynamics 365 Sales and Superoffice come with per-field update rules (fill only when empty, always overwrite, only on a new account) and an hourly recheck of every CRM record, and a REST API with change tracking, JSONL streaming, webhooks, SFTP and file export covers delivery well beyond a plain push. I found no public information on stated API limits or per-call costs, and nothing on which data the customer may keep after cancellation. 6 6 5 5 2
The Skeptic
Native connectors to HubSpot, Salesforce, Pipedrive, Dynamics 365 Sales and Superoffice with per-field update rules (fill only when empty, always overwrite, only on a new account), an hourly recheck of CRM records, and a REST API with change tracking, JSONL streaming, SFTP export and webhooks make this a credible sync-and-enrichment story. We found no public information on deletions propagating into synced records when a person objects, on API rate limits or per-call costs, or on what happens to the buyer's data and access once the subscription ends. 2 5 6 5
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 controller are Finnish — Vainu.io Software Oy, Helsinki, with a named data privacy officer and the Finnish Data Protection Ombudsman as supervisory authority — and hosting is stated as AWS in Ireland with MongoDB in Ireland, audited under SOC 2. The captured pages give different positions on storage location: the data and trust page says the data never leaves the EU, while both privacy statements say data may be transferred to and stored outside the EEA under safeguards such as standard contractual clauses. I found no published subprocessor list beyond the two named infrastructure providers. 7 4 3
The RevOps Manager
The controller is Vainu.io Software Oy in Helsinki with a named Data Privacy Officer, compute runs on AWS in Ireland and storage on MongoDB in Ireland, and data protection agreements and standard contractual clauses are offered. The captured pages give different positions on transfers: the data and trust page says the data never leaves the EU, while both privacy statements say data may be transferred to and stored outside the EEA under safeguards such as standard contractual clauses and adequacy decisions. Beyond the two named hosting providers we found no public information on a full subprocessor or data-partner list. 4 3 7 4
The Data Protection Officer
The controller is Vainu.io Software Oy of Helsinki, compute runs on AWS in Ireland and storage on MongoDB in Ireland, and data protection agreements or EU standard contractual clauses are offered. The captured pages give different statements on where data is held: the trust page says the data never leaves the EU, while both privacy statements say data may be transferred to and stored outside the EEA under those contractual clauses. We found no public information on a full subprocessor list beyond AWS and MongoDB named with their roles, or on named transfer destinations, so the end-to-end claim cannot be taken further. 4 7 3 4
The ABM Marketer
Vainu.io Software Oy in Helsinki is the named controller with a Data Privacy Officer, hosting runs on named EU infrastructure — AWS in Ireland for compute, MongoDB in Ireland for storage — and any transfers are covered by standard contractual clauses, adequacy decisions or data protection agreements. The captured pages give different figures on where data can sit, though: the Data & Trust page says the data never leaves the EU while the privacy statements say it may be transferred to and stored outside the EEA, and we found no public information on a full subprocessor list beyond the two named providers. 3 3 7 4
The DACH Sales Director
The controller and contracting entity are Vainu.io Software Oy in Helsinki with a named data privacy officer, and hosting is named publicly as AWS in Ireland with storage on MongoDB in Ireland, backed by SOC 2 and a trust centre with live control status. The captured pages give different statements on residency — one page says the data never leaves the EU while both privacy statements say data may be transferred to and stored at destinations outside the EEA under standard contractual clauses — and I found no public information on a subprocessor list. 7 4 3
The Skeptic
A Finnish controller with a named Data Privacy Officer, and hosting named publicly on AWS in Ireland and MongoDB in Ireland with encryption at rest and SOC 2 audit. But the captured pages give different figures on residency — the trust page says the data never leaves the EU while both privacy statements say it may be transferred to and stored at a destination outside the EEA, with standard contractual clauses and adequacy decisions as safeguards — and we found no published subprocessor list beyond the two infrastructure providers. 3 3 7 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 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
Two of three products carry public starting prices — Prospecting starting at 3,500€/year with a 200€ one-time onboarding fee, CRM starting at 4,200€/year with 750€ — plus Premium at +83€ and Full at +167€ per month, monthly prices on an annual licence excluding VAT, and a 12-month auto-renewing term with 60 days' notice. What a licence includes is stated: one country database, one to two seats, triggers and the Basic data package. The third product is "customized pricing for large data volumes", extra countries, seats and connectors are priced on a sales call, and the pricing page says "We confirm your price on the call" — so the real annual invoice is not computable from public pages. 2 2
The RevOps Manager
Two of three products carry public starting prices — Vainu for CRM starting at 4,200€/year plus a 750€ one-time onboarding fee and Vainu for Prospecting starting at 3,500€/year plus 200€ — with add-ons priced at +83 € per month for Premium and +167 € per month for Full, each licence including one country database, one to two seats and triggers, on monthly prices on an annual licence, excluding VAT. Vainu for Data is customized pricing for large data volumes, and extra countries, seats and connectors are priced on the same call, with the price confirmed on a 30-minute call. A buyer therefore cannot compute the real annual invoice from the public pages alone. 2 2
The Data Protection Officer
Public prices exist for two of the three products — "Starting at 3,500€/ year" plus a 200€ one-time onboarding fee for Prospecting and "Starting at 4,200€/ year" plus 750€ for CRM — with a twelve-month auto-renewing subscription, data packages priced as monthly add-ons (+83 € for Premium, +167 € for Full), one country database and one to two seats per licence, and VAT stated as excluded. The Data product carries customized pricing, and seats, extra countries and connectors are priced on a demo call where the price is confirmed; we found no public information on per-contact or per-data-type unit costs, so the annual invoice is not computable from public pages alone. 2 2
The ABM Marketer
Public prices exist for two of the three products — Vainu for Prospecting "Starting at 3,500€/ year" with a "+200€" one-time onboarding fee and Vainu for CRM "Starting at 4,200€/ year" with "+750€" — plus the Premium add-on at "+83 € per month" and Full at "+167 € per month", monthly prices on an annual licence excluding VAT, a 12-month auto-renewing term and 60-day cancellation notice. But Vainu for Data is "Customized pricing for large data volumes", extra countries, seats and connectors are priced on a call, and the vendor confirms the actual price on that call — so the real annual invoice is not computable from public pages alone. 2 2
The DACH Sales Director
Both main products carry public starting prices — Vainu for Prospecting at 3,500€/ year plus a 200€ one-time onboarding fee and Vainu for CRM at 4,200€/ year plus 750€ — with the Premium and Full add-ons at +83 € and +167 € per month on an annual licence excluding VAT, and every licence includes one country database, one to two seats and triggers. Extra countries, seats and connectors are priced on the same call and the data product is customized, so the real annual cost still ends in a 30-minute demo call rather than on the page. 2 2
The Skeptic
Two "starting at" prices are public — "Starting at 3,500€/ year +200€ / one-time onboarding fee" for prospecting and "Starting at 4,200€/ year +750€ / one-time onboarding fee" for CRM — with data add-ons at "+83 € per month" and "+167 € per month", "Monthly prices on an annual licence, excluding VAT", and a 12-month auto-renewing term with 60 days' notice. But extra countries, seats and connectors are priced on a call, the price is confirmed on that call, and the Data product is customized pricing for large volumes — so the real annual invoice for a given team is not computable from the public pages. 2 2
European sovereignty — proven facts
2 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity |
Not determined
unverified
Why unverified?Not confirmed on the vendor’s own pages as captured. |
— | uncited Report an error |
|---|---|---|---|
| Hosting location |
EU only
unverified
Why unverified?Both the privacy policy (S3) and the database privacy statement (S5) say data "may be transferred to, and stored at, a destination outside the European Economic Area", contradicting this Data & Trust page's claim. |
4/4 pts | 7 Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined | — | uncited Report an error |
| Transfer impact assessment |
Not needed, no transfer outside the EU/EEA
unverified
Why unverified?Both privacy statements nonetheless state that data may be transferred to and stored at destinations outside the EEA, contradicting the page's EU-only claim. |
1/1 pts | 7 Report an error |
Questions about Vainu
Is Vainu European?
Yes. whats-best.ai classifies Vainu as EU-Made.
Where does Vainu store data?
Vainu stores customer data in the EU, per the vendor’s page captured 16 Nov 2026.
Does Vainu have a free plan?
Not stated on the vendor’s pages as of 16 Nov 2026.
What are the best alternatives to Vainu?
As of 18 Nov 2026, the panel rates Dealfront (3/5), Lusha (2.5/5) and Apollo.io (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: Vainu alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 22 Sep 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Transfer impact assessment.
- Weak sourcing — Legal entity. Not confirmed on the vendor’s own pages as captured.
- Weak sourcing — Hosting location.
- 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.
- 32 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 9 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 6 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
- 4 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
- 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 data facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 hosting facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 support fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 sovereignty dimension could not be confirmed on the vendor’s own pages and is shown as unknown. Know more? Tell us
- The pricing here was last read more than 30 days ago. Vendors change prices without notice; the capture date is shown with every figure. Know more? Tell us
Sources (7)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.vainu.com Checked 16 Nov 2026 +1 earlier capture: 22 Sep 2026 Details →
- 2 Pricing page www.vainu.com Checked 16 Nov 2026 +1 earlier capture: 22 Sep 2026 Details →
- 3 Privacy policy www.vainu.com Checked 16 Nov 2026 +1 earlier capture: 22 Sep 2026 Details →
- 4 Privacy policy www.vainu.com Checked 16 Nov 2026 +2 earlier captures: 2 Nov 2026, 22 Sep 2026 Details →
- 5 CRM sync, enrichment & export — found from sitemap www.vainu.com Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
- 6 CRM sync, enrichment & export — found from sitemap www.vainu.com Checked 16 Nov 2026 +1 earlier capture: 1 Oct 2026 Details →
- 7 Security / trust page — found from the homepage www.vainu.com Checked 16 Nov 2026 Details →