Method

How the numbers are counted.

The totals on our home page come from one public endpoint that reads our production records. Here is what each one counts and what it leaves out. The weekly series and broker tables are on the proof page.

Registered data brokers on our list

What it counts. Brokers in our registry that are not marked delisted. A broker is marked delisted when it no longer appears in the newest registry we read.

What it does not. This is the number of places we can send a request. It is not the number of brokers that hold your data.

Deletion demands sent

What it counts. Removal request records that have a sent time, meaning our email provider accepted the demand for delivery. One record is one person and one broker.

What it does not. A demand that bounced later still counts as sent. Sent is not delivered, and delivered is not removed.

Demands answered by the broker

What it counts. Request records whose status says the broker wrote back: a deletion confirmation, a no-records answer, an acknowledgement, a reply that needs review, or a refusal.

What it does not. An answer is not a removal. Most answers are an acknowledgement or an instruction to use the broker’s own form.

Deletions with evidence

What it counts. Cases where the broker’s own reply states that the deletion is done, and a rule-based check finds that sentence in the broker’s text, not in our quoted letter. Counted once per person and broker, however many letters it took.

What it does not. Opt-outs, suppressions, promises to delete later, and replies we could not verify are not counted. Family member requests are left out.

Deleted or no records held

What it counts. Deletions with evidence, plus brokers that wrote back saying they hold no data on the person. Counted once per person and broker.

What it does not. A broker that never held the data did not delete anything, so this figure is never called a removal count.

Exposed data points found

What it counts. The sum of the exposure points recorded on each free scan: addresses, phone numbers, emails, relatives, associates, aliases and employers found (each category capped), one point if an age was found, plus breaches, pastes and dark web leaks for the email checked.

What it does not. Scans are searched by name, so these are likely exposures, not confirmed ones. Someone who scans twice adds twice. Free scans without an account are deleted after 24 hours, so this covers scans still on file.

Rules that apply to every figure

  • Aggregate only. The endpoint returns six totals. No names, emails or reply text.
  • Refreshed hourly. The server recomputes at most once an hour, and your browser may keep a copy for up to another hour, so a number can be a little behind.
  • Counts can go down. The totals count records that exist now. When a customer deletes their account, its requests and replies are deleted with it, so a total can fall.
  • Every account is included. Totals cover all customers, with the exceptions noted above. They are not a success rate. Many demands are still inside the 45-day window brokers have to respond.
  • A written confirmation is the broker’s statement. It is not an independent check that a listing is gone.
See the live totalsSee an example evidence timelineSecurity and data handling