UX Player Privacy Policy 

Effective Date: August 20, 2026

Last Updated: October 11, 2026

UX Player is developed and published by UX Horizon, India. This Privacy Policy explains how UX Player handles information when you use its local video and music player, Files, private Locker and Status Saver features.

1. Using UX Player without an account

You do not need to create a UX Player account or sign in to use the app's local features. The app does not ask for your name, phone number or exact date of birth. If you contact us by email, we receive your email address and the information you choose to include so we can respond to your request.

2. Local files and playback information

With the access you grant, UX Player reads local videos, music, photos, PDFs and other files to display, play, preview and manage them. It can use file names, paths, sizes, dates and media metadata locally for these functions. Playback history, resume positions, thumbnails, preferences and allowance counters are also stored on your device.

UX Player does not upload your local media, documents, file contents or Locker PIN to cloud storage operated by UX Horizon. App-generated advertising and analytics events do not include your file names, file paths, file contents or Locker secrets. Sharing a file with another app is a separate action you initiate. UX Horizon does not sell your personal media or operate a service for selling directly identifiable personal information; advertising providers process advertising-related information as described below.

3. Storage and other Android permissions

All files access supports the integrated file manager's browsing, searching, copying, moving, renaming and deleting of files and folders in accessible shared storage, including non-media files. Android's restrictions on private and protected folders still apply. Older Android versions use storage permissions instead. Media-management access supports user-requested changes to shared media. Access to original photo metadata can preserve information already embedded in a photo, including location metadata if present; it does not grant access to the device's live location.

Status Saver uses the storage access you grant to find accessible WhatsApp and WhatsApp Business status folders automatically where supported. If automatic access is unavailable, a supported version may offer Android's folder picker. Internet and network-state access support ads, consent services and enabled measurement. Biometric access supports optional Locker authentication. Foreground-service and wake-lock capabilities support playback. APK installation access is described below. Permissions do not themselves upload your files. You can review or revoke access in Android settings; affected features may then stop working.

4. Private Locker and encrypted files

Locker supports videos, music, photos and PDFs. Imported files are encrypted in app-private storage. Information needed to verify your PIN and the keys used for Locker remain on the device. When you view or play an item, the app may create temporary decrypted data locally and performs local cleanup for those temporary files.

Copying an item into Locker can leave the original outside Locker. Moving an item or deleting an original is a separate file operation. Restoring or sharing an item creates or exposes a copy outside Locker's protection. Keep your own copies of important files where appropriate; UX Player does not provide an automatic online Locker backup.

5. PIN recovery and Locker reset

Your PIN stays on this device. UX Horizon cannot recover it through an online account or email. Follow the information shown in the app before resetting Locker. Resetting or erasing Locker, clearing app data or uninstalling the app can permanently remove locked files and the information needed to access them. These actions do not delete copies that remain elsewhere in shared storage or in another app.

6. Optional biometric unlocking

If supported by your device and enabled by you, Locker uses Android's biometric authentication system. UX Player receives an authentication result, not your fingerprint, face image or biometric template. Biometric enrollment and processing are managed by Android and your device.

7. Status Saver

Status Saver reads available images and videos in accessible status folders, previews them and saves copies locally when requested. Starting with version code 11, it can find supported WhatsApp and WhatsApp Business folders automatically after suitable storage access is granted. Earlier versions and supported fallback flows use a source folder you select. Saved copies are placed in the device's Pictures or Movies area under UX Player. Revoking storage access or disconnecting a selected source does not erase copies you already saved.

Save or share only content you have permission to use. UX Player is not affiliated with WhatsApp or Meta's WhatsApp service and does not require access to your WhatsApp account or messages.

8. File sharing, external apps and APK files

When you choose to share or open a file with another app, Android passes the selected content to that app. Its handling is governed by its own privacy practices. External links, including this policy and links opened from ads, may open in a browser or another app.

The Files feature can pass an APK you select to Android's package installer. Android controls the installation and any required approval. UX Player does not silently install applications or use this feature to update itself outside Google Play.

9. Music playback and notifications

Music playback uses a foreground media service and Android media controls, which can appear while playback is active. UX Player does not request the runtime notification permission. Media controls and the playback-service notification are separate from an advertising or promotional notification service.

10. Google AdMob advertising

UX Player uses Google AdMob for rewarded ads. When ad services operate, they may collect and share an IP address and approximate location inferred from it, app and ad interactions, diagnostic information, and device or other identifiers, including the advertising ID where allowed. These support advertising, measurement and fraud prevention. UX Player does not request a location-sensor permission for ads.

Playback and Status Saver use allowances shown in the app. An offered reward is granted when the app receives and validates an earned-reward result. Ad availability can vary. Ad privacy choices are separate from the optional analytics choices described below.

See Google's Privacy Policy (https://policies.google.com/privacy) and Google Mobile Ads data disclosure (https://developers.google.com/admob/android/privacy/play-data-disclosure) for further information.

11. Ad privacy choices

The app uses Google's User Messaging Platform to obtain ad privacy information and show applicable consent or privacy choices. Available choices and ad behavior depend on your region, age-related settings and the consent service. Open Privacy settings, then Ad privacy choices, to review the options available to you.

Android also provides advertising-ID controls where supported. Declining personalized ads or changing an advertising-ID setting does not necessarily stop all processing needed to deliver permitted ads, measure their operation or prevent fraud. A privacy choice does not retroactively delete information already received by a provider.

12. Optional Firebase product analytics

Firebase Analytics helps us understand how app features are used and improve UX Player. On fresh installations of version code 12, its usage setting starts on for adult users where the app's current regional privacy checks permit default-on measurement. Collection stays off until an adult age range, 18 or older, is selected and the privacy check succeeds. Where prior consent is required, the default setting is not treated as consent; an affirmative usage choice is needed in Privacy settings. Existing installations retain their previous Firebase setting, including the earlier default-off state. You can turn it off under Privacy settings > Usage analytics. In earlier versions, Firebase usage analytics starts off and is enabled only by an adult who opts in.

When enabled, Firebase can measure first opens, sessions and configured events describing playback, playback controls, subtitles, Locker use, Status Saver and reward interactions using categories and counters. The service may also process app-instance identifiers and app, device and network information. UX Player does not add file names, paths, media contents or Locker secrets to event parameters. The app disables Firebase advertising-ID collection and keeps Firebase advertising-storage, ad-user-data and ad-personalization consent disabled. This does not mean that enabled analytics uses no identifiers at all.

See Google's Privacy Policy (https://policies.google.com/privacy) and Google Analytics data collection information (https://support.google.com/analytics/answer/11593727) for further information.

13. Meta app-install and usage measurement

For new installations of version code 10 and later, UX Player's first-run age-selection screen shows an Install measurement on/off control. The setting starts on, but Meta install reporting is eligible only after an adult age range is selected and the app's regional privacy checks permit it. You can turn it off before continuing setup or later under Privacy settings > Install measurement. The Privacy policy remains accessible in Privacy settings; version code 12 removes the duplicate policy link from the age popup. Existing installations retain their previous Meta install choice, including the previous default-off state. The app does not require Facebook login.

Meta's SDK can receive installation-related app, device, network, SDK-identifier and Play Store referral information to measure advertising campaigns. This can include an app-instance identifier, IP address, app version, Android version and device model. It is not an anonymous numerical counter. UX Player does not add file names, file paths, media contents or Locker secrets to its event parameters. Versions 10 and 11 do not send the app's playback, status, Locker or other configured feature-use events to Meta. Automatic broad usage-event logging and Meta advertising-ID collection remain disabled. These settings do not eliminate all SDK configuration requests, identifiers or install-related processing.

Version code 12 adds a separate Meta App Events usage setting under Privacy settings > Usage analytics. It starts on for fresh adult installations, subject to the regional Meta privacy safeguards and the Install measurement switch. Existing installations do not automatically gain usage tracking when they update. Users can disable Meta usage independently while keeping install measurement enabled; disabling Install measurement blocks both. Configured usage events describe the first library load, first video play, a playback milestone, status saves, first Locker import, subtitles, audio-track or playback-speed use and an engagement signal. Parameters are restricted to broad source categories and an applicable cycle number. Meta can also receive SDK/app-instance identifiers and app, device and network information. These settings remain off for unknown age and under-18 users and when required regional choices have not been provided.

Install reporting stays off until an adult age range is selected and the regional privacy status has been refreshed. Where applicable, the existing ad privacy flow must include the appropriate Meta and measurement choices. A refusal, an unavailable or unknown privacy result, or a region not supported by the app's measurement safeguards blocks reporting. Turning measurement off prevents new app-initiated requests; it does not recall a request already queued by the SDK or delete information Meta has already received. First opening the app is needed for app-side reporting; a download without opening is not a confirmed SDK install event. Reported events do not guarantee that Meta attributes an installation to a particular ad.

For version code 9 and earlier releases with Meta App Events, the separate Meta choice starts off and is enabled only by an adult who opts in through Privacy settings. Those versions can report selected playback, status, Locker and other feature interactions using categories and counters, without file names, paths, media contents or PIN information.

See Meta's Privacy Policy (https://www.facebook.com/privacy/policy/) for its handling of information.

14. Age range and children

UX Player is intended for users aged 13 and above and is not directed to children under 13. The app asks for an age range, not an exact birth date, and stores that choice locally. You can change it in Privacy settings.

Firebase usage analytics and Meta install/usage reporting remain off for users under 18 or until an adult age range is selected. The app applies age-related ad settings, including under-age-of-consent settings for users under 18 and child-directed settings when Under 13 is selected. The app sends Google age-treatment flags, such as whether under-age-of-consent or child-directed treatment applies, so Google can apply the appropriate ad and consent settings. These safeguards do not change the app's intended audience. If you believe a child has provided personal information to us, contact us at the email below. If we become aware of processing that violates applicable children's privacy laws, we will take appropriate steps to address it.

15. Third-party services and international processing

The advertising and measurement services described above process information according to your applicable choices, their configurations and their own privacy policies. Information handled by these services may be processed outside your country, including in countries with different privacy laws. Their policies explain their processing and safeguards. Local file access does not mean your media or Locker contents are sent to these services.

We may also handle information you send to support and disclose information where required by applicable law or to protect users and UX Horizon from fraud, abuse or security threats. External apps and websites you choose to use have their own privacy practices. Third-party policies do not replace UX Horizon's responsibility for its own implementation and privacy obligations.

16. Security

UX Player uses Android's app-private storage and local Locker encryption to help protect locked items. It does not provide a guarantee against every form of access, device compromise or data loss. Device security, access to an unlocked device and copies outside Locker remain important.

Google documents encrypted connections for information transmitted by its Mobile Ads and Firebase services. No electronic storage or transmission method can be guaranteed completely secure. Do not send your Locker PIN or private media to support.

17. Retention and local deletion

Local settings, playback information and app-private caches remain until removed by the app, Android or you. You can delete selected files using the app's available actions. Clearing app data or uninstalling removes app-private information and can permanently destroy Locker access. Files saved, restored, copied or shared into public storage or other apps may remain and need to be deleted separately.

Advertising and analytics providers retain information according to their policies and applicable service settings. Turning an option off or uninstalling UX Player does not itself delete information those providers already received. Support correspondence is handled to address your request and for any applicable record-keeping obligations.

18. Withdrawing choices and requesting data deletion

Open Privacy settings to change Usage analytics (called Optional analytics in earlier versions), Install measurement, Age range or available Ad privacy choices. In version code 12, Firebase and Meta usage have separate switches; Turn both off disables both usage settings. Install measurement remains a separate control, and turning it off also blocks Meta usage events. Saved choices are respected on later launches and updates. Turning measurement off stops new requests initiated through the app's measurement controls. It does not recall requests already queued by a provider's SDK or delete information already received.

For a privacy or deletion request concerning information held by UX Horizon, email business.uxhorizon@gmail.com with the app name, the type of request and enough non-sensitive detail to identify the relevant support interaction or information. Do not include your PIN or private files. As the app has no user account, we may be unable to associate provider-held information with you from your email address alone. We can explain the available request process; relevant Google or Meta privacy controls may also be needed. We cannot remotely delete files stored only on your device or promise deletion of records controlled by another provider.

Depending on where you live, applicable law may provide rights concerning access, correction, deletion, objection, restriction, portability or consent withdrawal, and the right to complain to a data-protection authority. Requests are subject to applicable law and reasonable identity verification. You can contact us about those rights and use the relevant provider's privacy controls for information it holds.

19. Changes to this policy

We may update this policy when UX Player's features or data practices change. The updated version will be published on this page with a revised Last Updated date.

20. Contact

Developer: UX Horizon

App: UX Player

Country: India

Email: business.uxhorizon@gmail.com