What the verifier checks
The public verifier accepts exported proof packet JSON or proof HTML with embedded packet data. It checks the signed payload hash for timeline events, participants, artifacts, redactions, and audit metadata.
Evidence
Proof packet verification for secure handoffs
ZipPigeon proof packets give teams a signed evidence record for sensitive handoffs. The public verifier checks packet integrity without requiring an account.
What it does not prove
A proof packet does not prove plaintext file contents, malware status, recipient identity beyond recorded workflow signals, or long-term storage state. It is evidence about the handoff record, not a substitute for legal discovery or compliance attestation.
Where packets come from
Signed-in users can export proof packets for uploads, shares, file requests, secure rooms, service-account activity, and related workflow records where the product has enough audit context.
When to use it
Use proof verification when a client, vendor, employee, auditor, or support counterparty needs a tamper-evident summary of what happened without receiving file keys or plaintext files.
Frequently asked questions
Can someone verify a proof packet without a ZipPigeon account?
Yes. The public verifier at /verify is designed for account-free packet integrity checks.
Does proof verification decrypt files?
No. It verifies evidence packet integrity. Plaintext file contents and file-key material remain outside the verifier.
Send the file. Keep control of the link.
Use ZipPigeon when a file needs to reach the right person without becoming another attachment or shared folder to clean up later.
Open signed-in sender