TRUST, EXPLAINED

Security is the work. Not the badge.

A password manager earns its place through its design, tests, and review. Here’s the protection we’re working toward, and the checks still ahead.

Current state · 14 October 2026

Foundations built. Validation underway.

The development build now includes a local encrypted vault, passphrase unlock and locking, encrypted backups, and local import foundations. Security review, recovery testing, independent interoperability, and production migration coverage remain open.

Release checks still ahead

  • Security review and independent vault interoperability
  • Recovery and fresh-install backup validation
  • Migration coverage across actual source exports
  • Apple provisioning and live iCloud / AutoFill checks
  • App Store purchase and restoration validation
THE RELEASE DESIGN GOALS

Protection that stays understandable.

Development design · validation underway

Encrypt before it leaves.

Vault content will be encrypted on the device before syncing. Passwords, authenticator seeds, titles, domains, and tags belong inside encrypted content. The local encryption foundation is implemented; key handling and independent format interoperability remain under review.

Sync without a new account.

CloudKit’s private database is the planned v1 sync path. Local encrypted storage must remain usable offline, during outages, and when the iCloud account or quota changes. Concurrent edits must remain recoverable.

Unlock is not recovery.

Touch ID and Face ID development integrations provide convenient access on an authorized device. They are not a guarantee of recovery. Backup and recovery behavior must be tested and documented before public release.

An independent way out.

Encrypted backups must restore on a fresh installation without iCloud. A portable export and a tested path into another application are release requirements. Your data should not depend on our website staying online.

PLANNED SYNC DATA FLOW

Your devices do the encryption.

Your MacEncrypted local vault
Encrypted content
Your iCloudPrivate CloudKit storage
Encrypted content
Your iPhoneEncrypted local vault

No UnumVault vault backend is planned for v1. Necessary sync metadata and the final encryption design will be documented before launch.

Apple’s CloudKit private database documentation
BEFORE REAL PASSWORDS

The checks that matter.

No independent security audit has been completed. We’ll publish the scope and results of any review when it happens.

  1. 01

    Vault & keys

    Validate the chosen engine, derivation, device-key storage, tamper detection, lock behavior, and interrupted writes.

  2. 02

    Recovery & backup

    Test lost-device scenarios and fresh-install restoration. State clearly what happens if all unlock material is lost.

  3. 03

    Migration & AutoFill

    Account for source items and files; check duplicate behavior, authenticator preservation, website matching, and extension access.

  4. 04

    Sync & review

    Exercise concurrent edits, deletion conflicts, retries, account changes, and quota failures. Review the security-sensitive code before public release.

Found something that needs attention?

For a security concern, email support@unumvault.app. Share reproducible behavior without including real passwords, seeds, or vault exports. The app’s formal disclosure process will be published before public release.

Support & release status