Privacy policy
Viora Play for Android · Updated 18 November 2026
Scope
This policy covers the Android phone, tablet and TV application Viora Play, including its discovery and supported-source modes. Features depend on app version, region and configuration. Signing in is required to use the current application. Android sign-in uses Google; an existing linked account retains its associated Viora data.
Account and social features
If you sign in with Google, Viora receives the account identifier, name, email and profile information supplied by Google. We do not receive your Google password. Existing account credentials and session tokens are used to authenticate and secure your account.
Friend invitations, connections, blocks, recommendations, messages and related read/delivery information are processed to provide social features. Information you send to friends is visible to the selected recipients. A copied share link may be opened by another signed-in user who has that link.
Country, activity and technical information
Your public IP is used to estimate country for regional catalog availability and configured features; the app does not request precise GPS location. Queries, requested titles and playback/source requests are sent to the relevant services.
Installation/app/device identifiers, acquisition attribution, interaction and viewing/progress information, diagnostics and service/security logs may be processed to operate the app, measure usage, prevent abuse and troubleshoot. Some preferences, favorites, caches and partial/completed downloads are stored on your device.
Notifications and advertising
If you enable notifications, a push registration token, installation identifier, platform, permission status and app version are registered with Viora and Firebase Cloud Messaging to deliver notifications. You can change notification permission in Android settings.
This Android application includes Google Mobile Ads and consent functionality. Google services may process IP-derived approximate location, device/advertising identifiers, app/ad interactions and diagnostic information to deliver and measure ads, prevent fraud and operate the SDK. Advertising behavior depends on availability, consent and applicable settings. Google services also have their own privacy policies.
App-install measurement with Meta
Android builds with Meta app measurement send install and app-session events and counts of completed registrations, content views, submitted searches, additions to favorites, playback starts, shares and download starts/completions, an anonymous app-scoped device identifier, app/device and operating-system information, IP/network information and SDK diagnostics to Meta to attribute installations and measure advertising effectiveness. Registration events include only the registration method (username, Google or Apple). Engagement events contain event names, not movie titles, content identifiers, search text, social messages, email, account identifiers, media/source links or viewing history. A local hashed registration receipt prevents duplicate signup reporting and is not sent to Meta. Advertising-ID collection and automatic purchase logging are disabled for this integration.
Meta processes measurement data under its own Privacy Policy. This integration is separate from Google sign-in and does not add Facebook login. SDK measurement failures do not block normal app use.
Media, external sources and peers
Video and download data normally travel directly between your device and the selected source or torrent peers rather than through a central Viora movie server. Source services, peers, streaming providers, catalog/CDN services and casting devices receive network information required for the connection. Torrent peers can observe your public IP and requested torrent information, and may exchange pieces with your device during a session.
External services operate independently. Some source and peer connections may use protocols without transport encryption. Viora account/API requests use HTTPS, but this is not a promise that every external media or peer connection is encrypted. Use sources you are authorized to access.
This Android release has no background transfer or background media foreground service. Downloads pause when Viora is minimized and resume when it returns. Automatic background seeding and Cast background notification/reconnection services are unavailable.
Device access and your choices
The app uses network access and app-owned storage for selected downloads. It does not require precise location, microphone, phone contacts or broad photo/video library permissions for its core features. Social connections are managed inside Viora.
You can choose whether to use social features, manage notifications and available consent choices, remove local downloads, clear device data, sign out or request account deletion. Signing out returns the current application to its required sign-in screen. Removing a local download is different from deleting an account.
Retention and deletion
Account and service data are retained while needed to provide the account/features or for operational, security and legal purposes. Deleting an account removes associated account data through the account-deletion process; security/legal records may be retained where necessary, and content already received by another user may remain with that recipient.
To delete your account, use Account → Delete account in the app and complete ownership verification. If you cannot use the app, email vioraplaysupport@gmail.com from the account email and request deletion. Do not send passwords or verification codes. Details: https://vioraplay.tech/install/android/delete-account/
Contact and changes
For privacy, support or rights inquiries, contact vioraplaysupport@gmail.com. We may update this policy as the Android application or its services change.