Use test data when possible
Use the demo or a dedicated test account for configuration checks. For routine sign-ins, use an authenticator that fits your security requirements.
Browser risks still apply
A compromised device, browser extension, page script, or clipboard tool may expose sensitive data. Local calculation alone cannot eliminate these risks.
Keep setup data private
Do not put secrets in public links, screenshots, issue reports, or support messages. Use Clear after a task, and close the page when finished.
What the tools do not verify
A code or valid URI does not prove ownership of an account. These tools do not bypass authentication, enroll keys with a service, or recover lost access.
Report a concern
Use the contact method published on the Contact page. Describe the issue with test data; do not send live setup keys, passwords, or recovery codes.