Privacy Policy

AvleaPlay is a local-first media player. Your media files, watch history, library index, favourites, Soundtrack Journal, AI subtitles and genre analysis stay on your device and are never uploaded. The app has no accounts, no advertising, no analytics, and nothing that reports back to us. This website counts visits, and only if you accept — see This website below.

Effective: 23 October 2026 · Applies to AvleaPlay for Windows (Microsoft Store and direct downloads) and AvleaPlay for Android (Google Play, phones, tablets and Android TV) · Publisher: tmnetworks, Greece · Contact: [email protected]

On Windows, most of what the app remembers lives in a folder that is yours to inspect or delete: Documents\AvleaPlay. On Android it lives in the app's private storage, which no other app can read. Clips you export go to Download/AvleaPlay, and snapshots to Pictures/AvleaPlay.

The complete list of network activity

Every item is optional and started by you. There is nothing else.

1. Music identification (built-in). When you press Identify, an acoustic fingerprint of the audio — integer hashes computed on your device, which cannot be turned back into audio — is sent to AvleaPlay's own recognition service (api.avleaplay.com) and answered immediately. The audio itself never leaves your device. The servers are in Germany and are reached through Cloudflare, which carries the encrypted connection and sees the request's IP address. We keep no account of you. The recognition service records no IP addresses at all; the web server in front of it keeps standard access logs that do contain them, rotated daily and kept for about two weeks. Alongside them we keep a short log of identification requests holding the time, the outcome and the two-letter country code Cloudflare reports — no address — so we can tell whether the feature is being used at all. It is rotated and discarded on the same two-week schedule.
2. Music identification (optional AudD tier). If you add your own AudD API key, a short audio snippet (about 25 seconds) is sent to AudD — a third-party service with its own privacy policy (audd.io) — and only when the built-in recognition could not name the track. Your key is never stored in plain text. On Windows it is encrypted by Windows (DPAPI) and kept in AvleaPlay's own app-data folder, readable only by your Windows account. On Android it is encrypted with a key held in the Android Keystore and kept in the app's private storage.
3. One-time model downloads. AI-subtitle models are fetched from Hugging Face and the genre-recognition model from avleaplay.com (also through Cloudflare), each only when you ask for the feature, over HTTPS and verified against a fixed checksum. AI subtitles and genre recognition then run entirely on your device. On Windows, the ONNX Runtime library that runs genre recognition is Microsoft's official build and writes Windows trace events while it works; whether Windows collects those is governed by your own diagnostic-data settings, and none of it reaches us.
4. Playing a stream you open. If you use Open URL, or open a stream address from the command line or from another app, AvleaPlay connects to the address you gave it, exactly as a browser would. We are not part of that connection and see nothing of it.
5. Links you follow from a match. Opening a recognised song in Spotify, Apple Music or YouTube launches your browser at that service with the track's name. That request goes from your browser to them, not through us.
6. Play on another device (local network). With Receive from this network switched on, AvleaPlay answers other AvleaPlays on the same Wi-Fi with its device name, its platform and a port. Switched off, it answers nothing and appears in nobody's list. When you send what you are watching, your device serves that one file to the device you picked, over your local network only, and the other device asks its own user before anything plays. The device name starts from your computer's name (or your phone's model), and you can change it in Settings. None of this passes through the internet or through us.
7. Sending a link to Android TV from your phone. The TV shows a local address and a six-digit code. Your phone's browser sends the link straight to the TV over your local network, and the TV asks before opening it.
8. Google Cast (Android phones and tablets). When you cast, the Cast device (a Chromecast, for example) loads Google's standard media receiver and fetches the video itself: from your phone over the local network, or from the stream's own address. The Google Cast library inside the app starts only when you tap Cast. From then on it sends Google anonymised usage and diagnostic information about finding Cast devices and about casting sessions, your device and the app. Google uses it to improve casting, under its own terms: see Google's Cast SDK data disclosure. Neither you nor we can switch this off, other than by not casting. We receive none of it.

This website

avleaplay.com measures how many people visit and which pages they read, with Google Analytics. It is separate from the app: nothing here is connected to anything the app does, and the app sends nothing to Google Analytics.

Nothing is stored on your device until you accept. On your first visit a banner asks, and until you answer, analytics storage is switched off through Google's Consent Mode — no cookie, no identifier, nothing written to your browser. If you decline, that stays the case for good; your choice is remembered in your own browser's local storage and nowhere else. If you accept, Google Analytics sets its own cookies, and Google processes the visit as a data processor under its own terms; you can withdraw by clearing this site's data in your browser, which brings the banner back.

Either way, Google receives the request itself, which necessarily includes your IP address, as it does for any site you open. We see aggregate reports — page views, countries, referrers — never individual people, and we do not run advertising and do not share this with anyone.

What stays on your device

Everything else, including all of this:

• Your media files, and every frame of them. Video never leaves your device for subtitles, for genre recognition or for anything else. It leaves only when you cast it or send it to another device yourself, and then only over your own network.
• Watch history and resume positions, the library index, thumbnails and favourites.
• The Soundtrack Journal: every song you identified, with the film it played in.
• AI subtitles, and the audio extracted to generate them.
• Logs, settings and your AudD key.

Permissions on Android

AvleaPlay asks only for what its features need:

• access to your videos and music, to list and play them (nothing is uploaded);
• network and Wi-Fi state, for streams, Cast and the local-network features;
• permission to keep running in the background while it plays, casts or sends to another device, which Android shows as a notification.

It does not ask for your location, contacts, camera or microphone.

Your control

You can undo each of the network features from Settings: remove the AudD key, delete downloaded models, clear the Soundtrack Journal, withdraw the Music ID consent (after which nothing is sent and the next Identify asks again), or switch off Receive from this network. On Android you can also withdraw media access in the system settings at any time.

Uninstalling on Windows removes the app and its own app-data (logs, the AudD key, AI-subtitle models). Your Documents\AvleaPlay folder — watch history, library index, thumbnails, Soundtrack Journal, exported clips and the genre model — is deliberately left behind so it survives a reinstall; delete that folder yourself to remove it.

Uninstalling on Android removes everything the app kept in its private storage, including the AudD key and downloaded models. Clips and snapshots you exported stay in Download/AvleaPlay and Pictures/AvleaPlay until you delete them.

Children

AvleaPlay is not directed at children and collects nothing from anyone, of any age.

Changes

If this policy changes, the new version is published here with a new effective date. The app still collects nothing, so a change about the app can only ever be about what it may send when you ask it to; a change about this website can only ever be about the visit counting described above.

Contact

For any privacy request, write to [email protected]. We are tmnetworks, in Greece; under the GDPR you may also complain to your national supervisory authority.