1. Scope
This policy applies to public pages and tools under the domain usepwd.com and its language directories (such as /en/). The operating display name is UsePwd.
This policy does not cover: what happens after you store a generated result in your own password manager; screenshots, copies, or forwards on the recipient’s device after you send a Burn-Link; or where a downloaded .lock / .enc file is stored off this device.
2. What no accounts means
Every tool works immediately — no sign-up. The site does not offer sign-up, sign-in, user profiles, or a vault, so it does not collect emails, usernames, or login passwords, and it does not issue login sessions.
Because there is no account, we cannot look up, export, or restore plaintext you once typed on a page as “a user.” If you need to keep something, copy, export, or download it to a device you control.
3. What stays in the browser by default
Password generation, Password Audit, privacy cleanup, and file encryption finish in the current tab using the browser Web Crypto API. The following are not sent to UsePwd as an HTTP request body by default, and are not written to analytics:
| Tool | Local handling | Is plaintext uploaded |
|---|---|---|
| Password Generator | Draws 6–128 character random strings or a readable passphrase with Web Crypto | No. After you close the page, the server has no copy of that plaintext |
| Password Audit | Estimates entropy and crack time locally, and checks a built-in public leaked-password list | No. Not a web-wide lookup, and the password is not sent to an external API |
| Privacy Cleanup | Strips tracking parameters from links; redacts phones, ID numbers, emails, and API keys | No. Pasted links and source text are not uploaded and are not written to analytics |
| File Encryption Box | Streaming AES-256-GCM encrypt/decrypt, one file up to 5 GB, written as .lock / .enc |
No. The file, passphrase, and filename are not uploaded; the server also never receives this ciphertext |
| Burn-Link | Encrypts or decrypts with AES-256-GCM in the current tab | Plaintext and the key are not sent as the request body. The server only stores ciphertext—see the next section |
4. Fields Burn-Link actually uploads
When you create a Burn-Link, the text is encrypted in the current tab first. The only fields sent to the server are:
ciphertext: encrypted ciphertextttl_hours: the lifetime you set, in hoursmax_reads: how many times it may be read
The decryption key is appended in the share URL # fragment as s.html?id={id}#{key}. The browser does not put text after # in the HTTP request, and access logs do not have that segment. The server cannot see plaintext and cannot decrypt for you.
After the recipient opens the read page and reaches the count you set, or after the TTL, ciphertext on the server is deleted and cannot be read again. A lost link also cannot recover a plaintext backup from the server.
5. Analytics
In production, the site uses self-hosted Matomo to record page views, link clicks, and the category and name of button actions (for example, “Copy password” or “Create link”). These events only describe which control you used. They do not include generated passwords, test secrets, cleanup source text, file contents, or Burn-Link plaintext.
Analytics requests go to the site path /tj/ and do not pass through a third-party ad network. Local previews (localhost / 127.0.0.1) do not send analytics. The analytics script may use a first-party cookie to tell returning visits from unique visitors.
6. Local storage
The language switch writes the directory you chose to browser localStorage so the next visit stays on the same language site. Plaintext, keys, and files produced by the tools are not written to localStorage or sessionStorage.
Clearing site data in the browser also removes the language preference and analytics cookies. That does not change whether a Burn-Link ciphertext is still stored on the server—that depends only on that link’s TTL and read count.
7. Opening a page
Visiting any web page produces HTTPS requests. Hosting and protection layers usually keep ordinary access records, such as IP address, User-Agent, request path, and time. Those records run the site. They do not include plaintext, files, or Burn-Link key fragments you typed in a tool.
8. How long we keep data
- Local tool results: exist only in the current tab. Content you did not copy, export, or download yourself will not appear on any remote after you close or refresh.
- Burn-Link ciphertext: stored using the
ttl_hoursandmax_readswritten at create time, and deleted on expiry or when the count is reached. - Language preference: stays in your browser until you clear site data or choose another language.
- Analytics and hosting logs: used to see whether pages work and which actions are used. They are not bound to a piece of plaintext. This policy does not promise a specific number of days.
9. What you can do
- If you only use the Password Generator, Password Audit, Privacy Cleanup, or File Encryption Box, you do not submit those tools’ plaintext or ciphertext to the server.
- If you do not create a Burn-Link, you do not submit ciphertext to the server.
- You can block or clear first-party cookies and
localStoragein browser settings. After cookies are blocked, language memory and some visit stats may stop working; the tools themselves still open and work. - You cannot ask us for “passwords saved in an account”—the site has no accounts and no vault.
10. Minors
The tools work on open. The site does not collect personal information from children on purpose, and it has no sign-up flow that would require a guardian’s consent. If you are a guardian, decide for yourself whether a minor may use these local tools.
11. How this policy is updated
If the local-compute scope, Burn-Link upload fields, or analytics boundary changes, we will rewrite this page and update the “Last updated” date above. Continued use of the site means you understand data handling as written in the updated text.
This page does not provide a support email. Terms of use are in the Terms of Service. To check on the spot whether a password, file, or key left the browser, open the notes on the matching tool page. Do not treat this policy as a how-to.