This privacy policy explains what information is collected when you use RetroBlast Arcade ("the app"), how that information is used, who it is shared with, and what rights you have over it. We try to keep this document plain and honest. If anything is unclear, please contact us at [email protected].
RetroBlast Arcade is published by Joeri Kros, an independent developer
based in the Netherlands. The app's package identifier is
nl.joerikros.retroblast.
For any privacy questions, requests, or complaints you can reach us at:
[email protected]
To be explicit about what stays out of the app:
The following information is saved locally on your phone using Android's DataStore Preferences. It is never uploaded to our servers (we don't run any), and we cannot read it remotely:
You can delete all of this at any time by going to Android Settings → Apps → RetroBlast Arcade → Storage → Clear data, or by uninstalling the app.
RetroBlast Arcade relies on a small number of Google services to show ads, understand which features are used, and find crashes. These services collect their own data according to their own privacy policies.
The app shows banner ads on the home and leaderboard screens, full-screen interstitial ads between games, and optional rewarded video ads (which you watch voluntarily for an extra life or continue). Ads are served by Google AdMob.
AdMob may collect:
AdMob uses this data to serve ads, measure ad performance, prevent fraud, and apply frequency capping. For details, see Google's Privacy Policy and how AdMob uses data.
The app uses Firebase Analytics to understand how players interact with the app in aggregate. No personally identifying information is sent. Events are tied to a Firebase instance ID, not to your name or contact details.
Examples of events the app logs:
The app also sets a few aggregate user properties such as total games played, favorite game, and longest streak.
Firebase Crashlytics collects crash reports so we can fix bugs. When the app crashes, it may send:
Crash reports do not contain your name, email, or any text you typed.
Firebase Remote Config lets us roll out small configuration changes (for example, tweaking ad frequency or enabling a new game mode) without shipping a full app update. The app downloads configuration values from Google. It does not send personal information; only an app instance ID is used so that experiments can be bucketed consistently.
For more about how Firebase products handle data, see Firebase Privacy and Security.
If you live in the European Union, the United Kingdom, or the wider European Economic Area, the app uses Google's User Messaging Platform (UMP) to ask for your ad consent the first time you launch the app. The consent form lets you choose between personalized ads and non-personalized ads, in line with GDPR and the IAB Transparency & Consent Framework.
Outside the EEA and UK, the app uses your advertising identifier as permitted by Google's standard policies and your device's "limit ad tracking" setting.
You can reset your Android advertising identifier or opt out of personalized ads at any time via Android Settings → Privacy → Ads.
INTERNET — required to load ads, send analytics events, deliver crash reports, and fetch remote config.ACCESS_NETWORK_STATE — used to check whether you are online before trying to load an ad.VIBRATE — used for haptic feedback during gameplay (you can turn this off in Settings).com.google.android.gms.permission.AD_ID — declared transitively by Google Play Services so AdMob can use the advertising identifier.The app does not request location, camera, microphone, contacts, storage, or any other sensitive permission.
RetroBlast Arcade is suitable for general audiences but is not specifically directed at children under 13. We do not knowingly collect personal information from children under 13. If you are a parent or guardian and you believe your child has provided information through the app, please contact us at [email protected] and we will help.
If you are in the European Economic Area, the United Kingdom, or Switzerland, the General Data Protection Regulation gives you the following rights over personal data we (or our processors) hold about you:
To exercise any of these rights, email [email protected].
An honest note: because the app does not ask for your name, email, or any other identifier, we usually have no way to look up "your" data on our side. Most of the data the app uses lives only on your device — you can clear it through Android Settings (see section 3). For data held by Google AdMob and Firebase, please also see Google's privacy controls.
If you are a California resident, the California Consumer Privacy Act gives you additional rights:
We do not sell personal information. Some advertising identifiers used by AdMob may qualify as "sharing" under California law for the purpose of cross-context behavioural advertising. EU/EEA-style consent does not apply in California by default — if you want to opt out, please email [email protected] or use Android's "limit ad tracking" setting.
If you are in Australia, we handle personal information in accordance with the Australian Privacy Principles set out in the Privacy Act 1988 (Cth). You can lodge a complaint with the Office of the Australian Information Commissioner (OAIC) if you believe we have mishandled your data.
Google AdMob and Firebase process data on servers operated by Google globally, including in the United States. Where data is transferred from the EEA, UK, or Switzerland to a country that does not provide an equivalent level of data protection, Google relies on Standard Contractual Clauses approved by the European Commission, as described in Google's data transfer framework.
Locally stored data is protected by the standard sandboxing and permission model of Android. Data sent to Google AdMob and Firebase is transmitted over HTTPS. No method of transmission or storage is 100% secure, but we rely on industry-standard practices provided by Google.
We may update this privacy policy from time to time — for example, when we add a new feature or when applicable law changes. The "Effective date" at the top of this page reflects the most recent version. We encourage you to review this page occasionally.
Questions, concerns, GDPR/CCPA requests, or anything else? Reach the developer at: