Keep passwords, files, and OTPon a device you control.
ChromVoid keeps the vault locally or on your phone. Browsers, desktop apps, and workflow tools receive temporary access for a specific action without moving the vault into a cloud account or browser profile.
Proof that the boundary is real
Coercion, device compromise, copied storage, and OPSEC assumptions are documented.
Choose Local mode or Mobile host before a browser or cloud account enters the workflow.
The extension receives grants from localhost instead of becoming another vault.
USB, WebRTC, and WSS carry encrypted traffic without becoming the trust anchor.
Deniability, live-device safety, and recovery all have documented limits.
When a password manager isn't enough
Some secrets need to stay useful without spreading trust into every surface that touches them.
Border checks, legal pressure, shared devices, browser autofill, copied vault files, and compromised live sessions are different risks. Treating them as one flat sync problem hides the boundary you actually need.
A single exposed app surface can reveal passwords, files, notes, and recovery paths together.
Data can leak into previews, clipboard history, temp storage, autofill, and sync layers.
Fast unlocks help daily work, but they do not always keep sensitive secrets away from browser profiles, previews, or temporary files.
Not every tool separates secrets by exposure level, device state, or the action that needs access.
Sensitive data can outgrow the place where you thought it lived.
Apps, sync layers, previews, and autofill expand what has to be trusted.
Travel, shared devices, recovery, and professional secrets often need a smaller disclosure boundary than ordinary autofill.
One controlled vault boundary for daily secrets
and pressure scenarios.
Start with passwords, OTP, notes, and files in a local vault. Add phone-held secrets, decoy vaults, localhost-only browser access, and workflow-specific approvals only where they reduce real exposure.
chromvoid/vault- Connect via SSH
- Verify host key
- Elevate with sudo
- Check system status
Stronger boundaries when your threat model demands them.
Plausible vault for regular accounts and low-risk data.
Different passwords unlock different secret surfaces.
Store logins and one-time codes without making a cloud account the main storage place.
Keep sensitive documents in encrypted vaults instead of loose files and previews.
Fill or copy secrets through temporary localhost permissions that do not turn the browser into a vault.
Use Mobile host, decoy vaults, and approvals when legal pressure, border search, or custody workflows need more.
Three decisions: where secrets live
what clients can learn.
Choose where the vault lives, connect apps and tools as clients, then give temporary permissions (grants) for specific actions. The value is less trust spread, not broader hiding.
Decoy vaults support controlled disclosure.
Hidden vaults keep limits visible.
Deniability is controlled disclosure for specific threat models. A decoy vault can hold routine low-risk data, while hidden vaults reduce obvious inventory markers. The limits depend on storage, device state, OPSEC, and the public Threat Model.
Architecture that keeps trust from spreading.
ChromVoid separates apps and tools from the place where the vault lives. Browser, desktop, and transport paths can do useful work without becoming storage.
Use the same boundary model across daily work and pressure workflows.
Each workflow starts with a user job: fill, mount, sign, recover, or connect remotely. The boundary decides what the surface can learn before the outcome happens.
Basic vault path is free.Pro adds advanced workflows.
Pro is one license for advanced workflow modules. Encryption, KDF, local vault architecture, and documented limits stay in the baseline.
For personal use, local vaults, and first supported workflows.
Start here if your platform has a current build below.
For Remote Access, Credential Provider, SSH Agent, Wallet, and Emergency Access when the module is available for your platform and runtime.
LDL means Lifetime Device License: a one-time license for Pro modules on up to three Core devices. Modules activate only when platform availability and runtime capability allow.
Encryption, KDF, local vault architecture, and documented limits are included in the basic vault path. Pro adds scale and convenience for advanced workflows.
Module and platform availability
This landing matrix is informational. Runtime access is still decided by platform support, module availability, and Core-authoritative entitlement checks.
Check which build is ready for your platform.
Builds are published as platforms become ready. Check the current platform state before installing or planning a setup.
Planned for upcoming releases.
Latest Android APK is published on GitHub Releases.
Planned for upcoming releases.
Planned for upcoming releases.
Planned for upcoming releases.
Short answers before you start.
Start with fit, limits, and platform status. Proof pages go deeper where it matters.
1.Who is ChromVoid for?
For people whose secrets face more than ordinary sync risk: security teams, privacy users, journalists, lawyers, activists, crypto operators, and anyone who needs local or phone-held boundaries.
2.Why not use a normal password manager?
Normal managers are good at convenience and sync. ChromVoid is for cases where browsers, cloud accounts, transport paths, or shared devices should not become the place where secrets live.
3.What does deniability mean here?
Decoy and hidden vaults support controlled disclosure, but the guarantees depend on device state, storage, OPSEC, and the public Threat Model.
4.What is ready today?
The basic vault path and selected platform builds are the starting point. Extended modules activate only when the module and platform runtime are available.
5.Is this overkill for daily use?
No. The basic path behaves like a local vault. Stricter boundaries are opt-in for workflows that need them.
6.Does the browser extension store passwords?
No. It talks to the local Desktop Gateway and receives temporary permissions (grants); it does not store the vault.
7.What if my storage files are copied?
Vault files are encrypted at rest, but master-password strength, key material, device state, and backups still matter.
8.What does ChromVoid not protect against?
No vault fully protects a compromised live device. ChromVoid reduces specific exposure paths; it does not replace OPSEC.
9.Are builds available now?
Some platforms have builds; others are in progress or planned. Check the availability matrix before installing.
10.What is LDL?
LDL is the Lifetime Device License for Pro modules on up to three Core devices when the module and platform runtime are available.
11.Where can I verify the security model?
Start with the public Threat Model, architecture diagrams, and GitHub repository before installing.
Download ChromVoid for your platform
after checking the threat model.
If secrets should stay useful without becoming cloud, browser, or sync-layer state, start with the download matrix and inspect the public security model before installing.
Core safety is not an upsell.Deniability has documented limits.Current limitations are documented publicly.