Support and corrections
Contact
Contact MemoriesGame for corrections, image issues, character name fixes, rights requests, accessibility notes and suggestions for new memory games.
What you can send
Use the contact channel for missing characters, incorrect names, broken images, rights-related requests, accessibility issues, language corrections or suggestions for new memory game variations.
When reporting a correction, include the page URL, the character or work name and a short explanation of what should change.
Responsible contact
MemoriesGame is maintained by Kevin Henrique. The best public contact point is KevinBK, where you can find project information and contact paths.
How to make a useful correction
The fastest corrections usually include four details: the full page URL, the current name or image, the suggested correction and the reason for the change. For example, if a character has an alternate spelling, include the version that should appear on the card and where that spelling is commonly used.
For broken images, duplicated cards or a work in the wrong category, mention whether the issue appears on mobile, desktop or both. If the same mistake appears across several pages, one clear example is enough to start the review.
Rights, removals and attribution concerns
If you represent a rights holder, artist, studio, publisher or licensing partner, send the page URL and explain the requested correction, replacement or removal. MemoriesGame is built as an independent play and discovery experience, and rights-related requests are treated with priority.
When a request involves an image, include the file or page where it appears and the material that should replace it if available. This helps avoid removing useful pages when a simple correction would solve the problem.
Public contact paths
The public project contact is handled through Kevin Henrique and the Suki Desu network. You can start through KevinBK or write to contato@skdesu.com with a clear subject related to MemoriesGame.
Messages about partnerships, suggestions for new categories, accessibility reports and privacy requests should include enough context to identify the page or feature involved.