General information and controller
This Privacy Policy governs the processing of information in the mobile application “RetroBoy” (hereinafter, the “App”), distributed via Google Play under identifier com.retroboy.emulator, developed independently without an associated legal entity. This policy is governed by the principles of data minimisation, purpose limitation and privacy by design (Art. 5 and 25 GDPR).
Collection and processing of personal data
Games, saves and settings are processed locally. If you enable Google Drive sync, battery saves, quick states, resume states, thumbnails and revision metadata are sent directly to your Google Account. When ads are requested, Google AdMob may process advertising or device identifiers, approximate location inferred from IP address, ad interactions and diagnostics.
- EMULATOR DATA: ROMs and settings remain on your device. Battery saves, quick states, automatic resume states and thumbnails are uploaded only if you connect Google Drive; they can also be exported manually. ROMs are never uploaded by RetroBoy.
- OPTIONAL GOOGLE ACCOUNT: No account is required to play locally. Drive sync requires choosing and authorizing a Google Account. RetroBoy stores the selected account locally and uses Google Play services for authorization; it does not store your Google password.
- ADVERTISING DATA: Google AdMob may collect and share advertising identifiers, approximate location, ad interactions and diagnostics with Google and its advertising partners to provide and measure ads, analyze performance and prevent fraud. The developer does not receive users’ advertising profiles.
Access to local files (ROMs and saves)
- —The App requires read and write access only to files and folders the user voluntarily selects via the official secure Android picker (Storage Access Framework / SAF).
- —ROMs (.gb, .gbc, .gba and supported archives), battery saves (.sav) and quick states are stored locally. You can export or import saves and compatible quick states as ZIP archives. If you choose an external folder, RetroBoy writes versioned ZIP backups of battery saves, quick states, resume states and thumbnails there automatically; it does not automatically import changes from that folder.
- —ROM files are never uploaded by RetroBoy. Google Drive sync, if enabled, uploads battery saves, quick states, resume states and thumbnails as described below. An external folder provider may upload selected backups under its own settings and policies. The user is responsible for owning a legal copy of imported titles.
Internet connectivity and third-party services
From version 1.0.7, gameplay previews are generated on your device without querying a cover repository. Internet is used for optional Google Drive sync and Google AdMob ad requests. Older versions may also download cover art when enabled. Ad requests are made only when Google UMP indicates that ads may be requested; regional consent choices are respected where required.
From version 1.0.7, RetroBoy automatically saves a small image of the last emulated game frame with its resume state and can show it in the library. This captures only game output, not other apps or your device screen. You can hide library previews in Settings. These thumbnails remain local unless included in Google Drive sync or exported backups that you enable. No cover images are downloaded or game titles sent to a cover provider by this feature. Older versions may query public repositories such as libretro-thumbnails on GitHub for covers: requests include game titles or filename variations and expose the device IP address to that provider. You can disable cover downloads in those versions. ROM contents, saves and account details are not sent to cover providers.
Tapping “Report an Error or Suggestion” opens the user’s default mail client to send a voluntary message.
Optional Google Drive sync and backup retention
From version 1.0.7, you can optionally connect Google Drive to sync battery saves (.sav), quick states, automatic resume states and thumbnails. RetroBoy requests only https://www.googleapis.com/auth/drive.appdata, which permits access to its private application data space, without general access to your other Drive files. This space is managed through Google Drive’s app settings and is not a normal visible folder. No developer-operated server receives these saves.
The app sends battery saves, quick states, automatic resume states, thumbnails and metadata needed to identify games, verify integrity and handle revisions: an identifier derived from game content, save digest, revision relationships, date and device model. Google also receives the network information needed to serve requests. ROMs are not uploaded by automatic sync. Before connecting, the app warns that cloud data takes priority over local data for the same games. Existing cloud copies download automatically before play; if no cloud copy exists, local progress uploads. If devices diverge, the cloud copy takes priority and previous local progress remains in recovery history. Incompatible states are retained for recovery with a matching emulator version. Your selected account and sync ledger remain in private local app data. These save data are not used for advertising or sold.
Earlier cloud revisions are retained for recovery and are not automatically deleted in this version; they use storage associated with your Google Account. Disconnecting Drive stops sync and requests revocation of access, but does not delete local or cloud saves. You can remove authorization through your Google Account controls and delete the app’s hidden data through Google Drive settings. External backups remain until you remove them from the chosen provider.
Imports and restores preserve previous local progress in recovery history within RetroBoy’s private app storage. Clearing app data or uninstalling removes this local history. Sync depends on connectivity, authorization, available storage and Android scheduling; check its status before switching devices. See Google’s Privacy Policy for Google’s handling of data.
Advertising through Google AdMob
The Google Play version uses Google AdMob (Google LLC) for banner and interstitial ads. AdMob may process the Advertising ID or other device identifiers, approximate location inferred from IP address, app interactions (including ad views or clicks), and diagnostic data to deliver and measure ads, analyze performance, and prevent fraud. Ad requests use a teen-directed treatment and are limited to content rated G. Where required, Google’s User Messaging Platform (UMP) presents choices to consent, reject, or manage options. You can reopen privacy choices from the app’s Settings when that option is available. Depending on your choices, location and ad availability, ads may be personalized, non-personalized, limited, or not requested. See Google’s Privacy Policy and how Google uses data in advertising.
The developer does not sell personal data. AdMob and its partners process information under their own policies and the choices presented through UMP. The developer does not receive a user’s Advertising ID or personal ad profile.
Optional purchase to remove ads
RetroBoy offers an optional one-time purchase to remove banners and ads shown when starting games. This is a permanent purchase, not a subscription. Google Play handles payment and billing details. RetroBoy does not receive your card details or require its own user account.
The app queries Google Play for purchase ownership and verifies the purchase signature. It stores the signed receipt and information needed to recognize the purchase locally on your device, including for offline use. This integration does not send receipts to a developer server or use them for advertising or analytics. Google Play may receive the product identifier and purchase token when processing and acknowledging the transaction.
You can restore your purchase with the same Google Play account from the menu or Settings. A refund or revocation may disable ad removal after the app checks ownership again with Google Play. Clearing app data removes the local receipt but does not cancel or refund the Google Play purchase. See Google’s privacy policy for Google’s handling of payment data.
Device permissions
RetroBoy uses permissions needed for emulation, optional sync and advertising:
Children’s privacy (COPPA / GDPR-K)
The Google Play audience declaration for RetroBoy is ages 13 and older. Ad requests apply a teen-directed treatment and a maximum content rating of G. The app does not request precise location permission. Parents or guardians can contact the developer through the support contact on the Google Play listing with privacy questions.
Information security
Android isolates the app’s local files and controls access to selected documents and folders. Drive requests use HTTPS and are authorized by Google Play services. Saves are sent directly to Google rather than to a developer-operated server. Save integrity checks and recovery history help detect damaged archives and preserve progress when restoring; users should also keep independent backups.
Changes to this privacy policy
We may update this Policy to reflect functional improvements or regulatory adjustments. Any modification will be published on this same page with its effective date. The date shown in the header (“Last updated”) determines the applicable version. Continued use of the App after publication implies acceptance of the current version.
Contact and user rights
For questions about RetroBoy, contact the developer through the support details on its Google Play listing. For information, choices or rights requests concerning advertising data processed by Google AdMob, consult Google’s privacy tools and policies linked above. The developer does not receive users’ advertising identifiers or personal ad profiles.