How to choose consistent account labels
A label separates deterministic credentials. Learn a naming system that stays private, stable, and easy to recreate.
What a label does
The label acts as account-specific context. The same master inputs with “email-personal” and “shopping-main” should produce different outputs.
Build a stable convention
Choose a format before creating many accounts. For example: service purpose, account role, and optional revision. Keep capitalization and punctuation consistent because exact differences may change outputs.
What to avoid
Do not put passwords, PINs, recovery codes, or highly sensitive personal details in labels. Avoid conventions you are likely to rename later.
When a password must change
A deterministic system needs a reproducible way to rotate credentials. One approach is a revision suffix such as “-v2”. Record the non-secret revision without recording the generated password.
Keep a non-secret index
You may maintain a list of service names, labels, versions, and revision numbers. This index is useful for recovery and is less sensitive than a password list, though it should still be protected.