Last updated 13 August 2026
This policy sets out what Elastic Player does with information and, more usefully, what it never touches in the first place.
Server addresses, usernames, passwords, and playlist contents are stored on your device and sent only to the provider you entered them for. We run no server that holds them and no account system to attach them to.
Your connections and credentials, the playlists and catalogues fetched from them, your favourites, your playback positions, and your settings are all held locally. Deleting a connection removes its data; deleting the app removes all of it.
Elastic Player has no accounts. You never give us an email address in order to use it, we hold no profile for you, and there is nothing to log into. This is also why we cannot restore your playlists if you lose your device — we never had them.
We do not receive your IPTV credentials, the contents of your playlists, or any record of what you watch. Streams travel directly between your device and your provider; they do not pass through us.
The free version of the mobile app shows ads served by Google AdMob. The app requests non-personalised ads only, which asks Google not to use profiling to decide what you are shown.
Even so, Google receives the technical data needed to deliver and count an ad: your IP address, device and app information, and an advertising identifier used for frequency capping and fraud prevention. Google's handling of that is governed by its own privacy policy. You can reset or limit the advertising identifier in your device settings, and the paid version removes ads altogether.
The mobile app includes Google Firebase Analytics and Crashlytics. Analytics records aggregate usage — app opens, sessions, device model, approximate region and similar — against a per-installation identifier. Crashlytics sends a diagnostic report when the app crashes, describing the state it was in when it failed.
We use both only to see which features get used and what is breaking. Neither receives your playlists, your credentials, or what you were watching.
When you add a connection, your device talks to that provider directly. The provider can see your IP address, which streams you request, and when — exactly as it would with any other player. What it does with that is covered by its privacy policy, not ours. Choose your provider accordingly.
If you use the contact form or email us, we receive the name, email address, and message you send, plus the topic and platform you picked. We use them to answer you and for nothing else: no marketing, no mailing list, no sale to anybody.
The form delivers mail through Resend, our email provider, which processes the message in order to send it. Correspondence stays in our mailbox for as long as it is useful as support history, and you can ask us to delete it.
The site sets no advertising or tracking cookies. Your language and theme are kept in your browser's local storage so the site remembers them, and nothing about that leaves your browser. Our host keeps ordinary server logs, including IP addresses, for security and diagnostics.
Elastic Player is not directed at children and we do not knowingly collect information from them. Because the app plays whatever source is added to it, we cannot filter what a given provider serves; supervising that is a matter for whoever owns the device.
On-device data lasts until you delete it. Support email is kept while it remains useful and then removed. Analytics and crash data are retained according to the Firebase retention settings on our project.
Depending on where you live, you may have the right to access, correct, or delete personal data we hold. In practice we hold very little: support correspondence, and analytics tied to an installation identifier rather than to you by name. Write to us and we will act on whatever we have.
You can erase everything the app holds about you yourself, at any moment, by removing the connection or uninstalling the app.
If what the app collects changes, we will update this page and the date at the top of it.
Questions? Visit the support page or write to us directly.
This document is published in several languages. Where the versions differ, the English text applies.