AUDITION 2 REVIVAL
Personal data
Audition 2 Revival personal data processing policy. Operator: sole proprietor Vadim Sergeevich Voevodin. Version: 2026-11-08.
Version: 8 November 2026
1. Why data is needed
Data is needed to create and protect your account, provide game access, save progress, investigate errors and handle enquiries. Registration creates the account directly without sending an email. The email address is stored as unverified and cannot on its own authorise password resets or account recovery. Data is not collected for promotional emails or sale to third parties.
Processing is based on actions requested by the user to provide the service, the necessary consents and the operator's legal obligations. Registration consent is given separately; simply visiting the website does not constitute consent.
2. What data is processed
Support emails do not need to include your password. Other players can see your profile and messages in public game chats; do not post personal information there.
- At registration: email address marked unverified, username and account identifier, profile gender, date of birth, salted password verifier, and a registration receipt with the versions and times of terms acceptance, policy acknowledgement and separate consent, plus an HMAC-derived IP identifier. Password confirmation is checked but is not stored separately.
- In the game: character name and appearance, progress, game statistics, social connections and messages needed for the relevant features to work.
- On connection: IP address, time, technical events and errors in authentication or the game service. Registration rate limiting stores an HMAC-derived IP identifier and attempt time, not the raw IP address in that attempt record. HMAC pseudonymisation does not make it non-personal data.
- When contacting support: information provided by the user, screenshots and diagnostic data the user chooses to send.
3. The website, email and diagnostics
The website does not use advertising trackers or third-party analytics. Registration uses a session cookie, __Host-au2_csrf, and a matching token to protect submissions. Direct registration sends no email and does not require a mail service. Email infrastructure processes the addresses and correspondence when you contact support by email; never send your password.
Technical service data and materials voluntarily sent to support are used to protect accounts and resolve problems. Do not attach other people's data, documents or secrets. Diagnostic data is not published with bug reports.
4. Storage, access and deletion
Account data and registration receipts are retained for the account lifecycle, subject to lawful termination and deletion requirements. Registration attempt records stop counting towards rate limits 24 hours after the attempt. Expired records are physically deleted on the next registration attempt; there is no separate cleanup timer while registrations are idle. Open beta game progress will be reset when testing ends; this does not automatically delete account data. Technical logs and backups do not justify indefinite retention.
The operator and authorised people or technical providers have access only to the extent needed to provide the service. Data may be disclosed to competent authorities where required by law. There are no public lists of email addresses or passwords.
Requests to access or correct data, stop processing, withdraw consent or delete an account can be sent to contact@dance-world.online or the operator's postal address. Include enough information to locate the account. The registration email is unverified: a matching sender address or access to that mailbox does not on its own prove account ownership. The operator checks identity and authority proportionately. Deleting an account may result in loss of progress; data that must be retained by law is kept only within that legal basis.
5. Contact and policy updates
The operator's contact details and postal address are available under “Project and operator”. When processing changes materially, a new version of the policy is published and, where necessary, renewed consent is requested.