Support

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. Export a .factlock sovereign key backup from Account & Settings and store it safely. Cloud sync stores ciphertext we cannot read; it is not a downloadable photo library backup.

From an archive item, tap Send Proof, set a one-time password, and share the .flcproof package, proof.json, and certificate PDF through the iOS share sheet. Recipients open factlockcam.com/open, choose the file on their device, and enter the password. Nothing is uploaded.

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 password only unlocks the sealed envelope. File, signature, and public-record checks are separate. Entering the correct password does not attest the Polygon transaction.

Capture records disclose the device_key_class reported by the device (software, secure_enclave, tee, or strongbox). That label describes the signing key class, not scene authenticity. Do not treat it as a hardware-attestation claim.

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 create a guaranteed legal outcome.

Proof hashes and ledger metadata sync to our backend. Sealed media lives on your device as encrypted .seal files. After sealing, optional blind ciphertext may upload for the same account—we cannot read it, and you do not download it like a cloud photo backup. Send Proof shares a password-protected .flcproof file that you deliver yourself; recipients unlock it locally at factlockcam.com/open.

Two files, both yours. Account & Settings → Backup & Restore → Export archive keys writes a password-protected .factlock with your sovereign decryption keys—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.

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.

Lock Archive removes cryptographic keys from this device but keeps local .seal files. Import your .factlock backup to unlock the app again; cloud data for your account is unchanged. Burn Account permanently deletes your account, cloud ciphertext, 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 decrypt cloud sync again. After that, bring back individual items from any .flcproof sealed backups in Account & Settings → Backup & Restore. Without .factlock, encrypted cloud and local assets are inaccessible; only saved .flcproof copies remain unlockable.

Open Account & Settings → Burn Account and confirm twice. This permanently deletes your Supabase identity, linked cloud storage, local archive, and keys. A prior .factlock backup cannot resurrect that account.