Waalaxy

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.

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.

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.

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.

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.

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.

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.