Video Player Privacy Policy

Store/ASO title: Video Player - Vidorec In-app product name: Media Player - Vidorec (media.player.vidorec) Last updated: 31 August 2026 Published at: https://www.vidorec.com/privacy/video-player

The short version

Your videos stay on your device. Vidorec cannot browse your library: it opens only the file you choose. We do not upload your media, its name, storage path, content URI or subtitle text.

Firebase Analytics and Firebase Crashlytics continuously process a limited set of technical usage, device and crash data so we can measure reliability and fix problems. Vidorec creates a random pseudonymous install ID and binds it to both services; Google also assigns a Firebase app-instance ID. These identifiers let a support message be matched to that install's usage journey and crash history. Advertising-ID collection is disabled.

There is no Vidorec account, login or media cloud.

What we do not collect

We do not collect:

Your video, audio or image files, or any frame, thumbnail or sample of them.
File names, file paths, folder names or content URIs.
Subtitle text, including subtitle files you add yourself.
A listing of your media library or the titles in your recent list.
Contacts, accounts, phone number, calendar, messages or installed-app list.
Precise location or advertising identifiers.
Payment-card, bank-account or Google Play payment credentials.

Google Analytics can derive an approximate country or region from a masked IP address before discarding that address. Vidorec does not request device location permission and does not receive precise location.

The app's custom analytics layer has no parameter for a media name, path, URI, subtitle text or other media content. Uncaught error messages are also redacted before Crashlytics receives them; only the error category and stack trace are recorded.

What we collect and why

The following technical collection is continuously enabled:

Firebase Crashlytics

Crashlytics receives the app-generated pseudonymous install ID as its user identifier, Firebase's app-instance ID as a diagnostic key, the redacted error category, stack trace, app version, Android version, device model, installation source and limited playback-state values such as a generated session ID and error code. This is used to diagnose crashes and reliability failures. It never includes the selected media's identity or content.

Firebase Analytics

Analytics receives the app-generated pseudonymous install ID as GA4 User-ID and the app_device_id user property, Firebase's pseudonymous app-instance identifier, and automatically generated app/session information such as first open, app lifecycle, device type, operating-system version, language and approximate country or region. It also receives the following custom product events:

Playback started, became ready, ended or failed.
Whether the device reported the selected media shape as playable.
Features used and purchase/restore-flow outcomes.
Screen views, foreground/background transitions, app version, release channel and free/lifetime entitlement class.

Media is described only by non-identifying technical categories:

Container category from a fixed list, such as mp4 or mkv; anything else is reported as other.
Codec category, such as video/avc.
Resolution, duration, watch time, completion and startup latency as buckets or measurements used for quality analysis.
Random process/session identifiers that are not a file ID, device ID or stable media ID.

Purchases and updates

Google Play Billing handles the lifetime-unlock transaction. Google Play tells the app whether the purchase is pending, completed, restored, cancelled or failed. When Play and Analytics are linked, Analytics may also automatically record the product ID and name, price, currency and purchase state. We do not receive payment credentials. Our custom product events do not send an order number, account identifier or payment details.

The app also asks Google Play whether a newer version is available.

Support messages

The support form does not submit itself. If you deliberately send a report, the report contains your written message, app version, language, a fresh random report ID, the same pseudonymous install/User ID already used by Analytics and Crashlytics, and the Firebase app-instance ID when available. Both identifiers are shown in the report preview and make the report traceable to the correct install's GA4 journey and Crashlytics history. They are not account, advertising or hardware identifiers. An email address is included only if you ask for a reply. Technical details are included only if you turn on the attachment switch after seeing the exact preview; they can include device/Android/app versions, installer, entitlement class and non-identifying playback shape/error values. They never include a media name, path, URI, content or subtitle text.

A direct report that cannot immediately reach our service may remain protected by Android app isolation in a bounded local queue and retry on a later launch. Email delivery is handled by the email app/provider you choose and is subject to that provider's policy.

What stays on your device

The app stores the following locally:

Recently opened videos: local URI, display name, watch position and time.
Playback preferences, subtitle appearance settings and favourites.
Lifetime-unlock entitlement state and pending Play acknowledgement state.
The random pseudonymous install ID used for support/Analytics/Crashlytics correlation.
Up to five direct support reports waiting for delivery, only when you chose to send them and delivery was temporarily unavailable.

These local records are not uploaded as records. Only the pseudonymous identifiers, technical categories and events described above can be sent. Local data is removed when you clear app data or uninstall the app. You can erase the recent list at any time with Settings > Privacy > Clear recent list. Your media files are not changed or deleted.

Permissions and network access

The app uses:

Internet: analytics, crash reports, purchases, update checks, support reports you submit and HTTPS media streams you choose to open.
Notifications: playback controls and update notifications.
Foreground service (media playback) and wake lock: continued playback while the app is in the background or the screen is off.

The app does not request broad storage or media-library permission. Android's system picker grants access only to the single file you select. For an HTTPS stream, the remote host you choose receives the normal network request and is governed by that host's own privacy practices.

Retention and deletion

Local app data remains until you clear it or uninstall the app.
Crashlytics retains crash reports and associated identifiers for up to 90 days under Google's standard service terms.
User- and event-level Analytics data follows the linked Analytics property's configured retention period and is not kept by us beyond Google's supported standard limit of 14 months. Aggregated reports may remain without a user-level identifier.
Submitted support reports are retained only as needed to resolve the report, prevent abuse and meet applicable legal obligations.

There is no Vidorec profile to delete. The support preview shows the install and report IDs you can include in an access or deletion request. Instructions and a contact route are at https://www.vidorec.com/data-deletion. Clearing app data or uninstalling removes all local state, including the pseudonymous install ID and local support queue.

Children

The app is not directed at children and does not knowingly collect information from children. It has no account system or social features.

Providers and your rights

Google processes Analytics, Crashlytics, Play Billing and Play update data as a service provider. Depending on where you live, you may have rights to access, correct, delete, restrict or object to processing. Because Vidorec has no user account and Firebase identifiers are pseudonymous, include the install ID or report ID shown in the support preview, the app name and relevant dates when contacting us so we can evaluate a request without asking for unnecessary personal data.

Google's handling is described at https://policies.google.com/privacy and https://firebase.google.com/support/privacy.

Changes

If the app's data practices change, this page and its last-updated date are updated at the same time.

Contact

support@deepliy.com