Privacy Policy

1. General

1.1. This Privacy Policy (the "Policy") follows Federal Law No. 152-FZ of 27.07.2006 "On Personal Data" (the "Law") and sets out how personal data is processed and protected.

1.2. The operator is Klimov Artyom Konstantinovich (Климов Артём Константинович), INN 667222284833 (the "Operator"). Contact details are in section 14.

1.3. The Policy covers personal data the Operator receives through paradoxclient.com, the Paradox Client and launcher software, and the account services around them (together, the "Service").

1.4. The Operator shows no ads, uses no analytics SDK, tracking pixels or cookies, does not sell personal data and does not pass it to ad networks, data brokers or analytics companies.

1.5. The Policy is public at paradoxclient.com/privacy. Terms it does not define have the meaning given in the Law and the Public Offer.

2. Purposes

2.1. The Operator processes personal data to:

• register and run Paradox accounts;
• provide friends, direct messages, voice and cloud settings;
• conclude and perform the Paradox Plus contract, including payment, automatic renewal, refunds and tax accounting;
• handle user requests and claims;
• keep the Service working and secure.

3. Legal grounds

• performance of a contract with the data subject, or steps taken at their request before one (Article 6(1)(5) of the Law);
• the data subject's consent where data is given by choice: a profile picture, linked third-party accounts (Article 6(1)(1));
• obligations the Operator has under Russian law, including tax law (Article 6(1)(2)).

4. Data subjects and data

4.1. The Operator processes data of Service users and Paradox Plus customers. No special categories and no biometric data are processed.

4.2. Registration asks for an account name and a password, or a Google or GitHub sign-in, and nothing else. An account record holds:

name

The name the user chose, 3 to 20 characters. Not an email address.

uid

Eight random characters used to add friends. Never changes.

salt, hash

A random 16-byte salt and a PBKDF2-SHA256 password hash with 600,000 iterations. The password itself is never stored. Empty for Google or GitHub accounts until a password is set.

mojang, nick

If a Minecraft account is linked: its uuid, taken from Mojang's answer, and the last in-game name.

created

When the account was registered.

friends, invites

Friends and pending invitations.

privacy

What friends may see: position, dimension, game mode, health, inventory, waypoints, the client badge.

key, identity

Public X25519 and Ed25519 keys. Private keys are made on the user's device and never sent.

mail, receipts

Encrypted messages waiting for delivery, and delivery receipts.

configs

Saved client settings: title, share code and author name.

role, banned

The account role and whether access is restricted. Grounds for a restriction are in the Public Offer.

providers, email

Linked Google, GitHub or Discord accounts, and an email address if the provider gave one or the user entered it.

avatar

An optional profile picture the user uploaded.

plus, cosmetics

Subscription start and end dates, and cosmetics granted to the account.

device

The kind of the last connection: desktop (pc) or mobile (mobile).

4.3. A session is a random 32-byte token valid for 72 hours. At most five are kept at once. The server stores only a hash of each.

4.4. Signing in with Google, GitHub or Discord stores the provider, the user's permanent id there, the login or display name, and the email address if the provider gave it.

4.5. Paying for the Subscription stores the payment service invoice number, account name, plan, amount, payment method and time, and for automatic renewal the id of the first payment. Card details never reach the Operator.

4.6. Technical data: the IP address sent with every request, and the launcher version, operating system, CPU architecture and release channel that the launcher sends when it checks for updates, without an account name or device id.

5. How data is processed

5.1. Processing means collecting, recording, organising, accumulating, storing, updating, using, transferring in the cases in section 6, anonymising, blocking, deleting and destroying personal data, by automated means.

5.2. The client runs on the user's device. It contacts the Operator's server only after sign-in, and only for features that need it. The interface, modules and local settings work without the server.

5.3. Signing in to Microsoft happens between the user and Microsoft. The Microsoft password never reaches the Operator, and Microsoft tokens stay on the user's device. Game ownership is checked by the launcher asking Mojang, and the answer is not stored by the Operator.

5.4. Signing in with Google, GitHub or Discord never gives the Operator the provider password. The narrowest scopes are requested: openid email profile at Google, read:user at GitHub, identify at Discord. The provider token is used for one request and not kept. The email address is never used to sign in or to find an account.

5.5. Direct messages are end-to-end encrypted. The server keeps ciphertext only until it is delivered, at most 512 messages per mailbox, and has no key to decrypt it. Voice and screen sharing are encrypted between devices and not recorded.

5.6. Presence in game (position, dimension, game mode and anything else the user allows) goes only to accepted friends, lives in server memory for the connection and is never written to disk.

5.7. Server logs hold IP addresses and are used only to keep the Service running and investigate failures. They are not matched to accounts and not shared.

6. Transfer of data

6.1. Data goes only to services the user chose to use, and only what the request needs:

• Mojang and Microsoft, when signing in with Microsoft;
• Google, GitHub and Discord, when signing in or linking an account;
• the payment service: amount, plan and account name when paying. It processes payment data itself under its own rules.

6.2. The Operator provides data to public authorities where Russian law requires it.

7. Retention

• account data: until the account is deleted;
• sessions: 72 hours or until sign-out;
• undelivered messages: until delivered;
• one-time Google or GitHub sign-in codes: two minutes;
• presence: for the connection only;
• server logs: within log rotation;
• payment records: as long as refunds and tax accounting need them.

8. Deleting an account

8.1. A user may have their account deleted by writing to support@paradoxclient.com or on Discord or Telegram from that account. Deletion cannot be undone.

8.2. The whole account record, friendships and invitations on both sides, and all sessions are deleted.

8.3. Deletion does not reach what is already on other users' devices (delivered messages, imported settings), encrypted backups where a deleted account may remain for up to five weeks, or payment records needed for refunds and tax accounting.

9. Rights of the data subject

9.1. The data subject may:

• learn how their data is processed;
• have it corrected, blocked or destroyed if it is incomplete, outdated, inaccurate or not needed for the stated purpose;
• withdraw consent;
• complain to Roskomnadzor or a court.

9.2. Requests go to support@paradoxclient.com. The Operator answers within 10 working days.

10. Security measures

• data travels only over encrypted connections (TLS);
• passwords and session tokens are stored only as hashes;
• direct messages and voice are end-to-end encrypted;
• database backups are encrypted;
• access to the Operator's servers is restricted.

11. Cookies

11.1. The Site sets no cookies and loads nothing from third-party servers. After sign-in the session token is kept in the browser's local storage and removed on sign-out.

11.2. The numbers on the front page (players online, accounts) are anonymous counters.

12. Children

12.1. The Service is not meant for anyone under 13. A legal guardian may have a minor's account deleted as described in section 8.

13. Changes

13.1. A new version takes effect when published on the Site. A change in what data is processed is also announced on Discord and Telegram before that processing begins.

14. Operator details

Operator

Klimov Artyom Konstantinovich (Климов Артём Константинович)

INN

667222284833

Email

support@paradoxclient.com

Site

paradoxclient.com