Live totals from the same records our customers’ dashboards read. Each number has its definition printed next to it, and the method is below. No customer can be identified on this page.
Computed . Recomputed at most once an hour.
28,668
Deletion demands sent
A legal deletion demand, written for one person and addressed to one data broker’s privacy contact, that our email provider accepted for delivery. It still counts if it later bounced. Sent is not delivered, and delivered is not removed.
6,764
Demands the broker answered
The broker wrote back about the demand and we recorded the answer: a deletion confirmation, a “no records” answer, an acknowledgement, a refusal, or another reply that needs review or a further step. An answer is not a removal.
272
Confirmed removals
The broker wrote back saying it deleted the person’s data, and that sentence is in the broker’s own reply, which we keep on file. Counted once per person and broker, however many demands it took. An opt-out, a suppression or a promise to delete later is not counted.
1,072
Brokers with no records
The broker searched and wrote back that it holds no data on the person. The data is not there, but nothing was deleted, so these are never counted as removals. Counted once per person and broker.
Not counted as removals: 273 cases where the broker confirmed an opt-out or a suppression without saying it deleted anything. The data is still held, so we label these “suppressed, not deleted”.
Week by week
The last 12 weeks
Weeks start on Monday, UTC. Demands are dated when our email provider accepted them. First replies are demands whose first broker reply on file arrived that week. Confirmed removals are dated by the broker’s confirmation. “<5” means between 1 and 4, hidden so a small count cannot point to one customer.
Week of
Demands sent
First replies
Confirmed removals
Aug 31
1,580
526
11
Sep 7
22
272
8
Sep 14
884
323
25
Sep 21
706
215
33
Sep 28
3,354
583
27
Oct 5
2,068
662
19
Oct 12
881
499
49
Oct 19
<5
289
28
Oct 26
388
132
11
Nov 2
0
190
10
Nov 9
630
198
13
Nov 16(so far)
<5
38
10
Broker by broker
Which brokers write back
Rates use only demands that reached the broker (not bounced, with a delivery receipt or a reply on file) and were sent at least 45 days before the figures were computed, so every broker had at least that long to reply. A broker is named only with at least 20 such demands from at least 5 different customers, and brokers marked as delisted are left out. Answered means the broker wrote back to GhostVault in any form, including an automatic acknowledgement or an early reply whose text we did not keep. Deletion in writing is the share of those demands where the broker’s reply states a completed deletion.
Most responsive
Highest share of demands answered.
Broker
Demands
Answered
Deletion in writing
Plunge, LLC
37
100%
21.6%
Venntel, Inc.
36
100%
0%
Data Axle Inc.
35
100%
0%
MV Digital Group, LLC
35
100%
0%
Nachal Inc.
35
100%
11.4%
AppLovin Corporation
32
100%
0%
Rushmore Labs, LLC
32
100%
21.9%
Captiv8 Inc.
31
100%
0%
Ripple Effect Strategies
23
100%
17.4%
Chex Systems, Inc.
20
100%
0%
Least responsive
Lowest share of demands answered.
Broker
Demands
Answered
Deletion in writing
Mobilewalla, Inc.
48
0%
0%
PrivCo Holding Inc
48
0%
0%
Slashdot Media, LLC
48
0%
0%
Collective Data Solutions, LLC
47
0%
0%
Datasys Group, Inc.
47
0%
0%
DTN, LLC
47
0%
0%
Equifax Information Services LLC
47
0%
0%
Equifax Workforce Solutions LLC
47
0%
0%
FinThrive Healthcare, Inc.
47
0%
0%
Predictive Pop, Inc.
47
0%
0%
560 brokers meet the sample threshold. A broker with no reply on record may have answered another way, for example inside its own web portal or directly to the customer, so a low rate is not by itself a finding that the broker broke the law.
Methodology
Where the numbers come from. They are computed by code from our production records: every demand we send and every broker reply, stored in full. Nothing on this page is typed in by hand.
How replies are classified. An automated classifier sorts each reply into a category such as confirmation, no records, acknowledgement, request for more information, suppression or refusal. The category alone never makes a removal. A reply counts as a confirmed removal only when a separate rule-based check finds, in the broker’s own text rather than in our quoted letter, a sentence saying the deletion is done. Promises (“will be deleted”), work still in progress, conditional wording and “no records found” never pass. A reply a customer forwards to us counts only when its email authentication (DKIM) ties it to the broker or the broker’s privacy vendor.
Suppression is not deletion. An opt-out, a “do not sell” or a suppression list entry leaves the data with the broker. We report those separately and never count them as removals.
Submitted is not removed. A demand that was sent, or even delivered, is only a demand. It becomes a removal when the broker says in writing that the data is deleted.
Limits of a written confirmation. A confirmation is the broker’s own statement, not an independent check that a listing is gone. Some confirmations say the broker keeps limited data, for example records it must keep by law; they still count because the broker states the deletion was completed. A missing confirmation does not prove a broker kept the data.
Older replies. We began keeping a full copy of every broker reply on 1 August 2026. An earlier reply whose text we did not keep is never counted as a confirmed removal.
Privacy. Aggregate counts only: no customer names, emails or reply text. Counts from 1 to 4 are hidden. Demands filed for family members count toward demands sent, answers and first replies, and are left out of the outcome counts and the broker tables.