1. Who We Are
TubPlayer ("the App") is developed and published by Tubs Software ("we", "us", "our"). This privacy policy explains what data the App collects, how it is used, and the choices available to you.
2. Data We Collect
| Data | Storage | Shared? |
|---|---|---|
| Playlist credentials (server, username, password, playlist URL, or Stalker MAC) | Encrypted on your TV; temporarily stored on our pairing relay if you choose phone setup | Only for optional phone setup, through Cloudflare or Google Firebase (see Section 3) |
| EPG source URL and label | Stored on your TV; temporarily stored on our pairing relay if you choose phone setup | Only for optional phone EPG setup (see Section 3) |
| Playlist content (channels, movies, series, EPG) | Device only; local SQLite database | Never |
| Watch history & progress | Device only; local SQLite database | Never |
| App settings & preferences (theme, parental PIN, display options) | Device only; SharedPreferences (PIN is SHA-256 hashed) | Never |
| Search history | Device only; SharedPreferences (max 20 entries) | Never |
| Crash reports & diagnostics | Firebase Crashlytics | Anonymous (see Section 4) |
| Backup files (if you enable cloud backup) | Your Google Drive; AES-256-GCM encrypted before upload | Your account only (see Section 5) |
| Content metadata (posters, plots, ratings) | Device only; fetched from TMDB, cached locally | Never |
| Donation record (if you donate on tubplayer.com: email address, amount, date, payment reference and status) | Our server (tubplayer.com, hosted by Hostinger); the payment itself is held by Stripe | Stripe processes the payment (see Section 6) |
| Hashed device identifier (if you activate a device after donating) | Our server, linked to your donation email | Never |
| Diagnostic logs (only if you choose to send them from Settings) | Our server (tubplayer.com, hosted by Hostinger); deleted after 5 days | Never (see Section 7) |
3. Playlist Credentials
Entering details directly on your TV
When you enter playlist details directly in the App, credential values are encrypted at rest on the TV using AES-256-GCM with a key protected by the Android Keystore. They are then used to connect from your TV to your IPTV provider. Preference names and other non-secret metadata may remain visible in the App's local preferences.
Optional phone setup
If you scan the setup QR code and enter details on tubplayer.com/setup.html, your server address, username, password, playlist URL, portal URL, MAC address, and any optional Stalker serial number, device IDs, signature or username/password you submit are sent over HTTPS to TubPlayer's pairing service and temporarily stored there. This allows the paired TV to collect the details.
If you scan the EPG QR on Add EPG Source and enter details on tubplayer.com/epg.html, the XMLTV URL and optional label are sent over HTTPS to the same pairing service. XMLTV URLs often include provider username and password in the query string.
If you scan the Google Drive QR on Backup & Restore, your phone opens tubplayer.com/drive.html and Google's normal sign-in screen. After you allow access, Google Drive tokens for this app are sent over HTTPS to the same pairing service so the TV can finish connecting. You are not asked to type a device code.
Two pairing services are currently in use, and which one handles your details depends on the version of the App on your TV. Sessions started by current versions are handled by Cloudflare Workers and Durable Objects. Sessions started by older versions are handled by a Firebase Cloud Function and temporarily stored in Google Cloud Firestore. The setup page tells you which service is handling your session before you submit anything.
A setup session normally expires after 15 minutes. The credential payload is removed when the paired TV claims it or when an expired session is next processed. The remaining session record is then scheduled for automatic deletion - by a scheduled task on Cloudflare, or by Google Cloud Firestore's TTL system for the older service. Deletion is asynchronous and may not happen immediately. Credentials submitted through phone setup are not sent to Firebase Analytics or Crashlytics and are not intentionally written to server logs.
Log messages that might contain stream URLs are sanitised in release builds to strip credentials before being written to Logcat or Crashlytics.
TubEdit phone editor
TubEdit lets you edit your TV's category and channel lists from your phone at tubplayer.com/tubedit. When you pair your phone with the code shown on your TV, the names, order, visibility and logos of the list open on the TV are relayed to your phone through TubPlayer's TubEdit relay, which runs on Cloudflare Workers and Durable Objects, and your changes are relayed back to the TV. The relay does not store your lists: it keeps only the pairing session and rate-limit counters, and a session ends after 20 minutes without activity or when either side leaves. Playlist credentials and stream addresses are never sent. Like phone setup, the relay is encrypted in transit by HTTPS but is not end-to-end encrypted.
Channel logos. Your TV sends your provider's logo address for a channel only when it contains no login details. Many provider logos use plain http, which phones will not show on a secure page, so your phone loads those through tubplayer.com, which fetches the image from your provider's server on your phone's behalf. The address is not stored; we keep only a short-lived request counter, keyed to a one-way hash of your phone's network address, to limit abuse. A logo you choose is saved only on your TV. Logos chosen from TubEdit's logo library between 17 and 19 October 2026 link to the free tv-logos collection on GitHub, so while one of them is on your list, GitHub sees your TV's and phone's IP addresses when they show it. Choose another logo, or the playlist logo, to stop this. Since then, library logos are copies served by TubPlayer's logo service on Cloudflare Workers, which sees the IP address of the phone or TV showing one and the image requested.
Logos on your TV. Manage Channels on your TV can also search TubEdit's logo library. When you open Manage Channels for a playlist, your TV downloads the library's list from tubplayer.com and shows its images from TubPlayer's logo service on Cloudflare Workers, so both see your TV's IP address and the files requested. Nothing about your lists or playlists is sent, and a logo you choose is saved only on your TV.
4. Crash Reports & Analytics
The App uses Firebase Crashlytics (provided by Google) to collect anonymous crash reports and non-fatal error diagnostics. Crashlytics is disabled in debug builds and enabled only in release builds.
What is included in crash reports:
- Device model, Android version, and app version
- Stack traces and error codes when a crash or playback failure occurs
- Navigation context (which screen was active, which section was selected)
- Stream error details (error code, error type, server domain only - never the full URL or credentials)
- Playlist type counts (e.g. "2 Xtream, 1 M3U" - never playlist names, URLs, or credentials)
What is never included:
- Playlist credentials (server addresses, usernames, passwords)
- Stream URLs (only the server domain is logged, never the path which contains credentials)
- Content you watch, your watch history, or your favourites
- Any personally identifiable information
Crashlytics data is governed by Google's Firebase privacy policy.
Firebase Analytics:
The App also includes the Firebase Analytics SDK, which is bundled with Crashlytics and supports its diagnostics. The App itself logs no custom analytics events. The SDK does, as standard Firebase behaviour, automatically collect a limited set of anonymous app-usage signals (such as app opens and session counts) and a pseudonymous app-instance identifier. This data is used only to support app stability and diagnostics - never for advertising and never to identify you. Advertising-ID collection and ad-personalisation are explicitly turned off: the advertising-ID permission is removed from the App, and the SDK's ad-ID and ad-personalisation signals are disabled. This data is governed by Google's Firebase privacy policy.
5. Google Drive Backup (Optional)
If you choose to connect your Google account for cloud backup, the App uses Google's drive.file scope. This is the most restrictive Drive scope available - it only allows the App to access files that it has created itself.
How backup works:
- Your app data (playlists, settings, watch history, credentials) is encrypted on your device using AES-256-GCM before being uploaded
- The encrypted backup file is stored in your personal Google Drive account
- We have no access to your Google Drive or your backup files
- You can disconnect Google Drive at any time from the App's settings, and delete backup files directly from your Google Drive
If you do not enable Google Drive backup, no data is sent to Google Drive and no Google account connection is made. Local backups to your device's Downloads folder are also available and do not involve any cloud service.
6. Donations & Device Activation (Optional)
TubPlayer is free and a donation unlocks no features. Donating only hides the Donate reminder on the devices you activate.
Donating through Google Play
If you installed the App from Google Play, donations are Google Play purchases. Google processes the payment under its own terms and privacy policy; the App checks the purchase with our server so the reminder can be hidden.
Donating on tubplayer.com
If you installed the App from tubplayer.com, donations are made on tubplayer.com/donate and paid through Stripe. You enter your card or wallet details on Stripe's own checkout page; we never see or store your card details. After a payment, Stripe tells our server your email address, the amount and currency, the payment reference and its status (including any later refund or dispute). We store these as your donation record.
We use your email address only to send you activation codes, to recognise your donation when you activate another device, and to answer you if you contact us. We never use it for marketing and never sell or share it.
Activation codes
Activation codes are 8-digit, single-use codes that expire 10 minutes after they are sent. We store only a one-way hash of each code, never the code itself.
Device identifier
When you activate a device, the App sends our server a one-way hash of the device's Android ID. On Android 8 and later this ID is specific to the App; the original ID never leaves your device and cannot be recovered from the hash. We link that hash to your donation email so the device stays activated after a reinstall and so a refund can switch it off again. The App also keeps a signed activation token on the device so it can recognise the activation while offline; the token contains only the hashed identifier.
Rate limiting
To stop abuse of the donation and activation pages, our server counts requests per network address. Addresses are stored only as one-way hashes and are deleted within a day.
7. Sending Logs to Support (Optional)
If something is not working, you can choose to record a diagnostic log in the App (Settings, Send Logs) and send it to us. Nothing is recorded for sending or sent unless you start it yourself, a recording lasts at most 10 minutes, and you can review everything on the TV before it is sent.
What a log contains:
- TubPlayer's own log messages from the recording and from shortly before it, including the names of channels and programmes you played during that time
- Your device's specifications (manufacturer, model, Android version, memory, storage and display details) and the App version
- Your App settings, and the type and size of each playlist
- A one-way hash of the device's Android ID, so that several logs from the same device can be linked. The original ID never leaves your device, and this hash is different from the one used for donations
What is removed before anything is stored or sent:
- Usernames, passwords, tokens, email addresses and MAC addresses
- The names and addresses of your IPTV provider's servers, which are replaced by anonymous labels
- Playlist names, and the name you gave your device
Logs are sent over HTTPS to our server (tubplayer.com, hosted by Hostinger) and you are given a reference number to quote to support. Logs are used only to investigate the problem you report, and may be analysed with automated tools, including AI. They are deleted automatically after 5 days. To stop abuse, our server counts submissions per network address; addresses are stored only as one-way hashes and are deleted within a day.
8. TMDB (The Movie Database)
The App uses the TMDB API to fetch content metadata such as movie posters, plot summaries, cast information, and ratings. These requests are made directly from your device to TMDB's servers and contain only the content title being searched - no personal information, credentials, or device identifiers are included. Fetched metadata is cached locally in the App's database.
TMDB is a third-party service governed by its own privacy policy.
9. Data Stored on Your Device
App data - including playlists, channel guides, watch history, favourites, parental settings, and preferences - is stored locally on your device in a SQLite database and Android SharedPreferences. Data is transmitted when required for features you choose, including connecting to your IPTV provider, fetching TMDB metadata, diagnostics described in Section 4, Google Drive backup described in Section 5, and optional phone setup described in Section 3.
The parental control PIN, if set, is stored as a one-way SHA-256 hash. The original PIN cannot be recovered from the stored hash.
10. Third-Party Services
| Service | Purpose | Data Sent |
|---|---|---|
| Your IPTV provider | Stream content, fetch channel lists, EPG | Credentials you configured |
| Cloudflare Workers & Durable Objects | Optional phone-to-TV playlist setup and Google Drive phone sign-in (current App versions) | Submitted playlist details or short-lived Google Drive tokens, plus a pseudonymous session/network identifier for the short-lived relay (see Sections 3 and 5) |
| Firebase Cloud Functions & Cloud Firestore | Optional phone-to-TV playlist setup (older App versions); fallback Google Drive device authorisation | Submitted playlist details and a pseudonymous session/network identifier for the short-lived relay, or Google Drive authorisation data (see Sections 3 and 5) |
| Cloudflare Workers & Durable Objects (TubEdit) | Optional TubEdit phone editing | Names, order, visibility and logo addresses of the list being edited, plus a pseudonymous session/network identifier for the short-lived relay (see Section 3) |
| tubplayer.com | Showing plain-http provider logos in TubEdit; the logo library's list for Manage Channels on the TV | The logo address, used to fetch the image and not stored; your TV's IP address when it downloads the list (see Section 3) |
| Cloudflare Workers (TubEdit logo library) | Showing logos from TubEdit's logo library, on your phone or in Manage Channels on your TV | The IP address of the phone or TV and the image requested (see Section 3) |
| GitHub (tv-logos collection) | Showing a logo chosen from TubEdit's logo library on 17–19 October 2026 | Your TV's and phone's IP addresses and the image requested (see Section 3) |
| Firebase Crashlytics | Crash reporting | Anonymous diagnostics (see Section 4) |
| Firebase Analytics | Anonymous app-usage diagnostics (bundled with Crashlytics; no custom events) | Anonymous automatic usage signals; no advertising ID (see Section 4) |
| TMDB API | Content metadata | Content titles only |
| Google Drive | Cloud backup (optional) | Encrypted backup file to your own account |
| Stripe | Optional donations on tubplayer.com | The payment details you enter on Stripe's checkout; Stripe tells us your email address and the payment outcome (see Section 6) |
| Hostinger | Hosts tubplayer.com, its donation and activation service, and logs you choose to send | Donation records and hashed device identifiers (see Section 6); diagnostic logs (see Section 7) |
11. Children's Privacy
The App is not directed at children under the age of 13. We do not knowingly collect personal information from children. The App includes parental controls that allow a parent or guardian to restrict access to playlist management features using a PIN.
12. Data Retention & Deletion
All locally stored data can be deleted by:
- Removing individual playlists from the App (deletes all associated content, history, and credentials for that playlist)
- Clearing the App's data through Android Settings → Apps → TubPlayer → Clear Data
- Uninstalling the App (removes all local data)
Crashlytics data is retained by Google according to their standard retention policy (typically 90 days for crash data). We do not have the ability to associate crash reports with individual users.
For optional phone setup, the credential payload is removed when claimed or when expiry is processed. Sessions normally expire after 15 minutes. The remaining session record is scheduled for asynchronous deletion one hour after session expiry - by a scheduled task on Cloudflare, or by a Firestore TTL timestamp on the older service; actual deletion may occur later.
Google Drive backup files remain in your Google Drive until you delete them. Disconnecting Google Drive from the App does not automatically delete previously created backup files.
Diagnostic logs you send from the App are deleted automatically 5 days after they are received. To have one deleted sooner, email support@tubplayer.com with its reference number.
Donation records and the hashed identifiers of activated devices are kept for as long as they are needed to recognise your donation and to meet our accounting and tax obligations. Unused activation codes are deleted about a week after they expire. To have your email address and activated devices removed, email support@tubplayer.com from the address you donated with; your devices will then show the Donate reminder again. Stripe keeps its own payment records under its privacy policy.
13. Changes to This Policy
We may update this privacy policy from time to time. The effective date at the top of this page will be updated accordingly. Continued use of the App after changes constitutes acceptance of the updated policy.
14. Contact
For questions about this privacy policy or how the App handles data, contact us at support@tubplayer.com.