This policy describes how RetroVault (package com.retrovault.emulator), published by GukoMentum, handles information when you use the Android, iOS, Amazon, or Web versions of the app. It is written for store disclosure and end-user transparency. It is not legal advice.
1. Who we are
RetroVault is a retro game emulator and homebrew catalog app. The developer/publisher identity is GukoMentum. For privacy questions, rights requests, or catalog takedown notices, contact us using the details in Section 10.
2. Summary
- We use Google Firebase (Analytics, Crashlytics, and Remote Config) for product analytics, crash diagnostics, and remote feature configuration.
- The app makes network requests for Remote Config, game cover thumbnails, and optional catalog game-file downloads.
- Favorites, download history, ROMs, thumbnails cache, and resume data are stored on your device in app-private storage or local preferences.
- If you import your own ROM files, those files stay on your device and are not uploaded to GukoMentum servers.
- Mobile store builds are intended to ship without a third-party mobile ad SDK. Web builds may optionally enable AdSense when that build flag is turned on.
3. Information collected through Firebase
When Firebase initializes successfully, the following Google Firebase services may process data:
3.1 Firebase Analytics
- Types: App interactions and other usage events (including automatic Analytics events and custom events such as device authenticity probe metrics), device/app identifiers used by Firebase (for example Firebase installation identifiers), and coarse device/app metadata needed to attribute events.
- Purpose: Analytics — understand feature usage, stability trends, and product performance.
- Processing: Sent to Google Firebase over encrypted connections. Collection typically begins after Firebase dependency checks succeed at app start.
3.2 Firebase Crashlytics
- Types: Crash logs, stack traces, and diagnostic/app-performance related data; device and app metadata associated with a crash report.
- Purpose: App functionality and analytics — diagnose crashes and improve reliability.
- Processing: Sent to Google Firebase when a crash or non-fatal issue is reported.
3.3 Firebase Remote Config
- Types: Configuration fetch requests and related identifiers/metadata needed to return parameters (for example catalog safety flags such as whether certain content rails are shown).
- Purpose: App functionality — remotely configure feature behavior without shipping a new binary.
- Processing: Requests go to Google Firebase; returned values are applied on-device.
Firebase is operated by Google. Google may process data as described in Google’s privacy documentation for Firebase products. We treat SDK collection as app collection for Play Data Safety and similar disclosures.
4. Other network activity (non-Firebase)
Depending on features you use, RetroVault may also contact:
- Cover / thumbnail hosts — for example GitHub-hosted thumbnail URLs, Archive.org assets, or other CDN URLs referenced by the catalog — to display game artwork. Requests generally include the image URL and standard HTTP client metadata.
- Catalog file download endpoints / proxy — when you choose to download a catalog game, the app fetches the file through the configured download URL or proxy. Downloaded files are stored in app-private persistent storage on your device.
- Web ads (Web builds only, when enabled) — if a WebGL build is compiled with the AdSense flag, Google AdSense / H5 Games Ads may load creative and related measurement scripts in the browser. Mobile Play/App Store builds are expected to keep ads off unless an ad SDK is later added intentionally.
These hosts receive standard network request data (IP address, user agent, requested URL) as part of ordinary HTTPS traffic. We do not operate a RetroVault account system and do not ask you to create a username or password.
5. Information stored only on your device
- Favorites and download registry — stored in local preferences (PlayerPrefs).
- Downloaded catalog ROMs, cached thumbnails, and resume manifests — stored under the app’s private persistent storage.
- Imported user ROMs — copied into app-private storage (for example a
UserRomsdirectory) after you pick a file with the system document picker. The app reads only files you explicitly select. Imported files are used for local playback and are not uploaded to our servers. - Controller / layout preferences and similar settings — stored locally on the device.
On Android, local import uses the Storage Access Framework document picker and does not require broad external-storage permissions for this flow.
6. How we use information
- Operate and improve RetroVault (catalog browsing, downloads, emulation, settings).
- Measure usage and diagnose crashes via Firebase.
- Apply remote configuration for safety and product flags.
- Respond to support, privacy, or rights-related requests you send us.
We do not sell your personal information.
7. Sharing and service providers
- Google Firebase / Google — Analytics, Crashlytics, and Remote Config processing.
- Content hosts / CDNs / download proxy operators — receive technical request data when the app fetches thumbnails or catalog files you request.
- Advertising partners (Web, only if AdSense is enabled in that build) — may receive ad-related data in the browser.
We may also disclose information if required by law or to protect users, the public, or our rights.
8. Retention and deletion
- On-device data: Favorites, downloads, imported ROMs, and local caches remain until you clear app data or uninstall the app. Uninstalling RetroVault removes app-private sandbox storage, including imported ROMs stored there.
- Firebase / Google: Analytics, crash, and Remote Config-related data are retained according to Google Firebase product retention settings and Google’s policies. We do not operate a separate RetroVault cloud profile that lets us remotely wipe a specific user’s local library.
- Requests: Contact us (Section 10) if you need help understanding deletion options for Firebase-held diagnostics or analytics associated with your use of the app.
9. Children
RetroVault is a general-audience emulator and is not directed at children under 13 (or the equivalent minimum age in your country). We do not knowingly collect personal information from children for the purpose of creating child accounts. If you believe a child has provided personal information through support channels, contact us and we will take appropriate steps.
10. Contact and catalog rights requests
For privacy questions, Data Safety clarifications, or support:
- Email: support@retro-playground.com
- Developer: GukoMentum
- App: RetroVault (
com.retrovault.emulator) - Policy URL: https://retro-playground.web.app/privacy/
If you are a rights holder and believe catalog artwork or a listed homebrew title should be removed or corrected, email the same address with:
- Your name / organization and contact details
- The game title and platform/system as shown in RetroVault
- A description of the rights you hold and the change you request (removal or correction)
- Links or other evidence supporting the request
We will review complete requests and respond as reasonably practical.
11. Security
We use HTTPS for network requests to Firebase and typical catalog/thumbnail hosts. Local game files remain in the OS app sandbox. No method of transmission or storage is 100% secure; please keep your device updated and avoid installing modified copies of the app from untrusted sources.
12. International processing
Firebase and other service providers may process data in the United States or other countries where they operate. If you use RetroVault from the EEA, UK, or similar regions, those transfers occur as part of using Google’s services under their terms and safeguards.
13. Changes to this policy
We may update this page when our product, SDKs, or legal requirements change. The “Last updated” date at the top will change when we do. Continued use of RetroVault after an update means you should review the revised policy.
14. Store listings
This HTML page is the public privacy policy intended for Google Play, Apple App Store, Amazon, and in-app “Privacy Policy” links. The same URL should be entered in store consoles and opened from the app via a browser link.