Privacy Policy

Last updated: October 11, 2026

Kingsreach has not launched publicly. This policy separates behavior found in the current source from requirements intended for public release. Every item marked TBD must be confirmed before launch; this page is not a completed privacy disclosure.

1. Controller and contact details

Kingsreach is published under the MikoAppz developer/publisher brand. MikoAppz is not presented as a registered business. The controller's legal identity and contact information are not confirmed:

Data controller's legal name: TBD
Registration/CVR number: TBD
Registered business address: TBD
Privacy contact email: TBD
Data protection officer contact, if applicable: TBD

2. Data and account identification

A unique Gameplay ID identifies each Kingsreach player account. The current pre-release client displays this identifier as the "Kingsreach ID". Current source code handles account and sign-in identifiers, player names, account-linked game state, and world chat message text, sender identifiers and names, and timestamps. The exact data categories in the release build must be confirmed before launch.

The developer intends to minimise the personal information collected. This is a product requirement, not a claim that collection has already been fully measured or independently verified. Account-linked gameplay data is needed to operate the multiplayer game and preserve player progress.

3. Purposes and legal bases

The current code uses account and sign-in data to authenticate players and associate accounts with game state. It uses game data to provide gameplay and chat data to provide world chat. The legal basis for each purpose, any legitimate-interest assessment, and whether consent is used are TBD and must be confirmed by the controller before publication.

4. World chat and moderation evidence

Release requirement: ordinary world chat messages must be deleted automatically no later than 180 days after they are created. This is a maximum retention limit, not an implemented guarantee. The current source stores chat messages, but automatic deletion within this period has not been verified and must be implemented and verified before public launch.

Moderation snapshots may be retained only when they are needed as evidence supporting an actual moderation action. A snapshot that does not support an actual action must be deleted. The moderation evidence retention and deletion process is unresolved and is not verified as operational. Its justified retention period and deletion controls are TBD; evidence must not be kept indefinitely without a defined justification and retention policy.

5. Sign-in providers and recipients

Current source includes Google sign-in and Apple Game Center sign-in. Provider-specific data exchanged, each provider's role, and any international transfers and safeguards are TBD. Hosting, database, support and other applicable processor identities, roles and locations are also TBD and must be confirmed before launch.

6. Planned subscriptions

Subscriptions are planned to be offered exclusively through Google Play or the Apple App Store and are not available for purchase in the current pre-release environment. Kingsreach does not directly collect or store payment card details. Whether any transaction or subscription status data is shared with or stored by Kingsreach, and the relevant store and other parties' roles, are TBD. Purchases, renewals and cancellations will be handled through the applicable store under its terms and applicable consumer law.

7. Other retention and legal exceptions

Account, gameplay, operational log and backup retention periods or criteria are TBD. Any information retained to meet a legal obligation must be identified with its purpose and retention period before launch. No category or period of legally required retention is asserted here. Security measures to disclose are also TBD.

8. Your privacy rights

Where the GDPR applies, you may have rights to access and correct your personal data, request erasure or restriction, object to certain processing, and receive data in a portable format where legal conditions are met. If processing relies on consent, you may withdraw it without affecting earlier lawful processing. You may complain to a competent data protection supervisory authority. Contact the controller using the privacy contact above; the response timeframe is the one required by applicable law.

9. Account deletion

Players must be able to request deletion of their account and associated game participation and data. The current source contains an in-game request path, but it is feature-gated and complete deletion is not operationally verified. See the Account or Data Deletion page. Deletion does not remove independent records controlled by Google or Apple. Any applicable legal retention exception, its purpose and period are TBD and must be explained before launch.

10. Age policy and updates

The intended age group, age rating and any child-specific data practices are TBD. We will update this policy if data practices change, and will complete the required privacy disclosures before public release.

For privacy questions, contact: TBD (privacy contact email).

Unresolved legal bases, controller details, processors, transfers, retention rules, security details and age-related practices remain TBD. The 180-day chat deletion rule and moderation evidence rules are release requirements, not verified current behavior. Store privacy declarations must match the released app.

← Back to Kingsreach