.prfd turns a JPEG into evidence.
Cryptographically sealed at capture,
fraud-checked before signing,
verifiable anywhere.
Trivially forgeable. Trivially swappable. And since 2024, trivially AI-alterable — fifteen seconds in Photoshop or Stable Diffusion turns an intact box into a "damaged" refund claim.
The driver opens the delivery app and takes a photo. Location, time of capture, and device fingerprint are bundled with the image.
The bundle is transmitted to our cryptographic infrastructure and sealed in real time. The signing key lives in a hardware security module and never touches the driver's device.
A complete .prfd file is returned to the carrier's system. The original photo bytes are preserved exactly — no compression, no rewriting, no metadata loss.
Anyone with the public verification key can confirm a .prfd file's integrity in milliseconds. Customers, insurers, auditors, and dispute platforms all see the same answer.
Competitors store fraud scores in some database — quietly editable later. We weld the score to the file. Click below to try to tamper.
The verdict, the photo, and the metadata are welded into one signature. Touching anything inside the file is what voids it — a successful tamper produces a worthless artifact that fails verification the instant anyone checks. There is no edit that helps the attacker.
The fraud verdict is part of the signed manifest, not a record looked up later. Flip "fraud" to "clean" and the signature dies with the edit — there is no path to a file that's both rewritten and valid.
Swap one pixel and the photo hash mismatches the manifest. We don't need to see the original to know it was altered — the math says so in milliseconds.
Every .prfd carries its own proof. A verifier checks the file against our public key and gets a definitive yes or no in milliseconds. To forge one, an attacker would have to break the cryptography itself.
A .prfd binds the photo, its location, and a server-anchored
timestamp into one cryptographic seal. Any byte change breaks it. Before
sealing, a proprietary forensic stack analyzes each capture for signs of
staging, substitution, or manipulation. The result verifies in
milliseconds, anywhere.
Like JPEG for photos or PDF for documents, .prfd is a wire format we authored. MIME type, file signature, spec — ours. Owning a format is the playbook that built Adobe. Anyone can read it; the spec authority is the company.
Every .prfd file in the wild points back to our public key. Network-effect asset.
Refusing imports at the format level — before the camera opens — beats every after-the-fact heuristic.
The score is inside the seal. Editing it breaks the signature. Hard to walk back once standard.
One file, one verification call. Competitors stitch together five services.
.prfd sealed in your return flow ends the ambiguity. Every refund claim comes with evidence anyone can verify.Server is built. Format is locked. Spec is publishable. The next build turns a verifiable file format into a camera you put in a driver's hands.
Apple App Attest and Google Play Integrity do the heavy lifting. We ship the surface on top.
A new file format. A new evidence standard. We're working with select retailers, carriers, insurers, and return-management platforms on early deployments. If verified evidence — on either side of the transaction — would change your numbers, let's talk.