Contact
Bug reports about counting are the most useful thing you can send.
Get in touch
Email is the only channel, and there is no contact form — a form would mean a server receiving text, which is exactly what this site is built to avoid.
Everything arrives in one inbox and is read by the person who wrote the site. Expect a reply within a few days rather than within the hour; this is an independent project, not a support desk with a rota. Reports that come with enough detail to reproduce the problem are the ones that get fixed first, simply because they can be.
Reporting a counting problem
If a number looks wrong, the report that gets it fixed fastest includes: the exact text (or a short sample that reproduces it), the number you expected, the number you saw, and what you compared it against.
Differences from a word processor are often a genuine rule difference rather than a bug — hyphens and hyperlinks are the usual culprits — but they are still worth reporting, because the rules should at least be documented clearly enough to explain the gap.
Accessibility
If something here is difficult or impossible to use with a keyboard, a screen reader or magnification, that is treated as a defect and not as an enhancement request. Please say which assistive technology and browser you were using.
The site is built to meet WCAG 2.1 AA and is tested at each release for contrast, focus order, keyboard reachability and screen-reader labelling. Automated checks catch a useful fraction of accessibility problems and miss the rest, so a report from somebody actually using the thing is worth more than any audit tool.
Translation and language
The site is published in English and Brazilian Portuguese, and both versions are written rather than machine-translated. That means both can be wrong in the ordinary way writing is wrong: an awkward phrase, a term that is not what people in the field actually say, an example that does not travel.
If a sentence in either language reads as though it were translated, that is a defect worth reporting. Point at the page and the phrase, and say what a person would say instead.
Privacy questions and data requests
The privacy policy covers what happens to your text, which is nothing, and what is stored on your device, which is a short list of preferences. If something there is unclear or appears to contradict what the site does, that is worth an email — a privacy policy that does not match the software is a bug in one of them.
There is no account and no server-side record of you, so there is no stored profile to request, export or erase. Advertising cookies set by Google can be inspected and switched off through the links in the privacy policy, and clearing this site's data in your browser removes every preference it has saved.
Suggestions, and what will not be built
Suggestions for new counts, new presets or new modes are welcome, particularly when they come with the situation that prompted them. The situation is the useful part: it is much easier to design the right feature from a description of the deadline somebody was up against than from a description of the feature.
Two things are settled and will not change. This site will not generate, rewrite, expand or complete text, and it will not send what you write to a server. Requests for either are not ignored out of stubbornness — they are the two constraints everything else here is built on top of.