Support / About

Local encryption tools, not a password manager

UsePwd is a set of local encryption tools in your browser, not a password manager. Generate a password, check its strength, clean tracking URLs, share a one-time secret, or encrypt a file — all with Web Crypto and AES-256-GCM in this tab. There is no account, and we do not keep your secrets.

No sign-up No vault Never uploaded
01 / Identity

What it is, and what it is not

Drop the brand name and this page answers whether this is a password manager. The home page covers what the product does; the Privacy Policy covers what the server receives.

UsePwd is
  • A local-first toolkit Five public pages generate, audit, clean, and encrypt in the browser. Plaintext, keys, and files are not sent as request bodies by default.
  • No sign-up No sign-up or sign-in. The top bar only has a language switch—no user menu.
  • Checkable on the spot Strength grades, before/after cleanup, and Burn-Link burned states are all visible in the current tab.
UsePwd is not
  • Not a password manager There is no vault, no device sync, and no way to recover a password you generated as “a user.”
  • Not a web-wide breach lookup Password Audit checks a public weak-password list shipped with the page. It does not query an external breach API.
  • Not a hosted helpdesk No support email, and no promised uptime percentage or response time.
02 / Choice

Why we do not run a vault

An account would mean we keep a record that belongs to someone. We choose not to keep that record.

Many sites ask you to register, then store secrets in their vault. UsePwd does the opposite: the tool finishes in the current tab, and after you close it the server has no plaintext it can look up by user. For long-term storage, put the result in a password manager or device you control—we do not host it, so we cannot recover it for you.

Burn-Link is the only tool that sends ciphertext to the server: text is encrypted locally with AES-256-GCM, and the key is appended after # as s.html?id={id}#{key}. The read page is public to the recipient; ciphertext is deleted after the read limit or expiry. That is still not a vault—there is no account, and the server cannot restore plaintext.

03 / Who uses it

No need to register first

Engineering, support, and outbound backups can open the matching page and finish there. The three links below go to live tools, not a roadmap.

04 / Checkable

What you can see on the spot

Any site can print a slogan. UsePwd only writes promises you can verify in the current tab: where computation runs, what is not uploaded, and whether you must register first.

Where it runs 01 Generation, audits, cleanup, and file encryption use the browser Web Crypto API in the current tab.
What is not uploaded 02 Plaintext is not put in the request body by default. Burn-Link only submits ciphertext; the key stays in the # fragment.
No sign-up 03 No sign-in dialog and no “add to vault.” The top bar only has a language switch.
Written limits 04 Data handling is in the Privacy Policy. Terms of use are in the Terms of Service.
05 / Limits

What we do not provide

Trust comes from what you can check. The items below are outside UsePwd’s scope, and this page will not describe them as upcoming features.

Storage and recovery 01 We do not store, sync, or restore your passwords, cleanup source text, or encrypted files by account.
Web-wide breach lookup 02 Password Audit is not Have I Been Pwned. Missing the built-in list does not mean a password was never leaked.
Complete redaction guarantees 03 Privacy Cleanup follows common formats and cannot catch everything. Review important outbound text yourself.
Support and SLA 04 No support email, and no promised uptime percentage, response time, or compensation terms.
06 / FAQ

Start with identity

No. UsePwd is a browser-local encryption and privacy toolkit. There is no account, and we do not store your secrets. For long-term storage, put them in a password manager you control.

Is it a password manager 01 No. We are a local toolkit. There is no vault, and we do not keep your secrets.
Why no sign-up 02 Without accounts, there is no plaintext we can look up by user. Open, use, and leave.
Where passwords live 03 Only in the current tab. Copy or export if you need to keep them. There is no vault on this site.
How to verify 04 Open the Network panel and inspect the request body. The key sits after # in the address and is not sent with HTTP.
How to reach us 05 There is no support email. Rules are in the Terms of Service; data limits are in the Privacy Policy.
07 / Next

Once identity is clear, use the tools

This page is not a substitute for the tools. To generate a local password, send a one-time secret, or check what the server receives, open the matching page.