GRAVE CLIENTPRIVACY POLICY
Working draft — not yet effective. This page must be checked against the released service and reviewed before publication.
1. Who operates the service
Grave Client is an independent launcher project. The legal name and contact address of the data controller must be supplied before public release. This draft distinguishes currently observed website behaviour from proposed future launcher features.
2. Current static website
The supplied static website contains no built-in registration form or first-party analytics script in this release preparation. It stores the selected light/dark theme in browser local storage. A deployed web host may separately log requests and IP addresses; its actual practices must be checked and described before publication.
3. Launcher accounts and authentication
The launcher supports a Microsoft sign-in flow for Minecraft Java Edition. Depending on implementation, authentication can involve account identifiers, Minecraft profile name/UUID and temporary access or refresh tokens. The final policy must identify which values are retained, for how long, where they are stored and how they are secured. Never disclose passwords to Grave Client.
4. Technical and diagnostic information
Future releases may process launcher version, operating system, crash diagnostics, errors and performance measurements to maintain reliability and security. We must identify the actual fields and any optional collection before enabling telemetry. Sensitive data should be minimised or redacted.
5. Mod and server interactions
Searching for mods or using featured servers may involve requests to third-party APIs or servers, which can receive network information such as IP address. The launcher may locally store selected versions, profiles, installed mods and preferences. The precise processing must be confirmed against released code.
6. Purposes and legal bases
Potential purposes include delivering requested features, account authentication, fraud and security prevention, technical support and optional analytics or advertising. For UK and other applicable privacy laws, the appropriate lawful basis for each purpose must be recorded before collection. Optional nonessential tracking may require consent.
7. Advertising and sponsorships
Grave Client may later show clearly labelled sponsored server placements or advertisements. This draft does not mean behavioural advertising is already enabled. Any advertising identifiers, partners, profiling and user controls must be described before deployment, with consent where required.
8. Cookies and similar technologies
Essential technologies may support security and preferences. The current static site stores theme preference in local storage. If nonessential analytics or advertising cookies are added, a suitable consent mechanism and cookie details must be provided where required.
9. Sharing and service providers
Potential recipients may include web hosts, infrastructure providers, Microsoft sign-in services, mod catalogue providers, crash-reporting vendors or future advertising partners. Actual processors, international transfers and safeguards must be verified and documented before launch. We do not claim to sell personal information.
10. Retention and security
Personal data should be kept only as long as needed for the stated purpose, with access restrictions and appropriate technical safeguards. Specific retention periods, storage locations, backup practices and deletion procedures must be documented before public launch.
11. Your choices and rights
Depending on applicable law, you may have rights to access, correct, erase, restrict or object to processing, withdraw consent and complain to a regulator such as the UK Information Commissioner’s Office. A working contact channel and request process must be published before launch.
12. Children and younger users
We must account for age-appropriate privacy design and any applicable parental permission or consent requirements. Personalised advertising and profiling involving children require particular care and may be inappropriate. We will not assume an arbitrary 18+ age limit.
13. International transfers
If personal data is processed outside the UK or other applicable jurisdiction, the transfer mechanism and relevant safeguards must be disclosed after confirming actual providers and locations.
14. Changes and contact
Draft prepared 25 October 2026. The final policy must state an effective date, operator identity, privacy contact, accurate current collection, retention periods, processors and any necessary consent choices before publication.