Privacy without an asterisk.
Olive Remote controls your music library locally without accounts, analytics, advertising, or a cloud music library. Optional internet radio uses the external services described below.
What we collect, use, share, retain, and protect
Olive Remote does not operate a service that collects your music library, private device addresses, or local playback activity. These data remain on the device running the app and the compatible Olive music server on your private local network. The app does not create an account or use analytics, advertising, cloud music storage, or a remote relay. Optional internet radio sends search requests to a station directory and connects your Olive to a station provider, as explained below.
If you voluntarily contact support, we collect only the information you enter in the form, such as your reply email address, message, and any optional device or compatibility details. We use it only to answer the request or provide the separately opted-in compatibility or availability follow-up you requested. We do not sell this information or share it for advertising. The support request is delivered to our private support mailbox and is not stored in an Olive Remote application database. You may request deletion by contacting support. We protect support submissions in transit with HTTPS and restrict them to the support workflow described below.
Optional internet radio
When you choose Find stations, the app sends the station name, country, and genre filters you enter to Radio Browser over HTTPS. The directory receives your public IP address and ordinary connection metadata needed to answer the request. These searches are user-initiated; your local music library and private Olive address are not included. The app does not send account credentials, cookies, or a browser referrer with these requests. Learn about the directory at Radio Browser.
When you play a station on a compatible Olive, the app sends the stream address to that Olive over your local network. The Olive then connects to the station provider, which receives its public IP address and stream request. Some station streams use unencrypted HTTP; others use HTTPS. Radio Browser and station providers control their own server logs and retention, which Olive Remote does not manage. Olive Remote does not receive or retain your radio searches or listening history on its servers.
Radio favorites are stored locally until you remove them, clear app data, or uninstall the app. You can use local-library features without searching for or playing internet radio. Requests about data retained by a directory or station provider must be directed to that provider.
iOS, Android, and local web applications
Device addresses, discovered service descriptions, request history, protocol logs, settings, and music metadata remain on the phone, tablet, or computer running the application. Native device backup is disabled on Android. The software communicates with private-network music servers selected or discovered by the user.
Public website
The public website contains no analytics SDK, sign-in system, advertising network, cookies, or cross-site tracking. Firebase Hosting necessarily processes ordinary web-server connection data such as IP address and request metadata to deliver the site.
Submission source labels
Some help links contain a predefined source code, such as the name of a public help page or community. During ordinary browsing, the page keeps that code only in the current URL and tagged links; it does not copy it into cookies or browser storage. Like any requested URL, it may appear in ordinary Firebase Hosting request metadata. If you submit the diagnostic form, the code is included with that request so Olive Remote can understand which public resource led to a useful support conversation. The site code does not read raw browser referrers or include them, usernames, profile identifiers, or arbitrary campaign parameters in the diagnostic; ordinary Firebase delivery logs may still contain incoming request-referrer metadata under Firebase’s own logging policies.
Diagnostics
Diagnostics are exported only when the user chooses to create a local JSON file. The exporter redacts likely library names and personally identifying fields. Users should review exported files before sharing them.
Private support and owner diagnostics
The optional support form asks for a reply email address and message, plus optional name and device details. The owner diagnostic asks for model, optional firmware, startup and network state, main problem, country, reply email, and the description you choose to provide. Do not submit IP addresses, serial numbers, credentials, music titles, playlist names, or library metadata. A Firebase Function processes the submission only to deliver it to the private support mailbox through Google’s email service. Olive Remote does not store these requests in an application database. For abuse prevention, the function holds a one-way address hash in short-lived instance memory to enforce an hourly rate limit; it is not placed in the message or an application database. Email providers retain delivered messages under their own policies, and ordinary technical request metadata may appear temporarily in service logs for security and reliability.
Consent and deletion
Reply consent is required and authorizes use of the submitted details only to assess and answer that request. A separate, unchecked option may authorize one email when relevant compatibility testing or store availability opens for that model. It is not a general marketing subscription. You can withdraw that optional permission or request deletion from the support mailbox by submitting a support request from this site.
Third parties and trademarks
Users may alternatively open an issue on GitHub; public issue content is governed by GitHub’s terms and privacy policy. The public information site and support endpoint are delivered by Firebase. This independent project is not affiliated with or endorsed by the original hardware manufacturer. Product names are used only to describe compatibility.
Changes
Material changes to this notice will be published here and in the public source repository.