Hide publishes verified 30-, 90- and 180-day durability cohorts—not requests sent. Small samples remain unpublished, and missing follow-up is never counted as success.
Hide preserves the complete case. A removal counts only at the fourth stage, after the public source has been checked again.
Every metric needs at least 20 eligible cases or responses in its own denominator before Hide publishes a value.
A metric is published only after at least 20 eligible cases or responses exist for that exact denominator. Until then, the page shows “Collecting evidence.”
Cases waiting on a source remain in the relevant outcome denominator. Possible identity matches and possible relistings do not become confirmed failures until a person reviews them.
Updated November 2, 2026 from aggregate product records. No names, emails, source URLs or individual case details are published.
Hide records delivery as activity and counts success only after a reviewed source response and either a public-source check or the person’s explicit confirmation.
Delivered removal requests that later reached a source-evidenced or person-confirmed removed outcome.
Median elapsed days from confirmed request delivery to a source-evidenced or person-confirmed removal.
Confirmed exposure cases that produced an explicitly approved removal operation.
Each stayed-removed rate is published beside its observation coverage. Missing checks never count as success and cannot disappear from the denominator story.
Verified removals with a successful clear observation reaching 30 days and no person-confirmed relisting inside that window.
Verified removals with a successful clear observation reaching 90 days and no person-confirmed relisting inside that window.
Verified removals with a successful clear observation reaching 180 days and no person-confirmed relisting inside that window.
Removal cycles old enough for a 30-day outcome that have complete observed follow-up through that window.
Removal cycles old enough for a 90-day outcome that have complete observed follow-up through that window.
Removal cycles old enough for a 180-day outcome that have complete observed follow-up through that window.
Person-confirmed relistings first observed within 30 days, among removal cycles with a confirmed return in that window or a successful clear observation reaching the full window.
Person-confirmed relistings first observed within 90 days, among removal cycles with a confirmed return in that window or a successful clear observation reaching the full window.
Person-confirmed relistings first observed within 180 days, among removal cycles with a confirmed return in that window or a successful clear observation reaching the full window.
Identity errors, stale monitoring, incomplete recurring cycles, undelivered alerts and falsely reassuring Verify results are product failures. A harmful outcome enters this measure only with a concrete user-reported confirmation basis.
Discovery candidates rejected as a different person, divided by all candidates the person reviewed.
Active monitoring schedules checked within their promised interval.
Active full-source discovery schedules that are not more than 36 hours beyond their next promised cycle.
Started recurring-discovery cycles that reached a terminal dated brief and advanced the schedule exactly once.
Recurring-discovery alerts with a confirmed provider delivery event, divided by alerts Hide attempted to send.
Median elapsed minutes from the provider accepting a recurring-discovery alert to its signed delivery event.
Completed daily 07:00 UTC scheduler windows with a signed, fully successful lifecycle heartbeat, over the trailing 30 completed windows beginning with the first retained heartbeat.
User-reported harmful messages with a concrete confirmation basis that previously received Scam Check's lowest concern band.
Optional post-case responses measure clarity and time saved. Completed-case support demand and first-response time show whether the workflow remains understandable and serviceable.
Median elapsed minutes from creation of a confirmed exposure case to its first explicitly approved removal operation.
Completed cases the person reported as clear without needing help.
Median net user time saved: the user-reported manual time estimate minus self-reported active time spent using Hide.
Completed exposure cases that opened a private Hide support conversation, divided by all completed cases.
Median elapsed minutes from the first person message in a case conversation to Hide's first operator reply.
The metrics cover eligible cases handled through Hide. They exclude sources Hide failed to discover, people who did not confirm a possible match and outcomes that were never reported.
A competitor comparison requires the same authorized cases, definitions and completed follow-up for both products.
Read the evidence methodology