GoPlayer

Effective September 23, 2026

Privacy Policy

This policy explains how GoPlayer handles information related to you. GoPlayer is operated by NEXTB LTD ("we", "us").

中文版 / Chinese version

1. Overview and scope

This policy explains how GoPlayer (an Android app, "the app") handles information related to you. The app is provided by NEXTB LTD ("we", "us").

The app is a local video and music player. It also provides a browser, downloads (including BitTorrent downloads), casting, file transfer, a private vault, a music alarm, ringtone setting, cleanup and recycle bin, WhatsApp status saving, audio conversion, and help & feedback.

This policy covers only the app itself. Websites, download sources, BT networks, and casting devices you reach through the app, and any other app you choose to use to send feedback or share a file, are each responsible for their own privacy policy.

In brief:

  • We do not operate our own servers. The app does not require registration or sign-in and has no cloud sync.
  • Your media files, playback history, browsing history, private vault, and similar data are stored on your device, and we cannot access them.
  • The app shows Google AdMob ads and includes the Google Cast component. These Google components collect certain data under Google's own rules and send it to Google, as described in Section 4.

2. Information we do not collect

  • We do not operate any server, and the app has no channel that uploads your data to us.
  • The app does not require registration or sign-in and has no cloud sync.
  • Other than the Google components described in Section 4, the app integrates no other analytics, crash-reporting, or attribution service, and has no analytics upload of our own.
  • The app does not request permission to read your contacts, SMS, call log, or calendar, and does not request permission to read your photos (images).
  • The app does not read your location coordinates. The location permission that Android 12 and earlier requires as a precondition for the file-transfer hotspot is only a system requirement; the app does not read or send location coordinates.
  • The app does not request permission to read the list of apps installed on your device.

3. Data processed only on your device, by feature

The data below is read, generated, and stored by the app on your device and is not sent to us. Unless stated otherwise, it is stored in the app's private storage.

3.1 Media library and playback

  • The app reads the videos and music on your device (for example, file name, folder, duration, and size) to display, search, manage, and play them.
  • The app stores playback history, playback position, playlists, subtitles, and player settings.

3.2 Browser

  • Browsing history, search history, bookmarks, and tab state are stored on your device.
  • Cookies, site storage, page cache, and form data written by the websites you visit are stored on your device.
  • You can use "Clear browsing data" in the browser to clear the browsing data above at once (except bookmarks, home-screen shortcuts, download tasks, and downloaded files), or clear browsing history or search history separately.

3.3 Downloads and BT downloads

  • Download tasks, BT task records, and downloaded files are stored on your device.

3.4 Private vault

  • Files you move into the private vault are encrypted and stored on your device (AES-GCM), and require the PIN you set to open.
  • The recovery email you enter when creating the private vault is also stored only on your device, in encrypted form. The app does not use it to send email, and currently cannot use it to recover your PIN.
  • If you forget your PIN, your private files may not be recoverable. Uninstalling the app or clearing app data deletes the files in the private vault.

3.5 Music alarm and ringtones

  • Alarm time, repeat rules, the chosen ringtone, and similar settings are stored on your device, used to ring on schedule, and to restore alarms after a device restart, a time change, or an app update.
  • When you set an audio file as the system ringtone, the app changes the system ringtone setting after you confirm, and may save a copy of that audio file on your device for use as the ringtone.

3.6 Cleanup and recycle bin

  • The cleanup feature scans media files on your device and lists them by criteria such as file size and whether they have been played in the app; files are deleted only after you confirm.
  • The recycle bin lists videos and music that have been moved to the system recycle bin; you can restore or permanently delete them.
  • Clearing the app's own cache only removes the app's temporary files.

3.7 WhatsApp status saving

  • You need to grant access to the WhatsApp status folder through the system file picker. The app only reads the videos in that folder and does not modify or delete the originals.
  • Videos you choose to save are copied to storage on your device (on Android 10 and later, the Movies/GoPlayer/Status folder).
  • The app is an independent app and is not affiliated with WhatsApp or its parent company.

3.8 Audio conversion

  • Extracting audio from a video is processed on your device, and the result is stored on your device.

3.9 Local records for file transfer

  • Received files and receipt records are stored on your device.

3.10 Local records related to advertising

  • To control how often ads appear, the app records, on your device, ad impression counts and timing, reward progress, and an in-app event queue.
  • These records are stored only on your device; we have no server that receives them. When you withdraw ad consent, the local in-app event queue is cleared.
  • Your ad consent choice is also stored on your device.

3.11 Backup

  • The app disables system backup and device-to-device data migration. The data above does not go into Google cloud backup and is not migrated automatically when you switch devices.

4. Data that leaves your device

In the situations below, data leaves your device. Other than data automatically collected by Google components, this data is sent directly to the website, device, or app you choose, only when you actively use a given feature, and does not pass through us.

4.1 Advertising: Google AdMob and Google UMP

  • The app uses the Google Mobile Ads SDK (AdMob) to show ads, and the Google User Messaging Platform (UMP) SDK to request and manage your ad consent choice.
  • According to Google's public documentation, the Google Mobile Ads SDK automatically collects the following data and shares it with Google, for advertising, analytics, and fraud prevention:
    • Approximate location: an approximate location derived from your IP address, not precise GPS location;
    • In-app interactions: for example, ad clicks, app open counts, and video ad viewing;
    • Diagnostics: for example, startup time, jank rate, and battery-use performance data;
    • Device or other identifiers: the Android advertising ID and App Set ID.
  • Google states that the data above is encrypted in transit using TLS.
  • Google has not separately published a list of the data types collected by the UMP SDK itself. UMP is used to show the consent form and privacy options.
  • The app currently integrates only Google AdMob and no other ad network.
  • For how Google uses this data, see the Google privacy policy and related documentation listed in Section 11.

4.2 Casting: Google Cast SDK and local-network casting

  • The app includes the Google Cast SDK. According to Google's public documentation, this SDK automatically sends general device-discovery and casting-session events, mobile device information, and client app information to Google in encrypted form, for analytics and to improve the service; this does not include the specific media content you cast. Google does not provide an opt-out or deletion method for this data.
  • The app only searches your local network for casting devices after you tap search.
  • When you start casting, your phone temporarily provides your chosen media (including subtitles) to the TV or receiver you selected, over your local network. This local-network transmission is not necessarily encrypted, so only use this feature on a network you trust. How the receiving device handles this content is decided by its manufacturer.

4.3 Browser, downloads, and BT downloads

  • Browser: when you visit a website with the built-in browser, that website receives your IP address, browser information, and cookies, just as it would in any other browser, along with anything you fill in, submit, or upload on its pages. How the website handles this information is governed by that website's own privacy policy.
  • Downloads: when you start a download, the app sends a request to the server hosting the download address, including the download URL, the referring page address (Referer), the browser identifier (User-Agent), and any cookies supplied by the referring page. The app supports HTTP downloads, and HTTP connections are not encrypted.
  • BT downloads: these require your confirmation before starting. BT connects to other peers and tracker servers, shows your IP address to other peers, and, during transfer, uploads the pieces of files you have already downloaded to other peers, which also consumes data. BT transfer is not guaranteed to be encrypted. You can pause at any time; the transfer continues in the background after you leave the page.

4.4 File transfer

  • File transfer only happens when you actively initiate it, and both devices need to use the app. The receiving device displays a pairing QR code, and the sending device scans it with the camera.
  • Files are sent directly to the other device, over the local network you choose (the same Wi-Fi, or a hotspot created by the receiving device), and the transfer is encrypted.

4.5 Help & feedback

  • The app does not send feedback on its own. After you tap "Send", the system share panel lets you choose an app (for example, a mail app) and a recipient, and that app sends the feedback under its own privacy policy.
  • Feedback content includes: the issue type, the description you write, an error code (if any), any screenshot you choose to attach (optional), and, if you check the box, accompanying diagnostic information.
  • Screenshots are recompressed, removing metadata such as capture time and location.
  • Diagnostic information only includes: app version, build type, Android version, device manufacturer and model, and interface language; it does not include file names, paths, playback history, or device identifiers. You can preview this information before sending.
  • If you send feedback to goplayer@nextb.uk, we only use it to respond to and handle your feedback.

4.6 Share and "open with another app"

  • When you use "Share" or "Open with another app", the file you select is handed to the app you choose, and that app handles it under its own privacy policy.

5. Advertising and your choices

  • Consent form: in regions where the law requires consent (for example, the European Economic Area, the United Kingdom, and Switzerland), the app shows a consent form through Google UMP. The app does not request ads before your consent status is determined. Your choice affects how Google serves ads to you, for example whether personalized ads are shown.
  • Certain US states: where applicable, you can opt out of related data processing under local law through Privacy options.
  • Privacy options: where required by your region, the app's Me tab shows Privacy options, which you can open at any time to change or withdraw your consent. After you change or withdraw it, Google decides, based on your choice, whether to serve ads and which kind (for example, only "limited ads" that are not customized using personal data, or no ads at all); the app also clears the local in-app event queue at the same time.
  • Advertising ID: you can reset or delete your advertising ID in Android system settings (the exact location varies by system version and device manufacturer, generally under Google or privacy-related settings).

6. Permissions

Runtime permissions can always be denied, and later withdrawn in system settings. Denying a permission may disable the related feature without affecting others. Permissions marked "granted automatically at install" are granted by the system at install time, without a prompt.

Media and storage

  • Read videos (READ_MEDIA_VIDEO, Android 13+): scan, display, manage, and play the videos on your device. Required for the video library; if denied, you can still open individual files with "Choose video or audio".
  • Read audio (READ_MEDIA_AUDIO, Android 13+): music library and alarm ringtone selection. Required for the music library.
  • Partial media access (READ_MEDIA_VISUAL_USER_SELECTED, Android 14+): if you only allow access to some videos, the app can still use that subset. Optional.
  • Read storage (READ_EXTERNAL_STORAGE, Android 12 and earlier only): media library, alarm ringtones, and WhatsApp status file reading on older systems.
  • Write storage (WRITE_EXTERNAL_STORAGE, Android 9 and earlier only): deleting files and writing ringtone files on older systems.

Notifications and background operation

  • Notifications (POST_NOTIFICATIONS, Android 13+): show playback, download, transfer, and alarm notifications. Optional; if denied, you may not see these progress and control notifications.
  • Foreground service (FOREGROUND_SERVICE, FOREGROUND_SERVICE_MEDIA_PLAYBACK, FOREGROUND_SERVICE_DATA_SYNC): background playback, private-vault playback, and alarm ringing; downloads, BT downloads, and file transfers that you start. Granted automatically at install.
  • Wake lock (WAKE_LOCK): keeps playback, downloads, transfer, and the alarm from being interrupted while running. Granted automatically at install.
  • Vibrate (VIBRATE): alarm vibration. Granted automatically at install.
  • Exact alarms (SCHEDULE_EXACT_ALARM, needs to be enabled in system settings on Android 12+): lets your music alarm ring on time. Only needed if you use the alarm.
  • Restart receiver (RECEIVE_BOOT_COMPLETED): restores alarms after a device restart, a time change, or an app update. Granted automatically at install.
  • Modify audio settings (MODIFY_AUDIO_SETTINGS): equalizer, bass, and reverb adjustments. Granted automatically at install.
  • Write system settings (WRITE_SETTINGS, needs to be enabled in system settings): sets an audio file you confirm as the system ringtone. Only needed when setting a ringtone.

Network and connectivity

  • Network access (INTERNET): browser, downloads, BT downloads, casting, file transfer, and ads. Granted automatically at install.
  • View network state (ACCESS_NETWORK_STATE): determines whether the network is available, used for pausing/resuming downloads, casting, and transfer. Granted automatically at install.
  • Change network connection (CHANGE_NETWORK_STATE): binds the connection to the local network you choose during file transfer. Granted automatically at install.
  • Change Wi-Fi state (CHANGE_WIFI_STATE): creates the local hotspot used for file transfer. Granted automatically at install.
  • Nearby Wi-Fi devices (NEARBY_WIFI_DEVICES, Android 13+): discovers and connects to the file-transfer hotspot; declared as not used to infer location. Only needed when using file transfer.
  • Location (ACCESS_FINE_LOCATION, ACCESS_COARSE_LOCATION, Android 12 and earlier only): required by the system when using the Wi-Fi hotspot feature on older systems; the app does not read location coordinates. Only requested during file transfer.
  • Camera (CAMERA): scans the file-transfer pairing QR code; the camera feed is used only for on-device recognition while scanning and is not uploaded. Only needed while scanning.

Permissions added by the Google Ads SDK

  • Advertising ID (com.google.android.gms.permission.AD_ID): lets the ads SDK read the Android advertising ID, for advertising and fraud prevention. Granted automatically at install.
  • Ad-services related permissions (ACCESS_ADSERVICES_AD_ID, ACCESS_ADSERVICES_ATTRIBUTION, ACCESS_ADSERVICES_TOPICS): advertising-related permissions from the Android Privacy Sandbox, declared by the ads SDK. The app's own code does not actively call the Attribution Reporting or Topics features.

Other

  • DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION: an internal permission automatically added by an Android development library, used only to protect the app's internal communication and not related to your data.

7. Storage and retention

  • The data described in Section 3 stays on your device until you delete it in the app, clear the app's data, or uninstall the app.
  • Files you save to public storage or a folder you choose (for example, downloaded files, audio-conversion results, saved status videos, or files received through file transfer) are not the app's private data; they usually remain after you uninstall the app, and you need to delete them yourself.
  • We have no server, so we do not store your data on our side, except feedback you actively send us.
  • Data collected by Google components is stored and processed by Google under Google's own privacy policy.

8. How to delete your data

  • Browsing data: use "Clear browsing data" in the browser, or clear browsing history or search history separately.
  • Private vault: use "Delete all private data" in the private vault settings.
  • Media files: delete within the app, or permanently delete through cleanup and the recycle bin (requires your confirmation).
  • All of the app's data: find GoPlayer in Android system settings and clear its storage, or uninstall the app.
  • Ad consent: change or withdraw it through Privacy options.
  • Advertising ID: reset or delete it in Android system settings.
  • Data collected by Google components: these Google SDKs provide no in-app deletion option; you can manage your data as described in Google's privacy policy.
  • Feedback you sent us: email goplayer@nextb.uk to request deletion.

9. Children

The app is not directed to children under 13, and we do not knowingly collect personal information from children. If you believe a child has provided us with personal information, for example through feedback, please contact goplayer@nextb.uk and we will delete it.

10. Security

  • Files in the private vault are encrypted and stored on your device.
  • File transfer is encrypted over the local network.
  • The app's data does not take part in system cloud backup or device-to-device migration.
  • Feedback screenshots have metadata removed, and diagnostic information does not include device identifiers.
  • No measure can guarantee absolute security. Transfers over HTTP downloads, BT downloads, and local-network casting are not necessarily encrypted; please set a screen lock on your device and only use these features on a network you trust.

11. Third-party services and their privacy policies

Every third-party component in the app that collects or sends out data is provided by Google: the Google Mobile Ads SDK (AdMob), the Google User Messaging Platform (UMP) SDK, and the Google Cast SDK.

12. Changes to this policy

When this policy is updated, we will publish the new version and update the effective date. If there is a material change -- for example, collecting a new type of data or integrating a new third-party service -- we will state this prominently in the app or on this page.

13. Contact us

If you have any questions about this policy or your data, please contact us: