Your media stays on your device. Video Player - Vidorec opens only the file you choose; that media's name, path, content URI, content and subtitle text are never sent to analytics or crash reporting. Firebase Analytics and Crashlytics continuously process a limited set of pseudonymous technical events, installation identifiers and crash reports so we can measure reliability. Advertising-ID collection is disabled. Advanced features are unlocked by one lifetime purchase processed by Google Play Billing or Apple StoreKit, depending on your platform, with a visible and free restore action. The support form sends only when you deliberately submit it; an e-mail address and technical attachment are optional.
Locally Stored Data
- The media you open — it stays where it already is on your device and is never copied to us
- Playback position, recents, watch progress and favourites, so you can continue where you left off
- Your preferences: subtitle appearance and timing, playback speed, fit profile and gesture sensitivity
- Your lifetime entitlement and any pending store transaction state, so verified access remains reliable offline
- Up to five support reports waiting for delivery, only after you chose to send them and the service was temporarily unavailable
Advertising
There are no ads on the playback surface and there is no aggressive upgrade flow that interrupts you. The app does not build an advertising profile and does not target you with advertising. The upgrade message appears only when you show intent towards an advanced feature, and the purchase screen never blocks basic playback. Advanced value is sold once as a lifetime entitlement through Google Play Billing or Apple StoreKit, depending on your platform; we never see your card or payment details.
Internet Usage
- Verifying and restoring your one-time lifetime purchase and checking for updates (Google Play or the Apple App Store)
- Pseudonymous technical events and crash reports used to measure reliability (Firebase)
- Sending feedback from inside the app after you press send: your message, plus your e-mail address and technical attachment only if you add them
- Fetching an HTTPS media stream only when you choose to open that address
- Opening and playing local media remains available without a network
Permissions
- Access to your media: the Android or iOS system file picker grants the app access only to the file you select; no broad media-library permission is requested
- System playback controls: the notification area or Lock Screen and Control Center controls drive the same session, depending on your platform
- Internet: Analytics, Crashlytics, store purchase and update checks, a support report you submit, and an HTTPS media stream you choose to open
What we can collect
The data contract is deliberately narrow. Firebase may process the following technical fields to keep playback reliable and to understand which features work:
- A stable pseudonymous install/user ID generated by the app, used as the Analytics User-ID and app_device_id and as the Crashlytics user identifier, plus the separate Firebase Analytics app-instance ID
- Automatically generated app lifecycle, session, language, device and operating-system information
- Approximate country or region derived by Google from a masked IP address; no precise location permission is requested
- The product event that happened and a random playback/session identifier that is not a file or device identifier
- Media capability class — for example whether the device could decode the file, not what the file was
- Whether the action succeeded, or the classified reason it failed
- Container and codec categories, resolution/duration/watch-time buckets, completion and startup-performance measurements
- Purchase and restore state; linked Play/Analytics services may automatically record product ID, product name, price and currency, but never payment credentials
This is pseudonymous technical data: it may distinguish one app installation, but it is not a Vidorec account and does not contain the identity or content of the media you watched.
What is never collected
These are excluded by design, not by policy alone. They are not sent to analytics, not written into crash reports, and not uploaded anywhere:
- The name of your media
- The folder or storage location of your media
- The content of your media
- Subtitle text
- Contacts, messages, installed-app list, precise location or advertising identifier
- Your Google account identity, payment credentials or an order number in Vidorec's custom events
- A support diagnostic attachment, unless you explicitly choose to add it after seeing its preview
Error logs are written so that they cannot carry a personal media identifier. If a crash happens while you are watching something, the report describes the failure, not the file.
Feedback you send us
The support form sends only after you press send:
- What you write in the feedback form reaches us, so that we can understand the problem you are reporting.
- Your e-mail address is optional. Leave it blank and no reply address is included; add it and we use it only to reply to you.
- App version, language, the stable pseudonymous install/user ID, the Firebase Analytics app-instance ID and a new random report ID are always shown in the preview and included so the report can be correlated with the same installation's Analytics journey and Crashlytics history. Additional device/OS/app details and non-identifying playback shape are attached only if you enable the technical-details switch after reviewing the preview.
- If delivery is temporarily unavailable, up to five reports you already chose to send can remain in the app's private local queue and retry on a later launch.
- Feedback is not used for advertising and is not sold.
The form never submits itself. A report you already chose to send may retry later if its first delivery attempt failed.
Your controls
The choices stay with you:
- Attaching extra technical details to a support report happens only after you explicitly choose it.
- Permissions are requested during the action that needs them, with the reason visible, and you can withdraw them in your device settings.
- Data we hold is kept for a limited and documented period rather than indefinitely.
Always-on pseudonymous technical events and crash reports never include your media, its name, path, content URI, content or subtitle text. Basic local playback does not depend on a network connection.
Purchases and your entitlement
Advanced features are a single one-time lifetime purchase, not a subscription:
- The purchase is processed and verified by Google Play Billing or Apple StoreKit, depending on your platform. Your card and payment details never reach us.
- The connected store and analytics service may automatically record product ID, product name, price, currency and purchase state; Vidorec's custom events contain no order or account identifier.
- The scope of the lifetime entitlement is stated on the purchase screen at the moment you buy.
- Once the entitlement has been verified, it keeps working offline; playback is never made dependent on a network connection.
- Restoring a purchase is visible, free and easy, and follows your store account rather than a single installation.
Basic playback of your own media stays free. The purchase screen never blocks it.
Retention and deletion
Data is kept only for a defined purpose and period:
- Local app data remains until you clear it or uninstall the app.
- Firebase Crashlytics keeps 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 property's configured retention period and is not kept beyond Google's standard 14-month upper limit; aggregate reports may remain without a user-level identifier.
- Support reports are retained only as needed to resolve the report, prevent abuse and meet applicable legal obligations.
Use the data-deletion instructions below or contact support@deepliy.com with the install/user ID or report ID for a support-report request.