WrittenCheck

Contact us

Email is the only way to reach us. A person on the team reads every message.

Email us. We read every message.
writtenchecksupport@gmail.com

We're a small team, so replies can take a few working days. We write back in English. You're welcome to write in any language the detector supports, and we'll do our best.

Reporting a wrong result

If the detector got something wrong, we'd like to know. It helps us find weak spots and improve the next version. Please tell us:

  • the score and confidence you got,
  • the language of the text,
  • whether a person or an AI wrote it, as far as you know,
  • roughly how long the text was.

You can include the text if you're happy to share it. We only use it to look into the problem. We won't publish it, and we delete it once we're done. Please don't send texts that contain someone else's personal details.

Bugs and problems with the site

Tell us what you did, what you expected and what happened instead. The device, browser and page address help a lot. A screenshot is welcome.

Mistakes in a blog post

If you spot a factual error, a broken link or an out-of-date source in one of our articles, email us with the article's address and what's wrong. We check every report and correct real mistakes. See our editorial policy for how corrections work.

Privacy requests

For questions about your data, or to have a blog comment removed, email us with "Privacy" in the subject line. The privacy policy explains what little we collect.

Copyright and other legal notices

If you believe something on this site infringes your rights, email us with the page address, what you own and what you'd like us to do. We'll look into it and reply.

Feedback and ideas

Want a new language, a new feature or a guide on a topic? Tell us. Many of our improvements start with an email from someone using the tool.

Before you write

The answer may already be on the site. How it works explains scores, test results and limits. The terms of use and disclaimer explain how results should and shouldn't be used.