THE DEEPFAKE-DEFENSE CAMERA
FactLockCam fingerprints photos and videos at capture, signs the record, and anchors it publicly—so a later altered copy cannot match the earlier record.
Verifies the exact file and signed record—not the physical truth of the scene.
Asset fingerprint · SHA-256
9f2c7e1a4b8d03e6c5a1f7d29b4e6c8a0d3f5b7e9c1a2d4f6b8e0c2a4d6f8b1e
A changed copy fails the file check first. Each result is independent of the others.
Anchor the Original. Verify it yourself.
See how it worksWhat it does
Three stages at capture, three separate results at verification. Nothing depends on trusting us.
SHA-256 · exact bytes
The instant you capture, FactLockCam hashes the exact media bytes. One changed byte produces a different fingerprint.
Canonical manifest · owner key
A canonical capture manifest — fingerprint, length, MIME type, UTC metadata, key class — is hashed and signed by your key.
Polygon · public record
When the device is online, the manifest hash is published to Polygon. The transaction is the public reference a later copy is compared with.
Fingerprint. Sign. Anchor.
Deepfake defense starts at capture
Every photo and video is fingerprinted the instant you capture. FactLockCam signs that capture record and, when the device is online, publishes the record hash to an independent public ledger. Every signed record discloses how it was signed.
Change the file. Break the match.
Independent verification
Send a password-protected .flcproof package. Recipients open it locally in a browser—nothing uploaded—and check the file, the signature, and the public record as three separate results.
Change the file. Break the match.
The fingerprint of the original is fixed in the signed record. Edit a pixel, re-save the file, or strip metadata and the new fingerprint diverges immediately. The verifier does not judge how the image looks — it compares bytes with the earlier record.
Run the live challengeOriginal · recorded at capture
9f2c7e1a4b8d03e6c5a1f7d29b4e6c8a0d3f5b7e9c1a2d4f6b8e0c2a4d6f8b1e
Altered copy · inspected later
9f2c7e1a4b8d03e6c5a1f7d2e07c3a5f9b1d8e2c4a6f0b3d5e7c9a1f2d4b6e8c
Why you need it
The enemy is doubt introduced after the fact: a submitted photo is changed, the other party says it was edited, or a recipient cannot tell which copy came first. FactLockCam creates a signed, publicly anchored capture record before manipulation occurs. It does not guess whether pixels look AI-generated; it compares the file with the earlier record.
Can you trust it
FactLockCam is built so you do not have to trust us. Only you hold the keys. Recipients inspect a package locally. The signed record can be compared with a public Polygon transaction. Every signed record discloses how it was signed.
Media is encrypted on-device. FactLockCam cannot read your archive or reset a lost password.
A .flcproof package opens in the browser on their own device. Nothing is uploaded to us.
The signed manifest hash can be checked against a Polygon transaction anyone can look up.
Exactly what a passing check shows, and the notes professionals need, are published in the threat model and Terms of Service.
THE DEEPFAKE-DEFENSE CAMERA
Free to start. Capture inside FactLockCam, keep the sealed original in your archive, and share a package a recipient can check themselves.