Contact

A comparison gave the wrong result

This is the most useful thing you can send, and the reports genuinely drive the matching improvements. Include both inputs if you are able to share them, which language was selected in the picker, whether you were in Smart or Strict mode, and what you expected the result to be instead. A move reported as a delete-plus-add, or two blocks matched that should not have been, are both worth writing about.

If the text is confidential, please do not send it. A reduced example that still reproduces the problem is more useful than a real document you have to redact, and far less risky for you.

A language is missing

Syntax-aware comparison currently covers JavaScript, TypeScript, TSX, Python, JSON, CSS and HTML. Everything else is compared as prose or plain text, which works well for documents and less well for code with unusual block structure. Requests are tracked, and the ones that come up repeatedly get added first, so it is worth telling us which one you need.

Privacy and data questions

Your text never leaves your browser, so there is generally no stored data for us to look up, export, or delete — which is also why most data requests have a very short answer. If you want that confirmed in writing, or you have a question the privacy policy does not settle, write and ask.

Response times

This is a small project, not a support desk. Most messages get a reply within a few days. Bug reports with a reproducible example are answered first, because they are the ones that can actually be acted on.