Privacy policy
How the site, browser storage, public contact channels, and third-party platforms handle information.
Last updated: August 4, 2026. The effective date is the date this page is publicly published.
1. Scope
This policy applies to the content and contact channels controlled by us on the LunaDeerMC official website and its documentation pages. It does not apply to GitHub, Afdian, KeyAnchor, QQ, Modrinth, Minecraft server platforms, website hosts, or other third-party services. Once you enter those services, their privacy policies and user agreements apply.
This policy describes current handling practices only. If a work, community, or external service has a separate privacy notice, read that notice first.
2. Information we may handle
Information you provide
When you contact the maintenance team by email, GitHub Issue, QQ group, or another public or private channel, you may choose to provide:
- your name, nickname, email address, QQ number, or another contact method;
- an order ID, purchase record, license information, or other materials used to verify an entitlement;
- a problem description, logs, configuration excerpts, attachments, device details, or runtime-environment information;
- comments, Issues, code, screenshots, or other content you post on a public channel.
We use this information only as necessary to answer questions, provide technical support, verify transactions, maintain community order, handle security issues, or comply with legal obligations. Remove passwords, access tokens, license keys, home addresses, payment-card numbers, and other unnecessary sensitive information before submitting logs.
Technical information generated when you visit
The website host, CDN, network operator, or related infrastructure may generate access logs according to how it operates. Logs may include an IP address, access time, request path, HTTP status code, browser and operating-system identifiers, and referring page. We do not determine every field or retention period recorded by third-party infrastructure; check the relevant service’s policy for those details.
As of the date of this policy update, the site has no site accounts, site comments, internal contact form, online-payment backend, or advertising/analytics user-profiling system. Site-search parameters are used only for the in-page search interaction and are not connected to a site account.
Browser storage
To remember your theme choice, the site may store a theme preference in the browser’s localStorage. Work pages may temporarily store GitHub Releases query results in sessionStorage for the current browsing session to reduce repeated requests. This information normally remains on your device or in the current browser session; it is not used to create a site account or identify your real-world identity. Clearing site data in the browser removes the relevant entries.
3. How we use information
We use information received directly for the following purposes:
- providing, maintaining, and improving the website, docs, and work;
- responding to collaboration, technical-support, refund, or security questions;
- verifying orders, licenses, and the requester’s identity, and preventing abuse, fraud, and repeated claims;
- diagnosing failures and protecting the security and stability of the site and work;
- complying with applicable laws, regulatory requirements, or dispute-handling needs.
Unless you authorize it, the law requires it, or it is necessary to complete a service you requested, we do not sell your personal information or build a long-term profile unrelated to your use of the site.
4. Sharing and third-party services
Downloads, code hosting, version information, payments, license activation, file extraction, and community communication may open on third-party platforms. Information you submit on those platforms is received and handled directly by the relevant platform, for example:
- GitHub may handle repositories, Issues, Release queries, and account activity;
- Afdian may handle sponsorships, product purchases, orders, and payment-related information;
- KeyAnchor may handle information needed for license activation, resource extraction, and one-on-one support;
- QQ, Modrinth, hosts, CDNs, and other services may handle accounts, devices, logs, and content under their own rules.
Some work-page features make a direct browser request to the GitHub API. This request is not proxied by the site server, so GitHub may see the network and device information needed for the request. We do not control third-party privacy practices, retention, cross-border transfers, account security, or service availability. Before submitting information to an external platform, make sure you understand its policy and provide only what is necessary.
Information may also be provided to necessary service providers, professional advisers, or competent authorities when needed to provide a requested service, protect the site and users, handle legal proceedings, or comply with a binding legal requirement. We limit such handling to what is reasonably necessary and do not use it for unrelated purposes.
5. Retention and security
We keep emails, support records, and transaction-verification materials sent directly to the maintenance team for as long as needed to complete the matter, handle potential disputes, or meet necessary legal obligations. When no longer needed, we delete, anonymize, or stop using them. Public-platform content and account data are retained according to the platform’s rules and the user’s management of that account.
We use access controls, data minimization, and security-management measures appropriate to the team’s size and the processing context. Internet transmission, email, and third-party platforms cannot be guaranteed to be completely secure. Use private channels for necessary materials and do not expose credentials on public pages.
6. Your rights and how to make a request
For information you provided directly to the maintenance team, contact zhangyuheng@lunadeer.cn to request access, a copy, correction, deletion, withdrawal of authorization, or cessation of use. To protect information security, we may request reasonable identity or entitlement-verification materials; verification materials are used only to process the request.
If information was collected directly by GitHub, Afdian, KeyAnchor, QQ, or another third-party platform, send requests for access, correction, deletion, account closure, or payment records to that platform. Information that must be retained by law, used to handle a dispute, or kept to protect another person’s rights may not be deleted immediately; we will explain the reason where applicable rules allow.
7. Children
The site is not intended to collect children’s personal information. Children should access the site and submit information to external platforms under a guardian’s guidance. If a guardian believes that a child provided unnecessary personal information to the maintenance team, contact us at the email above so we can verify and handle it.
8. Updates and contact
If the site adds accounts, forms, analytics, advertising, payment, or another feature that materially changes information handling, we will update this policy before or when the feature goes live and provide additional information where necessary.
For privacy questions, requests, or security issues, email zhangyuheng@lunadeer.cn. For data held by a third-party platform, contact that platform as well.