Public vs Non-Public Data Broker Coverage: Buying Guide

Public and non-public data broker coverage solve different privacy problems. Public people-search removal targets listings that other people can find. Non-public coverage targets information held or distributed through restricted business databases. Before buying, ask which source classes your plan includes and how the service verifies each type of request.

A larger coverage total does not mean that more records were found about you, or that every request succeeded. Choose a plan around your exposure and the evidence it provides. A clean public scan cannot establish that every non-public database is empty.

What are you paying to cover?

Buying question	Public people-search coverage	Non-public broker coverage
Where is the information?	Searchable listings or reports available to members of the public	Restricted business systems, datasets or partner distribution
How might a service find it?	Search supported sites and match visible records	Use supported identifiers and rights-request workflows; a public scan may not be possible
What evidence is useful?	Matched URL, check date and listing status	Request scope, matching method, response and stated action
What can remain?	Original public records, unmatched listings and new exposures	Permitted retention, another controller's copies or records outside the request scope
What should the contract clarify?	Sites and aliases included, recurring checks and exceptions	Included source classes, jurisdictions, request authority and outcome reporting

Use the data removal comparison hub when you are ready to compare service choices. This decision comes before comparing headline totals: first establish whether the total describes the problem you need solved.

Start with the exposure you can describe

If strangers can search your name and find an address or relatives, prioritize the relevant public listings. Keep the URLs privately and check that the plan includes those sites. A service with a clear public-record match and follow-up process may fit this immediate need.

If your concern is business-contact distribution, marketing audiences or restricted datasets, ask about the relevant non-public source class. Do not infer that a people-search scan also inspected those systems. Some services send requests to supported brokers without first observing a public listing.

These categories are practical coverage descriptions, not a simple legal division. A paywall alone does not settle whether a company is a public people-search provider, and restricted access does not mean data use carries no privacy risk. Record type, purpose and applicable law still matter.

What current provider documentation shows

OneRep separates source classes by plan

OneRep's current coverage help distinguishes people-search sites included in all plans from non-public brokers included in Pro plans. Its pricing page reader representation, checked November 10, lists 317 public and 559 non-public sources, totaling 876.

That explicit split helps buyers understand the upgrade. It does not prove that a customer has a record at all 876 sources or that all requests produce deletion. The direct pricing browser was security-challenged during this review, so no checkout test or new purchase-price verification is claimed here.

A public-listing-only buyer may not need the same scope as someone seeking restricted-database requests. Confirm the selected plan's current list and reporting before paying. Keep the custom-removal versus standard-coverage decision separate: it concerns requests outside a plan's normal list, not the definition of public and non-public sources.

Malwarebytes describes database scans and mixed removal work

The current Malwarebytes Personal Data Remover page advertises scans across 500+ broker databases, automatic and guided removals, and continued monitoring with progress information. Its standalone card says $99.99 per year for one adult, billed annually, as checked November 10.

Automatic and guided work can be a useful combination for someone willing to complete the required steps. However, that product card does not provide a directly comparable public-versus-non-public breakdown. Do not reinterpret “500+ databases” as 500+ public listings, 500+ hidden sources or a measured success rate.

The Malwarebytes review covers the broader purchase and workflow questions. Confirm the selected offer and renewal terms; a promotional bundle price is not interchangeable with the standalone plan or its future renewal.

Ask for evidence that fits the source

A public listing can sometimes be checked again using its URL. The useful record is the matched listing, the check date and what changed. A temporary error page or missing search result alone may need another check before it is treated as removal.

For a non-public source, ask what “removed” means in the report. Did the broker confirm deletion, apply a sale opt-out, retain a suppression marker or say that no matching record was found? Those are distinct outcomes. A screenshot cannot prove the contents of a database that was never publicly accessible.

Our guide to data removal reports explains how to read statuses and counts.

Ask the provider to distinguish completed actions from requests still awaiting a response, and broker-side confirmation from the service's own observation.

What broader coverage cannot promise

Coverage is the scope of a service's work. It is not ownership of a broker's response, a guarantee of universal legal eligibility or permission to erase every regulated record. Some information can be retained for specific obligations or purposes, and a request may apply only to particular processing.

Neither source class includes every news page, government record or social-media post. A search-engine result may need its own process after a source changes. New data, identifiers or recipients can also create work after the first request round.

CrabClear should be evaluated against the same standards. Its supported workflows and recurring service do not give it visibility inside every private database or control over every recipient. Ask about the actual source and reporting, rather than assuming any provider can verify all behind-the-scenes copies.

Choose the narrowest plan that addresses your need

List the specific public exposures or non-public data uses that concern you.
Check the selected plan's source classes, geography and matching requirements.
Ask how automatic requests, guided steps and unresolved cases are reported.
Compare ongoing work and renewal terms after confirming scope.
Use direct manual requests where a small number of clear workflows is enough.

The free-scan versus paid-removal guide explains what payment adds after discovery. When the fit is clear, review CrabClear pricing against the same questions. The goal is relevant coverage and understandable evidence, not the largest unqualified number.

Frequently asked questions

Does no public scan result mean no broker has my data?

No. It describes what that scan found within its supported scope and matching limits. It does not establish the contents of every restricted database.

Is non-public coverage always worth an upgrade?

It depends on the data use you want addressed and the work included. Ask for relevant source classes and outcome reporting before paying for a broader catalog.

Can I compare two totals directly?

Only after understanding what each counts. Domains, databases, affiliates, custom requests and other source categories can produce very different totals.

Should every completed request have a screenshot?

No. Screenshots can help with public listings, while a non-public request may rely on a broker response or suppression confirmation. Evidence should match the claim being made.

Sources and verification

Official sources were checked November 10, 2026. OneRep's reader and indexed support documentation supplied plan-scope evidence; its direct browser pricing page was challenged. Malwarebytes' live product card was inspected in a browser. Counts are dated vendor descriptions, not comparative effectiveness measurements. No paid account, checkout or removal outcome was tested.