Privacy Policy

No JellyPlayer account

JellyPlayer does not require a JellyPlayer account. We do not ask you to create a profile, and we do not run an account system for watching or managing your playlists.

App data stays on your device

Playlists, saved lists, watch progress and settings are stored locally by the TV, desktop and web players; offline downloads are a desktop feature. In the web player, local data belongs to that browser. There is no JellyPlayer cloud library or cross-device sync. Clearing app or browser data can remove locally stored information.

If you add a remote playlist URL or sign in to an external Xtream Codes provider, the app connects to the servers you choose so it can load the content from that provider. Those provider services are separate from JellyPlayer and have their own privacy practices.

No advertising trackers

JellyPlayer does not include advertising trackers. Usage analytics described below helps us understand which apps and features are useful. We do not sell personal data.

Usage analytics and your choice

JellyPlayer uses Rybbit, hosted at analytics.jellyplayer.net. On the website and browser player, it measures general page visits, download-button clicks, app activity, successful playlist setup, playback attempts, success or failure and time actually playing. It records broad content types, not what you watch. Desktop and TV versions that include a Usage analytics setting also report their platform, operating-system version, app version, general screens and first observed launch. Older native versions without this setting do not send these events. Browser events may include the interface language and the public release article being visited. When you open the website from the browser player's app link, a broad source marker can connect that visit with download clicks for up to 30 minutes in the same browser tab.

Usage analytics is enabled by default. Turn it off using Usage analytics in the website footer, the browser player's profile menu under Privacy, desktop Settings, or TV Settings → General. The preference applies to that app or browser; changing it on one device does not change other devices. Turning it off stops future events. Clearing local data resets the preference.

A random identifier stored locally lets Rybbit recognise the same app installation or browser over time. It is not your name, email address, provider account or hardware ID. Reinstalling or clearing local data can create a new identifier. A first observed launch may come from an existing installation after an update; it is not proof of a new install.

Events do not include playlist or provider URLs, credentials, search terms, content titles, viewing history, form entries or raw error reports. Session replay and automatic form, clipboard and button recording are disabled. Rybbit may derive approximate location and device information from network requests; storing raw IP addresses in Rybbit is disabled. The hosting logs described below are separate. Analytics is disabled on the TV pairing and Support pages.

Website hosting logs

Like most websites, jellyplayer.net may be served through hosting and infrastructure providers that process standard technical logs, such as IP address, browser user agent, requested URL, timestamp, and error information. These logs are used for security, debugging, and keeping the site available.

Encrypted TV pairing

When you use your phone to pair a TV, the browser encrypts your playlist name and provider details for the TV before sending them. The relay stores the encrypted payload temporarily, not public plaintext credentials. The TV holds the private key needed to decrypt it. Sessions expire after 10 minutes and are removed when the TV collects the payload. This transfer is not an account or a sync service.

The relay also processes the pairing code, public key and technical request information needed to route and protect the transfer. Keep the code private. Once imported, the TV stores your playlist locally and connects to your chosen provider.

Support reports and reply contact

Support shows the reporting form’s current availability. When enabled, submitting the form sends your chosen category, platform, summary, details and any reply contact you provide to the support team’s private Telegram chat through an internal bot, not the public community group. You do not need a Telegram account or to open or contact a bot. Do not include passwords, provider or playlist URLs, payment details, or other secrets.

Basic diagnostics are optional, displayed for review and sent only if you opt in. The allowed fields are app version, OS version, device model, playback engine, stream type, playlist type, a safe error code and library counts. We do not automatically attach raw logs, content names, local paths or playlist credentials.

If you want a reply, provide an email address or, optionally, a Telegram username. Staff can use that contact to follow up; the form does not send automated email replies. You can also submit without reply contact. Telegram processes the report and supplied contact information under its own privacy policy because it is used for internal delivery to staff. This is not an end-to-end encrypted Telegram Secret Chat.

For questions about a report or deletion, use Support and quote the report ID if available. Posts you make in the community group are visible to that group, unlike private support reports.

Downloads and updates

When you download an app build or check for updates, your device may request files from the hosting location used for JellyPlayer releases. Those requests can create normal server logs at the hosting provider.

Changes

This privacy policy may be updated as JellyPlayer evolves. The date at the top of this page shows when the current version was last updated.