Bamboo Player for Android privacy policy

Last updated: 8 October 2026.

Controller and contact

Pedro Joaquín García, publicly identified as the developer under the name Joaquin Garcia, is responsible for Bamboo Player. For app support, privacy questions or data rights requests, email juakigarcia8@gmail.com with the subject “Bamboo Player Android Privacy”.

This policy describes the Android version. Bamboo Player plays the files, links and playlists you choose. You can use it without creating a Bamboo account; an account is optional and enables library synchronisation. Any Xtream server account you enter belongs to that provider.

Request account and data deletion. You can request it by email even after uninstalling the app.

Your library and files

The app stores configured playlists, provider access details, favourites, playback history and progress, settings and library organisation on your device. Credentials and the catalogue are encrypted using keys protected by Android Keystore. Playing a local file does not upload its content to our servers.

Android's document picker lets you choose which files the app can access. Downloads are stored in the app's storage. Artwork, descriptive metadata and download indexes may be kept in local caches or indexes to improve presentation and avoid repeated loading.

Connections to your providers

When you add a playlist, request programme information, play or download content, your device connects to the address you selected. That server receives the request, your connection IP address and, where needed, credentials or headers required to provide its service. Its terms and privacy practices apply to that processing.

Bamboo supports HTTPS and HTTP sources, including local network sources. HTTP does not encrypt traffic; protection depends on the protocol and provider you select.

Metadata, images and operational logs

To display titles, summaries, cast, ratings and images, the app requests information from Bamboo Player's metadata service. Requests include search terms, content titles or identifiers, the type of request and your language and region preferences. Some requests happen automatically to complete information for titles in your playlist. We do not send your IPTV passwords or entire library to this service.

Metadata queries go through our server using a verified temporary session tied to Android Play Integrity. The app distributed through Google Play does not contain TMDB or TheTVDB API credentials or the previous shared proxy token. Queries are sent in the HTTPS request body; operational activity for this route does not store the search text, IP address or installation identifier together with catalogue activity. We keep a shared descriptive-data cache to respond quickly. It contains information about requested films, series or people without associating it with your installation.

The hosting service still receives your connection IP address and may log the date, requested path, HTTP status and technical browser or app information. Access logs do not include these query bodies or the session bearer token. Log rotation is configured for 14 daily files and may vary with activity and maintenance. Operational metadata records have cleanup for entries older than 90 days, performed during requests; this is not immediate deletion at that exact deadline.

TMDB and TheTVDB metadata is requested through our server. Images are downloaded from their servers or addresses supplied by your playlist, exposing the image request and connection IP address to those services. The device's region preference adapts information; the app does not request GPS location.

Series credit detection

To move automatically to the next episode, the app may analyse reduced frames during the final part of an episode and locally recognise text patterns associated with credits. The frames, recognised text and detection result are processed only in memory on the device: they are not stored or sent to Bamboo or Google.

This feature uses Google's ML Kit. The SDK may send Google technical device and app information, performance metrics, API configuration and version, input and output sizes, event types and error codes for diagnostics, usage analytics, maintenance, improvement and abuse prevention. This technical data does not contain the frames, recognised text, the title you are playing or the detection result. Google states that it is encrypted in transit and is not shared with third parties. See ML Kit data information and its terms and privacy information.

Purchases, subscriptions and restoration

Pro plans are purchased through Google Play Billing: a monthly subscription or a lifetime one-time purchase, depending on the options Google Play displays in your region. Google handles payment and billing details; Bamboo does not receive your card number or Google account password. Prices, offers and conditions are shown before you confirm a purchase. You can manage or cancel a subscription in Google Play; uninstalling Bamboo or requesting data deletion does not itself cancel a subscription.

To activate, restore and verify a licence, the app sends Bamboo the product identifier, Google's purchase token, a random installation identifier and the information needed to validate the request. Bamboo checks the purchase or subscription status, expiry and acknowledgement with Google. We do not activate Pro solely from a preference stored on your phone. Pending purchases do not grant paid access until Google confirms completion.

We store the encrypted purchase token, its verification hash, the product, status and dates needed to verify the entitlement. This allows payment acknowledgement, refund or expiry detection and restoration on a legitimate installation. The app receives a temporary signed authorisation bound to its installation. It can retain offline access for up to seven days and never beyond the subscription expiry confirmed by Google. Android purchases are verified with Google Play and are not transferred through backups or iOS purchases.

We may also grant complimentary access through an authorised code, without charging you or replacing Google Play with another payment system. Redemption sends the code over HTTPS; we retain only its hash, its installation association and necessary dates. Renewal uses a previous signed authorisation and the same integrity checks; the app does not retain the code. Inactive associations are removed after 90 days, and the code can be redeemed again while authorised. We may revoke these grants; a previously issued authorisation can remain valid offline for up to seven days.

Integrity and abuse prevention

We use Google Play Integrity to check that the app, its distribution licence and the device meet the security requirements for protected services. Google receives app metadata —package, version and signing certificate—, the Google Play licence status, device attestation information and a request hash. Bamboo receives the result needed to authorise the operation. These checks are not used for advertising or profiling your viewing habits. See Play Integrity data information.

Metadata sessions last up to 15 minutes and are reused during that period. Verification and rate limits use a random installation identifier and technical hashes to prevent request replay and abuse. The server does not retain the full Integrity token or complete attestation response; it temporarily retains the request hash, outcome and signed authorisations it issues. IP rate-limit hashes use a server-held key. These are pseudonymous data; encryption or hashing alone does not make them anonymous.

Optional usage statistics

If you keep usage statistics enabled, the app sends events over HTTPS to Bamboo for app opens and activity, onboarding, plan screens, purchase and restore attempts and outcomes, playlist imports and refreshes, searches, playback, PiP and Cast. These records help monitor app operation, understand which features are used and diagnose errors.

Each event includes random installation, session and event identifiers, Android or Android TV platform, device manufacturer and model, operating system version, app version and build, language, timezone and date. The server retains the connection IP address and technical connection and client hashes with the event. The installation identifier links events from the same installation; the session identifier groups activity within an app run. These are pseudonymous data, not anonymous statistics. They are not associated with your Bamboo account, and we do not use the IP address to infer your location.

Details may include Pro access and verification status, the selected plan, purchase attempts, cancellations, pending or completed purchases, trial duration and error codes; playlist type, channel count, local or remote source, connection protocol and a shortened hash of the source domain; the broad content type used —live channel, movie or series—, search result counts and types and query length ranges. They do not include accounts, complete playlist addresses or credentials, played titles, search terms, purchase tokens or advertising identifiers. The domain hash does not contain the complete URL, path or parameters; it may link events involving the same provider.

You can disable these statistics in Settings → Library and privacy → Usage statistics. They are initially enabled; disabling them stops new sends and deletes the pending local queue without preventing app features. The local queue holds up to 500 events and discards events older than seven days. Received events are retained for up to 90 days, with daily cleanup. To request deletion of your installation records, email juakigarcia8@gmail.com and include the identifier you can copy in Settings → License and plans → Copy installation ID for support. Deleting a Bamboo account does not automatically delete these records because they are not associated with that account.

Google Cast

When you cast to a receiver you select, it receives the content or its address, title and artwork. Local files may be served to the receiver over your local network. The Google Cast SDK also sends anonymous technical usage and session logs to Google to improve its operation. Google states that these logs are encrypted in transit and cannot be individually opted out of or deleted through the app. See Google Cast data information.

Optional account and library synchronisation

You can create an account with a name, email and password or sign in with Google or Apple in Settings → Synchronisation. Google's Firebase Authentication manages identity, email verification, password recovery and linked sign-in methods. It receives the account data needed for those methods, such as name, email, user identifier, credentials and authentication tokens, plus IP and technical client data for security. If you select Google or Apple, those services receive your sign-in request under their policies. Bamboo does not receive the password for your Google or Apple account. We do not use your account for advertising.

If you accept library synchronisation and sign in to your account, the app synchronises with our HTTPS service sync.bambooplayer.es, hosted on a VPS, to retrieve and update IPTV sources and playlists, favourites, personal lists and their names and members, content titles and references, watched items, playback positions and duration. Source packages can include the M3U catalogue, server and playback addresses and provider credentials, including Xtream credentials, to configure your other devices. This data is associated with your Firebase identifier. Local videos and downloaded media files are not uploaded to synchronise the library.

Requests are authenticated with Firebase tokens and encrypted over HTTPS. Source packages are encrypted in VPS storage and their backups are encrypted. The server holds the keys needed to decrypt source packages: this synchronisation is not end-to-end encrypted. Favourite and progress records are stored in a server database with restricted access; we do not claim that the whole database has field-level encryption. Local data remains protected by Android Keystore.

You can sign out to stop synchronisation. Signing out, uninstalling or clearing local data does not delete the account or data stored by the service. Account deletion and its exceptions are explained below. Your account does not replace Google Play purchase verification or transfer an Android purchase to iOS.

Backups and shared documents

You can export a backup or link a shared document using your chosen file provider, in addition to account synchronisation. Backups are password-encrypted with AES-GCM; you must keep that password to restore them. The shared-document password is stored encrypted on the device. Local file access permissions and Pro licences are not transferred in the backup.

If you enable shared-document updates, Android may modify the document in the background. Its storage and retention depend on your chosen provider. This document-based mode does not need a Bamboo account, and Android does not sync through iCloud. You can unlink the document in settings; doing so does not delete existing copies from your provider.

Purposes, legal basis and recipients

We process the information needed to provide the features you request and protect the service. Processing necessary to use those features is based on providing the service; limited security and diagnostic logs are based on the legitimate interest in keeping it secure and operational. Optional permissions and features are enabled through your choices in the app or Android.

Recipients may include hosting and backups for the synchronisation service, Google/Firebase for account management, Google or Apple if you select their sign-in methods, metadata providers, Google Play for purchases and integrity checks, Google for ML Kit technical metrics, Google Cast and providers or receivers you configure. We do not sell personal data or include behavioural advertising. External services may process data outside your country; their terms and policies explain that processing. Links to trailers, websites or other apps open external services with their own policies.

Purchase verification and restoration provide the service you have bought. Fraud prevention, integrity checks and rate limits are based on the legitimate interest in protecting the service. If a check prevents a legitimate operation, contact us for support and review. Google applies its own terms and privacy policy to payments, the Google Play account and data it handles directly.

Retention, deletion and your rights

Your account and synchronised library are kept while you maintain the account, until you request deletion; the service currently does not automatically delete accounts for inactivity. Technical receipts preventing repeated synchronisation batches are cleaned after 30 days through periodic maintenance. Encrypted service backups rotate using thresholds of three days on the VPS and seven days at the external destination; a backup created before deletion may remain until the next cleanup. If a backup needs to be restored, pending deletions must be reapplied before serving that data again.

Firebase states that it keeps authentication IP logs for a few weeks and other authentication information until user deletion is requested; afterwards, it removes data from live and backup systems within 180 days. Firebase Authentication processes that data in the United States. See Firebase privacy and retention information.

Local data remains until you remove it using the available features, clear the app's data or uninstall it. Exported files and backups must also be deleted at their destination. Server response and replay-prevention records are cleaned up after approximately one day; rate-limit counters after two days. Inactive installation associations are removed after 90 days. Cleanup runs periodically and may complete after the stated threshold.

Purchase records are kept while needed to validate or restore an active entitlement, including a lifetime purchase. Inactive purchase or expired subscription records are removed after 90 days without a recent verification under the service cleanup process. Periodic checks can update pending, paused or recovering purchases. Additional information may need to be retained for a legal obligation or outstanding claim; Google and other providers apply their own retention periods. Aggregated or anonymised data no longer permits individual deletion.

You may request access, correction, deletion, restriction, objection or portability where applicable by emailing juakigarcia8@gmail.com with the subject “Bamboo Player Android Privacy”. To help locate records, include the approximate date and feature used and, if available, your installation support identifier. Do not send IPTV passwords, purchase tokens, card numbers or private files. We may request proportionate information to confirm the request relates to you. Deletion of technical or purchase records not removed with the account is handled through this contact, does not require a Bamboo account and may require fresh verification if you later restore a purchase. It does not delete records Google must retain or stop future billing; manage subscriptions in Google Play.

Delete your Bamboo Player account and data

Without installing the app: email an account deletion request to juakigarcia8@gmail.com with the subject “Delete Bamboo Player Android account”. Include the email used in Bamboo and whether you signed in with email, Google or Apple. For Apple's hidden-email option, include the private relay address used by your Bamboo account. You may also request deletion of specific data while keeping the account, indicating which data. Do not send passwords or tokens. We will proportionately verify that you own the account, for example by replying to its registered address, before deleting it and notifying you of the outcome. You do not need to reinstall the app or purchase Pro.

In the app: open Settings → Synchronisation → Manage account → Delete account and confirm your identity using that account's sign-in method. The app requests deletion of synchronised records and files from the VPS, then deletion of the Firebase user; linked Apple access is revoked during this process. If the process reports an error, use the contact above to complete and check deletion.

The active service deletes the associated sources and credential packages, favourites, personal lists, watched items, progress and synchronisation receipts; deletion of the identity and account data is requested from Firebase. We retain only the deleted account's identifier and deletion date to prevent a device with an old session from uploading the library again. This security record has no automatic expiry and contains no library, email or passwords. Earlier backups and Firebase follow the retention periods explained above.

Deleting an account does not erase the library or downloads remaining on your devices, backups exported to another provider or your IPTV provider, Google or Apple account. You can delete those at their own destination. Purchases and security records not linked to the account follow the earlier retention periods; you can request their deletion by email with the installation identifier, if available. Account deletion does not cancel a Google Play subscription: you can manage it in Google Play before or after requesting deletion.

We will handle rights requests within the applicable legal time limits. You can also complain to the Spanish Data Protection Agency or your country's competent authority.

The app is not directed at children. Contact us if you believe we have improperly received a child's data. We will publish material policy changes on this page and update its date.