Make a password that fits the account—not a template.

Control length and character sets, avoid ambiguous glyphs, and generate a fresh value locally for each account.

Your selected policy is applied before a cryptographically secure random value is produced.

Build a policy that the service accepts

Set a length from 8 to 128 characters. Select lowercase, uppercase, digits and symbols independently. The generator requires at least one selected set, includes one character from each enabled set, fills the remainder uniformly, and shuffles the result with cryptographic randomness.

Exclude commonly confused characters when a service or human workflow needs it
Tune length instead of relying on a named preset
The estimated entropy is a model of the generator, not a promise of account security

Use it safely

Generate one distinct credential per account. Copy it directly into the destination or an approved password manager. Do not reuse a password, send it through chat or paste it into a support ticket. Turn on multi-factor authentication for email, administrator accounts and other high-impact services.

The generator never submits the value to the API
Saving is a separate, explicit action
Clipboard contents may remain available to other software on your device

Technical note

Random selection uses the browser's Web Crypto API and rejection sampling to avoid simple modulo bias. Generation requires a secure browser context. If Web Crypto is unavailable, the app stops instead of falling back to Math.random or showing a sample value.

Use the production HTTPS address
Keep your browser updated
A security strength estimate describes the generator—not the account's full security

How to read an entropy estimate

For independent, uniform selections from an alphabet with A possible symbols, a length L string has an idealized space of A raised to L. Its logarithmic size is L × log₂(A) bits. When a policy requires at least one symbol from several classes, the valid set is smaller; the generator's estimate should reflect the actual accepted output space rather than simply multiplying alphabet size by length.

Entropy is measured in bits of idealized search space
The model assumes the random source behaves as intended
It says nothing about phishing, malware, reuse or recovery weaknesses

Compatibility is a user choice

Some sites impose awkward character rules or reject long values. Treat character-set controls as destination compatibility settings, not as a universal recipe for security. Current NIST guidance emphasizes length and blocklists and advises against mandatory composition rules; a generator can still help you produce a value accepted by a particular service.

Prefer the longest value the destination accepts
Do not add predictable patterns to satisfy a rule unless the service requires it
Use a password manager so unique long values remain practical

A careful hand-off

After generation, the value appears on screen and may enter the operating system clipboard. Anyone with access to the unlocked device may be able to observe it. Paste only into the intended sign-in or password manager, then consider clearing the clipboard if the device is shared. If you save to Nuvquerio, use a separate vault passphrase you can reliably preserve.

Confirm the destination before copying
Avoid screenshots and shared-device clipboard history
Rotate the credential at the destination if exposure is suspected

Security is a workflow, not a label.

Review the implementation boundaries