Audio Bible — Privacy Policy
Effective date: 23 August 2026 | Last updated: 23 August 2026
This policy explains how Audio Bible (package com.bible.speech, "the app") handles your data. Please read it before using the app.
1. Summary
The app has no account system. There is no sign-up, no sign-in, and you are never asked for your name, email address, phone number, or any other personal identifier. The full Bible text is bundled into the installation and is read aloud offline — what you read and listen to is never sent to any server.
The app is free and supported by advertising. Ads, basic usage statistics, and crash reporting are handled by third-party services from Google, which collect the limited data described in section 3.
2. Data we do not collect
We do not collect, request, or access:
- Your name, email address, phone number, or any directly identifying personal information
- Accounts, passwords, or login credentials
- Financial or payment information
- Contacts, call logs, SMS messages, or email content
- Photos, videos, audio files, or other files on your device
- Calendar data
- Health or fitness data
- Precise (GPS) location
- Microphone recordings. The app's read-aloud feature is text-to-speech: it produces sound, it does not record any.
3. Data collected through third-party services
The app operates no servers of its own and sends no data on its own behalf. The following is collected automatically by the Google software development kits (SDKs) bundled into it:
| Data type | What it is | Collected by | Purpose |
|---|---|---|---|
| Approximate location | Country/region-level location derived from your IP address. No GPS or precise positioning. | Google AdMob, Google Analytics for Firebase | Serving regionally relevant ads, aggregate usage statistics |
| App interactions | Screens opened, books and chapters selected, readings completed, idle events, ad impressions and clicks | Google AdMob, Google Analytics for Firebase | Understanding which features are used, serving and measuring ads |
| Crash logs | Stack traces, time of the crash, which Bible translation was active | Firebase Crashlytics | Fixing defects |
| Diagnostics | Device model, OS version, app version, language setting, non-fatal errors | Firebase Crashlytics, Google Analytics for Firebase | Fixing defects, verifying compatibility |
| Device or other IDs | Android Advertising ID (AAID), Firebase app instance ID, Crashlytics installation ID | Google AdMob, Google Analytics for Firebase, Firebase Crashlytics | Serving and measuring ads, ad fraud prevention, counting unique users |
This data is used in aggregated or pseudonymous form. It does not identify you to us as the developer, and we make no attempt to identify you from it. The advertising ID and related advertising data are shared with Google for advertising purposes. Crash and diagnostic data are used only for debugging and are not shared with or sold to any third party.
We do not sell your personal data.
4. Data that stays on your device
The following is stored locally in the app's Android preferences. It never leaves your phone and is never transmitted to us or to anyone else:
- Per-chapter reading bookmarks (the verse you last reached)
- Speech rate and pitch settings
- Font size and dark mode settings
- Selected Bible translation
- Playback preferences such as repeat-verse and loop-chapter
Uninstalling the app deletes all of it.
5. Text-to-speech
Reading aloud is performed by the text-to-speech engine installed on your device — usually Google Text-to-speech or one supplied by your device manufacturer. The app hands the verse text to that engine for playback. The engine is a separate application governed by its own privacy policy, and some engines synthesise speech in the cloud. You can see and change which engine is in use under Settings → System → Languages & input → Text-to-speech.
6. Third-party services and their policies
- Google AdMob (advertising) — policies.google.com/technologies/ads
- Google Analytics for Firebase (usage statistics) — firebase.google.com/support/privacy
- Firebase Crashlytics (crash reporting) — firebase.google.com/support/privacy
- Google Privacy Policy (general) — policies.google.com/privacy
- How Google uses data from partner sites and apps — policies.google.com/technologies/partner-sites
7. Advertising and your choices
Users in the European Economic Area, the United Kingdom, and Switzerland are shown a consent form the first time the app opens. It names the advertising partners and asks for your choice. No ad request is made before you have answered it. You can reopen that form and change your decision at any time under Settings → Privacy options.
All users can limit ad tracking:
- Reset your advertising ID, or turn off ad personalisation, under Settings → Google → Ads
- Delete your advertising ID entirely under Settings → Google → Ads (Android 12 and later), after which the app receives only non-personalised ads
You will still see ads with personalisation turned off; they simply will not be selected based on your interests.
8. Children
The app is not directed at children under 13, and we do not knowingly collect data from them. If you believe a child has provided data to us, please contact us at the address in section 12.
9. Data retention
Crash and diagnostic data are retained by Firebase Crashlytics for approximately 90 days. Aggregated usage statistics are retained by Google Analytics for its default retention period. Advertising identifiers are retained according to Google's advertising policies. Settings and bookmarks held on your device persist until you uninstall the app.
10. Your rights and data deletion
Because the app has no accounts, we hold no dataset that maps to you as an individual, so we cannot look up, export, or delete a specific user's data by name or account. You can exercise control in the following ways:
- Stop further collection: uninstall the app.
- Break the link to existing data: reset or delete your advertising ID in system settings; previously collected advertising data can no longer be associated with your device.
- Withdraw advertising consent (EEA, UK, Switzerland): change it under Settings → Privacy options.
- Exercise rights against Google: for data held by Google, follow the procedures set out in the Google Privacy Policy.
If you are in the EEA, the UK, Switzerland, California, or another jurisdiction that grants you rights of access, correction, or deletion, you may still write to us at the address in section 12 and we will help to the extent the law requires.
11. International data transfers
The Google services used by the app may process and store data in the United States and other countries whose data protection laws may differ from those where you live. Google provides its own legal safeguards for such transfers, described in the Google Privacy Policy.
12. Contact us
Questions about this policy: jphfmail@gmail.com
You can also write to us from inside the app via Send feedback.
13. Changes to this policy
If this policy is revised we will update the "Last updated" date at the top. Material changes will be announced in the app or in the store listing. Please check back from time to time.