Privacy Policy

1. Information we may collect

When you register, log in, or use sync features, the site may process your email address, display name, password hash, practice progress, sync history, statistics, and leaderboard-related records.

The service may also record basic technical data such as request time, route path, IP address, browser type, and device information for stability and security purposes.

2. How this information is used

We use these records to support account access, password changes, session management, progress sync, leaderboard scoring, service maintenance, abuse prevention, and product improvement.

We may also review limited operational information when users report bugs, broken pages, account problems, or security-related issues.

3. Local storage and cloud sync

The site may save some settings and training state in your browser, such as language preference and local progress data, so the experience can be restored when you return.

Cloud sync is used to recover your account data and learning progress across devices. The current public API endpoint is https://api.mmccode.com.

4. Data security

Passwords are not intended to be stored in plain text. Reasonable validation and access controls are used where possible, but no online service can guarantee absolute security.

Users should also protect their own devices, browsers, and passwords, because account safety depends partly on the environment used to access the site.

5. Cookies and similar technologies

The site may use browser storage, cookies, and similar technologies to remember preferences, keep sessions working, restore progress, improve reliability, and support security-related checks.

If advertising or analytics services are enabled, those services may also use cookies or device-level identifiers for reporting, fraud prevention, and ad delivery where permitted.

6. Third-party infrastructure and advertising services

The current site uses Cloudflare Pages, Workers, and related infrastructure. The site may also use third-party services for analytics, monitoring, or advertising, including Google AdSense when advertising is shown on the site.

Third-party vendors may process limited technical data needed to deliver their services, and their own privacy terms may also apply to that processing.

7. Access, correction, and deletion requests

If you want to review, correct, or request deletion of account-related data, contact 415417421@qq.com and clearly describe the request. Include enough account context for the request to be matched to the correct record.

Some requests may require additional verification before account data is changed or removed, especially when the request affects synced records or account access.

What can be visible on the leaderboard and what stays private

Leaderboard features may show limited public information such as a display name, rank position, recent score, or performance summary needed to compare practice results. Those elements are visible because the feature itself is competitive and would not work if all ranking data stayed completely hidden.

Private account details such as password material, email inbox contents, support messages, and most operational logs are not intended to appear on public ranking views. If a learner wants to limit visibility, using a neutral display name is usually the simplest first step.

8. Your controls and consent choices

You can log out, clear local browser data, reset practice progress, or clear cloud data from within the product where supported. You may also manage cookies and related storage through your browser settings.

If a consent notice is shown for your region, you may use it to review or change advertising-related choices where available. Disabling some storage features may affect how the site remembers progress or sessions.

9. Data retention

Local data stays on your device until you remove it or your browser clears it. Cloud records may remain while the account exists unless you delete them, clear them through available product controls, or request removal.

Operational records may also be retained for limited periods when needed for service stability, abuse prevention, support review, or legal compliance.

How deletion requests interact with backups and logs

When a deletion request is completed, the goal is to remove or de-identify the account data that is still actively used by the product. Some residual traces may remain for a limited time in security logs, error records, or short-lived backups until those systems rotate or expire under normal maintenance.

This does not mean the deleted account remains a normal active profile. It means that operational systems may need a short overlap period so that recovery, fraud review, and service integrity processes are not broken by immediate destructive erasure across every infrastructure layer at once.

10. Policy updates

This policy may change when product features, hosting, third-party services, or legal requirements change. The current version will be published on this page.

The visible updated date on this page identifies the current public version of the policy.

Continued use of the site after a policy update may mean you accept the updated terms of data handling for the services you continue to use.

For how public educational content is reviewed, corrected, and kept separate from advertising choices, see Editorial Policy.