No analytics, no telemetry, no crash reporting
The app sends no usage data, no identifiers, no device fingerprint and no crash reports. There is no build flag to turn any of it back on, and no analytics SDK in the dependency list to turn on.
Ventic collects nothing about you. There is no account, no server, no analytics and no advertising - so most of this page is a list of the things that do not happen.
Last updated August 30, 2026
Nothing. Ventic has no backend of its own: there is no server that could receive your data, and no operator on the other end of one. Everything the app knows about you stays in its own storage on your device, and is deleted with the app.
The app sends no usage data, no identifiers, no device fingerprint and no crash reports. There is no build flag to turn any of it back on, and no analytics SDK in the dependency list to turn on.
There is nothing to sign into and no Ventic server to sign into it with. Your library, watch history, progress and settings are files on your own device.
A debrid key, if you use one, lives inside the source URL you added and is sent only to that source. A backup file leaves credential-bearing keys out.
Ventic ships with no sources configured. Until you add one, it queries no one for releases at all.
Your library and watchlist, playback position and watch history, the source URLs you added, player and interface settings, downloaded torrent data, and cached artwork. None of it is uploaded anywhere. Moving it to another machine is a file you export and carry yourself, and there is no sync service to opt into.
Besides the sources you add yourself and the peers your torrents connect to, the app makes requests to the services below. Each one sees your IP address, because every request on the internet does. None of them is sent an account, an identifier or a profile, because there is none to send.
Posters, backdrops, synopses, cast lists and ratings, and the title to IMDb id lookup a source is keyed by. Sent: the title or id being looked up. Used under the TMDB API terms.
The subtitle list, and the one case TMDB cannot produce an IMDb id for. Sent: the id of the title you opened.
A title's trailer, in YouTube's embedded player on its no-cookie domain, and only if you press play on it.
One unauthenticated request at startup asking whether a newer Ventic has been released. It sends nothing but the request itself.
A static supporters.json, read when you open Settings and then Support. Ko-fi itself is never contacted by the app.
Each of these has its own privacy policy, and what they do with a request is theirs to state, not ours. A source you add is a third party you chose: Ventic sends it the search you typed and nothing else, but it is that operator's policy that governs the request from there.
When you download a torrent, your IP address is visible to the other peers in that swarm and to the trackers coordinating it. That is how the protocol works in every client, not something Ventic adds, and nothing the app can hide. If that matters where you live, use a VPN or do not use the torrent engine.
The Android and Android TV build asks for these, and nothing else. There is no location, contacts, camera, microphone or advertising-id permission in the manifest.
Fetching metadata and transferring torrent data. Without it the app does nothing.
Keeping a download running while the app is in the background, which Android requires a visible service for.
The notification that service is required to show, and download-finished notices. Optional - denying it costs you the notice, not the download.
Stopping the device from sleeping mid-playback or mid-download.
Not in the Google Play build, which does not update itself - it sends you to Google Play. In the APK from GitHub it installs an update you chose to download, and nothing downloads or installs without you pressing the button.
Ventic is not directed at children and collects no personal data from anyone, of any age.
ventic.tv is a set of static files. It sets no cookies, runs no analytics and embeds no third-party scripts. The server keeps ordinary access logs, as every web server does.
If this policy changes, the date at the top changes with it and the edit is in the site's public git history. Ventic is open source, so none of the above has to be taken on trust - the network calls are in the code, and anyone can check that the list is complete.
Questions about this policy, or about anything the app does with your data, go to tilen.pirih@gmail.com - or to the issue tracker, where the answer is public and stays findable.