Digital GBA Privacy Policy
Operator: Starflow (스타플로우) · Contact: cs@starflow.co.kr · Effective: November 14, 2026
1. Scope and operator
Starflow operates Digital GBA for Android (com.starflow.digitalgba). This policy covers game execution, saves, file selection, patches, cheats, ads, optional usage analytics and crash reporting, and support.
The app has no registration or app-account login. Starflow does not require an account, name, phone number or birth date and does not set a direct user ID for analytics or reports. SDK-generated app-instance and installation identifiers may be used as described below.
2. Files and settings on your device
The app handles selected ROM copies and game names, favorites and recent-game information, in-game saves and automatic/manual states and previews, cheat names and codes, linked folders and access grants, and language, sound, speed, display, controller and optional collection settings locally.
The current app has no feature that uploads complete original game, save or cheat files to Starflow servers or attaches file contents to ad requests. App-authored analytics events and custom error logs exclude game/file names, paths, URIs, search terms, cheat codes, game-identifying hashes, game contents and original error messages. Section 5 explains the separate scope and limits of automatic crash diagnostics.
3. Advertising and Google SDKs
The app includes Google AdMob Home banners and app-open ads, and Google UMP. A prepared app-open ad may appear on return after ten continuous minutes in the background; it is not shown on a first launch or after fully closing and reopening the app. Ad content is capped at G, independently of the app's intended audience of adults aged 18 or older.
Google advertising SDKs may collect or share IP addresses, app/ad interactions, performance diagnostics and device identifiers such as advertising IDs and app set IDs for delivery, measurement, analytics and fraud prevention. An IP address may indicate approximate location. Google documents encrypted SDK transmission. Actual handling depends on SDK, device, consent and ad settings.
Live advertising uses UMP consent information and required forms to determine whether requests may proceed. When required by the SDK, Home's Ad privacy options lets you revisit choices. These advertising choices are separate from usage analytics and crash-report choices. Declining personalized ads or analytics does not stop all ad-related processing.
This version retains Google test ad IDs. Test ads can involve SDK networking and do not establish that live consent settings have been validated. Live publisher IDs, regional consent configuration and this policy must be updated together to reflect actual operations.
4. Optional usage analytics — Firebase Analytics
Usage analytics is off by default. Choose it on the initial choice screen or in Home's Settings and change it later. Declining analytics does not restrict games, saves or patches.
When enabled, the app can send screen categories and feature use such as game launch/pause/speed, saves, imports, patches, cheats, controller editing and settings, with fixed success/failure/cancellation categories and bounded counts, durations, speed and orientation values. Screens use fixed internal names. The app does not track every frame or individual controller press.
Firebase Analytics may process an app-instance identifier, sessions, basic app interactions and automatically recorded ad interactions, app/OS/device details, and SDK analytics information such as country or region. The purposes are understanding feature use, improving performance and quality, and troubleshooting. The app disables Analytics advertising-ID collection and sets its consent for ad storage, ad user data and ad personalization to denied. Advertising SDK handling and UMP choices remain separate under section 3.
Turning analytics off stops app analytics-event transmission and requests a reset of on-device Analytics data. Resetting or uninstalling does not immediately delete all information already sent to servers. See sections 7 and 8 and the linked Google guidance for retention and requests.
5. Optional error reports — Firebase Crashlytics
Crash reporting is also off by default and can be chosen independently of analytics. If enabled, Java and native/NDK crash or error states can be sent to Firebase Crashlytics for diagnosis and stability improvement. Reports may include stacks, thread/module/device/OS/app-version information, installation identifiers and limited diagnostic state. If both choices are enabled, permitted feature events may form breadcrumbs before an error.
App-authored error details use predefined feature and error categories. Automatic fatal exception stacks and native minidumps may nevertheless contain exception messages, paths or portions of memory from the error state. We do not guarantee that all automatic diagnostics exclude every file name or user-related detail. Consider this when choosing reporting.
Turning reporting off stops app-authored error reporting and requests automatic-report disabling and deletion of unsent reports waiting on the device. The SDK's automatic-report override may take full effect on the next app launch. The SDK may store local reports while automatic transmission is disabled; the app requests deletion of prior pending reports before re-enabling but does not guarantee confirmation that deletion has completed. Consenting may also allow reports already waiting on the device to be transmitted. Already transmitted reports are not immediately deleted by this local setting.
These choices govern analytics and report transmission, not every network operation by ads, document providers or SDK initialization. SDK installation and diagnostic information can be associated with an installation or report even without a real name or app account.
6. File access, export and external providers
The app uses file/folder grants from Android system pickers. It does not request all-files access, location, contacts or microphone permission. Android automatic app backup is disabled.
Exporting .sav files, save ZIPs or corresponding source writes to your chosen document provider. A cloud provider has its own transmission and storage practices. Save ZIPs can contain game names, saves, slots and previews, and exclude ROMs, cheats and app settings. Exported files are not separately encrypted by this app.
7. Retention and deletion
Private app data is retained for app functions. Clear Android app storage or uninstall to delete it. Removing a library game removes its ROM copy and entry but retains saves for re-import. Unlinking or internal removal does not delete external originals, exports or cloud copies; delete them at those locations too. There is no app account to delete.
Analytics and advertising retention follows Google's policies and actual service/project settings. Google describes retaining Crashlytics traces, processed dump information and associated identifiers for 90 days before starting deletion. SDK retention policies may change; see the current linked guidance. Local reset and collection withdrawal do not guarantee immediate, complete deletion of previously transmitted data.
8. Support, your rights and security
Send privacy, access, correction, deletion, restriction or consent-withdrawal requests to cs@starflow.co.kr. We act within our control under applicable law or explain the responsible provider's request channel. Do not attach ROMs, passwords, signing keys or unnecessary personal data.
Support email addresses and message contents are used to respond and deleted when the support purpose is complete and no longer requires them, except for necessary records under a legal obligation or unresolved dispute, within that scope and period. Internal files use Android app-private access controls, not a promise of separate encryption or external-backup security.
9. International processing and intended audience
Google advertising, Analytics and Crashlytics services and document providers may process information in other countries under their policies and configuration. The links below describe Google's processing locations, safeguards and rights channels. Visiting the public policy pages may involve Firebase Hosting processing request IPs for service operation and security. These policy webpages have no separate web-analytics script.
Digital GBA is a compatibility tool for adult retro-game users aged 18 or older worldwide. It does not ask for birth dates or exact age, store an age category, verify age or provide parental consent. Optional diagnostics consent is separate from age verification. Target audience and content rating are separate; actual ratings follow the store's questionnaire and assessment.
10. Policy changes
We may update this policy when features, SDKs, operations or law change, update the effective date and publish the changes in-app and on the public page, with further notice or consent where required.