UnoLock Threat Model

UnoLock brings client-side encryption, registered access keys and deliberate recovery choices together to protect the information you value. This overview connects common threats with the implemented controls that support your Safe.

Private content from the start

Files, notes, messages and private user-authored metadata are encrypted on your device before storage. Private names, titles, filenames and Space labels stay client-encrypted, giving important information a protected home beyond a readable cloud account.

Access you choose

Normal access combines a registered WebAuthn passkey or security key, a PIN and service authorization. The randomized image keypad lets you select the PIN without typing it. Additional access keys and Space permissions let you organize access around the devices and workflows you choose.

Forward-looking cryptography

AES-256-GCM protects client-encrypted content. ML-KEM-1024 and ML-DSA-65 are used in protected API connections and Vault Messaging. The client creates and wraps its content keys for later authorized use.

Compartmentalized sharing

Spaces separate different parts of your life. Shared Spaces let separate Safes work together, while Protected Spaces require the configured approval threshold before a requesting client reconstructs the Space key for its session.

Prepared responses and continuity

Sovereign hides marked sensitive Spaces when you enter the safeword PIN. HighRisk permanently deletes those marked Spaces while other Spaces remain available. Exit with Time Lock pauses the current access key for a selected whole-day period.

Lockout Guard prepares your own recovery path; LegacyLink prepares a path for a trusted successor. Save the generated recovery material outside the Safe and choose inactivity and delay settings as part of your plan.

Storage and hosting choice

Managed Spaces offer the storage-region choices shown in the app. Self-hosted nodes store encrypted archives on local disks, with explicit active/standby pairing available for replication. Independent Space backups add another route to recovery.

Threats and implemented controls

Threat	Implemented controls
Readable copies of private records in storage	Client-side content encryption, encrypted user-authored metadata and client-held keyrings.
Stolen reusable account passwords	Registered WebAuthn access keys, PIN authorization and server-enforced attempt controls.
Simple PIN keystroke logging	Randomized image keypad with click-based entry.
Network interception	HTTPS, protected API sessions and the Vault Messaging encryption protocol.
Unexpected browser interference	CSP and runtime checks for recognized API changes, injected elements and overlays.
Overly broad access	Separate access keys, Space permissions, Shared Spaces and Protected Space approvals.
Loss of an ordinary access device	Additional registered keys, prepared Lockout Guard recovery and independent backups.
Unplanned succession	LegacyLink recovery material, inactivity settings and instructions prepared for a trusted successor.

Updates and application delivery

The browser app uses HTTPS delivery, CSP and SHA-256 asset checks. Ready updates activate at startup before authentication. Release manifests and verification artifacts support independent checks; installed Tauri packages use their packaged-code and native update paths.

Explore the security features, Lockout Guard and LegacyLink to build a protection and recovery plan around what matters to you.