How we will measure removals
Production numbers, not marketing figures, once there are any. Every number published here will be dated, and the methodology is written out at the bottom.
Verified and acknowledged are counted separately and never added together. A verified removal means we re-loaded the live profile URL and it was gone. An acknowledged request means the broker confirmed receipt but publishes no page we can check.
Compliance rate by broker
Per-broker, for every site that publishes a profile we can re-check. Published once we have enough requests for a rate to mean anything, with the sample size beside it so you can judge that yourself.
Re-listing rate within 90 days
Data comes back — that is why removal is a subscription and not a one-time job. We will publish how often it comes back per broker, including where that makes the subscription look worse.
Methodology
This describes the paid tier, which does not exist yet. It will record every outbound request with a timestamp and the route used. For sites that publish a public profile, a scheduled job will re-load the exact URL we filed against, store a screenshot and a SHA-256 of the response, and mark the removal verified only when the profile is absent. For sites with no public page, we will record the acknowledgement and stop there: we will not infer deletion, and we will not count it as one.
Medians will be calculated on requests that reached a verified state; requests still open will be excluded and reported separately. Escalations will count once per broker per cycle. Each published figure will carry the date it was last refreshed.