Privacy Policy

Koplay mobile games · Effective 21 October 2026

This policy applies to every mobile game developed by Koplay (Chen Kopel, the developer named on Google Play; "we", "us") that links to this page (each a "Game"). It explains what information the Games collect, how it is used and shared, and the choices you have.

The Games currently show no ads, offer no in-app purchases and do not use your device's advertising identifier. They send gameplay analytics to one service provider, GameAnalytics. Some Games (currently Stack the Crowd) also use Google Analytics for Firebase, a service provider of ours run by Google, only to count how many people open the Game after installing it from our Google Ads campaigns; Google Ads receives those counts under Google's own terms. The Games send information to no one else.

A Game published together with a third-party publisher has its own privacy policy, linked from its store listing and inside the Game, and this page does not apply to it.

Information we collect

The Games do not ask for an account, name, email address, phone number, contacts, photos or precise location. If you email us for support or a privacy request, we also receive your email address and the information you choose to include.

While analytics is on (see "Privacy choices"), the Games send the following to GameAnalytics, our analytics provider:

• Gameplay events – levels started, completed, failed or abandoned, with a score such as the coins earned or how much of the level was completed, and in-game actions such as items unlocked or bought with in-game coins, upgrades, daily rewards and settings changes. The actions recorded depend on the Game.
• Sessions – when each play session starts and ends, how long it lasts, how many sessions have been played on the installation and the total time played.
• A random installation identifier – a random ID that GameAnalytics creates when analytics first starts in the Game (when it is first opened or, where the Game asks for your consent, when you allow it), keeps on your device and sends with every event. It contains no information about you. Clearing the Game's data creates a new one, and so does reinstalling the Game, unless Android's backup restores the Game's saved data (see "Data stored on your device").
• Device and app information – device model and manufacturer, Android version, the Game's version, package name and signing-certificate fingerprint, the versions of the GameAnalytics software and the game engine, the network connection type, which app store or installer installed the Game (for example Google Play), and whether the device appears to be rooted. GameAnalytics also receives your device's IP address when the Game connects, and uses it to determine your country.
• Install source – one category for how the Game was installed: from one of our Google Ads campaigns, found on Google Play, through another link, from outside Google Play, or unknown. The Game works this out on your device from which app installed it and, for installs from Google Play, from Google Play's Install Referrer service, which it asks until it gets an answer. The Game stores and sends only the resulting category. The referrer itself, including any ad-click identifier, is never sent to GameAnalytics or stored by the Game. In Games that use Google Analytics for Firebase, Firebase reads it separately, as described below. (The name of the app that installed the Game is sent separately, as part of the device information above.)
• Frame rate and loading times – summaries of how smoothly the Game runs, and how long it takes to start (until analytics starts and until you can first play).
• Error reports – error messages logged while the Game runs (by the Game, the game engine or its plugins), with technical details of where in the code they happened (stack traces), up to 10 per session. The GameAnalytics software also reports its own errors.

In Games that use Google Analytics for Firebase (currently Stack the Crowd), while analytics is on, Google's Firebase software in the Game also sends Google:

• App opens and sessions – the first time you open the Game after installing it, when later sessions start, how long the Game is in use, Game updates, Android updates, and when the Game is uninstalled or its data is cleared. Firebase receives none of the Game's gameplay events and no user ID.
• An app-instance identifier – a random ID that Firebase creates and keeps on your device. It contains no information about you. Clearing the Game's data or reinstalling it creates a new one.
• Device and app information – such as device model, Android version, language, the Game's version and which app store installed it.
• How you came to install the Game – for installs from Google Play, Firebase reads Google Play's Install Referrer on your device and sends the campaign it names, including the ad-click identifier of our Google Ads campaigns, so that Google Ads can count the install.
• Your IP address, which Google shortens (masks) before using it to estimate your approximate location (such as your country and region).

The Games do not collect your device's advertising identifier: GameAnalytics' and Google Analytics for Firebase's advertising-ID collection is switched off, and the Games do not request Android's advertising-ID permissions (including those of Android's Privacy Sandbox).

How we use information

• To understand how players progress through the Games and improve their levels, difficulty and features.
• To find and fix errors and performance problems.
• To see how players who installed a Game from our advertising campaigns play, compared with other players, and to count how many people open a Game after installing it from those campaigns, so that Google Ads can measure and adjust them.
• To respond to support and data-rights requests.

We do not use this information to identify you, to show you ads or to build advertising profiles.

Advertising

The Games show no ads and contain no advertising SDK. We advertise our Games elsewhere, for example with Google Ads app campaigns. Google measures installs from those campaigns through Google Play, and in Games that use Google Analytics for Firebase also through Firebase, which tells Google Ads when someone opens the Game for the first time after installing it from one of our ads. We use this to measure and adjust our own campaigns. Google Ads receives it as an independent controller and uses it under Google's own terms and privacy policy. We switch off ad personalisation, so we don't use it for remarketing or to personalise ads, and in the European Economic Area, the United Kingdom and Switzerland we tell Google not to use any of it for advertising (Google's consent settings for ad storage, ad user data and ad personalisation are set to denied there). To tell those installs apart from others, the Game reads Google Play's install referrer on your device as described under "Install source", and keeps and sends only the resulting category.

Third-party partners

The Games send information only to GameAnalytics, and, in Games that use it, to Google through Google Analytics for Firebase; both process it on our behalf as our service providers. When Firebase tells Google Ads that someone opened the Game after one of our ads (outside the European Economic Area, the United Kingdom and Switzerland), Google Ads receives that first open, linked to the ad click, as an independent controller under Google's own terms and privacy policy. Google also distributes the Games and runs our advertising campaigns. Separately, if you have switched on Android's backup, Android itself may keep a copy of the Game's saved data in your Google account (see "Data stored on your device").

• GameAnalytics (gameplay analytics, as our service provider) – GameAnalytics privacy notice (for its customers)
• Google (Google Analytics for Firebase, in the Games that use it, as our service provider; Google Ads, which receives first opens from our campaigns under Google's own terms; also distributes the Games through Google Play) – policies.google.com/privacy; how Google uses information from apps that use its services: policies.google.com/technologies/partner-sites; Firebase privacy: firebase.google.com/support/privacy

We do not sell your personal information and do not share it for personalised advertising: the only information that reaches Google Ads is the first opens described under "Advertising", used to measure our own campaigns.

Privacy choices

Games offered in the European Economic Area, the United Kingdom or Switzerland ask for your consent there before any analytics starts; a Game that doesn't ask is not offered in those countries. A Game asks when you first open it, and again at each launch until you answer. Until you choose Allow, it sends nothing to GameAnalytics or Google Analytics for Firebase, GameAnalytics creates no identifier, and the install source is not looked up. There, Allow turns on Firebase's counting of app opens only, and we tell Google not to use it for advertising. Refusing is as easy as allowing, and the Game works the same either way. In these countries, we rely on your consent for analytics. To decide whether to ask, the Game checks on your device the country of your SIM card, of your mobile network and of your language settings. It asks if any of them points to one of these countries or a territory linked to them, or if it can't tell. The result is not sent or saved.

Some Games have an Analytics setting (in Settings or in the pause menu). Some show it to every player, wherever they live; others show it only where they ask for consent, and to anyone who has answered there, wherever they play later. Where a Game shows this setting, you can turn analytics off, or back on, at any time. Every Game that asks for your consent has this setting, so you can withdraw your consent there as easily as you gave it. Turning analytics off stops it immediately: from that moment the Game sends nothing more to GameAnalytics or Google Analytics for Firebase, and it doesn't start either on later launches. Events recorded before you turned it off but not yet sent stay on your device and are sent only if you turn analytics back on. In the European Economic Area, the United Kingdom and Switzerland, turning it back on asks for your consent again.

Wherever you live, and whether or not a Game shows an Analytics setting, you can also stop all collection by uninstalling the Game, and you can make the Game start over with a new random identifier by clearing its data. You can also email us at support@koplaystudio.com to object to the processing or to ask for your data to be deleted (see "Your rights").

Data stored on your device

Your progress (such as levels, in-game currency, unlocked items and settings like sound, vibration and reminders) is saved on your device, together with your analytics choice if you have made one and, once analytics has started, the GameAnalytics random identifier, the install-source category and any events not yet sent, and, in Games that use Google Analytics for Firebase, Firebase's app-instance identifier, its on/off setting and its events not yet sent. You can delete it at any time by clearing the Game's data in your device settings or by uninstalling the Game. If Android's backup is switched on for your Google account, Android may also keep a copy of this data in your backup and restore it when you reinstall the Game; you can turn backup off, or delete the backup, in your device's or Google account's backup settings. None of this deletes data already sent to GameAnalytics or Google; see "Your rights" to request deletion of that data.

Notifications

If a Game offers reminders, it asks for your permission to show notifications (on Android 13 and later) and, if you allow them, schedules local reminders on your device (for example, that a daily reward is ready). The reminders are created on your device; the Games use no push-notification service. You can turn them off in the Game's settings, where available, or in your device's notification settings.

Security and data retention

The Games send data to GameAnalytics over encrypted (HTTPS) connections. Under its data processing terms with us, GameAnalytics deletes the personal data it processes for us when the retention periods in those terms end; these are currently between 1 month and 18 months, depending on the kind of data (see clause 8 of GameAnalytics' data processing addendum). Google Analytics for Firebase also receives data over encrypted connections. We set Google Analytics to keep event data linked to the app-instance identifier for 2 months, after which Google deletes it; reports keep only totals that identify no one. First opens that Google Ads has received as conversions are kept by Google Ads under Google's own retention rules (policies.google.com/technologies/retention), not ours. We keep emails you send us only as long as needed to answer them and to handle your request.

International transfers

GameAnalytics and Google may process information in countries other than yours, which may include the United States. Where required, such transfers are protected by appropriate safeguards such as the European Commission's Standard Contractual Clauses.

Children

The Games are not directed at children under 13 (or the minimum age of digital consent in your country), and we do not knowingly collect personal information from them. If you believe a child has provided us with personal information, contact us so we can investigate and arrange deletion where required.

Your rights

Depending on where you live (for example under the GDPR, UK GDPR or US state laws such as the CCPA), you may have the right to access, correct, delete or receive a copy of your personal data, to object to or restrict its processing, and to opt out of the sale or sharing of personal information or targeted advertising. Where we rely on your consent, you can withdraw it at any time in the Game's settings (see "Privacy choices"); withdrawing it does not affect the processing that took place before.

To make a request, including a request to delete your data, email us at support@koplaystudio.com and include the name of the Game. The Games do not show you the random identifier that GameAnalytics uses, so to help us find your data, also tell us your device model, the country you played in, and roughly when you installed the Game and when you last played it. We will ask GameAnalytics to delete the data that can be linked to your installation, and we will tell you if we cannot find it. Google Analytics for Firebase links its data only to a random app-instance identifier that the Games don't show, so we usually can't find your data there; Google Analytics deletes it automatically after 2 months, and clearing the Game's data makes Firebase start over with a new identifier. For a first open that Google Ads received from one of our campaigns, Google's own privacy controls apply (policies.google.com/privacy). We will respond within the time required by law, and we keep your email only as long as needed to handle your request. To delete what is stored on your device, clear the Game's data or uninstall it (see "Data stored on your device"). You can also contact GameAnalytics directly at privacy@gameanalytics.com, and you can lodge a complaint with your local data protection authority.

Changes to this policy

We may update this policy from time to time, for example when a Game adds or removes a service. If a Game adds ads, in-app purchases or another service that collects information, this policy will be updated, or the Game will get its own policy, before that version is released. Changes are posted on this page with a new effective date.

Contact

Koplay (Chen Kopel). Questions about this policy or your data: support@koplaystudio.com