Panel 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 GetEmails, LLC · www.rb2b.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.
RB2B at a glance
- Vendor
- GetEmails, LLC
- Headquarters
- Not stated on the vendor’s pages as of 16 Nov 2026
- Data hosting
- Outside the EU by default; pages mention the United States source, captured 16 Nov 2026
- Free plan
- Yes, per the vendor’s own page source, captured 16 Nov 2026
- Starting price
- “STARTER $79 /mo” (vendor’s words) source, captured 9 Nov 2026
- Panel verdict
- The AI panel rates RB2B 2/5, the mean of 6 judges. RB2B, from GetEmails, LLC of Austin, Texas, identifies visitors to your own website: person-level records — names, work emails, LinkedIn URLs — are US-only by design, while company-level identification runs globally through Demandbase. 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
RB2B, from GetEmails, LLC of Austin, Texas, identifies visitors to your own website: person-level records — names, work emails, LinkedIn URLs — are US-only by design, while company-level identification runs globally through Demandbase. The scoring is strongest on visitor identification and pricing transparency: all four tiers are public — Free at $0/mo with 150 monthly resolutions, Starter at $79/mo with 300, Pro at $149/mo, Pro+ at $199/mo — with overage at 45¢ per resolution on Starter and 25¢ on Pro and Pro+, and a 7-day trial requiring no credit card. The weak points are sovereignty — Texas governing law, US hosting, a self-serve DPA, and no public information found on EU hosting, a named subprocessor list or a transfer basis — and data coverage, because the database is designed to exclude emails and phone numbers of EU or UK residents, leaving European traffic at company level only. Data provenance scored 4-6, prospecting compliance 3-4 and CRM sync and export 5-6; no genuine split between judges was flagged.
Speaks for it
- Person-level identification of US traffic — names, work emails, LinkedIn URLs — plus global company-level identification through Demandbase's reverse-IP network
- All four tiers publicly priced — Free $0/mo, Starter $79/mo, Pro $149/mo, Pro+ $199/mo — with overage published at 45¢ per resolution on Starter and 25¢ on Pro and Pro+
- Native HubSpot and Salesforce integrations add RB2B-specific contact properties and timeline events, with returning visitors updating existing profiles rather than duplicating
- High-intent signals documented — Hot Pages tagging, Hot Leads ICP filtering, pageview history, and Slack or Teams alerts routed to the assigned rep
- Published 2025 opt-out record of 23,323 requests, all complied with, none denied, with a one-day median response and a retained suppression file
Held against it
- Sovereignty scored 1-2, the lowest in the table: GetEmails, LLC under Texas governing law, service hosted in the United States, and no public information found on EU hosting, a named subprocessor list or a transfer basis
- The database is designed to exclude emails and phone numbers of EU or UK residents, so European traffic yields company-level data only
- There is no prospecting search, and no public information was found on do-not-call register checks or country-aware outreach flags
- The captured pages give different statements on API availability, and CSV export is Pro-only, manual download, capped at a 365-day window
- All payments are nonrefundable, with no public information on per-seat costs beyond a single seat, credit rollover, VAT treatment, or included resolutions for Pro and Pro+
Best for
- You sell primarily to US buyers and want named visitors — names, work emails, LinkedIn URLs — pushed to Slack or your CRM in real time
- You want global company-level identification with alerts routed to assigned reps and lead routing by company size or industry
- You buy self-serve and want every tier priced publicly, from the Free plan at $0/mo with 150 monthly resolutions upward
- You run HubSpot or Salesforce and want website activity logged as timeline events on enriched contact records
Avoid if
- Your pipeline needs person-level contact data for EU or UK prospects, since the database is designed to exclude their emails and phone numbers and person-level identification never runs outside the United States
- You want to search a prospect database by job title or firmographics rather than identifying visitors already on your own site
- You need refunds or credits for inaccurate data, since the terms state all payments are nonrefundable
The scores
| Criterion | Panel median |
|---|---|
| Coverage, accuracy & freshness | 1.5 of 5 |
| Data sources & lawful basis | 2.5 of 5 |
| Visitor identification & intent signals | 3 of 5 |
| Prospecting workflow & outreach rules | 2 of 5 |
| CRM sync, enrichment & export | 2.5 of 5 |
| European sovereignty | 1 of 5 |
| Pricing transparency | 3 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
This is visitor identification of your own traffic, not a searchable contact database: the person-level data is names, work emails and LinkedIn URLs for US visitors only — the documented export columns include a work email but no phone number — and the vendor states its database is designed to exclude emails and phone numbers of EU or UK residents, so for DACH prospecting there is no person-level data at all. Coverage claims are identification rates of your own site (15–45% by plan) rather than market coverage, and we found no public information on record counts, an email verification method, or a refresh cadence. Company-level data is global via Demandbase with industry, headcount and revenue fields. 6 7 10 5 2
The RevOps Manager
Identification rates per plan and level are published — 15-20% on lower tiers, 35-45% on Pro+, up to 70-80% of US traffic combined — together with the fields delivered: work email, LinkedIn URL, title, industry, headcount and revenue estimates. But person-level resolution is US-only and the database is designed to exclude emails and phone numbers of EU or UK residents, so a DACH pipeline gets company names and nothing person-level. We found no public information on email verification, a refresh cadence or accuracy guarantees. 6 7 2 5
The Data Protection Officer
This is a visitor-identification service rather than a multi-country contact database: person-level records are US-only by design, EU or UK contact identifiers are excluded from the database, and global coverage exists only at company level through Demandbase. The data types and firmographics delivered per identified profile are documented down to individual export columns, with identification-rate targets per plan and acknowledged accuracy caveats; but we found no public information on email verification methods, refresh cadence or record counts, and the terms provide output data 'as is' with all payments nonrefundable. 10 1 2 4 5
The ABM Marketer
Coverage is documented as identification rates rather than a database count — 40-45% of US traffic resolved to a person, another 30-35% to a company globally, 15-20% on lower tiers — and company profiles carry industry, employee count and revenue. For my European accounts the picture is thin: person-level identification is US-only and the database is designed to exclude the emails and phone numbers of EU and UK residents. I found no public information on verification methods or refresh cadence, and payments are nonrefundable, so data quality stays my cost. 4 6 7 1 5
The DACH Sales Director
Person-level identification is US-only by the vendor's own statement, so for my German, Austrian and Swiss accounts the sellable coverage is company-level only, at a stated 15–20% (35–45% on Pro+); the export columns do include industry, estimated employee count and revenue. I found no public information on total record counts, email verification, per-country figures or any credit-back for wrong data, and the terms state all payments are nonrefundable. 5 7 10 2 4
The Skeptic
The vendor publishes identification rates rather than database counts — 15–20% of traffic at basic resolution, 35–45% with premium resolution, 70–80% combined for US traffic — and exports carry firmographics such as industry, employee count and estimated revenue. But by its own statement person-level identification resolves US data subjects only, and the database is designed to exclude emails and phone numbers of EU or UK residents; we found no public information on verification method, refresh cadence or an accuracy guarantee, and the terms state all payments are nonrefundable. 1 6 7 5 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 — 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 — a disclosed contributory database, third-party data providers, public APIs, and LinkedIn-style career databases for enrichment — with consent and legitimate interest named as legal bases, a privacy notice addressed to the people in the contributor database, and a working opt-out: 23,323 requests in 2025 all honored with a one-day median response, plus a retained suppression file. It stops short of the top marks because the vendor's stated position is that GDPR does not apply to its US-only person-level product, and we found no public information on Art. 14 notifications to the people in the database or a published balancing test. 3 5 3
The RevOps Manager
Source categories are named — third-party data providers, integration partners, public APIs and the internet — and the contributory database is disclosed as such, with consent or legitimate interest named as the legal bases. The privacy policy doubles as the notice to people in the database, with a self-service opt-out backed by published 2025 figures (23,323 requests, none denied, one-day median response) and a suppression file kept so re-collected data stays excluded. We found no public information on per-record source traceability, an Article 14 notification practice, or a published balancing test. 3 3 5
The Data Protection Officer
Source categories are named — third-party data providers, public sources, and a disclosed contributory database matched against a described fully-permissioned publisher network — consent and legitimate interest are the stated processing bases, the privacy notice is addressed to the people in the database, and there is a self-service opt-out, a request-to-know route, published request statistics, and a suppression file designed to keep removed people excluded on re-collection. We found no public information on an Article 14 notification practice for people when they are added, or on a published balancing test, and the vendor's stated position is that GDPR does not apply to its person-level service, so EU records are avoided by exclusion rather than grounded in a named lawful basis. 3 3 8 5
The ABM Marketer
Source categories are named — a contributory database built from customer sites, third-party data providers and integration partners, and public sources — with consent and legitimate interest stated as the bases, a privacy notice addressed to the people in the database, and a self-service opt-out form plus a permanent suppression file; all 23,323 data-subject requests received in 2025 were complied with and none denied. I found no public information on per-record source or collection date, a published balancing test, or notification of people when they are added. The stated position is that no product is directed at the EU or UK, so the GDPR machinery a European buyer would ask for is not the frame. 3 5 3
The DACH Sales Director
Source categories are named — a "fully-permissioned" contributory publisher network, third-party data providers, public APIs, LinkedIn and career databases for enrichment — with consent or legitimate interest named as the legal basis, a privacy notice addressed to people in the contributor database, and a self-service opt-out form backed by a suppression file so objections stick. I found no public information on an Article 14 notification practice, a published balancing test, or a per-record source and collection date. 3 3 6 1
The Skeptic
The privacy notice names sources in general terms — third-party data providers, public APIs and the internet, a "fully-permissioned publisher network" — and openly discloses a contributory database, addresses a notice to the people in it, and offers a self-service opt-out form whose 2025 statistics are published (23,323 requests, none denied, one-day median response). Legal bases are named only generically ("your consent or on legitimate interest"), and we found no public information on notifying people when they are added to the database, a published balancing test, or per-record source traceability. 3 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; 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
This is the core product and it is strong: person-level identification of US traffic plus global company-level through a named partner, Demandbase, with page-level signals (Hot Pages, pageview history, recent URLs), ICP tagging, and Slack alerts routed to the assigned rep. By design EU traffic only ever gets company-level — person-level never fires outside the US — and the vendor states that consent capture plus a consent management solution are required for the global company-level script. It falls short of the top marks because operation is cookie-and-device-ID based rather than cookieless, the vendor states it does not enforce consent on the customer's behalf, and we found no public information on a TDDDG position. 7 1 2 5
The RevOps Manager
Person-level identification is documented as US-only technology that never resolves individuals outside the United States, while company-level ID runs globally via Demandbase with a consent management solution explicitly required for the global company-level product. Page-level intent tagging (Hot Pages), ICP filtering (Hot Leads), per-company visit history and Slack alerts routed to assigned reps are documented, and responsibility for consent on the tracking script is stated to sit with the customer. We found no public information on cookieless operation or a position specific to the German TDDDG. 1 7 11 2 5
The Data Protection Officer
The architecture is the one I look for on European traffic: person-level identification never runs outside the United States, EU visitors can only ever be resolved to company level, and the vendor states a consent management solution is mandatory for the global company-level product — while expressly leaving consent enforcement to the operator. High-intent page tagging, ICP filtering, visit history per profile and alerts routed to assigned reps are documented; but tracking runs on first and third-party cookies and device IDs, and we found no public information on a §25 TDDDG position, cookieless operation, or named consent-platform integrations. 1 7 11 2 5
The ABM Marketer
The product does what I need on the company side: global company-level identification through a named partner — Demandbase's reverse-IP network — with real-time pushes to Slack and Teams on every plan, lead assignment to reps by company size or industry, and Hot Pages and Hot Leads tagging I can trace back through pageview history and recent page URLs. Person-level identification resolves 40-45% of US traffic into names, work emails and LinkedIn URLs, but it is US-only and the script runs on first- and third-party cookies and device IDs rather than cookieless. The consent position is stated but shifted to me — RB2B does not enforce consent on my behalf, and a consent management solution is mandatory only for the global company-level identification — and I found no public information on a German TDDDG position. 1 7 10 11 2 5
The DACH Sales Director
This is the core product: person-level resolution of US visitors plus global company-level identification through Demandbase's reverse-IP network, with visit history, filters, Hot Pages high-intent tagging, and Slack or Teams alerts routed to the assigned rep. The vendor mandates a Consent Management Solution for its global company-level identification while putting consent enforcement squarely on the customer, and person-level identification never happens outside the United States; I found no public information on cookieless operation or a specific position on Germany's §25 TDDDG consent rule. 1 7 1 1 2 5
The Skeptic
Person-level identification of named individuals with work email and LinkedIn URL is documented and confined by design to US visitors, with global Demandbase reverse-IP company identification for everyone else and a plainly stated consent position: global company-level identification requires a consent management solution, and RB2B does not enforce consent on your behalf. Filters, pageview history, hot-page tagging and Slack alerts routed to the assigned rep are all documented. It stays below the top tier because the script matches visitors through first- and third-party cookies with no public information on a cookieless mode, company-level tracking of EU visitors is enabled by default, the vendor states regional exclusions are not supported, and we found no public information on a TDDDG or ePrivacy position. 1 7 11 2 5
Prospecting workflow & outreach rules
Show reasoningHide reasoning
How this is scored
Search, list building and outreach — and whether the product helps the buyer stay within UWG §7 and the GDPR once the list exists, rather than leaving the legal risk entirely with the customer.
0 — No search, list building or outreach; the product only stores leads entered or captured elsewhere.
3 — Search with filters on firmographics and job title, saved lists, and export of the contacts found.
5 — Advanced filters (technographics, hiring or funding triggers), saved searches with alerts, a suppression or do-not-contact list, and guidance on GDPR or cold-outreach rules for EU contacts.
8 — Country-aware handling (for example German contacts flagged where cold calls and emails require consent under UWG §7), phone numbers checked against national do-not-call registers where they exist, and opt-outs from outreach synced back to the database.
10 — Compliance is part of the workflow: outreach channels restricted or flagged per country and contact type by default, suppression shared across the whole account and every export, the Art. 14 notice supported at first contact, and a documented record of how each contact entered the buyer's pipeline.
The SDR Team Lead
List building here means filtering your own identified visitors — page views, hot pages, hot-lead ICP tags, with pre-export filtering and CSV export on Pro — not searching a market by firmographics or job title, and we found no public information on saved lists. The compliance guidance is essentially that person-level is US-only, consent is the customer's responsibility, and this is not legal advice; we found no public information on country-aware flags for German contacts, do-not-call register checks, or a do-not-contact suppression list tied to outreach. 9 10 2 5
The RevOps Manager
This is not database prospecting: leads are your own visitors, filtered by page views, hot-page views and ICP match, with exclusion lists for domains and URLs and CSV export gated behind the Pro plan as a manual download. The compliance guidance on the pages concerns California opt-out links, and the vendor states it does not enforce consent on the customer's behalf. We found no public information on country-aware outreach flagging, do-not-call checks, or opt-outs syncing back from outreach. 7 9 10 2
The Data Protection Officer
This surfaces the buyer's own visitors rather than searching a prospect database: identified profiles can be filtered by engagement and ICP fit before export, exclusion lists for domains, URLs and lists are supported, and CSV export is limited to the Pro plan with a maximum 365-day window. Some guidance exists — websites are told to carry a California opt-out link and are told the consent burden is theirs — but we found no public information on do-not-contact screening, country-aware flags for cold outreach, or outreach opt-outs syncing back to the data. 10 2 9 7
The ABM Marketer
There is no prospecting search — I cannot look up contacts by title or firmographics; filters on page views, hot page views and Hot Leads apply only to visitors my own site captured, and exports are CSV with pre-export filtering. The compliance help that exists is shaped around California and the tracking script: an opt-out link recommendation for California residents, no way to configure regional exclusions for tracking, and the statement that RB2B does not enforce consent on my behalf. I found no public information on country-aware outreach flagging, do-not-call screening, or a documented record of how each contact entered my pipeline. 4 7 9 10 2
The DACH Sales Director
What exists is capture-side: filters on identified profiles (page views, hot pages, ICP-based Hot Leads), Exclusions for domains, URLs and lists, and Pro-only CSV export — I found no public information on searching a prospect database, so the workflow starts from visitors already on your site. The vendor states consent enforcement is the customer's responsibility, states that regional tracking exclusions such as excluding specific regions are not supported, and stamps its GDPR page "THIS IS NOT LEGAL ADVICE"; I found no public information on do-not-call register checks or any guidance on German cold-outreach rules under UWG §7. 9 10 2 5 7
The Skeptic
This is not a search product: the workflow filters and routes your own site's visitors — Hot Leads ICP filtering, Hot Pages tagging, exclusion lists for domains, URLs and lists, CSV export and pushes to outreach tools such as Instantly and HeyReach — rather than searching a market for contacts. The compliance posture is stated explicitly and puts the risk on the buyer ("RB2B does not enforce consent on your behalf"), the vendor states regional exclusions such as for California are not supported, and we found no public information on country-aware outreach flags, do-not-call register checks, or opt-outs synced back from outreach. 7 9 10 2
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 HubSpot and Salesforce pushes with RB2B custom properties, timeline events, enrichment of contact records, and lead-assignment rules, plus webhook, Zapier, Clay and CSV export on Pro and above — though the captured pages give different figures on an API, with the homepage listing RB2B APIs while a help article states there is none and none is planned. CSV is manual download only with a 365-day cap, and we found no public information on bidirectional sync, on deletion propagation when a person objects, or on which data a customer may keep after cancelling. 10 11 1 2
The RevOps Manager
Native HubSpot and Salesforce integrations with OAuth-style setup, RB2B-specific contact properties, timeline events, lead routing by company size and industry, and returning visitors updating existing profiles rather than duplicating; webhook and Zapier sit alongside CSV export. Exports are manual downloads only, with no automatic delivery to external systems, and the captured pages give different statements on whether a public API exists at all. We found no public information on bidirectional sync or scheduled re-enrichment, and the license to store output data runs only throughout the subscription term, with all payments nonrefundable. 4 6 10 11 1 2
The Data Protection Officer
Native HubSpot and Salesforce integrations are documented with custom properties, timeline events, enrichment of existing records, and returning visitors updating existing profiles rather than duplicating them; CSV export and webhooks are gated by plan, and the captured pages give different accounts of API availability, one listing APIs while a support article states there is no API and none is planned. We found no public information on bidirectional sync, deletion propagation when a person objects, or retention rights after cancellation, and the license to store output data runs only for the subscription term. 11 6 10 4 1
The ABM Marketer
Native OAuth-style HubSpot and Salesforce connections add RB2B-specific contact properties and timeline events, enrich existing contact records with website activity and company information, and update returning visitors' profiles instead of duplicating them; webhooks, Clay, Apollo and Zapier round out the Pro plans, and CSV export runs daily plus on demand with filters. The captured pages give different statements on API availability — one links to APIs while a support article says there is no user API and none planned — and I found no public information on bidirectional sync, scheduled re-enrichment, or data rights after cancellation beyond nonrefundable payments and a storage license that runs with the subscription term. 4 6 10 11 1 2
The DACH Sales Director
There is a native HubSpot integration via OAuth that adds RB2B-specific contact properties and timeline events, with lead-assignment rules by company size, industry or lead source, and Salesforce, Clay, Zapier and webhook sit among the integrations — the captured pages give different totals, 36 apps on one and 50+ on another. CSV export is Pro-only, manual download, capped at a 365-day window, with no automatic delivery to external systems, and the captured pages give different information on API availability — one help article states there is no API and none on the roadmap while other pages list APIs. I found no public information on bidirectional sync, deletion propagation when a person objects, or retention rights after cancellation. 2 10 11 1 2 2
The Skeptic
Native HubSpot and Salesforce connectors are documented with enrichment of existing contacts (website activity, lead source, LinkedIn profile, company information) and returning-visitor profile updates, alongside a webhook and Pro-only CSV export delivered by email link. The captured pages give different statements on API availability — a support article says none exists and none is planned, while the homepage links to APIs — and we found no public information on bidirectional sync, deletion or objection propagation, or keeping data after cancellation; the output-data license runs only "throughout the term of Customer's subscription". 2 4 10 11 1 2
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 is GetEmails, LLC of Austin, Texas under Texas governing law, the service and website are hosted in the United States, and the vendor states it has no EU or UK establishment and directs no product at the EU — a DPA is listed among its compliance documents, but we found no public information on a subprocessor list, an EU hosting option, or a transfer basis. The mitigation for EU visitors is exclusion: the database is designed to exclude EU and UK residents' emails and phone numbers, so EU traffic yields only US-processed company-level data. 4 5 3 5 1
The RevOps Manager
The contracting entity is GetEmails, LLC of Austin, Texas under Texas governing law, the service is hosted in the United States, and the vendor states it has no EU or UK establishment and no product directed at the EU. EU and UK personal identifiers are excluded from the database by design, though global company-level tracking of EU visitors is enabled by default. A DPA is listed among self-serve compliance documents, but we found no public information on EU hosting, an Article 27 representative, a named subprocessor list, or a transfer basis for the data that is processed. 4 3 5 1 5
The Data Protection Officer
The contracting entity is GetEmails, LLC of Austin, Texas under exclusive Texas jurisdiction, the service is hosted in the United States, and we found no public information on a transfer basis for European data, an EU representative, or a published subprocessor list — while a data processing agreement is offered among the public compliance documents. The database is designed to exclude EU and UK personal identifiers, yet global company-level tracking is enabled by default for all accounts, including European Union visitors. 3 4 1 7 5
The ABM Marketer
The contracting entity is GetEmails, LLC d/b/a RB2B in Austin, Texas under Texas law, the service and website are hosted in the United States, and the vendor states it has no establishment in Europe or the UK and no product directed there; EU and UK residents' contact details are excluded from the database by design, though company-level identification of EU visitors still runs. A data processing agreement is offered among the compliance documents and SOC 2 Type II is claimed. I found no public information on EU hosting options, a subprocessor list, or the legal basis for transfers covering European-territories visitors. 4 7 3 5 1
The DACH Sales Director
Everything sits in the United States: the contracting entity is GetEmails, LLC in Austin, Texas under Texas law, the service and website are hosted in the United States, and the vendor states it has no European establishment and no product directed to the EU or UK. A DPA is listed among the compliance documents and the database is designed to exclude EU or UK residents' personal data, but I found no public information on an EU hosting option or an EU representative — for a Mittelstand buyer, that is the whole story. 4 3 5 5 1
The Skeptic
The contracting entity is GetEmails, LLC in Austin, Texas under Texas governing law, the service is hosted in the United States, and the vendor states it has no EU or UK establishment and no product directed at the EU or UK. A self-serve DPA and a GDPR/CPRA FAQ are listed, but we found no public information on EU hosting options, an EU representative, or a transfer basis for the European-territory traffic the privacy policy nonetheless addresses. 4 3 5 1
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
All four tiers are public with billing period and included monthly resolutions — Free $0 /mo with 150 company-level resolutions, Starter $79 /mo with 300, Pro $149 /mo, Pro+ $199 /mo self-serve up to 2,500,000 resolutions — with overage quoted at 45¢ per resolution on Starter and 25¢ on Pro and Pro+, additional domains at $99/mo, a 7-day Pro+ trial with no credit card, and auto-renewal and nonrefundability stated plainly. Full cost computability for a team is not possible from these pages: we found no public information on per-seat costs beyond the first seat, credit rollover, or VAT treatment, and payments are explicitly nonrefundable, which is the opposite of a credit-back for inaccurate data. 4 2 2
The RevOps Manager
All four tiers are priced publicly — Free at $0/mo with 150 monthly resolutions, Starter at $79/mo with 300, Pro at $149/mo, Pro+ at $199/mo — with per-resolution overage published at 45 cents on Starter and 25 cents on Pro and Pro+, extra domains at $99/mo, self-serve volumes up to 2,500,000 monthly resolutions, and custom pricing only above 12,500 resolutions on Pro+. Refunds are explicitly unavailable and auto-renewal terms are stated. The captured pages do not state resolution counts for the Pro and Pro+ base tiers, credit rollover, separate seat costs, or VAT treatment. 2 4 2 2
The Data Protection Officer
Every tier is priced publicly with its monthly resolutions — Free at $0/mo with 150, Starter at $79/mo with 300, Pro at $149/mo and Pro+ at $199/mo — together with overage rates of 45¢ per resolution on Starter and 25¢ per resolution on Pro and Pro+, $99/mo for additional domains, and a 7-day Pro+ trial; the terms state all payments are nonrefundable. But subscriptions are per seat, we found no public information on additional seat pricing, credit expiry or rollover, or VAT treatment, and the captured pricing pages give different accounts of where self-serve volumes end. 2 2 4 2
The ABM Marketer
Every tier is public — free at $0 with 150 monthly resolutions, Starter at $79/mo with 300, Pro at $149/mo, Pro+ at $199/mo — plus per-resolution overage of 45¢ on Starter and 25¢ on Pro and Pro+, extra domains at $99/mo, a 7-day Pro+ trial and a forever-free plan with no credit card, with resolutions as the billing unit and company-level identifications consuming them. I cannot compute a full invoice from public pages: the resolutions included with Pro are not stated, rollover is not stated, per-seat costs beyond a single seat are not public, and VAT treatment is not stated. The captured pages also give different figures on where self-serve Pro+ volumes top out — one says volumes above 12,500 monthly resolutions are priced with the team, another that self-serve runs to 2,500,000 resolutions a month. 4 7 2 2
The DACH Sales Director
Credit where due: every tier is public — FREE $0/mo, STARTER $79/mo, PRO $149/mo, PRO+ $199/mo — with monthly resolution volumes on the lower tiers, overage at 45¢ per resolution on Starter and 25¢ per resolution on Pro and Pro+, extra domains at $99/mo, a 7-day Pro+ trial without a credit card, and self-serve purchasing up to 2,500,000 resolutions a month. The terms also state plainly that all payments are nonrefundable. I found no public information on per-seat costs, VAT treatment, or credit expiry and rollover, so the annual invoice is not fully computable from the public pages. 2 2 4 2
The Skeptic
Four tiers are priced monthly ($0, $79, $149, $199) with monthly resolutions stated for the free plan (150) and Starter (300), overage quoted at 45¢ per resolution on Starter and 25¢ per resolution on Pro and Pro+, additional domains at $99/mo for up to five, and self-serve Pro+ up to 2,500,000 resolutions a month before custom pricing. What blocks full computability: we found no public information on included resolutions for Pro and Pro+, credit expiry or rollover, per-seat costs or VAT treatment; the terms state all payments are nonrefundable with a 30-day fee-dispute window, and the captured pages give different descriptions of the free trial (Pro versus Pro+). 4 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 | — | uncited Report an error |
|---|---|---|---|
| Hosting location |
Outside the EU
unverified
Why unverified?The statement is in the privacy policy's international-transfers section and covers the Service and Website generally without naming data-center locations. |
0/4 pts | 3 Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement |
Published, self-serve
unverified
Why unverified?The excerpt only links out to the compliance documents; the DPA text itself is not reproduced in any captured excerpt. |
1/1 pts | 1 Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about RB2B
Is RB2B European?
No. whats-best.ai classifies RB2B as Rest of world.
Where does RB2B store data?
RB2B stores customer data outside the EU by default, per the vendor’s page captured 16 Nov 2026. The vendor’s pages mention the United States as hosting location, per the vendor’s page captured 22 Sep 2026.
Does RB2B have a free plan?
Yes. RB2B has a free plan, per the vendor’s page captured 16 Nov 2026.
What are the best alternatives to RB2B?
As of 18 Nov 2026, the panel rates Dealfront (3/5), Lusha (2.5/5) and Vainu (2.5/5) highest among the other 48 Lead Generation products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Dealfront (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: RB2B 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 — Data processing agreement. The excerpt only links out to the compliance documents; the DPA text itself is not reproduced in any captured excerpt.
- Weak sourcing — Hosting location. The statement is in the privacy policy's international-transfers section and covers the Service and Website generally without naming data-center locations.
- 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 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
- 12 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 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 legal 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
- 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 (11)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.rb2b.com Checked 16 Nov 2026 +2 earlier captures: 9 Nov 2026, 22 Sep 2026 Details →
- 2 Pricing page www.rb2b.com Checked 16 Nov 2026 +2 earlier captures: 9 Nov 2026, 22 Sep 2026 Details →
- 3 Privacy policy www.rb2b.com Checked 16 Nov 2026 +1 earlier capture: 22 Sep 2026 Details →
- 4 Terms of service www.rb2b.com Checked 16 Nov 2026 Details →
- 5 Security / trust page www.rb2b.com Checked 16 Nov 2026 +2 earlier captures: 9 Nov 2026, 30 Sep 2026 Details →
- 6 Visitor identification & intent signals — found from sitemap support.rb2b.com Checked 16 Nov 2026 Details →
- 7 Visitor identification & intent signals — found from sitemap support.rb2b.com Checked 16 Nov 2026 Details →
- 8 Prospecting workflow & outreach rules — found from sitemap www.rb2b.com Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
- 9 Prospecting workflow & outreach rules — found from sitemap support.rb2b.com Checked 16 Nov 2026 Details →
- 10 CRM sync, enrichment & export — found from sitemap support.rb2b.com Checked 16 Nov 2026 Details →
- 11 CRM sync, enrichment & export — found from sitemap www.rb2b.com Checked 16 Nov 2026 Details →