Privacy Policy

OPlayer

Last updated: July 3, 2026

This Privacy Policy explains how OPlayer (“we,” “us,” or “the App”) collects, uses, and protects your information when you use our Android video player application.

1. Information We Collect

1.1 Information Collected by the App Itself

OPlayer is a video player and local media library browser. It does not require you to register or sign in, and it does not upload your video files or full media library to our own servers. Specifically:

We do not require collection of your name, postal address, government-issued identification number, or similar information;
We do not actively read or upload device identifiers that can directly identify an individual, such as IMEI, device serial number, ANDROID_ID, Advertising ID (GAID), or Wi-Fi MAC address, for our own server-side storage;
Theme, language, player settings, decoder options, gesture preferences, and other app settings are stored locally on your device (DataStore / SharedPreferences);
Playback history, resume positions, favorites, playlists, search history, and network URL history you use in the app are stored locally on your device (Room database and DataStore);
The app scans local videos through Android MediaStore and related system APIs, reads file paths, file names, duration, size, and similar metadata, and displays them in the library UI. This media information is processed on your device and is not uploaded to our servers to provide core playback features;
When you play a network stream, the app connects to the URL you enter or open. That connection is between your device and the remote server or service you choose. We do not operate that remote content server;
When you take a screenshot during playback, the image is saved locally (for example, under Pictures/OPlayer on your device) only when you actively use that feature;
When the app crashes, a local crash screen may show technical logs on your device. You may choose to copy or share those logs through the system share sheet. Separately, crash diagnostics may be sent to Firebase Crashlytics as described in Section 1.2.

[Important] About your videos and media files: OPlayer reads and plays video files that you already have on your device or that you open through a link. Video content itself is not transmitted to our servers. Media management actions such as rename, delete, share, or open with another app occur only when you actively initiate them, using Android system APIs on your device.

Opening videos from other apps: If you open a video file or streaming link from another app (for example, through “Open with” or a share intent), OPlayer receives the URI or link needed to start playback. We do not assume separate privacy obligations for how the app that shared that content handled it.

Picture-in-picture and background playback: If enabled in settings and supported by your device, playback may continue in a floating window or in the background through a foreground media playback service. This processing stays on your device and is not uploaded to our own servers.

1.2 Information Collected by Third-Party Services

The app uses the following third-party services, which may collect certain information:

Firebase Analytics

We use Firebase Analytics to understand how users interact with the app and to improve the experience. Firebase Analytics may collect:

App usage events: screen or feature usage, flow statistics, and similar data;
Device information: device model, Android version, language settings, screen-related parameters, and similar data;
Performance and stability metrics: launch and runtime statistics (as actually provided by Google).

Important: Firebase Analytics is designed for product and aggregate analysis. It is not used to upload your video files or full local media library. For more information, see Google’s official documentation: https://firebase.google.com/support/privacy

Firebase Crashlytics

We use Firebase Crashlytics to automatically detect and report app crashes and errors so we can fix issues and improve stability. Crashlytics may collect:

Device information: device model, Android version, manufacturer, and similar data;
App state: information related to app operation at the time of a crash;
Error information: stack traces, error messages, crash logs, and other technical diagnostic information.

Important: Crashlytics is primarily used for technical diagnostics and app improvement. Crash reports may include file paths or technical context visible in a stack trace, but are not intended to include the content of your video files. For more information, see Google’s official documentation: https://firebase.google.com/support/privacy

Firebase-related data is handled in accordance with Google’s Privacy Policy. For more information, see: https://policies.google.com/privacy

General note (not directly identifying individuals): Data collected through Firebase is generally processed in aggregated or de-identified form and is not used to directly identify a specific individual, and is not used to read or upload the video files in your media library.

Important: We do not provide a user account system and do not operate our own servers for storing users’ personal data or video content. Data processed by Firebase is subject to Google’s data retention and security practices; retention periods follow Google’s rules.

2. Permissions Requested by the App

The permissions below are based on the Release merged manifest for OPlayer. The actual permissions shown on your device may differ by Android version; please refer to App info in your system settings.

2.1 Permissions Declared by This App

The following permissions are declared in our app manifest for core functionality:

Permission	Purpose
`android.permission.READ_MEDIA_VIDEO`	On Android 13 and above, read video files on your device so the app can scan your local media library, display folders and videos, and play local files.
`android.permission.READ_EXTERNAL_STORAGE` (maxSdkVersion 32)	On Android 12 and below, read video files from shared storage so the app can scan and play local media.
`android.permission.WRITE_EXTERNAL_STORAGE` (maxSdkVersion 32)	On older Android versions, save playback screenshots to your device and support certain local file operations (such as rename or delete) when you actively use those features.
`android.permission.INTERNET`	Play network video streams from URLs you enter or open (for example HTTP, HTTPS, HLS, DASH, RTSP, RTMP, or similar protocols supported by the player), and transmit Firebase Analytics and Crashlytics data as described above.
`android.permission.FOREGROUND_SERVICE`	Run a foreground service while media playback continues in the background, where supported by your settings and device.
`android.permission.FOREGROUND_SERVICE_MEDIA_PLAYBACK`	Identify the foreground service type as media playback on supported Android versions.

2.2 Permissions Merged Automatically by Third-Party SDKs

The following permissions may appear in the final merged app manifest because third-party SDKs (Firebase, Google Play services, and related libraries) automatically introduce them during the build process. They are not declared by our app code for active app features.

Permission	Purpose
`android.permission.WAKE_LOCK`	May briefly hold a partial wake lock so background measurement or transmission tasks can complete.
`com.google.android.gms.permission.AD_ID`	This permission may be automatically merged by Google Play services or Firebase-related components to support Google-provided measurement or attribution features, where applicable. This app does not use your media library for ad targeting.
`android.permission.ACCESS_ADSERVICES_ATTRIBUTION`	This permission may be automatically declared by Google Play services-related components and relates to the Android Ads Services framework. Our app code does not directly call this API.
`android.permission.ACCESS_ADSERVICES_AD_ID`	This permission may be automatically declared by Google Play services-related components and relates to the Android Ads Services framework. Our app code does not directly call this API.
`com.google.android.finsky.permission.BIND_GET_INSTALL_REFERRER_SERVICE`	This permission may be automatically declared by Google Play services or measurement components to obtain app install source information, where applicable.

[Storage note] OPlayer needs access to video files on your device to scan and play local media. On Android 10, the app may use legacy storage access behavior where supported by the system so that local file paths remain accessible for scanning and playback. The app does not request camera, microphone, precise location, contacts, or phone state permissions for core features.

[Note] You can manage or revoke permissions in system settings. Revoking storage access will prevent the app from scanning or playing local videos. Revoking network access will prevent network streaming and may affect Firebase diagnostics.

3. System Sharing, Opening Methods, and Other Services

When you use features such as Share, Open with another app, or Share crash logs, the app uses Android system intents (for example ACTION_SEND or FileProvider) so you can choose the destination app. This flow involves the Android system and the app you choose. We only pass the content you choose to share when you actively initiate sharing, and we do not assume separate privacy obligations for how third-party receiving apps handle that data.

When you enter or open a network video URL, playback data is exchanged between your device and the server or service at that URL. Network URL history is stored locally on your device for your convenience and is not uploaded to our own servers.

The app does not provide online social feeds, cloud video hosting, or user account services. If a future version adds new online features, we will update this policy and adjust permission and data security disclosures as needed.

4. How We Use Information

We use relevant information only for the following purposes:

Scanning, browsing, searching, and playing local video files on your device;
Playing network streams from URLs you provide or open;
Managing playback features such as subtitles, audio tracks, playback speed, playlists, favorites, resume position, picture-in-picture, and optional background playback;
Saving screenshots locally when you actively choose to capture a frame;
Performing local media management actions such as rename, delete, or share when you request them;
Improving app performance and stability, and identifying and fixing crashes and errors;
Understanding aggregated usage to optimize the experience and user flows.

5. Data Sharing and Disclosure

We do not sell, trade, or rent your personal information for unrelated marketing. Data processing or disclosure may occur only in the following circumstances:

Firebase services: Technical and statistical data collected or processed by Firebase Analytics and Crashlytics is handled by Google in accordance with its Privacy Policy;
Network playback: When you play a remote URL, your device communicates with the server or service you selected;
Your active sharing: Apps you choose through the system share sheet or “Open with” flow;
Legal requirements: Where required by applicable law, or in response to lawful requests from courts or other competent authorities, we may disclose necessary information as required by law.

6. Data Security

We take your information security seriously. Local media browsing, playback, and most preferences are processed on your device. When analytics and crash diagnostics are transmitted through Firebase, industry-common transmission and protection measures are typically used (such as HTTPS, as actually implemented by Google). We do not use your video library for sale or for purposes inconsistent with this policy. We do not transmit or store your video files on our servers.

Android backup: The app may participate in Android backup/restore mechanisms according to system and manifest settings. Backup behavior depends on your device, Android version, and Google account settings. Locally stored playback history, preferences, and library metadata may be included in device backup if enabled by the system.

7. Children’s Privacy

This app is designed for general users and is not directed specifically at children. We do not knowingly collect personal information from children. If you are a parent or guardian and believe we have processed information relating to a child, please contact us and we will take appropriate steps after verification, as required by applicable law.

8. Changes to This Policy

We may update this Privacy Policy from time to time. The updated version will be posted on this page (or at the same link shown in the app settings), and the “Last updated” date will be revised. If changes are material, we will provide notice as required by applicable law. We recommend reviewing this policy periodically.

9. Your Rights

To the extent permitted by applicable law, you may have the right to know about, access, correct, delete, or restrict processing of information relating to you. For information processed by Google through Firebase, please see the privacy and account tools provided by Google. Where your device or Google provides such options, you may also limit certain data collection by adjusting device settings, advertising, and analytics preferences (subject to current system and Google options). You may uninstall the app at any time to stop using it. After uninstallation, local app data in the app’s private directory will be deleted according to system rules, but video files on your device and content you previously saved or shared to other apps will not be automatically deleted.

10. Contact Us

If you have any questions, comments, or suggestions about this Privacy Policy or our data practices, please contact us:

Email: doesantalya@outlook.com

11. Consent

By using OPlayer, you acknowledge that you have read and understood this Privacy Policy. If you do not agree with this policy, please do not use the app.