Privacy Policy
Bible Teum is a Bible-reading habit app that you can use without an account. Bible passages and references you read, copied text, highlights and notes, and the list of apps you lock stay on your device. Section 3 explains what information leaves your device for ads, purchases, feedback, updates, and optional usage statistics.
1. Information kept on your device
- Reading and copying history, drafts, highlights and notes, and your reading-plan progress.
- Your settings, including your translation, reading amount, unlock rules, and the number of temporary unlocks.
- The apps you choose to lock and whether they are locked or unlocked.
You can delete this information in the app. Uninstalling the app removes its local data. If you export a JSON backup, it goes to the location you choose.
2. What App Lock checks when you enable it
- Android. An Accessibility service checks on your device whether a chosen app is on screen. It checks each open window’s type, position, size, whether it has input focus, whether it is in picture-in-picture, and the app’s package name. It does not read screen text, messages, input, or images. It does not store or send window information or your usage history for the chosen apps.
- iPhone. Apple’s Screen Time handles the apps you select using identifiers managed by Apple. Bible Teum cannot see which apps those identifiers represent.
App Lock is not an assistive feature. You can turn off Accessibility or Screen Time access in your device settings at any time.
3. Information sent outside the app
- Ads from Google AdMob. Basic shows one banner ad on the home screen. The app requests non-personalized ads and does not show the iPhone tracking prompt. To serve and measure ads and prevent fraud, Google may collect app-instance or advertising identifiers, IP address, approximate location derived from IP address, app and device type, and ad views or taps. We do not send reading or copying records, highlights and notes, chosen app names, or screen information to Google. Premium has no ads. See Google’s policy.
- Premium and Support purchases. Premium is available through the App Store or Google Play. Support is available on supported iPhones. Each store handles the payment, and we do not receive card or store account information. The app checks purchase and subscription status when you open or return to it. On your device, it stores Premium product IDs, verification times, the end of the current billing period when the store provides it, and the start and end times of the one-month pass. While a pass is active, it also stores the latest observed device time so turning the clock back does not extend the pass. The app does not send these purchase-verification records to the statistics server.
- Feedback through Google Forms. If you submit the form, the operator receives the feedback you enter, an email address if you choose to provide one, and the preselected device type, iPhone or Android. See Google’s privacy policy.
- App updates through Expo. The app connects to Expo to check for and download updates. The request may include your operating system, app project details, a random installation token, and ordinary network information such as IP address. It does not include reading or copying records, chosen apps, or screen information. See Expo’s privacy policy.
- Checking for a newer store version. When the app starts, it reads a version file on this GitHub Pages site to check for a newer App Store or Google Play release. GitHub may receive ordinary network information such as IP address. The request does not include your app data. See GitHub’s privacy statement.
- Optional usage statistics. This setting is off by default. If you enable it in an app version that offers it, the app sends a randomly generated installation identifier and event identifier, event time, operating system, app version, and usage events over HTTPS to help improve the app. Events include opening the app, finishing setup, starting or completing reading, completing copying, enabling App Lock, unlocking after reading or copying, and viewing, starting, or restoring Premium. A separate random ID links the start and completion of the same reading. The app does not send earlier records, Bible passages or references, copied text, notes, chosen app names, account information, prices, or purchase details in these statistics. Supabase Pte. Ltd. receives requests, stores events in a database in Seoul, South Korea, and calculates totals. Supabase may temporarily keep connection information such as IP addresses in operational and security logs. These logs may be processed in the European Union, and retention depends on the Supabase plan. Bible Teum does not store raw IP addresses in usage events. See Supabase’s data processing information and logging documentation. Daily cleanup deletes individual usage events after 180 days.
- The Bible translations currently available in the app can be read offline.
4. Sharing and sale of personal information
We do not sell personal information. Section 3 lists the external services we use for ads, purchases, feedback, updates, and optional usage statistics. We use these statistics to improve the app. Our public dashboard shows only counts and rates aggregated across app installations that opted in. Individual events and installation identifiers stay private.
5. Children
The app is not directed at children under 13, and we do not knowingly collect their personal information.
6. Your choices
You can export or delete local records in the app’s data settings. You can use the app without enabling statistics. Turning off ‘Share usage statistics’ stops new collection and clears pending events. When the app can connect, it requests deletion of previously sent events. To prevent late retries from recreating deleted statistics, daily cleanup removes the hashed installation identifier after 31 days from deletion. If you uninstall the app before it can send that request, the 180-day retention schedule applies to usage events. You can limit ad tracking in your device settings. To request deletion of feedback or ask a question, email rbqls6651@gmail.com.
7. Changes
When this policy changes, we post the updated version and its effective date here.