AudibounceThe developer of Audibounce collects nothing. Everything the app handles stays between the app and your own Audiobookshelf server.
What the developer collects
Nothing. Audibounce has no analytics, no crash-reporting service, no advertising, no tracking and no third-party SDKs. The developer never receives your library, your listening history, your credentials or anything else.
What the app handles, and where it goes
Audibounce talks to the Audiobookshelf server you enter, and nowhere else.
Signing in
Your server address and sign-in method are stored in the app's settings on your Mac. Access tokens (or your API key) are stored in your Mac's Keychain. If you use single sign-on, the sign-in page is shown by macOS and comes from the identity provider your server is set up with. Your password is sent only to your server or identity provider, and isn't stored.
Your library and listening
Book details, cover art and audio come from your server. Your listening position is sent to your server so you can continue on other devices. When you're offline, progress is kept on your Mac until it can be delivered.
Downloads
Books you download for offline listening are stored on your Mac, inside the app's own container. You can remove them in the app at any time.
Desktop widget
The app shares what's playing (title, progress and small cover images) with its own widget, through a container on your Mac that only Audibounce and its widget can read.
Your server
Your Audiobookshelf server is run by you, or by whoever operates it. Its own privacy practices apply to what's stored there.
Children
Audibounce doesn't knowingly collect information from anyone, including children.
Changes
If this policy changes, the new version will be posted here with a new effective date.
Contact
Questions about this policy: dev@n8er.app