What to capture
- Vehicle positions, damage panels, and surrounding context from several angles
- Road conditions, signs, and lighting as they appear at the scene
- A short clip if motion or sequence matters more than a still
Capture inside FactLockCam rather than the system camera so the signed manifest and fingerprint are recorded with the file. A GPS reading, when available, is sealed inside the package you share and is not part of the signed manifest.
How the record is sealed
The app computes a SHA-256 fingerprint, signs a canonical capture manifest, and encrypts the media in your local archive. When the network is available, the manifest hash can be anchored to Polygon to create an independently checkable existence window.
Add context without changing the original
Title and description live with the archive item. They do not rewrite the sealed bytes or the signed manifest. Use them to explain what a recipient is looking at.
Send a portable package
Send Proof writes one .flcproof file, and the app makes the unlock key, so you do not create a password. A small proof opens in the recipient's browser from the link, and nothing is uploaded. Videos can get big. A proof is large when the video or photo inside is 25 MiB or more. A large proof opens in the free FactLockFile desktop Viewer, coming for Mac, Windows and Linux once each version is tested. Its unlock key comes as a note beside the file. The recipient should keep both together.
What verification shows
A passing check shows that the inspected bytes match the recorded fingerprint, the signed manifest has not changed, the signing address recovers as recorded, and, when the public record is available, that the signed record existed no later than the Polygon block shown. The capture time itself comes from the phone's clock. It verifies the exact file and signed record; the full scope is on the threat model page.
