Support

FactLockCam is operated by factlockcam LLC, a Florida limited liability company founded in 2026. Company facts, privacy boundaries, and verification limits are published at factlockcam.com/trust/.

Paul D. Ensor founded FactLockCam. A short biography is at factlockcam.com/company/paul-ensor/. His public LinkedIn profile is linked from that page.

FactLockCam uses passwordless email OTP. Enter your email in the app, then paste the one-time code from your inbox. No password is stored on our servers.

No. Only you hold the keys—we cannot decrypt your archive or reset a lost backup password. FactLockCam does not keep a copy of your photos or videos. Export a .factlock archive-keys backup from Account & Settings → Backup & Restore and store it safely, and keep .flcproof sealed backups of the items themselves.

From an Archive item, tap Send Proof. The app builds one .flcproof file and makes the unlock key, so you do not create a password. A small proof opens in the browser from the link, with no app and no account. A large proof (photo or video 25 MiB or more) is shared with a note named factlockcam-unlock-key.txt beside the file. A large proof opens in the free FactLockFile desktop Viewer, coming for Mac, Windows and Linux once each version is tested. Media is never uploaded or stored by FactLockCam. Three results wait on the other side: the file, the signature, and the public record.

No. FactLockCam verifies the exact file and the signed capture record. It does not prove what was in front of the lens, a named identity, or that a claim will be accepted. See the threat model and Terms of Service.

The app stores a SHA-256 fingerprint of the captured bytes. A later copy matches only if those bytes are identical. Changing even one byte produces a different fingerprint and fails the file check.

The local seal still fingerprints and signs the capture. The Polygon anchor waits until the device can reach the network. Recipients can still check the file and signature. The public-record check stays pending until a transaction hash exists.

No. The link only opens the sealed envelope. File, signature, and public-record checks are separate. Opening the package does not attest the Polygon transaction.

Partly. The phone's device key is hardware-backed: Secure Enclave on iOS, and StrongBox or TEE on Android when the phone has one. The owner signature that factlockcam.com/open checks is made with a software key held in the phone's secure storage, not in hardware. Neither key shows what the camera saw, and neither is hardware camera attestation. Each capture record discloses the device key class the phone reported (secure_enclave, strongbox, tee, or software).

Professionals should read the Terms of Service. Verification can show that inspected bytes match a signed record and, when present, a public transaction. It does not promise any legal outcome.

Proof fingerprints and public-record details sync to our backend so records can be anchored and restored. Your photos and videos stay encrypted in your on-device Archive, and FactLockCam holds no copy. When you use Send Proof, you send the .flcproof file yourself through the app you choose. A small proof's link carries only the unlock key, never the file. Media is never uploaded or stored by FactLockCam. The messaging app you choose may keep its own copy.

Two files, both yours. Account & Settings → Backup & Restore → Export archive keys writes a password-protected .factlock with the keys that decrypt your Archive—not photos or videos. Re-export it before Lock Archive, uninstall, or device replacement. For the media itself, open any archive item and choose Export sealed backup to save a password-protected .flcproof copy of that item wherever you keep records. New sealed backups use the current .flcproof format, and older ones still open.

Keys first: after Lock Archive or a reinstall, the locked screen asks for your .factlock file and password. Then items: Account & Settings → Backup & Restore → Restore sealed backup (or the Restore backup tile in an empty Archive), pick a .flcproof file, and enter its password. The item returns with its original fingerprint and capture record—no new seal, no quota used. FactLockCam cannot recover a lost backup password. A sealed backup whose photo or video is 25 MiB or more does not restore into the phone's Archive. A large proof opens in the free FactLockFile desktop Viewer, coming for Mac, Windows and Linux once each version is tested. Keep the file and its password.

Lock Archive removes cryptographic keys from this device but keeps your encrypted files on the device. Import your .factlock backup to unlock the app again; your account and ledger records stay in place. Burn Account permanently deletes your account, ledger and quota records, local archive, and keys. A .factlock from before Burn cannot restore that burned identity.

Uninstalling removes local keys and usually local sealed files. Sign in with the same email, then import your .factlock file on the locked screen to unlock any local files that survived. Bring media back from any .flcproof sealed backups in Account & Settings → Backup & Restore. FactLockCam does not store your photos or videos in the cloud. Without those backups, only saved .flcproof copies remain unlockable.

Open Account & Settings → Delete Account → Burn Account. Check the irreversibility box and type OBLITERATE. That calls perform_full_burn and wipes the local archive and keys. A prior .factlock backup cannot resurrect that account. Full instructions: factlockcam.com/delete-account/.

A proof is large when the photo or video inside it is 25 MiB or more. It does not open in the browser. A large proof opens in the free FactLockFile desktop Viewer, coming for Mac, Windows and Linux once each version is tested. There is no download yet. For now, save the .flcproof file and the note named factlockcam-unlock-key.txt in the same folder and keep both. Without the key, the file cannot be opened. A lost key note can't be recovered. First check the text of the message the proof came in, because the key may also be there. If it isn't, ask the sender to run Send Proof again. That makes a new file with a new key.

You never make a password. The FactLockCam app makes the unlock key. For a small proof, it is in the link after #key=. That part is never sent to our server, and the page removes it from the address bar. For a large proof, the phone shows the key with a Copy button before sharing and sends it as a note named factlockcam-unlock-key.txt beside the file. When the note is in the same folder as the proof, the desktop Viewer will fill it in. A proof cannot expire or limit attempts, so anyone with the file and its key can open it. A lost key note can't be recovered. First check the text of the message the proof came in, because the key may also be there. If it isn't, ask the sender to run Send Proof again. That makes a new file with a new key.

Device time is the time your phone reported at capture. No one else checks it. The public-record time comes from Polygon: it shows the signed record existed no later than that block. A capture made offline gets its public record after the phone reconnects.

FACTLOCK IT™ with the FactLockCam app. When you capture in the app, the original stays encrypted in your Archive, a SHA-256 fingerprint of the exact file is sealed into a signed capture record, and a fingerprint of that record is anchored on Polygon (pending until the phone is online). Anyone can check later that the file hasn't changed.