These articles explain how local encryption works — they are not a substitute for the tools. Current pieces cover why an LLM relay can still sell Agent call logs as-is after SSH private keys and cloud tokens go into a prompt, why, after you close a burn-after-reading tab, the key after # can still come back from Recently closed tabs, why pasting that link into a chat that generates a preview does not always use up the read, why clipboard history still keeps plaintext after you copy a generated password, why format redaction can still point to the same customer before you paste a ticket into a chat AI, what UTM and click IDs carry when a campaign link is forwarded, why a rotated API key should not go back into chat after an env leak, and why a URL hash fragment never shows up in server logs. The facts match the tools: no accounts, and plaintext stays off the server by default.
Newest first. Titles and summaries match the article topic—not the product definition on the home page, and not the how-to on each tool page.
A relay must read plaintext before it can forward. SSH keys and cloud tokens in an Agent prompt land in call logs that can be sold as a bundle. Compare what format redaction covers on the spot. Open immediately — source text is not uploaded.
Read the articleClosing the tab does not erase the # key. Session history keeps the full URL; Recently closed tabs can reopen it. Check a dummy link with Ctrl+Shift+T. Opens immediately — plaintext stays off the request by default.
Read the articleA card in the channel is not the same as the recipient reading ciphertext. A preview fetch usually reads the page title. It does not click Open and view, and it does not take the key after #. Check it with a dummy link. Opens immediately — plaintext stays off the request by default.
Read the articleA browser Copy button writes the system clipboard, not a password-manager exclude flag. Win+V keeps up to 25 items. With sync or Universal Clipboard, plaintext can reach another device. Check it with Win+V. Open immediately — the password stays off the request.
Read the articleStarring a phone number does not mean a ticket can no longer point to one person. Compare the six formats format redaction covers, and the names, addresses, and ticket IDs it leaves. Open immediately — source text is not uploaded.
Read the articleWhen a coworker, a support agent, or a customer forwards a campaign URL, utm_source, fbclid, and igshid travel into chat, tickets, and access logs. Separate business query fields from trackers, then check the local strip list. Open immediately — source text is not uploaded.
Revoking the old key is only half the job. Once the new API key is pasted into Slack, a screenshot, or a ticket, you leave a searchable, syncable, archivable plaintext copy. Check residue channels, then hand off with a local-encrypted one-time link. Open immediately — no sign-up.
Read the articleWhen a browser sends an HTTP request, text after # stays local. Burn-Link appends the decryption key after # in s.html?id={id}#{key}: the server only receives a ciphertext id, not the key. The read page is public to the recipient—no sign-up.
Articles cover concrete problems from engineering, support, and outbound backups. Algorithms, permissions, and what is uploaded match the live tools. We do not invent a second set of promises.
.lock / .enc.
# fragment.
Articles answer “why” and “how to check”: for example, why encryption stays in the current tab, and why a # fragment never enters an HTTP request. To generate a password, clean a link, or create a Burn-Link, open the matching tool page—you do not need to finish the article first.
# fragment. The key stays in the address bar and is not sent with the request.
Articles are not a substitute for the tools. To send ciphertext once, encrypt a file up to 5 GB locally, or confirm we are not a password manager, open the matching page.