RetroPaw

Privacy Policy

Last updated: April 2026

This Privacy Policy describes how RetroPaw (the “App”) handles information related to you. Where this Policy refers to permissions or device features, those descriptions follow what Google Play lists for RetroPaw and the declarations in the RetroPaw app package you install. If anything differs between this Policy and the Play listing for your installed version, the Play listing controls what is shown in the store for that version.

1. Scope

This Policy applies when you install and use the App on an Android device. If you do not agree, please stop using the App.

If you obtain the App through Google Play, installation, updates, billing, and related processing are also subject to Google’s and Google Play’s terms, policies, and privacy notices. We do not control those.

2. Information we process

We do not use the App to collect personal information for advertising or profiling. In normal use, the following categories apply:

(a) Files and locations you choose

Game files (for example ROMs), save locations, and similar items you select through the system file picker or equivalent are processed on your device in accordance with your choices. We do not operate an in-App feature in this build that uploads those files to servers we control for storage.

(b) Local app data

Saves, save states, settings, and similar data are stored locally on the device (or in storage locations the system or you grant the App access to), unless you use separate backup or sync tools outside this Policy.

(c) Device and system interfaces (local)

The App uses the Android APIs needed to run emulation, render video and audio, accept input, and respect your settings. Processing occurs on the device except where the operating system or Google Play handles data under their own rules.

(d) Network-related permissions in the shipped app

In the RetroPaw build we distribute, the app does not declare the Android permissions INTERNET or ACCESS_NETWORK_STATE among its own requested permissions. Your device, Google Play, and other apps may still use the network under their own rules; this sentence only describes what RetroPaw itself declares in that build.

3. Permissions and hardware features

This section tells you which permissions and hardware-related entries Google Play lists for RetroPaw, and what they are for in plain language. Technical Android names are shown where they match the store listing.

A. Permissions listed on Google Play for RetroPaw (four items)

The following exact names appear under Permissions in Google Play Console for RetroPaw:

  1. android.permission.RECORD_AUDIO
    Used only when a game or core needs microphone input and you grant microphone access in system settings, to supply audio to the emulation stack on the device. If you deny access, related features may be unavailable.

  2. android.permission.VIBRATE
    Used for controller/touch feedback and in-game vibration where supported.

  3. com.android.vending.CHECK_LICENSE
    Shown on Google Play for distribution/licensing verification handled by Google Play / Google when you obtain RetroPaw through the store. In the RetroPaw build we inspected, it does not appear among the app’s own uses-permission lines in the shipped manifest (see B below); the store listing can still show it.

  4. com.game.emulator.retropaw.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION
    Appears on Google Play and in RetroPaw’s shipped manifest as a signature-level permission plus matching uses-permission (a standard pattern when using current Android libraries). It is not a normal runtime permission for contacts, location, or similar user-granted data access.

B. Permissions RetroPaw declares in its shipped manifest (technical list)

For transparency, these uses-permission entries are present in the RetroPaw build we checked (they should match what the system associates with the app, aside from store-only entries such as CHECK_LICENSE as noted above):

C. Hardware features listed on Google Play (store scan — two items)

Google Play lists these under Features for RetroPaw:

D. Additional device-capability entries in RetroPaw’s shipped manifest

The same shipped manifest also includes (not necessarily shown in the short Features summary on Play):

These lines concern device capability for running the App, not access to contacts or messages.

4. Data storage, deletion, and security

On-device storage. Game content, saves, and settings are stored primarily on your device or in locations you or the system allow the App to use.

Deletion without contacting us. You can delete the App’s local data by uninstalling the App or using Clear storage / Clear data for this App in Android settings (wording varies by device). Whether backups or cloud copies exist depends on your device and account settings, not on this Policy.

What we do not operate for this build. Given Section 2(d), we do not operate a RetroPaw cloud service in that configuration that receives your ROMs, saves, or microphone streams for storage on servers we control. We therefore do not offer a separate “account deletion” portal for RetroPaw-hosted copies of those items for that configuration. If we add networked features in the future, we will update this Policy and, where required, provide appropriate controls.

Security. Use device lock screens and keep your accounts secure. Back up important data yourself before uninstalling or clearing data.

5. Third parties and libraries

The App is built with Android platform components and Jetpack (AndroidX) and other dependencies reflected in the shipped application. Their behaviour is governed by their licences and vendor documentation. For categories of data collected or shared as required by Google Play, complete answers belong in the Play Data safety section; this Policy is not a duplicate of that form.

When you use Google Play, Google processes information under Google’s policies. We do not control that.

6. Children

The App is not designed as a dedicated children’s product. If you are a parent or guardian and have questions about a minor using the App, contact us using Section 9. Rules for children’s data differ by country or region; this Policy does not provide legal advice for your specific jurisdiction.

7. Your choices

Where Android allows it, you can manage microphone access and other permissions the system associates with the App in system settings (the store may list permissions such as those in Section 3). Uninstalling or clearing app data removes locally stored App data on the device as described in Section 4, subject to backups outside our control.

8. Changes to this Policy

We may update this Policy when features or legal requirements change. For material changes, we will use reasonable means such as an in-app notice, store listing update, or the contact channel in Section 9. Continued use after the effective update means you acknowledge the revised Policy.

9. Contact us

Operator / legal entity:
Kunming Quyue Network Technology Co., Ltd.

Email:
quyuenetwork@gmail.com

Address:

Room 1-91, 33/F, Tower B, Zhongtie Yunshidai Building, No. 179 Wangqu Road,
Puji Subdistrict, Wuhua District, Kunming, Yunnan Province, China

10. Relationship to the store and Data safety

We complete Google Play’s Data safety questionnaire where required. On-device permission screens are controlled by Google and the OS. Wording there may differ from this document. This Policy is not a substitute for legal advice. Regulatory obligations depend on your jurisdiction and the Google Play policies in force when you use the App.