1. Scope
Personal-data operator: Калягин Андрей Владиславович, self-employed, taxpayer ID 773323995948. Processing started on 14 August 2026. Privacy contact email: team@maralys.com.
This Policy applies to maralys.com, MARALYS ID, game servers, the application, official mods and support.
2. Data categories
Account data includes email, username, display name and language; the password is stored only as an Argon2id hash. When an official mod signs in, the API receives the entered password over HTTPS only long enough to verify it and does not store it in plaintext. We also process IP, user-agent, sessions, security logs, game identifiers/progress/sanctions, MCOIN history, support correspondence, consent evidence and voluntarily linked public Steam fields.
The official desktop application reports the CPU model and logical thread count, total/free RAM, GPU name and driver, total/free system and application disk space, OS name/version/build/architecture and kernel, MARALYS/Electron versions, first/last-seen times and incomplete-collection codes. A firmware UUID or fallback machine identifier and a separate random installation ID are SHA-256 hashed on the client and then protected with a secret server HMAC. Hostname, local username, MAC addresses, plaintext UUIDs and serial numbers are not collected. Hardware specifications do not participate in device matching.
The official desktop also creates a local Ed25519 software-key pair to prove continuity of the client. Only the public key is sent to MARALYS; the private key remains on the device and is encrypted with a genuine OS protected-storage backend when available, otherwise its file is restricted to the current user. One-time enrollment challenges and request nonces are retained server-side only as short-lived SHA-256 values. This is not TPM or Secure Enclave hardware attestation.
Pixel Battle data includes season ID, cell coordinates and colour, action time, linked MARALYS ID, username, canvas version, contribution statistics, change history and reports. Coordinates, colour, time and username are public on the canvas and in replay; a profile link appears only for a public profile. Application-content data includes immutable revisions, text, attachments, categories, tags, content type, publisher kind, moderation status, reports and action timestamps.
3. Purposes and legal grounds
We process data to enter and perform the User Agreement, provide accounts and servers, prevent abuse, deliver support, meet legal obligations and pursue proportionate legitimate interests. Separate consent is used where legally required. Marketing uses separate optional consent.
4. Recipients
Access is role-limited. Authorities receive data only under a valid legal requirement.
- ООО «ТАЙМВЭБ.КЛАУД» (Timeweb Cloud), taxpayer ID 7810945525, primary state registration number 1227800052215, hosts VPS infrastructure, the primary database, files and backups in Russia. Official legal address: 420500, Республика Татарстан, М.Р-н Верхнеуслонский, г.п. Город Иннополис, г. Иннополис, ул. Университетская, д. 7, оф. 605.
- VK Digital Technologies LLC (VK WorkSpace) delivers service email and optional marketing email.
- Yandex LLC (Yandex Metrica) receives analytics data only after optional-cookie consent.
- No separate web-push provider is used.
5. Russian localisation and cross-border transfers
The primary recording, systematisation, accumulation, storage, update and retrieval of Russian citizens’ personal data use a primary database and backups on ООО «ТАЙМВЭБ.КЛАУД» (Timeweb Cloud) VPS infrastructure in the Russian Federation. The provider's legal address does not identify the physical location of a particular server. Steam is a separate foreign service. Any cross-border transfer is enabled only after the Operator completes the applicable assessment and Roskomnadzor procedure. Steam linking is optional unless licence proof is required for a specific server.
6. Retention
Account data remains while the account is active, then is deleted or depersonalised unless law, accounting, security or legal claims require limited retention. Only the latest readable desktop-device snapshot and software proof public key are retained while at least one linked account exists. After the last link is removed, readable specifications are cleared; opaque HMAC identifiers and active-sanction mappings may remain for the sanction and the security-policy retention period to prevent ban evasion. Used challenge and nonce hashes are deleted after their short technical lifetime. Active web sessions remain until sign-out, device revocation, or local-data removal; their protected refresh cookie is renewed during use within a technical window of up to 400 days. Mod refresh sessions last up to 90 days, and one-time codes no longer than their documented lifetime. Backups expire under a controlled rotation schedule.
7. Security
Controls include TLS, access separation, Argon2id, hash-only refresh-token storage, session revocation, logs, backups, dependency updates and incident response. No system is absolutely secure; use a unique password and report suspicious activity immediately.
8. Your rights
You may request processing information and a copy, correction, blocking, deletion, withdrawal of consent and a review of the Operator’s actions. Use the account form or privacy email. Identity verification may be required. Withdrawal is prospective and does not stop processing based on another lawful ground.
9. Children, cookies and changes
MARALYS ID is designed for adults aged 18+. Essential cookies secure sessions and forms; optional categories require a choice. Material policy changes receive a new version and renewed consent where law requires it.
10. Playtime and referrals
To display statistics and operate referrals, MARALYS processes application ID, MARALYS ID, Minecraft UUID and username, game/server session identifiers, Connector version, heartbeat sequence, cumulative active time, last contact, AFK state, referral code, attribution and reward status.
A server's public page shows a participant's position, display name, username and verified playtime. The avatar and profile link appear only when the public profile is open; email, UUID and session identifiers are not included in the ranking.
This confirms active play, prevents replay and abuse, displays time and balance, maintains the server ranking, credits MCOIN and supports reviews. Heartbeat receipts are retained for up to 48 hours; aggregate time, attribution and the immutable MCOIN ledger remain while the account is active and afterward only for security, disputes and mandatory records. Server secrets are stored only as cryptographic hashes.
11. Permanent-privilege checks
To avoid charging MCOIN for a temporary privilege already covered by a permanent one, the official Connector reports positive permanent LuckPerms group names and the observation time. The backend retains only groups referenced by active privilege products on the selected server; unrelated groups and individual permission nodes are discarded.
The snapshot is replaced on an authenticated game-session start and heartbeat, is used only for purchase and delivery checks, and is deleted with the account or server. Group names are never included in the public catalog or website responses: the interface receives only identifiers of products already owned. The last confirmed state may temporarily keep a purchase blocked after connectivity is lost to prevent an incorrect debit; a new authoritative snapshot updates it.
12. Essential Explore analytics
For signed-in users, MARALYS records actual Explore section and folder activations to operate shared navigation and calculate the Popular ordering. This processing is necessary to provide the service, does not depend on optional analytics consent, and is not used for advertising or personal profiling.
The analytics dataset stores no MARALYS ID, IP address or user agent. For a custom folder or link it retains only an escaped label and normalized destination without query, fragment or credentials, and never the owner. Idempotency receipts expire within 7 days, custom labels and destinations within 90 days, and built-in daily aggregates within 400 days; an anonymous lifetime total for built-in sections may remain while the service operates.