Juicy Remoter — Privacy Policy
Last updated: September 14, 2026
This Privacy Policy describes how Juicy Remoter (the "App") handles information. The short version: the App has no developer-operated backend, no accounts, no analytics, and no advertising. It communicates only with the JuicyPlayer server that you choose to connect it to, and it stores your settings locally on your device.
By using the App, you agree to this policy. If you do not agree, please do not use the App.
1. Overview
Juicy Remoter is a remote control client for JuicyPlayer, a self-hosted music player server. The App acts purely as a client:
- It does not collect, transmit, or sell any personal data to the developer or any third party.
- It contains no analytics SDKs, tracking libraries, crash-reporting services, or advertisements.
- All network traffic goes directly between your device and the JuicyPlayer server you configure (which may be running on your own computer or a server you control).
2. Data Stored on Your Device (Local Only)
The App stores the following information locally on your device only. This data never leaves your device except as described in Section 3, and you can remove it at any time by uninstalling the App or clearing its data.
| Data | Purpose |
|---|---|
| Server address and port | To reconnect to your JuicyPlayer server |
| Playback target preference | To remember whether playback is routed to the server or local output |
| Theme, language, and interface preferences | To restore your UI settings |
| Recent searches | To speed up repeated searches in your library |
| Library and album art caches | To display your library quickly and reduce network requests (library cache expires automatically after ~2 hours) |
| Queue and playback state | To restore your session |
The App does not store payment information, contacts, photos, location, or any identity documents.
3. Network Communication
All network communication is initiated by the App and directed at your own JuicyPlayer server or your local network:
- mDNS / Bonjour discovery — the App broadcasts a local discovery query (
_juicyplayer._tcp) on your LAN to find JuicyPlayer servers automatically. This traffic stays within your local network. - HTTP / HTTPS — used to browse your library, fetch album art, query playback state, and send control commands to your server.
- WebSocket — used for live "now playing" state updates from your server.
- OSC over UDP — used for low-latency playback commands (play/pause, seek, volume) to your server.
- Audio streaming — if you enable local playback, audio is streamed from your server to your device.
The App connects only to server addresses you enter or discover on your network. It never sends your data to any server operated by the developer.
4. Web Version
If you use the browser (web) build of the App, it is self-hosted: it is served either by your own JuicyPlayer server or from a location you control. The web build behaves the same as the native apps — it stores settings in your browser's local storage and communicates only with the server it was served from (or the server you explicitly configure). The developer does not host the web build and receives no data from it.
5. Permissions
The App requests only the permissions it needs to function:
- Network access — required to communicate with your JuicyPlayer server (all platforms).
- Local network — required for mDNS discovery and LAN communication (iOS, macOS, Android).
- Media / audio playback — required for local playback and the system media notification/controls (mobile and desktop).
- Notifications — optional; used for media playback controls and (if enabled) sleep-timer reminders.
Granting or denying a permission is under your control in your device's system settings. The App functions as a pure remote (server playback) without media permissions.
6. Third-Party Services
The App does not use any third-party analytics, advertising, crash-reporting, or data-broker services. There are no SDKs in the App that transmit data to third parties.
Note that this policy covers only the App. Your JuicyPlayer server is software you host yourself; how it handles data on its side (e.g., server logs) is governed by your own configuration and this policy does not apply to it.
7. Children's Privacy
The App does not knowingly collect any personal information from anyone, including children under 13 (or the equivalent minimum age in your jurisdiction). Since the App collects no personal data at all, no data about children is collected, used, or shared.
8. Data Security
All communication with your server occurs on infrastructure you control (typically your home LAN). The App applies the same protections as your server's configuration allows; if your server is exposed to the public internet, its security depends on your own setup and is outside the scope of this policy.
9. Your Rights and Choices
Because the developer never receives your data, there is nothing to access, correct, export, or delete on our side. You remain in full control:
- Delete local data — clear the App's data in your system settings, use in-app options (e.g., clear search history), or uninstall the App. All local data is removed with it.
- Web build — clear your browser's site data / local storage for the App's origin.
10. Changes to This Policy
We may update this policy as the App evolves. The "Last updated" date at the top will change whenever the policy is revised. Material changes will be reflected in the App's documentation or release notes.
11. Contact
If you have questions about this policy, please open an issue on the project's repository or contact the developer at hifior@foxmail.com.