Store and organize encryption keys locally with labels, expiry dates, and key type metadata. All data in IndexedDB.
Build a local catalog of encryption keys by saving each key with a label, an expiry date, and key-type metadata in the browser's IndexedDB storage. This is an organizer, so its useful result is a set of identifiable records rather than ciphertext, a derived key, or a cryptographic validity decision. The easy mistake is to read "local" as "automatically encrypted": local storage describes where the records stay, not whether the saved key material has an additional vault-encryption layer.
A saved item combines the key material with the label, expiry date, and key type supplied for that record. The manager writes that record to IndexedDB for this site's origin, allowing it to remain available across ordinary visits in the same browser profile. The documented purpose is record keeping; saving an entry is not evidence that its contents are cryptographically valid or match the declared type.
Labels distinguish keys that may otherwise look alike, while the expiry field records the date chosen by the user. These fields describe the catalog entry; they do not establish cryptographic validity, ownership, revocation status, or safe use. An expiry date should be treated as management information unless the interface explicitly indicates that an action is blocked or a record is removed.
No. The stated storage location is IndexedDB in the current browser, so creating and consulting records does not require sending key material to a server. That does not make the data immune to local access or loss: anyone or anything with suitable access to the same browser profile and site origin may present a risk.
Do not assume it does. The description establishes local IndexedDB storage, but it does not establish a master password, a separate wrapping key, or application-level encryption of stored records. Device or browser protections may exist outside this tool, but they are not a substitute for a documented vault feature when the stored material is sensitive.
The behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.
Generate strong, random passwords with customizable length, character sets, and complexity requirements.
Analyze password strength with entropy scoring, crack-time estimates, and improvement suggestions.
Create cryptographically random strings for API keys, tokens, salts, and unique identifiers.
Create QR codes for URLs, text, Wi-Fi credentials, vCards, and more with customizable size and colors.
Scan and decode QR codes from uploaded images or your device camera to extract embedded data.
Compute MD5, SHA-1, SHA-256, and SHA-512 checksums to verify file integrity and detect tampering.