Technical deep-dive
Peach is built so that the strongest claims are architectural, not procedural: no hosted vaults, no account database, and no product telemetry stream to "promise" not to misuse. The trust boundary stays on your device and on explicitly paired peers on the local network.
peach:v3:entries=247:zstd:aes256gcm:argon2id
Zero-knowledge vault encryption
Zero server dependency
No account creation
No product telemetry
Local-network peer-to-peer sync only
Portable PeachScript restore path
Peach encrypts vault data locally before it ever leaves process memory boundaries intended for serialization. PeachScript backups are derived from the encrypted container rather than from plaintext records.
There is no hosted account system and no recovery server. Recovery is handled on-device: a 12-word sequence generated locally when you set up Peach, and PeachScript backups you export yourself.
PeachScript is a dense textual transport wrapper around the encrypted vault package. Each export is a point-in-time snapshot of the vault data in that moment. Peach maps encrypted bytes into private-use runes so the backup remains copyable, storable, and restorable with the backup password instead of any vendor backend.
Sync is peer-to-peer on the local network. New devices are introduced through Chirp — an ultrasonic audio handshake — and after that, paired devices authenticate each other with Noise XX on every connection and exchange encrypted vault deltas without relaying through a third-party service.
Peach is designed to remove server-side breach classes, account takeover risk, and silent product telemetry collection. It does not claim to defeat a fully compromised endpoint or a user who reveals the unlock secret.
security fundamentals
Peach doesn't ask you to trust a company. The security claims are enforced by the code running on your machine.
Peach is built on TypeScript and SolidJS.
We designed Peach so that even we cannot read your passwords.
The only outbound connections are opt-in breach monitoring and an opt-in bug reporting system. Bug reports record only device type — for example, iPhone 15 or MacBook Air M2. No user IDs, no IP addresses, no account required.
Peach never asks for your email, your name, or any identifying information to use the product. There is no user database. There are no users—only installations.
Checkout is handled by Polar. Licenses are generated after payment and sent to your email within seconds. Purchaser information is not passed into Peach product infrastructure.
There is no Peach backend, no hosted vault service, no account system, and no customer database. When Peach is “breached,” there is no central vault trove or user table to steal.
Your vault is yours. Export as a standard CSV to move to any password manager, as PeachScript to restore into Peach on another device, or as a Peach Codex to keep a physical backup in a safe. No lock-in. No export fee.
Your license works offline forever. If Peach development stopped tomorrow, your installed copy would keep working indefinitely. No phone-home, no expiration.
extension | service worker | passkeys
extension | service worker | passkeys
Keystore TEE | biometric | autofill service | beta
Secure Enclave | Face ID
Peach does not require network access to unlock, browse, edit, export, or continue using a licensed installation. With no user-initiated action, there is no background service to contact.
Three flows can touch the network: Peach Sync when paired devices exchange encrypted data on the local network; breach monitoring when a k-anonymity prefix is sent for password exposure checks; and an optional, opt-in feedback and bug reporting system. The feedback system records no user-identifiable information — only device type (for example, iPhone 15 or MacBook Air M2). None of these paths creates a hosted Peach account or remote Peach vault.