1. Who this policy covers
This policy covers the FactLockCam app for iPhone and Android and the FactLockFile app for Mac. FactLockCam is a private, local-first archive. Only you hold the keys that decrypt your encrypted photos and videos. We do not track, profile, or sell your personal information. We cannot read your unencrypted files or recover lost keys. This policy describes the data that does leave your device, which processors receive it, why we keep it, and how you delete it.
Contact for privacy questions and deletion requests: support@factlockcam.com.
2. What we collect and why
We collect the following for App Functionality. We do not use it for tracking or advertising.
- Email address (linked to your account). Used to send a one-time Magic Number and to identify your account. We do not use email for marketing.
- User ID (linked to your account). A Supabase authentication identifier created when you sign in. Ledger rows and quota records are stored under this identity.
- Photos and videos (not collected by FactLockCam). Capture happens on device.
Original media stays in the app's private storage as encrypted files (they use the
.sealfile extension). We do not upload photos or videos, and there is no cloud media sync. - Other user content (linked to your account). Titles and descriptions you add, signed capture manifests, fingerprints, and Polygon transaction identifiers associated with your account. Media bytes are not included.
- Purchases (linked to your account). If you buy a plan or Incident Pack, the store's purchase identifiers (Apple transaction identifiers, or Google Play order identifiers and purchase tokens) and the product purchased are stored to grant and renew your Archive plan. We never receive your payment-card number.
- Precise location (not collected by FactLockCam). If you grant location
permission, live GPS coordinates appear on the camera viewfinder. When a reading is
available at the shutter, Send Proof includes that reading inside the encrypted
.flcproofpackage you share, and the certificate PDF can print it as device-reported. It is not written into the signed capture record and it is not uploaded to our servers. - Files you FactLock with FactLockFile for Mac (not collected by FactLockCam). FactLockFile does not upload the file itself. Its contents, name, folder path, and any EXIF or GPS data in it stay on your Mac unless you share the file. When you FactLock a file, our servers store the file's SHA-256 fingerprint, its size, a general file type, the FactLock time, a random package ID, your account and device IDs, the app version, and a public signing key address. We use these to keep your FactLock record and count your monthly allowance.
- Connection logs and sessions. When the FactLockCam or FactLockFile app connects to our servers, our hosting provider, Supabase, logs your IP address, approximate location, and basic connection details such as the app's user agent. We use these logs to run and secure the service. On our current plan, Supabase keeps them for 7 days. While you're signed in, your sign-in session also stores your IP address and user agent until you sign out or delete your account.
- Mac downloads. When you download FactLockFile from our website, we record the date, the file, the country the request came from, and the page that referred you. This isn't linked to your account. We use it to understand downloads.
3. Processors and public records
Email is not kept solely on your device. The following processors receive the minimum data needed to run the product:
- Supabase — authentication, profiles, quota/subscription status, proof-ledger metadata, FactLockFile records, and connection logs. The FactLockCam apps do not upload your FactLocked photos or videos to Supabase Storage or any other FactLockCam server. They stay on your device unless you choose to share them.
- Resend — delivery of the Magic Number email (your address and the one-time code).
- Cloudflare — hosting and delivery of this website, including
/openand/verify. Check the proof free online at Open Proof. For larger files, use the Free Mac Proof Utility (the Free FactLockFile Viewer for Mac). We use Cloudflare Web Analytics to count visits to this website. It does not use cookies or identify individual visitors, and it is not used in the app. - Blockchain relay — a hash of the signed capture manifest may be written as a public blockchain record of hashes. That record does not include your email, filename, or media bytes. The signature does not identify the owner.
- Apple — if you purchase a plan or Incident Pack, App Store billing and receipt verification use Apple's purchase identifiers. We do not receive your payment-card number.
- Google — if you purchase on Android, Google Play Billing and purchase verification through the Google Play Developer API use Google's order identifiers and purchase tokens. We do not receive your payment-card number.
- Stripe — if you buy a FactLockFile plan, Stripe processes the payment and manages your subscription. We keep Stripe's customer, subscription, and payment-event identifiers, the plan you chose, its status, and its billing-period dates. We don't store your card details.
4. On-device encryption
Hashing, AES-GCM encryption, and capture-record signing run on your device before any upload. Keys
stay in the device Keychain (and Secure Enclave when the device reports that class). Those keys
are never transmitted to or stored on our servers. Capture records disclose the
device_key_class reported by the device; that label describes the signing key
class, not scene authenticity, and is not a hardware-attestation claim.
5. Public ledger
A signed FactLock record includes a fingerprint of the file. When a chain record is written, it is a public blockchain record of hashes (SHA-256 of the signed capture manifest). Your filenames and file contents are not included. The signature does not identify the owner. The record is a fingerprint match, not a statement of physical truth.
6. Data protection and AI
FactLockCam does not share your data, files, or identity with third-party AI or machine-learning services. Hashing and signing run on your device.
7. Backups you control
We do not store your encryption keys or backup passwords. We cannot reset those passwords or decrypt your archive. Your FactLocked photos and videos live on your device as encrypted files. FactLockCam does not offer cloud media sync and does not keep a copy of your photos or videos.
You manage two backups and we hold neither: a .factlock file (Account & Settings → Backup & Restore → Export archive keys) containing your sovereign decryption keys, and optional per-item encrypted .flcproof copies (open any Archive item and choose Export sealed backup). Neither is media from our servers. Keys are restored on the locked screen; encrypted items are restored in Backup & Restore with the password you set. Losing keys without .factlock means permanent loss of access to encrypted assets still on the device; only .flcproof copies you already saved stay unlockable.
Lock Archive removes keys from the device but leaves the local encrypted files; import .factlock to unlock encrypted files that remain on this device. App uninstall removes local keys and usually the local encrypted files; after reinstall, sign in, import .factlock, then restore items from any .flcproof copies you saved. Burn Account deletes your identity, ledger and quota records, local archive, and keys—a prior .factlock cannot restore a burned account. See our Terms of Service for the full scenario table.
8. Retention and deletion
Account, ledger, and quota records stay until you delete the account or we
must retain a subset to operate the service (for example, a public blockchain record of hashes cannot be
reversed). Burn Account (Account & Settings, double confirmation, typed
OBLITERATE) permanently deletes the
server identity, ledger and quota rows, local archive, keys, and journal. Shared
.flcproof packages you already delivered are copies you control; we cannot revoke
them. Step-by-step deletion instructions are on
Delete Account. Email
support@factlockcam.com if you need
help locating the in-app deletion path.
Burn Account also deletes your FactLockFile records, devices, plan, and usage. It does not delete a small set of billing records we keep for accounting and fraud prevention: payment-event identifiers from Stripe, subscription notices from Apple and Google, and internal billing-correction notes. Burn Account cancels a FactLockFile plan before deleting your account. It does not cancel an App Store or Google Play subscription, so cancel those in your store account first.
9. Your choices
- Decline location permission. Capture and FactLocking still work; the viewfinder and any proof package omit GPS.
- Stay offline after you FactLock. A public blockchain record of hashes waits until the device is online; media stays local either way.
- Export or delete your archive from Account & Settings.
10. Children
FactLockCam is not directed at children under 13 and does not knowingly collect personal information from them.
11. Changes
If this policy changes, we will update the date on this page. Material changes that affect how we handle personal information will be reflected here before they apply to the App Store or Google Play builds.