Skip to content
FactLockCam
Use cases

Use case

Before the cars move, anchor the damage record.

After a collision, lighting, weather, and vehicle position change quickly. FactLockCam fingerprints the capture, signs the record, and lets you share a portable package others can inspect without installing the app.

  • Capture in-app
  • Optional location
  • Share via .flcproof

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, fingerprint, and optional location are recorded with the file.

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 a password-protected .flcproof file. Share it through the system share sheet and send the password separately. A recipient opens factlockcam.com/open, chooses the file on their device, and enters the password. Decryption happens in the browser; nothing is uploaded.

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 chain data is available—that the media existed within the displayed window. It verifies the exact file and signed record; the full scope is on the threat model page.

Next step

Anchor the scene before it clears.

The record exists the moment you capture. Share it later on your terms.