Legal

Privacy Policy

Effective Date: June 28, 2026  ยท  Last Updated: June 28, 2026

The short version: EarMuse doesn't collect any personal data or phone home to its developer. No analytics, no crash reports, no tracking, no accounts. EarMuse talks only to the Audiobookshelf server you configure. Your server address, username, and login tokens are stored securely on your device and sent only to your server. Your library and listening progress are cached on your device and synced through your server. Optional iCloud is used solely to keep your play queue in sync across your own Apple devices.

Overview

EarMuse ("the App") is a native macOS, iOS, iPadOS, and tvOS client for Audiobookshelf, an open-source, self-hosted audiobook and podcast server. EarMuse is an independent app and is not affiliated with, endorsed by, or sponsored by the Audiobookshelf project. This privacy policy describes how the App handles information.

Information We Collect

EarMuse does not collect any personal information. The App does not:

Your Audiobookshelf Server

EarMuse is a client for a server that you provide. To use the App, you enter your Audiobookshelf server's web address and sign in with your own credentials for that server. From that point on:

Because EarMuse talks to a server you control, how that server collects, stores, and processes data is governed by that server and its operator, not by the App developer.

Data Storage

To work quickly and offline, EarMuse caches your library locally on your Device in an on-device database: items, metadata, cover art, listening progress, bookmarks, playlists, and preferences. Audiobooks and podcasts you choose to download are stored as files on your Device so they play without a connection. This local data stays on your Device and is removed when you delete a download, sign out, switch accounts, or delete the App.

Listening Progress & Offline Changes

Your listening position and related progress are reported to your Audiobookshelf server, which is the system of record. When you listen offline, EarMuse records your progress locally and reconciles it with your server automatically when a connection returns. None of this progress is sent to the App developer.

iCloud Sync (Play Queue)

EarMuse uses Apple's iCloud key-value store for a single purpose: keeping your "Up Next" play queue in sync across your own Apple devices. The queue is scoped to your specific server and user, stored in your private iCloud account in accordance with Apple's Privacy Policy, and is not accessible to the App developer. Your listening progress itself syncs through your Audiobookshelf server, not through iCloud. If you disable iCloud or turn off queue sync, EarMuse continues to work using your server and local data.

Apple TV Pairing

To sign in on Apple TV without retyping your password, EarMuse can transfer your server credentials from your iPhone to your Apple TV over your local network. This transfer is end-to-end encrypted: the Apple TV generates an ephemeral key pair, your phone performs a key exchange and seals the credentials so that only that Apple TV can open them, and the Apple TV's private key never leaves the device. The Apple TV then signs in to your server with its own independent tokens. No pairing data is sent over the internet or to the App developer.

Podcast Discovery

If you browse podcast discovery charts, EarMuse fetches public chart data and artwork from Apple's podcast directory. These requests contain only what is needed to display and look up charts. They do not include your name, your server, account identifiers, or any other personal identity. Returned artwork is cached locally on your Device.

Third-Party Services

EarMuse does not integrate with any advertising networks, analytics platforms, or crash reporters. The only external systems the App communicates with are: your own Audiobookshelf server (for everything related to your library), Apple's iCloud (used solely for the optional private play-queue sync described above), and, if you use podcast discovery, Apple's public podcast charts. Each of these has its own privacy practices, which apply when your device communicates with them.

Children's Privacy

EarMuse does not knowingly collect any information from anyone, including children under the age of 13.

Changes to This Policy

If this privacy policy changes in a future version of the App, the updated policy will be published at this URL and the "Last Updated" date above will be revised. Continued use of the App after any changes constitutes acceptance of the updated policy.

Contact

Questions, issues, and feature requests are tracked publicly at the project's GitHub repository.