Contact
If you need help with the site, want to report a content issue, or have a privacy, account, or collaboration request, you can use the contact details below.
Last updated: July 21, 2026 · Public support contact for the maintained mmccode.com learning site.
Primary contact
Main contact email: 415417421@qq.com
Helpful subject lines include account issue, sync problem, bug report, privacy request, content correction, or collaboration.
Topics you can contact us about
Registration failures, password changes, login problems, or account access questions.
Cloud sync failures, missing progress, score issues, or unexpected ranking results.
Tutorial errors, unclear copy, broken links, translation mistakes, or policy-page corrections.
Data requests, account deletion questions, advertising questions, or collaboration outreach.
What to include when reporting a problem
Tell us exactly where the issue happened, such as login, profile, a training mode, or a specific tutorial page.
Describe the intended result and what the site actually did instead, including any visible error text.
Include your browser, approximate device type, and when the issue happened so it is easier to trace.
A screenshot or short screen recording is often the fastest way to explain layout, rendering, or account-state issues.
Privacy and account requests
If you need help with account records, cloud data removal, or other privacy-related questions, please state the request clearly in your email subject line. That makes it easier to route the request correctly.
For account-specific requests, include the relevant account email address and enough context to verify which record needs to be reviewed.
Advertising and partnerships
Advertising questions do not buy coverage or guarantee editorial placement. Commercial requests are handled separately from tutorial review and corrections so public learning content can stay credible for readers.
If your message is about ads, partnerships, or business outreach, review the Advertising page first, then contact the site through the main email with enough detail about the request. If your message is about content accuracy or corrections, use the public Editorial Policy as the review standard.
Before you email
If your question is about how to start, what screen to use, why audio is not playing, or how sync should behave, please check the Help Center and FAQ first. Those pages answer the most common public questions directly.
Direct email is still the right path for account-specific, privacy-related, or repeating technical issues that need case-by-case review.
When a public page is not enough
Public pages are the fastest answer for common questions, but they cannot see your individual account state, your specific sync history, or the exact conditions of a private bug. If the issue depends on your account, a failed login, a suspected privacy problem, or a repeated device-specific fault, direct contact is usually the correct next step.
This distinction helps keep the support path clear. Public content answers repeat questions for everyone, while contact exists for the cases that truly need person-specific review and follow-up.
What not to send in a first message
Do not send passwords, payment card information, or unrelated personal documents in a first support email. If the issue is technical, the most useful starting details are usually the page URL, device type, browser, account email, approximate time, and what action failed.
A focused first message is safer and easier to review. It reduces back-and-forth, protects your personal information, and makes it much easier to separate a real product issue from a misunderstanding about workflow or policy.
Project links
Public site: https://www.mmccode.com
GitHub repository: https://github.com/daijiandian/morse-trainer
Help Center: https://www.mmccode.com/help.html
FAQ: https://www.mmccode.com/faq.html
Editorial policy: https://www.mmccode.com/editorial-policy.html
Response expectations
A reply is usually sent within 3 to 5 business days. Requests that involve account review, data handling, or cross-service debugging may take longer depending on complexity.
Sending one clear email with complete context is more helpful than sending multiple short follow-ups without technical details.
If the issue resolves on its own after a reload or later sync, a short follow-up note is still helpful because it clarifies whether the original report was transient or repeatable.