Queue privacy policy
Effective 2026-07-31
Queue is a music player. It does not require an account, does not run ads, and does not include analytics or crash-reporting SDKs — no usage data is collected or transmitted anywhere.
This policy explains what data Queue handles, where it's stored, and who it's shared with.
Data stored on your device
If you connect a Jellyfin, Plex, Emby, or Navidrome server, Queue stores the server address, your username, and your password or access token in Android's EncryptedSharedPreferences (AES-256), a secure, app-private storage area on your device. This data is excluded from Android's automatic backup and is never transmitted anywhere except to the server you configured.
Non-sensitive app settings — such as which library is active, sync preferences, and Wi-Fi-only sync settings — are stored in ordinary app preferences on your device.
None of this data leaves your device except as described below, and all of it is deleted when you uninstall Queue or clear its app data.
Network connections Queue makes
Media servers you configure: when you add a Jellyfin, Plex, Emby, or Navidrome server, Queue connects directly to the address you provide to browse and stream your library. Queue has no visibility into or control over how that server handles your data — refer to that server's own privacy practices.
Plex sign-in: if you sign into Plex, Queue also authenticates through Plex's official plex.tv API, governed by Plex's privacy policy.
Casting: when you cast to a Chromecast device, Queue streams media directly to that device over your local network, and uses Google's Cast SDK (part of Google Play Services) to discover and connect to it. Data handled by Google Play Services is governed by Google's privacy policy.
Support links: tapping "Report Bug", "Request Feature", "Discussions", or "Docs" in Settings opens your browser to this site (no-nonsenselabs.com/queue). The bug-report link includes your app version and Android version/device model in the URL so it's pre-filled for you — this only happens when you tap the link, and only reaches this website, which is covered by its own terms as a public bug/feature tracker.
Queue makes no other network requests. There is no analytics, telemetry, or remote-configuration endpoint of any kind.
Permissions Queue requests
Media/storage access — to read the music files on your device.
Notifications and foreground service — to show playback controls and keep music playing in the background.
Bluetooth — to detect connect/disconnect events for per-device playback and equalizer behavior.
Internet and network state — to reach the media servers you configure and to cast to Chromecast devices.
Wi-Fi state — to read your current network's name (SSID) so you can restrict library syncing to a specific Wi-Fi network. This is only used for that feature, never for location tracking.
Microphone (RECORD_AUDIO) — Android requires this permission for the system Visualizer API that powers the equalizer's live output waveform. Queue does not record or transmit audio from your microphone.
Other permissions (wake lock, vibrate, boot, audio settings) support normal playback functionality and are not related to data collection.
What Queue does not do
Queue does not collect analytics or usage statistics, does not include crash-reporting SDKs, does not show ads, does not sell or share your data with third parties, and does not require or use any account of its own.
Children's privacy
Queue is not directed at children and does not knowingly collect personal information from anyone.
Data deletion
Because everything Queue stores lives on your device, you can remove it at any time by disconnecting a server in Settings, clearing the app's data, or uninstalling Queue.
Changes to this policy
If this policy changes, the effective date above will be updated. Material changes will be reflected in the app's changelog.
Contact
Questions or requests about this policy can be sent to support@no-nonsenselabs.com, or raised in Queue's Discussions or Bugs sections on this site.