Security
We don't ask you to trust us. We built Traccer so you don't have to. Your vault is encrypted on your device with keys only you control.
Architecture
Traditional password managers store your encrypted vault on their servers. Even though it's encrypted, it's still a target. A breach exposes encrypted data. A shutdown loses your access. A subpoena could compel them to hand it over.
Traccer has no central vault servers. Your vault exists only on your devices. Sync happens directly between them using peer-to-peer technology. There's no corporate database with millions of users' encrypted vaults.
Zero-Knowledge
"Zero-knowledge" is an overused marketing term. Here's what it actually means for Traccer.
Before your vault data ever leaves your device, it's encrypted with keys derived from your master password. We never see the plaintext.
Your master key is derived from your password using Argon2id — a memory-hard algorithm that makes brute-force attacks impractical. That derivation happens on your device. We never see your password or the resulting key.
We didn't build a recovery mechanism that lets us decrypt your vault. If you lose your password and recovery key, your vault is gone. That's the tradeoff for real security.
We use standard, audited algorithms — AES-256-GCM, Ed25519, Argon2id, Shamir's Secret Sharing. Not proprietary "military-grade" anything. Real cryptography that experts can verify.
Cryptography
| Purpose | Algorithm | Why |
|---|---|---|
| Password to key | Argon2id |
Memory-hard KDF, resistant to GPU attacks |
| Vault encryption | AES-256-GCM |
Authenticated encryption, industry standard |
| Digital signatures | Ed25519 |
Fast, secure signatures for sync and Pulse |
| Key splitting | Shamir's Secret Sharing |
Distribute recovery across guardians |
| Recovery phrase | BIP39 |
Standard for human-readable backup phrases |
We build on audited, open-source libraries: @noble/hashes, @noble/ciphers, @noble/ed25519, @scure/bip39. The same libraries used by MetaMask, Ethers.js, and major DeFi protocols. Audited by Trail of Bits and Cure53.
Transparency
We believe in complete transparency. Here's exactly what stays on your devices and what touches our services — and why they're architecturally separate systems that cannot access each other.
Architecturally separate: Our notification relay and billing services are completely isolated systems. They have no access to vault data because they don't have the endpoints, APIs, or encryption keys to request or decrypt it. The relay service only knows "send an email to this address" — not what's in your vault. These systems cannot intermingle by design.
P2P Technology
Your devices find and sync with each other using distributed hash table (DHT) technology — the same approach used by BitTorrent and other decentralized systems.
Your devices announce themselves to a distributed network of nodes. No single server knows where all devices are.
Once your devices find each other, they connect directly. Data transfers between them, not through us.
When direct connection isn't possible (~30-40% of cases), encrypted packets route through relay nodes — but they only see encrypted data, not content.
Traccer's P2P infrastructure leverages Holepunch's technology, built on the TRAC Network — powering decentralized applications without central servers. Pulse check-ins are recorded on-chain for immutable proof of life.
Roadmap
Independent security audit by a recognized firm. Budget allocated.
Detailed technical documentation of our architecture and crypto implementation.
Rewards for responsibly disclosed vulnerabilities.
Core cryptographic modules available for review. Built on audited @noble/@scure libraries.
Your passwords, seed phrases, and memories deserve protection you can verify. Try Traccer and see the difference.
Start your free trialNo credit card required. Full features for 7 days.
