The primary contact address is contact@modu.tools.
Contact
Contact modu.tools
For site questions, privacy questions, feedback, or domain inquiries, email contact@modu.tools.
Privacy requests
Include "privacy" in the subject line if the request is about privacy, cookies, advertising disclosures, or data handling.
Editorial
Guides and tool documentation are maintained by modu.tools Editorial.
Domain inquiries
If you are asking about the `modu.tools` domain, include your intended use and preferred contact method in the email.
Bugs versus content mistakes
A tool bug is something you can reproduce: the same input yields the wrong count, valid JSON is rejected, or a control is unusable with a keyboard. A content mistake is a wrong limit in a table, a claim that disagrees with the cited source, or a broken in-site link. Suggestions should fit a browser-local static utility site; we may decline ideas that need accounts or server-side storage of user drafts.
What we can help with
Write to contact@modu.tools about tool bugs (a control that miscounts, a converter that rejects valid input, an accessibility issue you can reproduce), content errors in guides or tool documentation, and product suggestions that fit a browser-local static site. Privacy and advertising disclosure questions belong here too; put “privacy” in the subject as noted above.
We do not offer custom development, account recovery for third-party apps, or legal advice. If the question is unrelated to modu.tools, we may not be able to help.
How to report a mistake
A useful report includes: (1) the full page URL, (2) a short quote of the sentence, table cell, or UI label that looks wrong, and (3) a primary source when the claim is about a rule or limit—for example a National Institute of Korean Language page, an RFC, MDN, Kakao Business docs, or SOLAPI guidance. Screenshots help for UI bugs; for encoding issues, paste a minimal sample string that reproduces the problem.
We aim to review reports and to update the page and changelog when a fix is confirmed. Please do not send passwords, personal documents, or live API keys—examples can be masked.