Your accounts.
Your important secrets.

New in 1.3.1

Choose your unlock duration

After unlocking, choose when the extension should lock and save that preference. You can change it later from the visible lock-policy control or Vault settings.

• When I leave the vault: lock when the extension popup closes.
• When Chrome closes: lock when the last normal Chrome window closes.
• Keep open during this Chrome session: no inactivity timer; closing the popup does not lock. A full browser restart, extension reload/update, explicit lock or connection expiry still ends the unlock session.
• After inactivity: lock after 1, 5 or 15 minutes.

Keeping a vault open only until the computer shuts down, while surviving a full Chrome restart, requires a separate desktop session service. That option is unavailable in this browser-only release; it does not pretend to detect a computer restart.

Cloud website and the paired extension

The Cloud website also offers lock choices after unlocking. Its manual mode keeps the key only in the current page's memory and can keep the vault open when moving between Cloud sections. Closing or reloading that page ends its in-page session.

To keep Cloud unlocked across page reloads until Chrome closes, install this local extension update and pair it with the same Cloud account and vault. Selecting Cloud's browser-close policy explicitly allows a separate website unlock grant in trusted extension session memory. The bridge runs only on https://cloud.alsalibi.de; it does not grant other websites access. No master passphrase or plaintext key is written to persistent storage. Cloud's explicit Lock, account sign-out, extension global Lock/disconnect, last-normal-window closure and browser startup revoke that grant. Automatic locking of the popup alone remains independent of this selected website policy.

Save protected Wi-Fi networks with SSID, password, security type and hidden-network setting. Secure notes can contain recovery codes, API keys and other private text. These items stay encrypted and are never offered for website filling.

The toolbar icon displays a green count of login accounts for the exact matching HTTPS website. Locking the vault hides the count. Enable Save and fill prompts and grant optional HTTPS site access once, then reload existing website tabs. A complete supported login can show a review prompt while you type; click it and review the draft before saving.

Cloud has category counts, a searchable list and a separate detail pane on desktop; mobile opens the selected item's details with a back button. Password health checks cover website logins and remain local.

Update a local extension

1. Download and extract the update.
2. Back up your existing extension folder, then copy the new runtime files into that same folder.
3. Reload Alsalibi Passwords in Chrome's extensions page. Keep its existing ID and connection by retaining the folder.
4. Check that the header shows v1.3.1, unlock and enable Save and fill prompts.

This file does not automatically replace a store-installed extension. A separately loaded local copy may need a new connection code. Use Chrome 127 or newer. The extension saves Wi-Fi passwords you enter; it does not extract the operating system's saved networks.

Import existing Chrome passwords

In Google Password Manager settings, export a CSV file, then choose Import from Chrome in Alsalibi Passwords. Review new, duplicate, conflicting and invalid counts before confirming. Parsing and encryption happen locally; only ciphertext is synchronized. Delete the plaintext CSV after successful import. This is migration, not continuous Google Password Manager synchronization.

Install and connect

1. Open Alsalibi Passwords in the Chrome Web Store and choose Add to Chrome.
2. Open Keys & passwords in Alsalibi Cloud. Sign in with your Cloud account.
3. In Alsalibi Cloud, open Passwords → Connect browser. Create the vault first if needed, then generate a one-use connection code. It expires after five minutes.
4. Open Alsalibi Passwords, read its data-handling disclosure and paste that code. Use the separate vault passphrase to unlock.
5. Open an HTTPS sign-in page, open the extension and choose the matching account. Press Fill. Supported visible forms are filled; you submit the form yourself.

Keys backups in Cloud

The Cloud backup panel has separate Check new and Upload new buttons. It shows whether the current vault revision is saved in the dedicated Passwords folder. Checking does not create a folder or copy. Uploading creates a complete encrypted snapshot, and a confirmed identical revision is not copied again.

In More → Vault settings, you can independently enable automatic snapshots after changes or every 7, 14, 21, 30 or 365 days. This is off by default and checks due work when you unlock, refresh or save while using the extension; it does not promise an exact background execution time. Normal encrypted synchronization continues independently. Retained snapshots are managed in Cloud and can contain older entries you have since changed or deleted.

Vault passphrases

New vault passphrases and passphrase changes accept 6–50 characters. A longer, unique passphrase provides better protection. Existing vault passphrases remain usable for unlocking. The extension uses the same encrypted vault format as the Cloud app; Cloud cannot recover a forgotten vault passphrase.

What to expect

Creating the Cloud vault happens in the Cloud app. Pairing, unlocking, refreshing and saving require access to cloud.alsalibi.de. The extension supports Arabic, English and German. It does not synchronize Chrome's separate bookmark tree; saved links belong to the encrypted vault.

Filling is limited to the selected, matching HTTPS site and a supported visible form in the main frame. If a form cannot be identified safely, use the explicit Copy action. Local password indicators check length and exact reuse; they do not perform an online breach scan. Browser Face ID or biometric unlock is not implemented in this extension.

Manage a connection

Use the lock-policy control or More → Vault settings to change when the vault locks. Choose Disconnect browser to remove this browser's encrypted cache and token. To revoke a server-side browser connection, use the Cloud app. Downloaded backups remain on your computer until you delete them.

Support

Email info@alsalibi.de with your browser version and a description of the problem. Do not send passwords, connection codes or encrypted-vault keys.

Read the extension privacy policy.