Privacy Policy

Last updated: 2026-10-10

This policy may be updated from time to time. The version you are reading now is the current one.

Who is responsible

This app, Plink Supreme (called Plinko Ultra until 2026-10-07), is made by Manuel Molina, an individual developer based in Spain. If you have any question about your data or this policy, contact privacy@delcid.es.

What the app stores on your device

Everything the app stores lives only in the app's own storage on your phone or tablet. Nothing here identifies you personally.

• android-games.device-id — the identifier this install is known by. On Android it is derived by one-way hashing (SHA-256) from an Android device identifier that is scoped to this app alone, so it stays the same if you uninstall and reinstall the app on the same device, and it changes only with a factory reset; the server receives the hash, never the underlying identifier. Where that identifier is unavailable, a random value generated on your device is used instead. It is not linked to your name, email, or any account, because the app has none. The app shows it under MORE → Device ID, which is where you find it to ask for deletion (see "Deletion and retention" below).
• android-games.credential.v1 — the credential the game server issued to this install, which proves to the server that records come from it. It is not a password and is never shown.
• android-games.nickname — a display name made up on your device from word lists (an adjective, a noun, and a number, for example "LuckyTiger482"). You can change it, but it is never a real name unless you choose to type one in yourself. Since v1.8 other players can see it: if one of your rounds reaches the leaderboard, your nickname is shown next to that score. Nothing else about you is shown — no identifier, no device details, no other rounds. If you would rather not be identifiable there, keep the generated name or pick another one that is not a real name.
• android-games.wallet.v1 — your play-money coin balance. This is not real money and has no cash value.
• android-games.outbox.v1 — a local queue of round, bonus, and profile records waiting to be sent to a game server (see "What we send" below).
• android-games.events.v1 — a local queue of usage events (see "Usage events" below) waiting to be sent. Kept to the most recent 2000 entries.
• pachinko.muted — your sound on/off preference.
• pachinko.panelSide — your left/right panel layout preference.
• pachinko.analytics — whether usage events are recorded (on, the default, or off).
• Your ad consent choice, kept by Google's consent SDK in the app's storage under the industry-standard IABTCF_… keys, so that it does not have to ask again (see "Rewarded video ads (Google AdMob)" below).

None of this is included in Android's backup to your Google account or in a transfer to a new device: the app opts out of both. Reinstalling on the same device usually continues where you left off, because the server recognises the device id; a new device starts as a new player.

What a round record contains

Every time you play a round, the app records the details of that round: gameId, bet, rows, difficulty, rtpVariant, seed, forced, bucket, multiplier, win, and balanceAfter. Each record also has an id and a timestamp taken from your device's own clock. A separate bonus record (amount, balanceAfter) is created if the game tops up your balance, and a profile record (nickname) is created if you change your nickname.

Usage events

To understand how the game is played — how long a first session lasts, how many players come back the next day, what happens when the coins run out — the app records a short, fixed list of events about your use of it:

• the app starting and stopping (with the session's length and number of rounds), and whether it was a first launch;
• a setting being changed (difficulty, rows, bet, sound, panel side, or this switch itself);
• autoplay starting and stopping, with how many rounds it ran and why it stopped;
• the "out of coins" notice appearing, and what lifted it;
• the daily streak panel being opened;
• the coin-pack shop being opened, and a coin-pack purchase being started, cancelled, refused or completed, and the coins from one landing;
• the outcome of Google's ad consent question at launch, and the rewarded-video row being tapped, an ad being shown, its reward being earned, or the ad failing;
• the device going online or offline.

Each event carries an id, the moment it happened on your device's clock, a session id, the app version and the language the app was displayed in. Nothing in an event identifies you beyond the same random device identifier the rest of the app uses; no text you type, no location and nothing about other apps is recorded. Rounds, rewards and nickname changes are not recorded again as events.

You can switch this off in the MORE menu under "Usage data". Switching it off empties the local event queue and stops recording; nothing already sent is affected. Events are recorded and sent by the app itself — there is no analytics SDK and no third party involved.

What we send

The app is built to send the round, bonus and profile records above, and the usage events, to a game server we operate, so that your balance is protected against tampering and your progress can be checked. Records are sent over an encrypted connection with a credential issued to your device. Until that server is running, nothing leaves your device — everything simply stays in the local queues on your phone.

In-app purchases (coin packs)

The app sells coin packs: play-money coins, bought with real money through Google Play. Buying is entirely optional — no purchase is needed to play, and the game keeps giving coins away for free.

• Google Play takes the payment. The purchase happens in Google's own dialog, inside the Play Store. We never see your card, your bank details, your billing address or your name, and no payment detail ever reaches this app or our server. That part of the purchase is covered by Google's own privacy policy.
• RevenueCat checks that the purchase is real. We use RevenueCat, Inc. (United States) as a processor that validates purchases on our behalf. It receives the identifier your install is known by — the opaque player identifier our server issued, with no name, email or account attached — and the purchase token Google Play issues, and it keeps a history of purchases under that identifier. It then tells our server, over an encrypted connection, that a pack was bought, so that the coins can be added to your balance. It receives nothing else about you: no rounds, no events, no nickname.
• What we store. For each purchase our server keeps one record: the store's transaction id, RevenueCat's event id, the product that was bought, the number of coins we credited, the price and currency Google charged, whether it was a real or a test purchase, the store, when the purchase was made and when we heard about it. It is linked to your player record so the coins land in the right balance.
• Coins are play money. They have no cash value, they cannot be exchanged, transferred or paid out, and nothing bought in this app has any value outside it. Nothing you buy is random: each pack states exactly how many coins it gives.
• Refunds go through Google Play. We cannot refund a purchase. Refunds are requested from Google (Play Store → your profile → Payments and subscriptions → Budget and order history) under Google's refund policy.

A purchase record is kept for as long as the player it belongs to exists. If you ask for your data to be deleted, the purchase record is unlinked from you rather than deleted: it keeps the transaction, the product and the coins, and points at nobody. We keep it because it is the record of a real payment for which Google still holds a receipt, and once unlinked it names no one.

Rewarded video ads (Google AdMob)

The app offers an optional rewarded video: in the ＋ COINS sheet you can choose to watch a short ad and receive 100 play-money coins for watching it to the end, up to three times a day (the day is counted in UTC). Watching is entirely optional — no ad is ever needed to play, and nothing in the game is held back if you never watch one. There are no other ads anywhere in the app: no banners, no ads between rounds, and no ad that starts by itself. An ad plays only when you tap to watch one.

• Google shows the ad. The ads are served by Google AdMob, provided by Google Ireland Limited in the European Economic Area and Switzerland and by Google LLC elsewhere. To choose, deliver and measure the ad and to prevent ad fraud, Google's ad SDK inside the app receives your device's advertising ID (unless you have deleted it in Android's settings), the IP address, information about the device and the app (such as the model, the Android version, the language and the app's version), and your consent choice (below). Google uses this data as an independent controller, under Google's own privacy policy; how Google uses data from apps that show its ads is explained at policies.google.com/technologies/partner-sites. We never receive the advertising ID or anything else Google's SDK collects. You can delete or reset your advertising ID at any time in Android's settings.
• Consent. In the European Economic Area, the United Kingdom and Switzerland, the app shows Google's consent form before the first ad is requested, and you choose whether Google may use your data to personalise ads. If you do not consent, the ads you watch are not personalised. You can change your choice at any time under MORE → Privacy & ad settings.
• What we send Google and keep ourselves. When you tap to watch, our server issues a one-time offer, and the app hands Google two values with the ad: the opaque player identifier our server issued (no name, email or account attached) and that offer's id. When you have watched to the end, Google tells our server so, in a request Google signs, and returns those two values with the ad's transaction id, the ad unit and ad network that served it and the reward. For each reward our server keeps one record: those fields, the coins credited and when, linked to your player record so that the coins land in your balance. The coins arrive a moment after the ad closes, once Google's confirmation has reached our server.
• Usage events. The ad events listed under "Usage events" above follow the "Usage data" switch like every other event.

A rewarded-ad record is kept for as long as the player it belongs to exists. If you ask for your data to be deleted, it is unlinked from you, like a purchase record: it keeps the transaction and the coins and points at nobody.

Server logs

Like any web server, the game server records each request it receives: the IP address it came from and technical details of the request — the time, the path requested, the response, and the identification string the app sends, which names the phone model and Android version. The server's record of a request also carries the device id of the install that sent it. These records are kept for security, to limit abuse (rate limiting) and to find faults, and are deleted automatically after 30 days.

What this app does not do

• No advertising except the optional rewarded videos described under "Rewarded video ads (Google AdMob)" above, which play only when you tap to watch one. No banners, no ads between rounds, no ad that starts by itself.
• No third-party analytics and no crash reporting. The usage events above are collected by the app itself, sent only to our own server, never shared and never sold.
• No third-party SDK except two: the purchase SDK described under "In-app purchases (coin packs)" above, which does nothing until you buy a pack, and Google's ad SDK with its consent SDK, described under "Rewarded video ads (Google AdMob)" above.
• No account, no login, no email address, and no password.
• No payment details. Coin packs can be bought (see "In-app purchases (coin packs)" above), but Google Play takes the payment: no card, bank or billing data ever reaches this app or our server.
• No access to your location, contacts, camera, microphone, or photos.
• The app uses only these permissions: internet access; seeing whether the device is online (network state); Google Play's billing, for coin packs; and the advertising ID (AD_ID), which Google's ad SDK adds so that it can read the advertising ID described under "Rewarded video ads (Google AdMob)"; keeping the screen on (WAKE_LOCK) while an ad plays; and running a foreground service (FOREGROUND_SERVICE), which Google's ad SDK uses for ad delivery. None of them asks you for anything.

Simulated competitors on the leaderboard

The leaderboard may include simulated competitors. When it does, a simulated competitor can hold a prize rank, which lowers the prize a real player receives; a simulated competitor is never paid.

Simulated competitors are generated by the game server. They are not other players, and nothing about you or any other player is used to create them. Prizes are play-money coins with no cash value, and a real player is always paid the prize for the rank the board shows them at.

Legal basis and your rights

We process the limited, anonymous data described above on the basis of our legitimate interest in operating and improving the game. Personalised ads rest on the consent you give in Google's consent form, which you can withdraw under MORE → Privacy & ad settings. You have the right to access, correct, erase, and object to the processing of any data associated with your device. If you believe your rights have not been respected, you can complain to the Spanish supervisory authority, the AEPD (Agencia Española de Protección de Datos). Given the small scale of this processing, no Data Protection Officer is required.

Children

This game is intended for adults and is not directed at anyone under 18. We do not knowingly collect personal data from anyone under 18.

Deletion and retention

Everything the app stores lives in the app's own storage on your device. Uninstalling the app or clearing its storage removes that data from your device.

On the server, round, reward and profile records are kept for as long as the player they belong to exists. Usage events are kept for 13 months and then deleted automatically.

To have your data deleted from the server, email privacy@delcid.es with your device id. You find it in the app under MORE → Device ID; tapping that row copies it. The device id is the only identifier there is — we cannot tell which records are yours from your name or email — so a request needs it to be carried out. Reinstalling the app does not delete anything on the server, since on the same device the id stays the same.

We delete the data within 30 days of receiving a request with a device id we can find, and reply to confirm. Deletion removes the player and everything linked to it: rounds, the coin ledger and balance, the records the app sent, usage events, the daily streak, challenge rewards, items, the device credential and the nickname, which becomes free for anyone to use. A leaderboard prize you won stays in that board's history, with its rank and amount but nothing linking it to you. A coin pack you bought stays as an unlinked purchase record, with its transaction, product and coins but nothing linking it to you (see "In-app purchases (coin packs)" above), and a rewarded ad you watched stays the same way (see "Rewarded video ads (Google AdMob)" above). What Google's ad SDK collected is held by Google, not by us; deleting or resetting your advertising ID in Android's settings is how you act on it.

The server's database is also copied to backups, which are never edited after they are made. Each backup is deleted automatically after 14 days, so no copy of your data remains once the backups made before the deletion have expired.

Server logs (see "Server logs" above) are not edited by a deletion; they expire on their own 30 days after each request.

If you keep playing on the same device after a deletion, the app registers as a new player with a fresh balance; nothing from before is restored.