Classic Retro Game EmulatorNo account, ever. Your games, saves and favorites stay on your phone. The app shows ads (never during gameplay) and sends usage/crash data automatically — that part is not opt-in today. The catalog/game-file server uses plain HTTP, not HTTPS. All of that is spelled out in full below.
1. Who this policy covers
This policy describes how the Classic Retro Game Emulator app for Android (“Classic Retro Game Emulator”, “the app”) and this website handle information. It is written to match what the app actually does, not a generic template.
The short version: Classic Retro Game Emulator has no accounts. Nobody signs up, logs in, or gives us a name or email address. The app does show ads, and it does send usage and crash data automatically — both are described in full below, including the parts that are less flattering than a typical “we respect your privacy” page tends to admit.
2. What we collect
Classic Retro Game Emulator does not ask you to create an account and does not ask for your name, email or phone number. The app contains none of the following:
- social login, payment, subscription or billing systems;
- chat, messaging or any way for users to contact each other;
- code that is downloaded and run as a new app feature after install (see Network requests for the one nuance here: per-console emulator files are fetched, not app code).
There are two things the app sends automatically, described in full in their own sections: advertising data (Google AdMob) and usage/crash data (Google Firebase Analytics and Crashlytics). Unlike many apps, the usage and crash reporting in Classic Retro Game Emulator is not an opt-in toggle — it is currently always on, with no setting to turn it off. If that matters to you, see Analytics & Crash Reports below before installing.
This website is a static set of pages. It does not set cookies, run analytics, or load third-party scripts or ads.
3. What the app stores on your device
To work offline after a download, Classic Retro Game Emulator keeps the following in its own app storage, which other apps cannot read. None of it is sent to us.
| Data | What it is | How to remove it |
|---|---|---|
| Game files | The games you chose to play or download, across any of the 11 consoles. | Delete a game, or Clear Cache in Settings. |
| Emulator cores | The per-console emulator engine files, downloaded the first time you play that console. | Clear Cache in Settings, or uninstall. |
| Save states | In-game save/load states, exports and imports, kept inside the emulator's own storage. | Uninstall or clear the app's data. |
| Favorites & recently played | Which games you've favorited and recently opened. | Un-favorite in the app, or clear app data. |
| Settings | Gamepad size and opacity, and similar preferences. | Clear the app's data in Android settings. |
Uninstalling Classic Retro Game Emulator removes all of it.
4. Network requests the app makes
Classic Retro Game Emulator works offline once a game and its console's emulator core are downloaded. Here is what it requests, and from where:
| When | What is requested | Stored? |
|---|---|---|
| You browse the catalog or library | Cover art for the games on screen. | Cached on your device. |
| You play or download a game | That game's file, from a third-party game server. | Saved in the app's private storage. |
| You play a console for the first time | That console's emulator engine files, from the same third-party server. | Cached on your device; not re-downloaded after that. |
A note we'd rather state plainly than leave out: requests to that third-party game server currently travel over plain HTTP, not HTTPS — that server does not support an encrypted connection at this time. Every other connection the app makes (ads, analytics) uses HTTPS. We're aware this is not ideal and are not going to pretend otherwise.
Who receives these requests
Cover art, game files and emulator cores are served by a third-party content server that we do not operate and whose logs we do not receive. Like any web request, it can see the technical details of what's asked for: your IP address, the file requested, and the time. How that server handles that information is governed by its own practices, not this policy. If you'd rather not make those requests, don't browse the catalog or play/download games while online.
5. Advertising
Classic Retro Game Emulator shows ads served by Google AdMob to stay free: on the Home screen (as part of the game shelves), on the Library screen, as a banner on a game's page, as an occasional full-screen ad when you exit the emulator, as a full-screen ad when the app returns to the foreground, and as a short rewarded ad you watch to unlock playing or downloading a game.
The rewarded ad before Play or Download has no skip option. You either watch it through (or it fails to load, in which case nothing is unlocked) or you cancel and the action doesn't happen. This is a deliberate choice, not an oversight, and we think you should know about it before installing rather than discover it the first time you tap Play.
There is never an ad while you are actively playing a game — only before/after and on the browsing screens described above.
To serve and measure ads, AdMob can use your device's advertising ID and can see the technical details of an ad request (your IP address, device and app information, and an approximate location derived from your IP). We do not receive or store this ourselves; it is processed by Google under Google's own privacy policy. You can review or reset your advertising ID, and control ad personalization generally, in your device's Google settings, or opt out of interest-based ads at adssettings.google.com.
6. Analytics & Crash Reports
Classic Retro Game Emulator sends usage and crash data through Google Firebase (Analytics and Crashlytics). Unlike a typical privacy-conscious app, this is not opt-in — there is currently no setting to turn it off. It is on from first launch.
What is sent:
- app-interaction events: viewing a game, favoriting a game, searching, starting/completing/cancelling/failing a download, launching a game in the emulator, and the result of a rewarded-ad watch — each tagged with the game's catalog id, never anything you typed into search beyond the search event itself;
- crash reports and non-fatal errors, including a stack trace, the app version, device model and Android version — this includes every unhandled error in the app, not only ones a developer specifically chose to report;
- Firebase's own device and app identifiers, used to group the above together.
None of this includes your name, your downloaded-games list as a whole, or your save data. It is processed by Google under Google's own privacy policy. Because there is no in-app toggle today, the only way to stop it is to not use the app, or to contact us below if you'd like this to become configurable.
7. Android permissions
Classic Retro Game Emulator requests:
- Internet and network state: to load covers, download games and emulator cores, and for ads and analytics, as described above.
- Vibration: for feedback when you tap on-screen controls.
- Storage (legacy, older Android only): a compatibility permission for Android versions before 13; it is unused on current Android versions.
The Google Mobile Ads SDK adds an advertising ID permission, standard for any app that shows ads, used only for the ad purposes above. The background download component the app uses also requests standard, non-sensitive permissions needed to keep a large download running (a foreground service and wake lock) — these don't involve any additional data collection.
Classic Retro Game Emulator does not request your location, contacts, calendar, photos, files, camera or microphone.
8. Controllers and audio
If you connect a gamepad or keyboard, Classic Retro Game Emulator reads its input only to control the game and does not record or transmit it. The app does not access your microphone and does not record audio.
9. How we protect your information
Your games, saves and settings live in the app's own private storage, isolated from other apps. Ad and analytics traffic uses HTTPS. The one exception — the plain-HTTP game-content server — is described in Network requests above, not hidden here.
No method of storage is perfectly secure, and a lost or unlocked phone exposes whatever is on it. Keep your device locked.
10. Your choices
Because we hold no account or personal profile about you, there is no account data to look up, correct or delete on our side. You stay in control of what's on your device:
- delete individual games, or clear everything, from the Downloads screen;
- un-favorite games at any time;
- clear the app's cache or data in Android settings, or uninstall it to remove everything;
- control your advertising ID and ad personalization in your device's Google settings.
There is currently no in-app control over the analytics/crash reporting described above. If privacy laws where you live give you rights over data a company holds (such as access, correction or deletion), they apply to any data processed about you — see Google's own privacy policy for the Firebase/AdMob side of that, and feel free to contact us with any question.
11. Children
Classic Retro Game Emulator is a general-audience game player, not directed at children. It does not knowingly collect personal information from anyone, has no accounts or chat, and does not configure its ads as child-directed. Parents and guardians should decide which classic games are appropriate for a child to play.
12. How long data is kept
On your device, data stays until you delete it or uninstall the app. Analytics and crash data sent to Firebase is retained under Google's own Firebase data-retention settings; we do not keep a separate copy ourselves.
13. Changes to this policy
If the app's behavior changes in a way that affects privacy — for example, if usage/crash reporting becomes an optional toggle, or the game-content server moves to HTTPS — this page will be updated and the date at the top will change. See also our Terms of Use.
14. Contact
For privacy questions, write to muha.syaifudin@gmail.com.