Why there is no contact form
A form on a static, database-free site has only two honest options: hand the message to the server's mail function, which on shared hosting is unreliable and easily abused, or post it to a third-party form service, which would mean sending visitor data to a company you did not choose. Neither is worth it for a site whose whole point is that nothing you type leaves your browser. Email keeps the promise intact.
What to include in a bug report
A report that can be reproduced gets fixed; a vague one usually cannot. Useful details:
- Which tool you were using, and the URL of the page.
- What you expected to happen, and what happened instead.
- The smallest piece of text that shows the problem. Please redact anything confidential — a two-line example is almost always enough.
- Which options were ticked, including any dropdown selection.
- Your browser and version, and whether you were on a phone, tablet or desktop.
Requesting a new tool
Suggestions are genuinely useful. The most helpful requests describe a task rather than a feature: what you are trying to achieve, what you currently do instead, and why the existing four tools do not cover it. Requests that fit the project's constraints — no server-side processing of your text, no accounts, no third-party scripts — have the best chance of being built.
Reporting a legal or content problem
If something on this site infringes your rights or contains an error you want corrected, email the same address with “Legal” in the subject line and include the URL and a description of the problem.
Please do not send confidential text. Bug reports are read by a human and kept in an inbox, unlike the tools themselves. A short synthetic example is always enough to demonstrate a formatting or counting problem.
Response times
This is a small independent project, so replies are not instant. Reports of incorrect output and accessibility problems are prioritised over feature requests.