Offline-first security apps have a practical challenge: people use more than one device. A vault that never leaves one phone can be very private, but it can also be inconvenient. LockWhisper v8 addresses that tension with private device sync for supported vault data.
Sync Without a LockWhisper Account
LockWhisper v8 does not require a LockWhisper account or a central cloud database for vault contents. Instead, supported data can move directly between trusted devices over encrypted peer-to-peer connections. The user chooses when to sync and which trusted device participates.
Why Peer-to-Peer Matters
Traditional cloud sync centralizes encrypted vault copies on a provider server. That creates a high-value target and adds account recovery, server retention, and infrastructure trust questions. Peer-to-peer sync narrows the model: the transfer is between devices the user controls, not through a LockWhisper-hosted vault service.
Supported Data, Not Magic Replication
It is important to be precise: v8 sync applies to supported vault data. Some modules, migrations, attachments, or app states may have their own handling rules. That wording matters because security software should avoid implying that every byte of every possible local state is automatically replicated.
Sync Complements Export
LockWhisper still supports deliberate import and export workflows. Export is useful for backup, migration, and long-term custody. Peer-to-peer sync is better for moving supported data between active devices. Both approaches keep the user in control of when data leaves the device.
The Local-First Trade-Off
Private device sync is not trying to copy the convenience model of a cloud password manager. It is a different trade-off: fewer centralized dependencies, less account infrastructure, and more deliberate movement of sensitive data. For users who choose LockWhisper because they do not want a hosted vault, that distinction is the feature.