Skip to content
FactLockCam
Use cases

Use case

Create the record before cleanup begins.

Storm damage, leaks, and loss claims are easier to explain when the original file and signed metadata can be inspected later. FactLockCam seals in-app captures into an encrypted archive you control.

  • Wide then close-up
  • Before and after pairs
  • Title without rewriting bytes

What to document before conditions change

  • Wide shots of the room or exterior, then close-ups of the damaged area
  • Before-and-after pairs when you can capture both states
  • Serial numbers, water lines, or debris that may be cleared

How FactLockCam seals the record

Capture inside the app. FactLockCam records the media fingerprint, file details, capture metadata, and optional location, then signs a canonical manifest. The encrypted item stays on your device.

Add context without changing the original record

Use Certificate Studio to add a title and description for the recipient. Those fields travel with the package; they do not alter the sealed media or the signed manifest hash.

Send and open without uploading

Share a password-protected .flcproof file. Recipients visit factlockcam.com/open, choose the file locally, and enter the password. FactLockCam does not host the recipient copy.

What the checks establish

Verification shows file integrity, signed-manifest integrity, signing-address recovery, and a bounded existence window when Polygon data is available. It verifies the exact file and signed record; the full scope is on the threat model page.

Next step

Document it before it is gone.

Debris gets cleared and water lines dry. The signed record does not change.