Claustra, from claustra.app, is a local-first password manager extension built to keep credential storage on the user's machine rather than in the cloud. It captures logins, offers fast search and in-page autofill while operating as a browser client that accesses an encrypted vault stored locally. Highlights include one-click autofill, smart site matching, advanced vault search, and a system-following dark mode. The tool targets privacy-conscious macOS users who want direct control over their credentials and keys.

How does the extension connect to your password store?

The extension acts as a browser client that communicates with a dedicated macOS desktop application, so the encrypted vault is handled on the host Mac rather than on external servers. That architecture means the extension depends on a paired desktop component for read and write operations, and the browser plugin itself primarily relays requests to the local application rather than storing credentials inside the browser profile.

What encryption and telemetry policies protect your data?

Claustra uses AES-256-GCM to encrypt the local database and implements a zero-knowledge model so the developer has no access to your keys. The extension is distributed with a strict no-analytics policy and contains no telemetry or tracking scripts, which reduces data exposure beyond the machine where the vault resides. Those choices minimize third-party data flows and place responsibility for backups with the user.

How does it behave in the browser and which browsers are supported?

The browser component is a lightweight Chromium extension that supports Chrome and other Chromium-based browsers such as Edge, Brave, and Vivaldi. In practice the client provides in-page autofill and search queries without adding a heavyweight UI layer to the tab, and it follows system appearance settings so dark mode aligns with macOS appearance preferences.

What operational trade-offs should you expect?

Because the product avoids cloud storage, there is no remote password reset or developer-side recovery; if the master password is lost the data cannot be recovered. The workflow therefore requires users to manage local backups and retain their master password. The design prioritizes device-level control and data sovereignty, which is a deliberate trade-off against cross-device cloud syncing.

Who benefits from this local-first approach and what to do next

Community feedback highlights a clean interface and a privacy-first orientation, making this a sensible choice for users who accept hands-on vault management. Practical advice: create an encrypted offline backup and store your master password in a secure place, since recovery is not available. For those prepared to manage backups and recovery themselves, the extension provides a focused, privacy-oriented alternative to cloud-based managers.