- 01
Capture inside the app
Photos and videos originate in FactLockCam. The system camera roll is not the source of the FactLocked original. When location access is on, the phone's GPS reading is kept with the capture on your phone and included in the proof package you share; it is not part of the FactLock record.
- 02
Fingerprint and signed manifest
The app computes SHA-256 over the media bytes and signs a canonical manifest that includes the fingerprint, file length, MIME type, UTC capture metadata (device-reported), signing address, and device-key class. The device key class is disclosed. FactLockCam does not claim hardware camera attestation.
- 03
Encrypted archive under your control
Media is stored encrypted on the device. Only you hold the keys; a .factlock backup carries them to a new phone.
- 04
Portable package, local unlock
Send Proof writes one .flcproof file. The recipient can check that proof free, online, at Open Proof. For larger files, use the Free Mac Proof Utility (the Free FactLockFile Viewer for Mac). The file and the signature are checked as separate results.
- 05
Scope of a passing check
Verification confirms the exact file and the signed record. The full ceiling, including what a passing check does not establish, is on the threat model page and in the Terms of Service.
How it works
How it works
Tamper-evident photo and video verification
FactLockCam creates a tamper-evident record: encrypted media and a signed canonical manifest.
- SHA-256
- Canonical manifest
- AES-GCM Archive
Next step
Start the record at the lens.
Everything above begins with one capture inside the app.