Privacy Policy

Last updated: November 2, 2026

The short version: Wristory does not sell your data, show ads, or use analytics. It talks to the Audiobookshelf server you set up and control yourself. The only information that reaches the developer is crash reports, which are described below.

Wristory ("the app", formerly called ABShelf) is an unofficial Wear OS client for self-hosted Audiobookshelf servers. This policy also covers its companion phone app, which shares this app's Google Play listing.

What the app stores, and where

On your watch, only:

• The server address (plus any home network addresses you add), username, and an authentication token for the Audiobookshelf server you connect to. The token is encrypted (AES-256, via Android's own hardware-backed Keystore) before it is written to disk, and is never stored in plain text.

• Your password is sent once, directly to your own server, to sign in. The app does not store your password.

• Audiobooks and podcast episodes you choose to download for offline listening (and, if you turn on Download next in series, the next book in a series you're listening to), along with their cover images.

• Your listening position, and which book or episode you listened to most recently (its title and how far through you are), so the app can offer to continue it.

• Bookmarks you add (a position and a name), kept on the watch until they are synced with your server.

• Playback settings and preferences (Wi-Fi-only options, playback speed, smart rewind, and similar).

If you add the Continue Listening tile or the watch-face shortcut, they display the title and progress of what you were last listening to on your watch face. They read this from your watch only, and you choose whether to add them.

None of this leaves your watch except to communicate with your own Audiobookshelf server, as described below.

Sent to your Audiobookshelf server (the one you configure yourself, not a server operated by this app's developer):

• Your login credentials, to authenticate you.

• Listening progress (playback position, and whether you've finished a book) and listening sessions (how long you listened, including offline listening, sent once you're back online), so your place and listening history stay in sync across your devices.

• Bookmarks you add or delete (a position and a name; books only).

• A device identifier (Android's standard per-device ID), used the way any Audiobookshelf client uses one: to tell playback sessions from your different devices apart on your own server.

This is the information any Audiobookshelf client needs to exchange with your server in order to work. The developer of this app does not receive any of it.

Signing in with SSO

If your server has single sign-on configured, signing in opens your identity provider's page in your paired phone's browser. That exchange happens between your phone, your identity provider, and your own server. This app is not a party to it and does not see your SSO credentials.

Crash reports

To find and fix bugs, the app uses Firebase Crashlytics, a crash-reporting service from Google. When the app crashes or hits a serious error, a report is sent to the developer through Firebase. A report can include:

• A technical trace showing where in the app the problem happened.

• The app version, your watch's model, and its Android (Wear OS) version, plus general device state at that moment, such as available memory.

• Random identifiers that Firebase creates for this installation of the app (a Crashlytics installation ID and a Firebase installation ID). They are not tied to your name, email address, or any account, and the app does not attach a user ID to reports.

• Short technical log messages the app records about what it was doing just before the problem (for example, that a download started or a sync failed). Authentication tokens are removed from these messages before they are sent.

• Error text from the failure itself. If the problem was a failed network connection, this text can include the address of the server that could not be reached.

Crash reports are used only to fix bugs. They are not used for advertising, and the app does not include Google Analytics or any other analytics. Google keeps Crashlytics crash data for 90 days before it begins removing it, and handles it under its own terms: https://firebase.google.com/support/privacy

There is no setting in the app to switch crash reporting off.

What this app doesn't do

• It doesn't run any servers that receive your listening data, credentials, or library. There is no backend operated by the developer.

• It doesn't use analytics or advertising SDKs. The only third-party service it includes is Google's Crashlytics, described above.

• It doesn't sell, rent, or share your information with third parties. Apart from crash reports, no information reaches the developer or anyone else.

• It doesn't track you across other apps or websites.

Permissions

The app requests only the Android permissions it needs to function:

• Network access, and permission to check the type of network and request a Wi-Fi connection: to reach your server, and so downloads can use Wi-Fi rather than the slower Bluetooth link through your phone.

• Notifications: for download progress and completion alerts, which can be turned off any time from within the app's own Settings.

• Foreground service and wake-lock permissions: so playback and downloads can continue while the screen is off.

None of these are used to collect information about you.

Data retention and deletion

Everything the app stores lives on your watch and is removed when you uninstall the app or clear its storage. Signing out deletes your authentication token right away; the server address and username are kept so the sign-in screen can fill them in again. Downloads stay until you delete them from within the app. Anything held on your Audiobookshelf server, such as listening progress and bookmarks, is managed through that server, which you control. Crash reports are kept by Google for 90 days, as described above, and are not linked to your identity.

Children's privacy

This app is not directed at children and does not knowingly collect information from anyone, of any age, beyond what is described above.

Changes to this policy

If this policy changes, the updated version will be posted at this same address with a new "Last updated" date above.

Contact

Questions about this policy can be sent to: contactclsstudio@gmail.com

Wristory is an independent, unofficial project and is not affiliated with or endorsed by the Audiobookshelf project.