Methods and boundaries
What does Hide’s evidence actually prove?

Ask about a method, source or limitation. Hide distinguishes an observation from a verified outcome and an unknown from a pass.

General information from an AI assistant, not a real check. Private by design, never sold or used for training.

Hide outcome standard

Personal exposure outcome metrics

These measures show whether Hide produces verified changes for eligible personal exposure cases. Small samples remain unpublished, and missing ground truth is never replaced with a synthetic score.

Counting rules

Removal outcome definition

Hide preserves the complete case. A removal counts only at the fourth stage, after the public source has been checked again.

  1. 01
    FoundA possible exposure exists
    Finding
  2. 02
    Removal requestedThe approved request was delivered
    Activity
  3. 03
    Source respondedA reply is attached to the case
    Evidence
  4. 04
    Removal verifiedThe source was checked again
    Outcome
  5. 05
    MonitoringThe result is tested over time
    Durability
Published with enough evidence0of 19 measures
Still collecting19separate denominators
Ground truth unavailable0shown, never estimated

Every metric needs at least 20 eligible cases or responses in its own denominator before Hide publishes a value.

Publication rules

Measurement denominators

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 September 18, 2026 from aggregate product records. No names, emails, source URLs or individual case details are published.

outcome

Verified exposure outcomes

A sent request is activity. Hide counts success only after a reviewed source response and either a public-source check or the person’s explicit confirmation.

Higher is betterVerified removal rate
Collecting evidence

Delivered removal requests that later reached a source-evidenced or person-confirmed removed outcome.

n = 0 of 20 minimumDelivery or a source claim alone never counts as removal. Hide requires either a reviewed public-source check or the person’s explicit observation; unresolved cases remain in the denominator.
Context, not a scoreMedian time to verified removal
Collecting evidence

Median elapsed days from confirmed request delivery to a source-evidenced or person-confirmed removal.

n = 0 of 20 minimumCalculated only for cases with both timestamps. A 404 or 410 verifies the exact source URL, not disappearance from every other source.
Higher is betterFindings leading to useful action
Collecting evidence

Confirmed exposure cases that produced an explicitly approved removal operation.

n = 0 of 20 minimumAn approved action may still be pending, fail delivery or require specialist review; it is not a removal claim.
durability

Outcome durability

Each removal cycle enters a 30, 90 or 180 day cohort only after Hide confirms a return inside that window or records a successful clear check reaching the full window. Missing checks never count as success.

Lower is betterRelisted within 30 days
Collecting evidence

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.

n = 0 of 20 minimumEach removal cycle is counted separately. Stopped, unavailable and unresolved checks are excluded rather than assumed clear; possible source changes count only after the person confirms a relisting.
Lower is betterRelisted within 90 days
Collecting evidence

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.

n = 0 of 20 minimumEach removal cycle is counted separately. Stopped, unavailable and unresolved checks are excluded rather than assumed clear; possible source changes count only after the person confirms a relisting.
Lower is betterRelisted within 180 days
Collecting evidence

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.

n = 0 of 20 minimumEach removal cycle is counted separately. Stopped, unavailable and unresolved checks are excluded rather than assumed clear; possible source changes count only after the person confirms a relisting.
integrity

Evidence and delivery quality

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.

Lower is betterFalse identity-match rate
Collecting evidence

Discovery candidates rejected as a different person, divided by all candidates the person reviewed.

n = 0 of 20 minimumThis measures candidate precision after human review, not recall of sources Hide never found.
Higher is betterEvidence checked on schedule
Collecting evidence

Active monitoring schedules checked within their promised interval.

n = 0 of 20 minimumA fresh check proves when Hide last checked the source, not that every copy on the internet is absent.
Higher is betterRecurring discovery on schedule
Collecting evidence

Active full-source discovery schedules that are not more than 36 hours beyond their next promised cycle.

n = 0 of 20 minimum active schedulesA schedule can be on time while an individual source is partial or unavailable. Source-level gaps remain visible inside each dated discovery brief.
Higher is betterRecurring discovery cycles completed
Collecting evidence

Started recurring-discovery cycles that reached a terminal dated brief and advanced the schedule exactly once.

n = 0 of 20 minimum started cyclesA terminal cycle may still contain a visibly unavailable source. Interrupted or still-running cycles remain in the denominator until they resume and complete.
Higher is betterNew-result alerts delivered
Collecting evidence

Recurring-discovery alerts with a confirmed provider delivery event, divided by alerts Hide attempted to send.

n = 0 of 20 minimum attempted alertsUser-suppressed alerts are excluded. Accepted, delayed, failed, bounced and complained messages remain unsuccessful until a signed delivered event is received.
Lower is betterMedian new-result alert delivery time
Collecting evidence

Median elapsed minutes from the provider accepting a recurring-discovery alert to its signed delivery event.

n = 0 of 20 minimum delivered alertsCalculated only for delivered alerts with both timestamps. Provider acceptance without a delivery event is not treated as delivered.
Higher is betterDaily scheduler reliability
Collecting evidence

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.

n = 0 of 20 minimum expected daily runsA day counts once even after retries. Partial, failed and missed windows after the first retained heartbeat count as unsuccessful; the open window and any time before that first heartbeat are not claimed.
Lower is betterVerify false-reassurance rate
Collecting evidence

User-reported harmful messages with a concrete confirmation basis that previously received Hide Verify's lowest concern band.

n = 0 of 20 minimumThe person must report a concrete confirmation basis, such as confirmation from the organization, bank, platform or incident team, or observed takeover or loss. This is structured user-reported ground truth, not independent verification. Unknown, unresolved and legacy outcome-only reports are excluded.
experience

Customer workload reduction

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.

Lower is betterMedian time to first approved action
Collecting evidence

Median elapsed minutes from creation of a confirmed exposure case to its first explicitly approved removal operation.

n = 0 of 20 minimum actioned casesCalculated only for cases that reached an approved operation. Cases with no approved action remain visible in the separate useful-action rate; approval does not prove delivery or removal.
Higher is betterCases completed without confusion
Collecting evidence

Completed cases the person reported as clear without needing help.

n = 0 of 20 minimumBased on optional post-case responses; non-responders and unfinished cases are excluded.
Higher is betterMedian net user time saved
Collecting evidence

Median net user time saved: the user-reported manual time estimate minus self-reported active time spent using Hide.

n = 0 of 20 minimumOptional estimates only. Negative values remain negative and mean Hide took more active time than the estimated manual route; Hide does not run an activity timer or infer savings for non-responders.
Lower is betterCompleted cases needing support
Collecting evidence

Completed exposure cases that opened a private Hide support conversation, divided by all completed cases.

n = 0 of 20 minimumOne case counts once even if the person sends several messages. A lower rate may indicate clarity, but it can also reflect unmet or unreported support needs.
Lower is betterMedian first support response
Collecting evidence

Median elapsed minutes from the first person message in a case conversation to Hide's first operator reply.

n = 0 of 20 minimumThreads without an operator reply remain unresolved and are excluded from the median; their count remains visible in the internal support queue.
Interpretation

Metric limitations

The metrics describe eligible cases handled through Hide, not every exposure or removal service on the market. They do not measure sources Hide failed to discover, people who did not confirm a possible match or 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