Privacy Policy for Audiobookly

Effective date: 7 August 2026
Last updated: 7 August 2026

This Privacy Policy explains how Audiobookly (“the app”) handles your information.

Audiobookly is an Android audiobook player published under the package name com.devmire.audiobookly.

Audiobookly is published by shreyas ubale , based in Bengaluru, Karnataka , India (“we”, “us”, or “our”).

For privacy-related questions, you can contact us at [CONTACT EMAIL].

At a Glance

Audiobookly is designed to be an offline-first audiobook player.

We do not operate an Audiobookly account server. Your audiobook library, listening positions, bookmarks, notes, and most app data remain on your device.
We cannot see what you listen to. Audiobook titles, file names, folder paths, playback positions, bookmarks, and notes are not sent to us.
Some features access the internet when needed, including connecting to your own Audiobookshelf server and looking up book metadata and cover artwork.
We may use Google Analytics for Firebase to understand general app usage and diagnose problems. Analytics does not receive the contents of your audiobook library.
Paid features may be offered through Google Play Billing. Payment information is processed by Google, and we do not receive your credit card or banking details.
Audiobookly contains no advertising or advertising SDKs.

1. Information Stored on Your Device

Audiobookly is an offline-first audiobook player.

The following information may be created and stored locally within the app’s private storage:

Your Library

This may include:

Book titles
Authors
Series information
Narrators
Durations
Chapters
Cover images
File paths for audiobooks you add

Listening Information

This may include:

Playback positions
Playback speed
Sleep timer settings
Finished or unfinished status
Listening history

Information You Create

This may include:

Bookmarks
Character notes
Custom chapter markers
Metadata you manually edit

App Preferences

This may include:

Theme preferences
Sorting options
Grouping preferences
Skip intervals
Other app settings

Cached Content

Audiobookly may cache cover artwork downloaded for books in your library.

This locally stored information is generally removed when you uninstall Audiobookly or clear the app’s storage through Android Settings.

Your audiobook audio files are never uploaded to us.

Audiobookly reads audiobook files from folders to which you explicitly grant access and plays those files directly from your device.

Optional Metadata Write-Back

If you enable metadata write-back, Audiobookly may modify metadata tags contained within audiobook files stored on your device.

This operation occurs locally on your device. The files or modified metadata are not sent to us as part of this feature.

2. Audiobookshelf Integration

Audiobookly can connect to an Audiobookshelf server that you choose and control.

We do not operate your Audiobookshelf server and do not receive the data exchanged between Audiobookly and that server.

When you connect an Audiobookshelf server:

You provide the server address and your username and password.
Your credentials are used to obtain an access token from your Audiobookshelf server.
The access token is stored securely using expo-secure-store, which is backed by the Android Keystore.
Your password itself is not retained after the access token has been obtained.

When synchronizing with your Audiobookshelf server, the app may exchange:

Book identifiers
Listening positions
Playback timestamps
A device identifier
A device label

The device information allows your Audiobookshelf server to distinguish between devices, including when handling synchronization conflicts.

Audiobook cover artwork and audio streamed or downloaded from Audiobookshelf are transferred directly between your Audiobookshelf server and your device.

The privacy and data-handling practices of an Audiobookshelf server are controlled by whoever operates that server.

In most cases, that will be you or an administrator you trust.

Disconnecting an Audiobookshelf server from the app removes its stored access token from your device.

3. Book Metadata and Cover Lookups

Audiobookly can use third-party book catalogues to find missing information such as:

Book titles
Authors
Narrators
Series information
Cover artwork

These lookups may occur when you add a book or manually request a metadata refresh.

Audiobookly may query the following services:

Service	Provider
Audnexus	Audnexus Project
Audible Catalogue API	Amazon
Open Library	Internet Archive
Google Books	Google

When a metadata lookup is performed, these services may receive the search text used for the lookup, typically a book title and author obtained from the audiobook’s metadata or folder name.

As with normal internet communication, these services may also receive:

Your IP address
Browser/network protocol information
Other standard information included with an internet request

These services do not receive from Audiobookly:

Your complete audiobook library
Listening positions
File paths
Bookmarks
Notes
An Audiobookly user account identifier

These services are independently operated and maintain their own privacy policies.

We do not control their data-handling practices.

4. Usage Analytics

Audiobookly may use Google Analytics for Firebase to understand how the app is being used, identify errors, and determine which features should be improved.

Firebase Analytics may collect information such as:

App Instance Identifier

Firebase may assign a pseudonymous identifier to an installation of Audiobookly.

This identifier is not your name or email address.

Device and Environment Information

This may include:

Device model
Android version
Audiobookly app version
Language
Approximate country-level location derived from your IP address

Usage Events

We may collect general information about how features are used.

Examples include whether:

A library scan was performed
A particular screen was opened
An Audiobookshelf server was connected
A particular app feature was used

Crash and Error Information

Diagnostic information may be collected to help identify crashes and software problems.

What Analytics Does Not Receive

We do not intentionally send the following information to Firebase Analytics:

Audiobook titles
Author names
File names
Folder paths
Listening positions
Bookmarks
Notes
Audiobookshelf server addresses
Audiobookshelf usernames or passwords

Google processes analytics information according to Google’s own privacy policies and terms.

If Audiobookly includes a Share Usage Data option under Settings → Privacy, disabling that option stops further optional analytics collection from the device.

Clearing Audiobookly’s application storage or reinstalling the app may also reset identifiers associated with the installation.

5. Purchases and Google Play Billing

Audiobookly may offer certain features through a one-time purchase using Google Play Billing.

Payments are handled by Google.

We do not receive or store:

Credit or debit card numbers
Bank details
Payment credentials
Billing addresses
Other payment instruments

Google Play may provide the app with information such as a purchase token or order identifier so Audiobookly can verify that you are entitled to purchased features.

Your entitlement may be associated with your Google account so that eligible purchases can be restored after reinstalling the app or moving to another device.

Refunds, receipts, billing records, and purchase histories are managed by Google Play according to Google’s applicable terms.

We do not use purchase information for advertising and do not sell purchase information.

6. Android Permissions

Audiobookly may request certain Android permissions depending on the features you use.

Internet Access

Used for:

Connecting to your Audiobookshelf server
Book metadata searches
Cover artwork downloads
Analytics, where enabled
Google Play Billing

Storage and Folder Access

Used to read audiobook folders that you explicitly choose.

If you enable metadata write-back, Audiobookly may also use this access to update metadata in audiobook files.

Access is limited to locations you authorize through Android.

Vibration

Used to provide optional haptic feedback when interacting with app controls.

Notifications and Media Controls

Used to display audiobook playback controls in areas such as:

The Android notification panel
Lock screen
System media controls

Audiobookly does not require access to your:

Contacts
Camera
Microphone
Precise location
SMS messages
Call logs
Health data

7. Advertising

Audiobookly does not contain advertising.

The app does not include advertising SDKs.

We do not sell your personal information for advertising purposes.

We also do not share your personal information for cross-context behavioural advertising.

8. Sharing of Information

We do not sell your personal information.

We also do not share your information with third parties for their own marketing purposes.

Information may reach third parties only when required by features you choose to use.

These include:

Your Audiobookshelf server when you configure Audiobookshelf integration
Book metadata providers when Audiobookly performs a metadata lookup
Google, where Firebase Analytics or Google Play Billing is used

We may also disclose information where required by applicable law or where reasonably necessary to establish, exercise, or defend legal claims.

9. Data Retention

Information Stored on Your Device

Information stored locally remains on your device until you:

Delete it through Audiobookly
Clear Audiobookly’s app storage
Uninstall Audiobookly

Because we do not maintain a server-side copy of this information, we generally cannot restore or remotely delete it for you.

Analytics Information

Analytics information is retained by Google according to the retention settings configured for the Firebase project and Google’s applicable policies.

Purchase Information

Purchase and transaction records may be retained by Google Play as required for purposes including:

Processing purchases
Restoring purchases
Refunds
Tax requirements
Accounting obligations
Fraud prevention

10. Security

Audiobookly takes reasonable measures to protect information handled by the app.

Audiobookshelf access tokens are stored using expo-secure-store, backed by the Android Keystore, instead of being stored as plain text in normal application storage.

Connections to supported internet metadata providers use HTTPS.

The security of connections to your personal Audiobookshelf server depends on how you configure that server.

For example, if you configure Audiobookly to connect to an http:// address on your local network instead of an https:// address, traffic to that server may not be encrypted.

No electronic storage or transmission method can be guaranteed to be completely secure.

11. Children’s Privacy

Audiobookly is not specifically directed at children under the age of 13, or the equivalent minimum age required by applicable law in your country.

We do not knowingly collect personal information from children.

If you believe that a child has provided personal information through Audiobookly in a way covered by this Privacy Policy, please contact us at [CONTACT EMAIL].

12. Your Privacy Rights

Depending on where you live, applicable privacy laws may give you rights concerning your personal information.

These may include the right to:

Access your personal information
Correct inaccurate information
Request deletion
Obtain a copy or export of your information
Restrict certain processing
Object to certain processing
Withdraw consent where processing relies on consent
Lodge a complaint with an appropriate data protection authority

Because most Audiobookly information remains exclusively on your device, you can exercise many of these rights directly by editing or deleting information within the app.

You can also clear Audiobookly’s storage or uninstall the app to remove locally stored Audiobookly data.

For pseudonymous analytics information, you may contact us at [CONTACT EMAIL].

Because analytics information is not directly associated with your name or email address, we may require an app instance identifier or similar information to identify the relevant records.

UK and European Economic Area

Where the UK GDPR or EU GDPR applies, depending on the particular processing activity, our legal bases may include:

Contract — where processing is necessary to provide app functionality or purchased features
Legitimate interests — where necessary to maintain, protect, diagnose, and improve the app
Consent — where required for optional analytics or similar processing

California

We do not sell personal information or share personal information for cross-context behavioural advertising as those terms are defined under applicable California privacy laws, including the CCPA/CPRA.

13. International Data Transfers

Third-party services such as Google’s analytics and billing infrastructure may process information in countries other than your own, including the United States.

Google maintains safeguards for international data transfers where applicable.

Traffic sent to an Audiobookshelf server is transmitted to wherever the server you configured is hosted.

Because we do not operate your Audiobookshelf server, we do not determine the location where that server stores or processes information.

14. Changes to This Privacy Policy

We may update this Privacy Policy from time to time to reflect:

Changes to Audiobookly
New or modified features
Changes in third-party services
Legal or regulatory requirements

When the policy changes, the Last updated date at the top of this page will be revised.

For significant changes, we may also provide notice within Audiobookly or through its Google Play listing where appropriate.

15. Contact Us

If you have questions, privacy requests, or complaints regarding Audiobookly or this Privacy Policy, contact:

Shreyas ubale
Bengaluru, Karnataka , India

Email: shreyasubale@gmail.com

App: Audiobookly
Android package: com.devmire.audiobookly