Trust and transparency

Clear boundaries are part of the product.

This page explains what GetEvidex verifies, what it does not verify, what stays local by default, and why the site stays modest about the technical result it can provide.

What GetEvidex verifies

  • Whether the selected record can be read in the expected structure.
  • Whether the signed payload bytes match the displayed payload.
  • Whether the signature check passes in the current browser when supported.
  • Whether a supplied local file hash matches the record hash when you choose to compare it.

What GetEvidex does not decide

  • It does not act as a legal authority.
  • It does not guarantee compliance in every jurisdiction or process.
  • It does not silently upload files by default.
  • It does not settle identity, intent, or broader factual disputes on its own.

What PASS means technically

The checks that ran here passed. PASS does not mean every possible fact about the record, file, sender, or legal context was resolved.
Signed vs unsigned
GetEvidex can confirm signed payload consistency when the data and browser support are present. Unsigned material remains outside that signed guarantee.

What stays local by default

  • Opening the file
  • Parsing the record
  • Hashing the local file
  • Signature verification attempt
  • Exporting a local summary

Status snapshot

Updated
Mode
Privacy facts

    Known limits