Contact

One address, read by the people who write the pages. There is no contact form on this site, because a form would mean sending your message through a third-party service, and this site does not send anything anywhere.

What to include

Factual corrections

These are the most valuable messages we get. Please include the page URL, the specific sentence you believe is wrong, and the primary source that contradicts it, provider documentation, the text of the regulation, or the Unicode Standard. Our corrections policy describes what happens next: substantive corrections change the page and move its "Last verified" date, and we say what changed rather than editing quietly.

A character the checker gets wrong

Two kinds of report, both useful:

• A character it misses. Tell us the code point, where you found it, and what it broke. If it is invisible, disruptive and appears in real text, it probably belongs in the table.
• A character it removes that it should keep. These matter more. If the cleaner damages text in a script we have not handled correctly, that is a bug we will prioritise. Please include the script and an example, and describe what the correct output should be.

Do not paste confidential text into an email to us. A description of the code points involved is enough, and the x-ray view gives you exactly that.

Privacy and data requests

Use the same address, and say clearly what you are asking for. Note that we hold very little: text you check never reaches us at all, and the only record connected to you is a consent choice stored in your own browser, which you can clear yourself from the privacy page.

Press and research

Happy to talk about how statistical watermarking differs from character-level marking, why third-party detection claims do not hold up, and what invisible characters do to production systems. We will decline to speculate about unannounced vendor plans.

What we cannot help with

• Determining whether a specific piece of text was AI-generated. Nobody can do this reliably from text alone, and we will not pretend otherwise.
• Removing a statistical watermark. It is not something a text tool can do, and we do not offer a workaround.
• Rewriting, paraphrasing or editing text. That is not what this site does.
• Support for other people's tools that claim to detect vendor watermarks.

Related pages

• About and methodology - how the pages here are researched and corrected.
• Privacy policy - what data exists and what does not.
• Terms of use - the short version of what this service is.