No data over bad data.
We would rather return nothing than return something wrong. This page explains what that means in practice: how we collect, validate, refresh and deliver every profile, email and phone number.
Three commitments behind every response
Freshness you can see
Every response carries the date of the last full profile refresh — not a light check on a few fields. Read it for free with /check before you decide how to resolve.
Quality by construction
Validation runs at sourcing, at refresh and at delivery. Bots, fakes and unverified records are kept out of the database — they never reach your product.
Matching precision
We never return a guess. Identity resolution runs every check we have and returns a confidence-scored match — or null.
We operate the whole pipeline, end to end
Since 2024 we no longer source data — we run the full infrastructure ourselves. That's what lets us guarantee what comes out of it.
We don't resell data. We validate it.
Where we use external sources, we never trust their flags. Every result passes our own checks before it reaches you.
Validated in real time, before delivery. Waterfall providers re-benchmarked monthly against ground truth.
The number exists and belongs to the person — not just one of the two.
Below the confidence threshold, the answer is null — never a best guess.
Why our numbers look smaller in benchmarks
Most providers count every record they hold. We only return profiles that passed verification. Fake accounts and bots are blocked upstream — so our coverage figures are lower, and our match is right.
Keep them all and every match is a coin flip. We remove them, so the match is the real one.
Two mechanisms keep the database fresh
Freshness is the hardest problem in B2B data. We don't solve it with a “30-day refresh” claim — we solve it with usage and with scoring.
Live API traffic
Every live person or company call re-fetches the source and updates the profile in our database. Usage keeps the data current by design.
Opt-out available by contract if you don't want your calls used for refresh.
Scored, tiered refresh
Every profile is scored on demand signals, job title and completeness, then assigned a refresh tier.
You decide how fresh is fresh enough
Freshness is a trade-off with latency and cost. We expose it instead of hiding it: check the date for free, then choose per request.
Send an ID or profile URL, get our last-updated date. Decide: cache, live, or skip.
"refreshType": "full"
The profile as stored, with its timestamp. Best for volume and latency-sensitive features.
Goes back to the source, re-validates, updates our database, returns the new version. For stale records and high-stakes decisions.
Rank providers by precision, not by count
Most waterfalls rank providers by match rate because quality is hard to measure. But a high-count provider placed first pushes its false positives straight into your product. Put the most precise provider first, then let lower-confidence sources fill the gaps if you want more coverage.
Compliance-by-design. Built to be defensible.
Reverse Contact is designed to support GDPR/CCPA-aligned data practices. We maintain clear sourcing principles, respect data subject rights, and prioritize accuracy over guesswork.
Don't take our word for it. Benchmark us on your records.
500 free credits, 7 days, no card. Run a sample where you already know the truth and measure precision — not just fill rate.
