Privacy Policy for Pixel Miner


Effective date: 16 November 2026

Publisher and data controller: Overload, an individual developer based in Vietnam

Contact for privacy questions, support and requests: overloadworkspace@gmail.com


This policy explains what information Pixel Miner (the "game") collects, why, who receives it, how long it is kept, and what choices you have. It describes the iPhone and iPad version (App Store) and the Android version (Google Play). Section 13 says what is different on Android. We wrote it to be read. If something is unclear, email us.


1. The short version


You do not need an account. We do not ask for your name, email address, phone number, contacts, photos, microphone or precise location.


The game is free and sells optional in-app purchases through Apple (iPhone and iPad) or Google Play (Android).


Gameplay, analytics and crash data: we always collect it, from the first time you open the game, to fix bugs, keep the game from crashing or freezing and balance it. The game does not ask first and has no switch to turn it off. You can ask us to delete it (section 6) or stop it by deleting the game. Buying things goes through the App Store or Google Play, which have their own data flows (see sections 2 and 3). On Android, the game connects to Google Play each time you open it, and Google receives a short technical message from that connection (section 2.7).


Ads: the game does not show ads at the moment. It contains advertising software (Unity LevelPlay) that is switched off and starts no network connection. If we switch ads on, we will update this policy first and, in the European Union, the European Economic Area, the United Kingdom and Switzerland, ask you before the ad software starts. Older versions of the Android game, from before the update that added the Privacy button, show ads and work differently. If the settings of your Android game have no Privacy button, you have an older version, and section 13 describes it.


Meta (Android only): to see which of our Facebook and Instagram ads lead to installs, the Android game sends Meta Platforms ("Meta") an install event, an app-open event and your Google advertising ID, and may send purchase events (section 2.4). You can stop it with the Do Not Sell or Share switch in the Privacy sheet once the game has started (it cannot take back what was already sent, and the Facebook software may still send an app-open event each time the game launches, before the switch is applied), and you can delete your advertising ID in your Android settings (section 4). Older Android versions have no switch and send these events whatever you choose (section 13). The iPhone and iPad game sends nothing to Meta, and it does not track you across other companies' apps and websites, so iOS does not show its tracking question.


You can use the Privacy button in the game's settings to read this policy, use the Do Not Sell or Share switch, ask us to delete your data and contact us.


Pixel Miner is a general-audience puzzle game. It is not designed for children.


2. Information we collect


Analytics and crash data (sections 2.1 to 2.3) are collected from the first time you open the game, whatever you do, and the game does not ask first. Meta event data on Android (section 2.4) is described there and in section 4. Older Android versions also send ad data (sections 2.4 and 13). Besides these, the game also has the store connection data on Android (section 2.7), the game content connections (section 2.8) and, on Android, the first-open information about how you found the game (section 2.9).


2.1 Device and app identifiers. A random installation ID (your Player ID) that the game creates on your device. It is not your name, email or advertising ID and is not shared with other apps. It is stored on your device, and we send it to PostHog and to Google Firebase (as its user ID). Google Firebase also creates its own app-installation ID. On Android, Google Firebase's notification software (Firebase Cloud Messaging) may also give your device a notification token, which stays with Google; we do not send notifications through it. Why: to count players and keep analytics consistent.


2.2 Gameplay and usage data. Examples: app opens, sessions, levels started, completed, failed or retried, coins, energy, gems and items you earn and spend, boosters and revives you use, chests, Battle Pass progress, buttons you tap, on older Android versions the ads shown, tapped or finished, settings you change and, when we test a game setting, which variant of the setting your device was given. Purchases: when you buy something, the game records which item, the price and currency, and the store's transaction number (Apple's, or Google Play's order number). We never see your payment card, your Apple ID or your Google account details. Why: to understand how the game is played, fix bugs, tune difficulty and decide what to improve.


2.3 Game settings, device and network information. The game asks our analytics provider for the current values of some game settings (for example how often certain screens appear). That request contains your Player ID and the device details below. Device and network details: device model, operating system and version, language, country, time zone, screen size and IP address. Our analytics provider receives your IP address with each message and uses it to work out approximate location (such as country and city). Why: to make the game run on your device and to produce regional statistics.


Crash and performance data. Crash logs, error messages, reports of the game freezing or not responding (on Android, "ANR" reports) and performance measurements, sent by Google Firebase Crashlytics. They contain technical details about your device and the state of the game when the problem happened. They are not linked to your Player ID. Why: to find and fix crashes and freezes.


2.4 Advertising measurement data (Android). This is the one kind of data the Android game sends to Meta, through the Facebook software inside the game. Meta receives an install event (the first time the game opens on your device), an app-open event each time you open the game, and, if you buy something, a purchase event that the Facebook software logs automatically. With these events the Facebook software sends your Google advertising ID, technical details (your IP address, device model, Android version, language, app name and version) and app details such as screen names. It also sends Meta reports when the game crashes or stops responding. Why: so we can see which of our Meta ads lead to installs and improve those ads. Meta uses the data under its own policy, including to deliver and measure ads and keep its services safe (section 3). The iPhone and iPad game does not send this data to Meta or to any advertising company. We do not receive Meta's data about you in a form that identifies you; we see totals and campaign results.


Older Android versions. Older versions of the Android game (section 13) also send ad data, from the first time you open the game and whatever you choose. Their ad software (Unity LevelPlay, with the Unity Ads network) starts each time the game opens, in every country, and the game does not ask first. It receives device and ad data to choose and show ads, to measure them and to prevent fraud: your IP address, device type, Android version, language, the app, the ads you saw or tapped and your Google advertising ID unless you deleted it. The ad providers use this data to show ads that are more relevant to you, and act as independent controllers for part of it (section 3). Those versions also contain software from AppsFlyer, a marketing measurement company; it is part of the game but is not switched on, and it sends nothing.


If we switch ads on in the current game, the ad provider will also receive device and ad data (section 3). That is not happening now.


2.5 Your privacy choices. Your Do Not Sell or Share choice, stored on your device. Why: to respect it. Older Android versions have no such switch and store no privacy choice (section 13). The Facebook software on Android starts before the game applies this choice, so with the switch on, the app-open event (with your Google advertising ID, unless you deleted it) may still be sent each time the game launches. Section 4 explains.


2.6 What you send us. Your email address and the content of your message if you contact support. Why: to reply to you.


2.7 Store connection data (Android). When the game connects to Google Play, which happens each time you open the game, the Google Play billing software inside the game may send Google a short technical message: the game's name and version, the billing software's version, your device model, Android version, country and language. We do not add your name, email, Player ID or advertising ID to it, and we do not receive it. Google uses it for its own purposes under Google's privacy policy (section 3). Why: it is part of Google Play's own billing software, which the game needs to show prices and complete purchases.


2.8 Game content connections. Every time you open the game it downloads level data from our own server (hosted on Google Firebase Hosting), downloads text translations from a Google service, and checks the current time with Google. Like any website, these servers see your IP address and basic connection details. We do not use these connections for analytics or advertising. Why: to load the game's levels and texts and keep timers correct.


2.9 How you found the game (Android). When you first open the game on Android, Google Play can tell the game which link or campaign brought you to the store page, for example a creator's video link. It is a short label such as the channel name (source, medium, campaign), not your name, email or advertising ID. We keep only those labels, attach them to your Player ID in PostHog, and use them to see which of our posts and videos bring players and how long those players stay.


We do not collect precise location, contacts, photos, files, microphone or camera data. We do not run user accounts. We do not knowingly create profiles that identify you by name. We do not make decisions about you by automated means that have legal or similarly significant effects.


3. Who receives information (service providers and stores)


We use a small set of third parties. Each has its own privacy policy, linked below.


Analytics and remote settings: PostHog (PostHog, Inc., United States). It receives gameplay and usage data, your Player ID, device and app details and, on Android, how you found the game (section 2.9). We use PostHog's Cloud in the United States: your data is stored on servers in the United States. PostHog can also process data elsewhere under the safeguards in section 9, and uses subprocessors such as Amazon Web Services; its list is at https://posthog.com/subprocessors . Its policy: https://posthog.com/privacy


Analytics and crash reports: Google Firebase (Google Analytics for Firebase and Firebase Crashlytics). It receives event data, the Firebase installation ID, device and crash data. We keep Google Analytics' advertising features switched off: Firebase does not receive your advertising ID and we do not use it for advertising. In older Android versions these features are not switched off, so Google Firebase may receive your Google advertising ID there (section 13). Its policy: https://policies.google.com/privacy


Advertising measurement (Android only): Meta Platforms (Meta Platforms Ireland Limited in the European Union, the European Economic Area and Switzerland, Meta Platforms, Inc. elsewhere). It receives the data in section 2.4. Meta's Business Tools Terms treat Meta and us as joint controllers of this event data in the European Union, the European Economic Area and the United Kingdom: we decide to send it so that we can measure our ads, and Meta decides how it uses it for its own purposes. Its policy: https://www.facebook.com/privacy/policy . To use your rights over what Meta holds, see section 6.


Ads: the game shows no ads at the moment (section 1). The ad software, Unity LevelPlay, is switched off and receives nothing. Before we switch ads on we will update this policy to name the ad providers and the data they receive.


Advertising (older Android versions only): Unity LevelPlay (the ad service of Unity Technologies, including ironSource, a Unity company) and Unity Ads, the ad network we use through LevelPlay. They receive the ad data in section 2.4. They decide which ads to show and may share data with advertisers and partners as described in their policy: https://unity.com/legal/game-player-and-app-user-privacy-policy . You cannot opt out of ads in a version that shows them. Older Android versions have no Do Not Sell or Share switch and do not ask for your permission first, in any country; you can reset or delete your advertising ID in your Android settings (section 4). AppsFlyer software is part of those versions but is not started and receives nothing.


Purchases: Apple on iPhone and iPad, Google Play (Google) on Android. When you buy something, the store handles the payment under its own terms and privacy policy and tells us that the purchase happened. The store acts for itself, not for us. Apple's policy: https://www.apple.com/legal/privacy/ . Google's policy: https://policies.google.com/privacy . On Android, Google Play also receives the store connection data described in section 2.7.


Overload does not sell your data for money. Because Meta uses the Android install and app-open events and the advertising ID for advertising purposes, some laws (for example the California Consumer Privacy Act) treat sending them as "sharing" for cross-context behavioural advertising; the Do Not Sell or Share switch in section 4 lets you opt out of further events once the game has started (the app-open event at launch may still be sent). Older Android versions have no such switch, so nothing in them stops these events or the ad data (section 13).


PostHog and Google Firebase act for us: PostHog under a data processing agreement with us, Google under its Firebase data processing terms. We require providers that act for us to protect your data to the same standard as this policy. Meta and the ad providers (see above) and the App Store and Google Play, which distribute the game and handle purchases, act for themselves.


4. Your choices


Analytics and crash reports. The game collects them from the first time you open it and does not ask first. There is no switch for them in the game. You can ask us to delete the data linked to your Player ID (section 6), you can object to this processing by email (sections 5 and 6), and you can stop all collection by deleting the game.


Do Not Sell or Share My Personal Information. A switch in the Privacy sheet (off by default). On Android, when on, the game tells the Facebook software to stop logging app events and stop collecting your advertising ID. The switch works once the game has started. It cannot take back what was already sent, and it cannot stop the events sent before the game could apply it: the install event and the first app-open event are sent when you first open the game, before you can reach the switch, and because the Facebook software starts before the game does, the app-open event may still be sent each time the game launches, even with the switch on. Apart from that launch event, with the switch on the game tells the Facebook software to log no further events. On iPhone and iPad the game sends nothing to Meta or any other advertising company, so there is nothing for the switch to turn off. If we switch ads on, the switch will also tell the ad provider that you opt out of the sale or sharing of your personal information, as the laws in some places ask. We do not discriminate against you for using it. Older Android versions have no switch (section 13).


Advertising ID (Android). Android has no tracking prompt. The Privacy sheet has an Advertising ID link that opens your Android settings, where you can reset your advertising ID or delete it (where these settings are depends on your phone). If you delete it, Meta gets no usable advertising ID. The install and app-open events are still sent, without it, unless you also use the Do Not Sell or Share switch. Older Android versions have no link in the game: use your Android settings directly; with the ID deleted, the events are still sent and, in those versions, ads are still shown (section 13).


Tracking prompt (iPhone and iPad). The game does not track you across other companies' apps and websites and does not use your iOS advertising identifier, so iOS does not show its tracking question for this game.


Ads. The game shows no ads at the moment. If we switch ads on, in the European Union, the European Economic Area, the United Kingdom and Switzerland the game will ask you for your permission before any ad software starts, with equally easy Accept and Decline buttons, and we will update this policy first. Older Android versions show ads and start their ad software each time you open the game, in every country including the European Union, the European Economic Area, the United Kingdom and Switzerland, and they do not ask you first. To stop the ads, update the game from Google Play (the current version shows no ads) or delete it.


5. Legal bases (where the law requires one)


Analytics and crash reports: our legitimate interests in keeping the game working, fixing crashes and freezes and improving the game (Art. 6(1)(f) of the GDPR and UK GDPR, and the Swiss Federal Act on Data Protection where it applies). The data is limited to what is listed in section 2 and we do not link it to your name. You can object at any time by email (section 6).


Android install, app-open and purchase events sent to Meta: our legitimate interests in measuring and improving our advertising (Art. 6(1)(f)). Meta has its own legal bases for what it does with the data (section 3). You can object at any time by email or with the Do Not Sell or Share switch.


Older Android versions: ads, and the Meta events sent without a switch: our legitimate interests in measuring and improving our advertising and in funding the game with ads (Art. 6(1)(f)). Meta and the ad providers have their own legal bases for what they do with the data (section 3). Older Android versions do not ask for your consent before their ad software or the Facebook software starts. You can object at any time by email (section 6), update the game or stop them by deleting it.


Purchases: we process purchase records to give you what you bought and to keep records the law requires (Art. 6(1)(b), (c)).


Replying to your support request: contract or our legitimate interest in helping players (Art. 6(1)(b), (f)).


Keeping a record of your choices on your device, preventing abuse and keeping the game secure: legitimate interests (Art. 6(1)(f)).


6. Your choices and rights


In the game: the Privacy sheet in the settings lets you switch Do Not Sell or Share, open the privacy policy, open the advertising ID settings on Android, ask us to delete your data and contact us. Older Android versions have no Privacy sheet: use your Android advertising ID settings (section 4) and email us.


Your legal rights. Depending on where you live (for example under the GDPR, the UK GDPR, the Swiss Federal Act on Data Protection, the California Consumer Privacy Act and similar laws) you may have the right to: know what we hold about you, get a copy, correct it, delete it, restrict or object to processing, withdraw consent where we asked for it, move your data, and complain to your data-protection authority (see section 14). We do not discriminate against you for using these rights.


How to use them. Email overloadworkspace@gmail.com. The game has no account, so we can only find analytics data that is tied to your device if you give us the Player ID (a random ID created by the game). It appears in the Privacy sheet and in the email the "Contact us" button prepares. Older Android versions do not show a Player ID, so those players cannot give us one. You can still email us without a Player ID, but we cannot look you up by name or email address, and without a Player ID we cannot find or verify device-linked analytics data; we will say so. We reply within one month. We may need to confirm the request came from the device. If you object to analytics or crash reports, we delete the data linked to your Player ID; because the game has no analytics switch, new data from that device keeps arriving until you delete the game, and we will tell you this in our reply. Data held by Meta, the ad providers, Apple or Google Play is held by them; ask them directly using their policies in section 3, and we will pass on what you tell us.


Deleting your data. When we receive a verified deletion request that includes a Player ID, we delete your player profile and all events linked to that Player ID in our analytics provider (PostHog), and ask our other service providers to delete theirs. Crash reports are not linked to your Player ID, so we cannot find them by it; they are deleted automatically after 90 days. Meta's install and app-open events, and the ad data from older Android versions, are not linked to your Player ID; Meta and the ad providers hold them. If there is no Player ID, we delete anything else we hold about you that we can find (for example, your support emails). You can also delete the app. Your game progress is stored on your device only; deleting the app removes it. Data that is not linked to you personally and statistics that are already aggregated stay.


7. How long we keep information


Analytics events (PostHog): up to 7 years from the date of the event; PostHog deletes expired events in batches, so deletion can come a little later. Your player profile (your Player ID with the device and country details attached to it) is kept until we delete it; we delete profiles with no activity for 12 months. Aggregated statistics that do not identify you are kept longer.


Analytics events (Google Firebase): up to 14 months.


Crash reports: 90 days, then removed from live and backup systems on the provider's schedule.


Store connection data (Android): kept by Google under Google's policies. We do not hold it.


Meta event data (Android): kept by Meta under its own policy (section 3). We do not hold it in a form we can link to you.


Advertising data (older Android versions): kept by the ad providers for the periods in their own policies (section 3). We do not receive or keep it in a form we can link to you.


Support emails: up to 24 months after the last message.


Your Do Not Sell or Share choice: stored on your device until you delete the app or change it.


8. Children


Pixel Miner is a general-audience puzzle game rated 4+ by Apple because it has no mature content. It is not directed at children and is not in the App Store's Kids category. On Google Play the game's target audience is adults, 18 and over. The game does not ask for your age and does not check it. We do not knowingly collect personal information from children under 13, or under the age at which your country requires a parent's permission for online services (up to 16 in some countries), and we do not knowingly send Meta data about children under 13. If you are a parent or guardian and you think a child has used the game, email overloadworkspace@gmail.com, with the child's Player ID if the game shows one. We will delete the data we hold.


9. International transfers


Overload is run by an individual developer based in Vietnam. The game is offered in the App Store and on Google Play in the European Union, the European Economic Area, the United Kingdom and Switzerland, and in most other countries. It is not offered in Vietnam. We view reports and data from the services in section 3 from Vietnam. PostHog is a US company and stores analytics data in the United States, and its network provider routes traffic through locations worldwide. Google processes analytics and crash data in the United States and other countries. On Android, Meta processes the event data in section 2.4 in the United States and other countries where it operates, and, for older Android versions, Unity and its affiliates, including ironSource (headquartered in Israel), process ad data in the countries stated in their policy. So your data may be processed in the United States, Vietnam, Israel and other countries, including countries outside the European Economic Area, the United Kingdom and Switzerland that do not have the same data-protection laws as your own.


Where the law requires safeguards for a transfer, we rely on approved ones. PostHog states that it takes part in the EU-US Data Privacy Framework, the UK Extension to it and the Swiss-US Data Privacy Framework. Our data processing agreement with PostHog also includes the European Commission's standard contractual clauses, the UK International Data Transfer Addendum and the Swiss adaptation of those clauses. Google's Firebase data processing terms rely on the Data Privacy Framework for Google entities certified under it, and otherwise on the standard contractual clauses. For Meta, the safeguards are those in Meta's Business Tools Terms and privacy policy (section 3). Unity's policy states that transfers outside the UK and EEA rely on adequacy decisions or standard contractual clauses. You can email us for details of the safeguard that applies to your data.


10. Security


Data sent between the game and our providers is encrypted in transit (HTTPS/TLS). Your game progress is stored on your device. No system is perfectly secure. If a data breach affects you, we will tell you and the authorities as the law requires.


11. In-app purchases


You can buy optional items (for example coins, energy, bundles and a Battle Pass) through Apple on iPhone and iPad and through Google Play on Android. The store processes the payment. If you bought "remove ads" earlier, it stays yours; the game shows no ads at the moment. Older Android versions sold "remove ads" through Google Play; it removes the ads those versions show. On iPhone and iPad, "Restore Purchases" in the game's settings re-applies purchases that can be restored. On Android, email us if a purchase does not appear. The game does not sell random items for money. If the game offers chests, they are earned by playing, and their drop chances are shown in the game.


12. Changes to this policy


If we change what we collect, add a partner that receives new kinds of data, switch ads on, or change how we use data, we will update this page and the date above before the change reaches the game, and ask again for your consent where the law requires it. The latest version is always on this page and inside the game.


13. Android


The current Android version of Pixel Miner on Google Play (the one with a Privacy button in its settings) works like the iPhone and iPad version, with these differences. Older Android versions are described at the end of this section.


Analytics and crash reports. As on iPhone and iPad they are always on from the first time you open the game, and the game does not ask first (section 4). This includes reports when the game stops responding.


Meta. Only the Android game sends Meta the install event, app-open events, purchase events and your Google advertising ID (sections 2.4 and 3). The Do Not Sell or Share switch and your Android advertising ID settings limit this once the game has started; the app-open event at launch may still be sent (section 4).


Advertising ID. Android has no tracking prompt. Meta uses your Google advertising ID, which you can reset or delete in your Android settings; the Privacy sheet links to them (section 4).


Ads. The game shows no ads at the moment (section 1).


Purchases. They go through Google Play, not Apple (sections 2.2, 3 and 11). Google Play's billing software also sends Google the store connection data in section 2.7 each time you open the game.


Older versions. Android versions of the game from before the update that added the Privacy button work differently. If the settings of your Android game have no Privacy button, you have an older version. In those versions: (a) the game shows ads, and its ad software (Unity LevelPlay and the Unity Ads network) starts each time you open it, in every country including the European Union, the European Economic Area, the United Kingdom and Switzerland, without asking you first; it receives your Google advertising ID unless you deleted it (sections 2.4, 3 and 4); (b) Google Firebase's advertising features are not switched off, so Google Firebase may receive your Google advertising ID; (c) Meta receives the install event, app-open events, purchase events and your Google advertising ID whatever you choose, because the game has no Do Not Sell or Share switch, no Privacy sheet, no Advertising ID link and no Player ID display, and asks no question when it first opens; some earlier builds that have the switch did not pass it to the Facebook software, so there the switch did not stop Meta's events; (d) deleting your Android advertising ID means Meta and the ad providers get no usable advertising ID, but the events are still sent and ads are still shown; (e) the game contains AppsFlyer software, which is not started and sends nothing; and (f) you can buy "remove ads" through Google Play, which removes the ads those versions show. Analytics and crash reports work as described above. To stop all of this, update the game from Google Play to get what is described in the rest of this policy, or delete the game (what Meta and the ad providers already received stays with them, section 6).


14. Support and contact


Support for Pixel Miner (questions, bugs, purchases, privacy requests): email overloadworkspace@gmail.com. Please include your device model, iOS or Android version and, if the game shows one, your Player ID. We reply within a few days, and to privacy requests within one month. Purchases and refunds are handled by Apple or Google Play: on iPhone and iPad use Apple's "Report a Problem" page; on Android see Google Play's refund help at https://support.google.com/googleplay/answer/2479637 .


Overload, Vietnam. Email: overloadworkspace@gmail.com

You may also complain to your local data-protection authority, for example the authority in the EU or EEA country where you live or work, the UK Information Commissioner's Office, or the Swiss Federal Data Protection and Information Commissioner.