Effective: August 26, 2026 Developer: Maksym Kozlov (contact@vinmara.com) Application: Ironclash, package com.vinmara.ironclash
This document describes what data the game transmits or stores, why, and for how long it is kept. The list is drawn from the actual database schema and the production network path, not from future plans.
| Data | Why | Where it lives |
|---|---|---|
| Email address | The sign-in identifier for the account | accounts.email |
| Password | Sign-in | The plaintext is transmitted over HTTPS and processed only in memory. It is never stored; only an irreversible digest is kept (scrypt with a random salt) |
| Fighter name | Shown to other players in battle, in the rating and in chat | characters.name |
Game progress: level, experience, attributes, health, currencies, items, wins and losses, the chosen look and battle scheme, position in the campaign.
Messages you write in chat are stored together with their time and recipient. Public chat is visible to every player. Do not write anything there that you consider private.
Technical account and session data: internal account and fighter identifiers, an irreversible digest of the sign-in token, and the time it was issued and revoked.
Optional first-party gameplay analytics: only after you enable “Share gameplay analytics” in Settings, the game uses gameplay, progress and purchase outcomes that occur from that consent onward, stores one account activity marker per UTC day, and records cumulative seconds while the game is in the foreground. Each foreground segment uses a random identifier solely to make retries idempotent. Earlier event history is not added retroactively. This is used only in aggregate reports to understand onboarding, return rates, battle balance, progression, currency sources and sinks, and purchase conversion. We do not store a screen, route or click history, free-form analytics payload, IP address, advertising/device identifier or install identifier for this purpose. The report contains no email address, account or fighter ID, fighter name, chat text or report details.
Purchase data: when you buy Crystals through Google Play Billing, the game receives the product identifier, purchase token, order identifier (when supplied), purchase time, quantity, purchase state, consumption state, country/region code and an opaque account-binding value. The raw purchase token is sent to the game server over HTTPS so the server can verify the purchase with Google Play. It is kept only while a failed or interrupted consume operation needs to be retried, then deleted after Google confirms consumption; an irreversible SHA-256 digest is retained to prevent duplicate grants and reconcile refunds. The game never receives or stores your card number, bank account, billing address or other payment credentials. Google processes the payment under its own privacy policy.
Optional rewarded advertising: Ironclash uses the Google Mobile Ads SDK to offer ads that you may choose to watch for a small amount of ordinary in-game Coins. Ads never grant Crystals, player experience or combat power. The game first runs Google's User Messaging Platform consent flow and does not initialize Mobile Ads unless that flow says ads may be requested. An ad itself is requested only after you tap the watch button.
According to Google's disclosure for the exact Mobile Ads SDK line used by the game, the SDK automatically collects and shares the device IP address, product interactions (including app launch, taps and video views), diagnostic information, and device or account identifiers such as the Android advertising ID and app set ID. Google uses this information for advertising, analytics and fraud prevention; it is encrypted in transit. An IP address may be used to estimate approximate location. The disclosure is maintained by Google at Google Mobile Ads SDK data disclosure.
For a reward, the game sends Google one random, single-use reward-intent ID as the server-side-verification custom_data value. It does not send the player's email, fighter name, account ID, character ID or game session token. The game server verifies Google's signed callback before granting Coins and stores the reward intent, Google transaction ID and grant status to prevent a duplicate reward. The operator dashboard separately stores daily aggregate AdMob report rows (date, country, ad format, impressions, estimated earnings and reporting currency). Those report rows contain no player or device ID.
Technical request metadata: your IP address and ordinary HTTP request metadata (such as the requested route and user-agent header) necessarily reach the Cloudflare reverse proxy/CDN and the hosting server. This metadata is processed transiently by the game application to route, secure and answer the request and is not stored in account or gameplay tables. It is not used for gameplay analytics, profiling or advertising. Infrastructure providers may retain limited operational or security logs under their own controls.
Chat safety data: the current Community Guidelines version you accepted, the time of consent, accounts you block, and reports you submit. A report records its category and may contain the reported message and optional details so the operator can investigate it even if the original message is deleted.
Support data: when you contact support inside the game, we store the subject, message text, timestamps, the replies sent by the operator, and the link to your account. The current message is also sent to the Ironclash operator mailbox at contact@vinmara.com as a notification. Replies are written in the protected Admin panel and delivered back to the same in-game conversation; email is not a second support record and players should not reply to the notification address.
We do not request GPS location or infer and store location from the IP address. We collect no contacts, list of installed apps, photos, microphone or camera data. Ironclash does not write the advertising ID or an install/device ID into its own account, gameplay or analytics tables. Google Mobile Ads handles the advertising and app-set identifiers described above; the game contains no separate third-party product-analytics SDK. Permissions unrelated to the game's actual features are stripped from the release build.
The primary reasons are to make the game work and keep it safe. The email identifies your account; progress survives between launches; the name lets opponents know whom they are fighting; consent, block and report records support moderation; support conversations let us answer account, purchase and gameplay questions; technical request metadata routes and protects the connection. If you opt in, existing gameplay/progress data, the daily activity marker and foreground time are used for first-party aggregate product analytics so we can improve onboarding, progression, battle balance and the game economy. They are not used for personalized prices or automated decisions about you. Rewarded-ad data is used to request and measure the ad, prevent reward fraud, grant the promised Coins once, and report aggregate ad performance and estimated revenue. Purchase data is used to verify and grant digital goods, prevent duplicate or fraudulent grants, consume completed purchases, reconcile refunds and keep the player's balance correct.
We do not sell data or pass account, fighter, chat, support or gameplay data to advertisers or data brokers. Infrastructure service providers — the hosting provider and the reverse proxy/CDN — process only the data technically required to operate, secure and deliver the game on our behalf.
Gameplay analytics are processed only by Ironclash on the same game server. No data from this first-party gameplay-analytics system is sent to a third-party analytics provider. This statement does not describe Google Mobile Ads' own advertising measurement, which is disclosed separately below.
Google Play processes purchase and payment data as the store and payment provider. The game sends a purchase token and package/product identifiers to the Google Play Developer API solely to verify, consume and reconcile the purchase.
Google processes the rewarded-ad data described above as the advertising SDK and network provider. Its handling is governed by Google's Privacy Policy and how Google uses information from apps that use its services. Ironclash does not give Google an account email, fighter name or stable game identifier for ad targeting or measurement.
We will disclose data on a lawful request from an authorized body — and in no other way.
Account, progress, chat, consent, block and support-conversation data are kept for as long as your account exists. Deleting the account immediately deletes its support tickets and messages from the game database. Copies already delivered to the operator mailbox follow the mailbox provider's operational retention and are deleted when no longer needed to resolve the request or a legal dispute. Sign-in tokens expire 30 days after being issued and are deleted.
Purchase records, token digests and refund/revocation records are retained while the account exists and afterwards only for the period required to prevent a refunded or duplicated transaction from being granted again and to meet legal, tax or dispute obligations. Account deletion removes the link to the fighter; transaction identifiers that must be retained are no longer used for gameplay, advertising or profiling.
Evidence attached to a safety report is kept for no more than 180 days from the report, unless a longer period is required by law. This bounded safety record may remain after the original message or account is deleted so an already-filed complaint cannot be erased before review.
Technical request metadata is not retained in the game's account or gameplay database. Infrastructure providers may keep limited operational or security logs for the periods set by their services and legal obligations.
Account-linked daily analytics activity markers and foreground-time segments are kept for no more than 90 days. Turning gameplay analytics off immediately deletes all of these records and excludes your account from future aggregate reports. Gameplay, battle and ledger records still required to operate the game follow the account retention rules above. Deleting the account also deletes them automatically.
Pending reward intents expire after a short verification window. Granted reward intents and transaction IDs remain linked to the account while it exists so the same verified view cannot be rewarded twice. Account deletion removes the account link immediately; the reward ledger follows the already documented anonymized-fighter retention, and any later callback becomes a no-op. Daily AdMob report rows are aggregate, contain no player/device identifier and may be retained for financial and operational reporting.
You can request a copy of your data or deletion of the account together with the fighter link, progress and messages. The bounded safety-report exception described above still applies. Write to contact@vinmara.com from the address the account is registered to. We will fulfil the request within 30 days.
Deletion is irreversible: progress cannot be restored afterwards.
You may enable or disable gameplay analytics at any time in Settings. It is off by default and disabling it does not restrict any game feature.
Where Google requires advertising privacy choices, Settings → Ad privacy opens Google's privacy-options form again. Android also lets you reset or delete the advertising ID in system privacy settings. Rewarded ads are optional: not watching one does not block campaign progress or any paid entitlement. The gameplay-analytics toggle is separate and does not grant or revoke advertising consent.
Passwords are stored only as an scrypt digest with a random salt. Traffic to the server goes over an encrypted channel (HTTPS); plain HTTP is forbidden in the release build at the level of the application's system network policy. The sign-in token on the device sits in the operating system's secure storage, not in an ordinary file.
No protection is absolute, and we do not claim otherwise.
The game is not intended for children under 13 and does not knowingly collect their data. If you discover that a child has created an account, write to us — we will delete it.
We will announce substantial changes to this policy inside the application before they take effect. The date at the top of the document always matches the edition in force.
contact@vinmara.com
Published at: https://ironclash.vinmara.com/privacy — this is the URL declared in Play Console. The page is served by the game server itself, reading this very file: there is no second copy of the text, so the published edition is always the one reviewed in the repository.