The plain-language version
Privacy policy
Sliver is local-first by design. Your audiobook library and listening history stay on your devices. Sliver sends anonymous usage, crash, and performance reports to Google Firebase, and connected features share data only when you use them.
Effective date: 4 October 2026
About Sliver
Sliver is developed by Jakub Piasecki. For privacy questions, contact [email protected].
Local audiobook data
Sliver accesses only audiobook folders selected by the user through Android's system file picker. It reads audiobook files and metadata such as titles, authors, artwork, duration, and chapters.
Sliver stores its library index, playback progress, listening status, and settings on the user's device. The developer does not receive this information and does not operate a server containing users' audiobook libraries or listening histories.
Sliver does not require an account and does not contain advertising. The anonymous usage, crash, and performance reports Sliver sends are described below.
Google Cast
When the user starts casting, Sliver temporarily makes the selected audiobook and its artwork available to the chosen Cast receiver over the user's local network. Access uses randomized, session-specific addresses and ends when the Cast session stops. The audiobook is not sent to the Sliver developer.
The Google Cast SDK collects anonymous information about Cast discovery, sessions, mobile device information, and application configuration. Google uses this information in aggregate to operate and improve Cast. This information is encrypted in transit and is handled according to Google's privacy policy.
Wear OS
When requested by the user, Sliver transfers selected audiobook chapters, metadata, and playback progress between the user's phone and paired Wear OS watch using Google Play services. Transfers may use Bluetooth, Wi-Fi, or Google-operated infrastructure. Cloud transfers through the Wear OS Data Layer are end-to-end encrypted. The Sliver developer cannot access this information.
Analytics and diagnostics
Sliver uses Google Firebase Analytics, Firebase Crashlytics, and Firebase Performance Monitoring to understand how the app is used and to find crashes and slowdowns. These services collect which screens are opened, when a library scan, playback, Cast session, or watch transfer starts and how it ends, crash logs and stack traces, app start and network timings, device model and operating system version, app version, and device and app identifiers including an app instance identifier and the Android advertising ID.
Sliver never sends audiobook titles, authors, file names, folder locations, search text, or playback positions to these services. Reports describe counts, durations, and outcomes only, and cannot be used to identify which books a user listens to.
This information is sent to Google encrypted in transit and is processed on the developer's behalf under Google's privacy policy. It is not used for advertising. Users can reset or delete the Android advertising ID in the device's Google settings.
Device backups
Sliver excludes data stored by both the phone and Wear OS apps from Android cloud backup and device-to-device transfer. This keeps the local library index, settings, playback history and progress, and the watch's offline audiobook audio and fragment catalog from being copied through those Android services.
The original audiobook source files selected on the phone are outside Sliver's application storage. Whether those files are backed up or moved to another device is controlled by their storage provider and the user's system settings, not by Sliver.
Data sharing and sale
Sliver does not sell personal information and does not share personal information with advertisers. Sliver shares audiobook data or playback progress with other devices only when required for user-initiated Cast or Wear OS features. Google processes the anonymous Cast SDK and Firebase information described above as a service provider to the developer.
Retention and deletion
Local Sliver data remains on the applicable device until the user clears Sliver's application data or uninstalls the app. Audiobook chapters copied to a Wear OS watch remain there until deleted by the user or the watch application is uninstalled. Removing a library folder revokes Sliver's access to that folder but does not delete the original audiobook files.
Google retains Firebase Analytics data linked to an app instance for up to 14 months and Crashlytics and Performance Monitoring reports for 90 days. Google determines the retention of anonymous Cast SDK information under its own policies.
Security
Sliver uses Android's application storage and scoped file-access mechanisms. Wear OS cloud transfers are end-to-end encrypted, and reports sent to Firebase are encrypted in transit. Cast audiobook streaming occurs over the user's local network, so users should cast only on networks they trust.
Third-party services
Sliver uses Google Play services, Google Cast, Wear OS services, and Google Firebase. Read Google's Privacy Policy for information about Google's data practices.
Changes to this policy
This privacy policy may be updated when Sliver's features or data practices change. Updates will be published on this page with a revised effective date.