Yunvy documents
Privacy policy
Last updated: [DATE]
Draft — requires legal review
This is a draft document for the upcoming launch, not a confirmation of current practices or compliance. Fields in square brackets must be completed by the developer after review.
We want the rules for handling data to be clear before the first battle. Below is the full structure of the draft policy for Yunvy. Until the developer confirms the actual practices, the capabilities described here should not be read as a description of a service that is already live.
1. Who is responsible for the data
This policy is meant to explain how personal data is processed in Yunvy, on the game’s website and when you contact the developer. Responsible party: [DEVELOPER NAME]. Contact for privacy questions: info@yunvy.org.
Before publication, the legal status, country and address of the responsible party must be stated, as well as the territory the document applies to. Availability of the mobile game and the future web version should be described separately if their practices differ.
To be completed: [STATUS AND ADDRESS OF THE RESPONSIBLE PARTY], [TERRITORY].
2. What data may be processed
The actual list of data has not been confirmed yet. Before launch, it should be checked whether an account, saved game progress, technical logs, device identifiers and support messages are planned. The categories listed are a checklist for review, not a statement that they are collected.
For each confirmed category, specify the source, the specific fields, whether providing them is mandatory and the consequences of refusing. Explain separately which data stays only on the device and which is sent to the developer or other recipients.
Not confirmed: [DATA CATEGORIES], [SOURCES], [LOCAL OR SERVER STORAGE].
3. Purposes and legal bases for processing
Each confirmed data category must be linked to a specific purpose: for example, running game features, replying to requests or fixing bugs. These are possible scenarios for assessment; their actual use must be confirmed by the developer.
Before publication, determine the appropriate legal basis for each operation under applicable law. If consent is required, explain how it is obtained and withdrawn. Do not treat installing the game as automatic consent to any processing.
To be determined: [PURPOSE FOR EACH CATEGORY], [LEGAL BASES].
4. Third parties and SDKs
The set of third-party services, libraries and SDKs has not been confirmed yet. Before launch, the game build and the website must be audited for analytics, crash reporting, advertising, cloud saves, payments or other external integrations.
For each actual provider, state its name, role, the data involved, the purpose of the transfer, the countries of processing and a link to its policy. Where needed, describe international transfers and the relevant safeguards. This draft neither confirms nor rules out any SDK.
Not confirmed: [PROVIDERS AND SDKS], [DATA TRANSFERS], [LINKS TO POLICIES].
5. Children and information for parents
The game is designed for school and university students, but the age rating, minimum age and rules for children’s access have not been set yet. Before launch, they must be aligned with the game’s actual features, Google Play requirements and applicable law.
If processing a child’s data requires the consent of a legal guardian, describe how that consent is obtained and verified. Parents or legal guardians can send questions to info@yunvy.org. The procedure for verifying authority and handling such requests must be defined before publication.
To be determined: [AGE RESTRICTIONS], [RULES FOR CHILDREN], [PARENTAL CONSENT PROCEDURE, IF REQUIRED].
6. Retention and security
Retention periods, data locations and security measures have not been confirmed yet. For each category, a specific period or clear criteria for setting it must be established, including backups and data held by third-party providers.
In the final policy, describe the organisational and technical measures actually in place without promising absolute security. If certain records must be kept because of legal obligations, explain their list, basis and retention period separately.
Not confirmed: [RETENTION PERIODS], [STORAGE LOCATION], [SECURITY MEASURES].
7. Your rights and requests
Depending on applicable law, you may have the right to access, correct, delete, restrict processing of, object to or port your data, and to withdraw consent. The scope of these rights and how to exercise them must be clarified in the final version.
To make a request, write to info@yunvy.org and briefly describe it. Do not send your password. The identity verification method, response time, possible exceptions and the supervisory authority contact must be defined before publication. How to request deletion is also described on a separate page.
To be completed: [PROCEDURE AND RESPONSE TIME], [SUPERVISORY AUTHORITY, IF APPLICABLE].