Legal
Terms of Service
Last updated May 2026
1. Acceptance of Terms
By using FactLockCam, you agree to these Terms of Service. FactLockCam provides tamper-evident digital archive services for media certification, encryption, and workflow support.
2. Digital Archive Certification
FactLockCam supports authenticity heuristics through three technical pillars:
- Integrity: Cryptographic proof that a file is unaltered (SHA-256).
- Ownership: Association with your authenticated identity and device signing where enabled.
- Timestamping: An immutable anchor on the Polygon blockchain when notarization is active.
This produces a certificate draft that documents the state of a digital asset at a specific point in time. It supports disclosure workflows but does not guarantee admissibility under FRE 902.
3. Permanent Ledger Records
You acknowledge that the Polygon blockchain is a permanent record. Once a cryptographic hash is anchored, it cannot be modified or deleted. FactLockCam has no authority or ability to alter blockchain records.
4. User Responsibility (The Verification Bridge)
A successful verification requires two components under your exclusive control:
- The Artifact: The original, unaltered file.
- The Identity: The credentials used to sign the asset.
If either is lost or modified, the cryptographic link for verification cannot be restored.
5. Non-Custodial Access Protocol
CRITICAL: FactLockCam utilizes non-custodial security. We do not store your encryption keys or backup passwords. We cannot reset your password, decrypt your archive, or recover lost keys. You are solely responsible for device access and for exporting and safeguarding your .factlock sovereign key backup (Account & Settings → Export archive keys).
6. Keys-Only Backup (Not Media from the Cloud)
The only backup you can create in FactLockCam is a password-protected .factlock file (Account & Settings → Export archive keys). It contains your sovereign decryption keys (EVM signing key and archive AES key)—not your photos, videos, or files downloaded from our servers. FactLockCam cannot restore access without your .factlock backup and backup password.
Re-export your .factlock periodically, before Lock Archive, before uninstalling the app, or before replacing your device. Keys are stable for a given app install; you do not need to export after every capture.
7. Where Your Archive Lives
FactLockCam is local-first:
- On your device: Sealed media is stored as encrypted
.sealfiles in the app sandbox. This is the archive you browse, verify, and export from the app. - On our servers (optional sync): After sealing, ciphertext may upload for the same signed-in account. These blobs are zero-knowledge—we cannot read them, and they are not a user-managed media backup you download from a dashboard. They can help re-sync after reinstall only when you import your .factlock keys and sign in with the same email.
- Send Proof (courier): Time-limited recipient links are delivery channels, not a substitute for your .factlock key backup.
8. Key Custody Scenarios
Losing your keys without a .factlock backup means permanent loss of access to
all encrypted assets—local .seal files and any cloud ciphertext for your
account.
| Scenario | Local keys | Local .seal | Cloud + account | .factlock backup |
|---|---|---|---|---|
| Normal use | Present | Present | Present if sync ran | Optional; re-export periodically or before Lock/uninstall |
Keys lost (no .factlock) | Gone | Unreadable | Unreadable | N/A — total loss |
| Lock Archive | Purged from device | Remain on device | Unchanged on server | Import to unlock app and read local archive again |
| App uninstalled | Gone (OS wipes sandbox) | Usually gone with app data | Still on server for same email | Must import after reinstall + sign-in to decrypt cloud sync |
| Burn Account | Purged locally | Wiped locally | Account and linked cloud data deleted | Useless for that burned identity |
Lock Archive ≠ Burn Account. Lock removes keys from this device but leaves local sealed files; import .factlock to resume. Burn permanently deletes your Supabase identity, associated cloud ciphertext, local archive, and keys—a prior .factlock cannot restore a burned account or its cloud archive.
9. Burn Account Is Irreversible
Burn Account (Account & Settings, with double confirmation) permanently destroys your remote account, profile-linked cloud storage, local archive database and sealed files, and cryptographic keys on the device. A .factlock file created before Burn cannot resurrect that identity or decrypt cloud data tied to the burned account. You may create a new account with the same email only as a fresh identity with no restored prior archive.
10. Integrity Maintenance
If the original file is modified or access to the certifying identity is lost, the link to the blockchain record is broken. FactLockCam cannot restore this connection.
11. Secure Delivery Expiration
The FactLockCam delivery system allows for secure, time-limited file access. Assets may have an expiration policy or limited access attempts. FactLockCam is not liable for assets that become inaccessible after expiration. Users are responsible for managing access permissions for their recipients.
12. Limitation of Liability
A certificate draft is a mathematical record of a digital state. It is not a guarantee of physical truth, accuracy of content, or legal standing. FactLockCam documents that a file existed in an exact state at an exact time; it does not verify the underlying claims within the file.
13. Service Availability
Services are provided "as is". FactLockCam is not liable for blockchain network congestion, device-level hardware failure, or third-party service interruptions that may affect the transmission or verification of assets.