JellyMusic

Privacy Policy

Effective: June 2026 Developer: Kamil Marczak Version 1.0
TL;DR

JellyMusic connects only to the Jellyfin server you provide. It collects no data on its own, sends nothing to external servers, and stores your credentials only on your device. Your music, your server, your data.

1. Overview

JellyMusic is a music player application that connects to your self-hosted Jellyfin media server — giving you a dedicated interface for browsing and playing your personal music library. It also supports casting playback to Google Cast-enabled devices such as Chromecast and Android TV.

This policy describes what data JellyMusic processes, why, and where it goes.

2. Data processed

JellyMusic processes the following categories of data, all of which originate from you and your own Jellyfin server:

  • Jellyfin server address — the URL you enter to connect to your server. Stored locally on your device so you don't have to re-enter it.
  • Jellyfin credentials — your username and password, used once to authenticate with your server and obtain a session token. The token is stored locally on your device; raw credentials are not persisted after login.
  • Session token — a temporary access token issued by your Jellyfin server after login, used to authenticate all subsequent API requests. Stored locally on your device.
  • Library content — track titles, artists, albums, and album artwork fetched from your Jellyfin server for browsing and playback. Loaded on demand and not cached to any external location.
  • Playback progress & history — current playback position and completion events, reported back to your Jellyfin server to update play counts and listening history. This data is stored on your server, not by JellyMusic.

3. How data is used

All data listed above is used exclusively for the following purposes:

  • Authenticating with your Jellyfin server and maintaining your session.
  • Fetching and displaying your music library for browsing and playback.
  • Reporting playback progress to your Jellyfin server to keep listening stats accurate.
  • Enabling Cast sessions by passing your server address and token to the Cast receiver running on your TV.

4. Data storage & transmission

No data leaves your infrastructure.

JellyMusic operates no backend, database, analytics service, or cloud of its own. All network communication is between the app and the Jellyfin server URL you provide — a server you own and control. Your credentials and session token are stored locally on your device using the platform's secure storage. Nothing is transmitted to the developer, advertisers, analytics platforms, or any third party.

5. Google Cast

When you cast music to a TV or speaker, JellyMusic passes your Jellyfin server address, session token, and track metadata to the JellyMusic Cast receiver running on that device. This communication happens over your local network via the standard Cast protocol. No Cast session data is transmitted outside your network or stored by the developer.

The Cast receiver loads the Google Cast Application Framework SDK from www.gstatic.com. See Google's Privacy Policy for how Google handles Cast-related telemetry.

6. Third-party services

JellyMusic does not integrate any third-party analytics, crash reporting, advertising, or tracking SDKs. The only external dependency is the Google Cast SDK, covered above.

7. Children's privacy

JellyMusic is not directed at children under 13. The application collects no personal data independently of your Jellyfin server, and does not knowingly process data relating to children.

8. Changes to this policy

If this policy is updated, the effective date at the top of this page will reflect the change. Material changes will be noted in the application's changelog. Continued use of JellyMusic after any update constitutes acceptance of the revised policy.

9. Contact

Questions about this policy or the application:

Kamil Marczak
me@kamilmarczak.pl
Wrocław, Poland