Corrections

Send correction reports to [email protected]. Include the page URL first, then the affected kanji, Card, Deck, Set, practice screen, or trust page when relevant.

A report can be short. What matters is that it points to the exact place, explains what looks wrong, and gives a suggested fix or supporting source when you have one.

Use a clear subject such as “Kanji Flash correction: 日 Card” or “Broken Deck link”. In the email, include the URL, affected item, issue, expected fix, and supporting source if available.

If the same problem appears across several pages, include one representative example first and say where else you noticed it.

You can report wrong readings, unclear meanings, awkward wording, useful-word issues, related-kanji issues, confusing Card or Deck membership, broken Kanji.Jepang.org links, layout problems, accessibility issues, practice behavior, and typos.

You can also report Contact, Privacy, Editorial Policy, Data Sources, or Disclaimer copy that feels unclear, unsupported, or too technical for learners.

Useful reports include a specific page URL, the relevant kanji or Deck name, the current text or behavior, what you expected instead, and a source or short reason when possible.

For kanji data, standard references, textbooks, official materials, or clear usage examples are helpful. For technical issues, include device, browser, and what happened.

Reports are reviewed before public changes are made. Kanji Flash compares corrections with available data and prioritizes fixes that improve learner understanding, source clarity, accessibility, or trust.

Kanji Flash does not guarantee that every suggestion will be accepted and does not promise a response time. Some reports need extra review, especially rare readings, specialist meanings, or disagreements between references.

For broader questions, use the Contact page. To understand content boundaries, read the Editorial Policy and Data Sources pages.

For questions about local progress, browser storage, imported saves, or exported saves, read the Privacy Policy.