Privacy Policy

01. What this policy covers

This policy describes VIO player 1.7.8 (Android package com.vio.player). Local video, music and Private Vault work offline without a VIO account. VIO uses Google AdMob to display advertising and includes optional Google Firebase reporting. Advertising and reporting have separate data flows and privacy controls, described below. Availability of purchases depends on Google Play and your region.

Privacy contact: vioplayer.support@gmail.com. A version reference on this website does not confirm that the build is already available in your country's Play Store.

02. Media, permissions and local information

With your permission or file selection, VIO reads media, subtitles and metadata to organise and play your library. Names, locations, dates, durations, thumbnails and artwork are processed on the device. Watched positions, favourites, playlists, queues, bookmarks, themes and track choices are stored locally. Saved queues may contain stream addresses. Special access is verified on the device; its signed activation proof is encrypted in private, backup-excluded storage using Android Keystore. The access code is not saved as plaintext or sent to our reporting services.

VIO does not upload your library, media files or playback history to a VIO cloud service. File actions you choose can modify, share, export or delete media. Sharing sends the selected content to your chosen app or recipient. Temporary playback/export files and thumbnails may be created locally.

Video/audio permissions provide library access. Older Android versions use storage permissions; file modifications can require Android confirmation. You can change access in Android Settings. VIO does not require contacts, camera, microphone or precise-location permission for playback. Background playback uses a media foreground service; notifications and connected devices may display public media titles or artwork. Internet access serves advertising, optional reports, Google Play and streams you open. Streaming connects to the provider of your chosen URL, which receives your IP address and request details. Use HTTPS where available. Before adding an HTTP stream, VIO asks you to acknowledge that its address and content are not encrypted; this is separate from Google SDK transport. A queued stream retains the address you chose.

Subtitle fonts are included inside the app and work offline. Your selected font is stored on this device; using a bundled font does not contact a font provider or upload subtitle text.

03. Optional Firebase reports

Crash reports, Usage analytics and Performance reports are on by default unless you have already switched them off. Each can be switched off independently. Enable or disable them in Settings → Diagnostics & analytics. Google processes enabled reports for our Firebase project to help us fix faults and improve the app. We do not use your name, email or a VIO account ID to identify Analytics users.

• Usage analytics: general public screen usage and SDK session/engagement events, with an app-instance identifier, app/device/OS details and approximate geographic information. Advertising ID collection and advertising use are disabled in the Firebase Analytics integration.
• Crashlytics: crashes, supported ANRs, generic playback error codes, technical stack frames, device/app details and installation/session identifiers. Native decoder crash reporting is not included.
• Performance Monitoring: supported app/screen timing and library-scan duration, with technical app/device information and identifiers. Automatic HTTP instrumentation is not enabled.

VIO does not attach filenames, folder paths, subtitle text, private stream URLs, Vault secrets, purchase tokens or media contents to reports. It removes exception messages and nested causes from forwarded Java/Kotlin crashes. Sessions that entered Private Vault are excluded from crash uploads; usage and performance reporting pause during private activity. These measures limit reports; they do not make technical identifiers anonymous.

Reports need a connection and can be delivered later. Crash reports are submitted on a later launch while the crash choice remains enabled. Turning a choice off stops new reporting for that service but cannot recall an upload already in progress or erase earlier server records. Reset local analytics clears local Analytics data and resets its identifier; it does not delete remote records. SDK configuration requests may still occur; VIO does not promise zero network traffic.

Firebase uses encrypted transport. See Firebase privacy and retention information and report controls and deletion assistance. Reporting choices are separate from advertising consent or Premium.

04. Google AdMob advertising

VIO does not show an age-selection popup at startup. Without a saved age choice, it applies conservative under-age privacy treatment to advertising. You may optionally select an advertising age group (under 13, 13–15, 16–17 or 18 or older) in Settings; the selection stays on this device. VIO does not ask for your date of birth. Google UMP receives an under-age-of-consent signal. You can change the group in Settings → Privacy & legal → Advertising age group. Selecting under 13 disables ads. Without an age choice, only restricted ad requests are eligible, and only when Google UMP permits them. Local playback remains available regardless of advertising eligibility. Ages 13–15 receive conservative under-age ad treatment; ages 16–17 receive teen treatment. Older ambiguous saved groups also use the restricted default without another automatic age question. The app requests non-personalised ads for all eligible users; this does not eliminate technical data processing.

VIO uses Google AdMob. When the Google Mobile Ads SDK operates, it collects and shares information with Google for advertising, analytics, measurement and fraud prevention. Depending on device availability, configuration and your privacy choices, this includes IP address and approximate location inferred from it; advertising ID, app set ID and applicable device/account identifiers; app launches, ad views, taps and other app/ad interactions; and diagnostic information such as launch timing, performance and hangs. Data sent by the SDK is encrypted in transit using TLS. The app declares Android Advertising ID permission for Mobile Ads. Availability and use depend on Android settings, applicable privacy choices and SDK age treatment; the permission alone does not mean an identifier is collected. When child or under-age protections apply, Google does not transmit the Android Advertising ID. Other SDK identifiers and technical data can still be processed. VIO does not supply your media files, filenames, private stream URLs or Vault contents to AdMob.

Google and participating advertising providers process data under their policies and applicable privacy choices. Review Google Mobile Ads data disclosures, Google’s Privacy Policy and Google’s use of information from partner apps. Information about applicable advertising partners and their purposes is available in the consent message where provided.

05. Advertising choices

VIO includes Google’s User Messaging Platform for configured advertising privacy messages. Where a message is required and available, it is presented before advertising that requires consent. You can revisit available choices in Settings → Privacy & legal → Privacy choices; this entry is shown when Google requires it. Message availability depends on the advertising configuration and your region. Local video, music and Vault do not require an advertising consent request to succeed. Relevant US-state choices to opt out of sale/sharing or targeted advertising are provided through the applicable privacy message. Consent preferences and related records are stored or processed to apply your choices.

Refusing personalised ads does not necessarily stop all technical processing or advertising. Non-personalised or limited ads can still involve permitted delivery/security data. Use the choices actually offered for your region. Accepting Terms does not override reporting choices or provide consent to personalised ads. Android advertising controls and My Ad Center have separate scopes; resetting an identifier does not erase all earlier records.

We do not sell your media or Vault contents. Ad-related transfers can fall within legal definitions of sharing or sale in some regions. Premium removes VIO-served ads when active; it does not disable separately controlled reports, delete past records, or remove ads embedded in external content.

06. Google Play purchases and themes

Optional monthly/yearly subscriptions use Google Play Billing. Google processes payment details; VIO receives purchase information required to verify and restore access, such as purchase status, token, product and order information. We do not receive your full card number or Google password. Verified purchase proof is protected locally using Android Keystore encryption and signing; it is not sent to Firebase reports.

Verified Premium can remain available offline for up to seven days after successful verification. An internet connection to Google Play is needed to verify it again, purchase or restore. Core local video, music and Vault remain usable offline. Theme preferences remain local. See subscription terms.

07. Device-only encrypted Private Vault

Private Vault encrypts selected video/audio files and filenames on your phone. Choose PIN or Pattern, or compatible fingerprint access with a PIN/Pattern backup. Android performs biometric authentication; VIO does not receive your fingerprint template. The Vault locks when you leave private playback or turn off the screen. Private playback is excluded from public history and media notifications.

Import verifies an encrypted copy before offering to remove its public original, with required Android/provider permission. Cancelling removal leaves the public original. Export creates an unencrypted copy; other originals, shared files and backups can remain outside the Vault. Encryption protects stored data but cannot guarantee protection on an unlocked or compromised phone.

There is no cloud backup, remote recovery or Forgot PIN/Pattern service. Losing credentials, keys or app storage may permanently lose access. Export wanted files and verify them before reset, uninstall or device replacement. Never send support your unlock secrets or private files.

08. External services and support

A stream provider receives the requested address, your IP address and technical request information when you open its stream. HTTPS encrypts transport; plain HTTP streams do not. Sharing destinations and external websites apply their own policies.

If you email us, we receive your address, message and any attachments you choose to send, and use them to answer your request. Our email provider processes correspondence. Send only necessary details; redact media names, secrets and private URLs. We may disclose information we hold when legally required or to address fraud or legal claims. Providers may process information internationally under their applicable safeguards.

09. Retention and deletion

Local preferences and files remain until you remove them, clear app storage or uninstall; Android may clear temporary files. VIO disables backup of its private app data. Shared media and exports are not automatically erased by uninstall. Android 11+ manages its recycle-bin expiry; on Android 8–10, VIO’s private recycle copies have no automatic expiry and are lost if app storage is cleared.

Support information is kept as needed to resolve requests and satisfy applicable legal obligations. Firebase/Analytics retention depends on the service and project settings; aggregate reports can last longer than identifiable event records. Google retains its own billing and advertising records under its policies. We do not promise a single deletion deadline for every provider. Contact us for the applicable retention setting and available deletion route.

Use Delete Data for local steps and requests. Turning reporting off or clearing the app does not erase every remote record or cancel a subscription. No security method is guaranteed against every attack.

10. Your rights and children’s privacy

Depending on your jurisdiction, you may have rights to access, correct, delete, obtain or restrict use of personal data, withdraw consent, or object to certain uses. Email vioplayer.support@gmail.com. We may need proportionate information to locate and verify a request; do not send identity documents unless a necessary secure process has been arranged. You can raise a complaint with your local data-protection authority or seek review where an appeal right applies. Withdrawing consent does not undo earlier lawful processing.

VIO has no account or curated children’s catalogue; users choose their own media. If a child has provided personal information to support, contact us so we can investigate and remove it where appropriate. Advertising is subject to the declared audience and applicable child-directed or under-age restrictions. This statement is not an age-rating claim.

11. This website and policy updates

These pages contain no analytics scripts, advertising, upload forms, tracking pixels or site-set cookies. GitHub Pages hosts them and may log technical request data; see GitHub’s Privacy Statement. Following a link or sending email involves the destination provider.

We update this policy when practices change, with notice and renewed consent where required. Developer: bullseye ARC. Privacy and support: vioplayer.support@gmail.com.