Hide methodology

Vendor Check coverage

Vendor Check reviews public company and register pages, news, reviews, professional networks, DNS, email policy, HTTPS policy and security.txt. Search snippets remain leads. Technical findings include the observed value, access time and method version.

Verdict definitions

Action

The observation supports a specific change. The report explains the evidence and a bounded next step.

Pass

The tested requirement was present and met the method's documented threshold at scan time.

Observed

A fact was visible, but presence alone is not enough to call it secure or insecure.

Unverified

A source timed out or could not be checked safely. Clear does not convert missing evidence into a pass or failure.

Safety boundary

The public scan does not scan ports, send exploit payloads, attempt sign-ins, test credentials or simulate attacks. It blocks private, local and reserved networks. Mail-policy checks do not prove live transport security. Company-scoped findings require domain ownership verification.

Personal outcome proof

Cases move through found, requested, responded, verified and monitoring. A request is never counted as a removal. Before delivery, the account owner approves the recipient and message. The owner completes any necessary identity check directly with the source.

Source captures store the final URL, status, selected headers, size, access time and cryptographic fingerprints. Monitored cases are checked every 30 days. Changes and possible relisting require human review.

Scam Check evidence

Scam Check reviews the request, payment destination, supplied email headers, sender mismatches, authentication records, domain history, lookalike characters, threat intelligence and bounded redirect traces. Evidence types remain separate.

Recognition runs in the browser. Screenshots stay on the device. Phone, bank and wallet checks validate formats, not ownership. Google Web Risk receives up to three submitted public URLs when enabled. Hide never turns absence from a list into a safe verdict.

Redirect tracing uses HEAD requests, follows no more than four redirects and never loads page bodies, attachments, scripts or forms. Missing evidence remains unknown.

Report limits

A result is a dated snapshot of a limited public surface. Penetration testing, internal security review, legal advice, compliance assessment and certification are outside its scope. Systems can change immediately after collection.

Inspect the personal outcome metrics, inspect the identity discovery benchmark, inspect the Scam Check benchmark, review the method changelog or inspect the technical scanner benchmark.

Corrections

If a result is inaccurate or a public source behaved unexpectedly, email info@hidedata.app with the report link and finding name. Reports expire after 90 days.