Privacy policy
What this app knows about you, which is almost nothing.
Last updated November 12, 2026.
The short version
This app has no accounts, no ads, no analytics and no trackers. Your highlights, notes and reading progress are kept on your own device, and they are not sent anywhere unless you turn on sync, which is off until you ask for it and is described below.
Two other things do leave your device, and both are described below. The passage you ask for, because the server has to be asked for it. And, if the app goes wrong, a report of what went wrong -- sent automatically. That report carries the error and which build you are on. It never carries what you were reading, and there is nothing in it that says who you are.
The server is asked for Bible text and commentary; it is not told who is asking.
What stays on your device
Your highlights and notes, including the words you marked. Which reading plan you are on and which days you have finished. Your settings: the translation, the reading background, the text size, the commentary you pinned, and the time of the daily reminder.
On the web these live in your browser's local storage. In the app they live in the app's own preferences. Clearing your browser's site data, or uninstalling the app, deletes them, and unless you have turned on sync there is no copy anywhere else. That is why the app can write them out to a file: it is the only backup there is, and it is free and always will be.
Sync, if you turn it on
Sync is off until you ask for it. While it is off, nothing in the list above leaves your device and this section does not apply to you.
If you turn it on, the app asks the server for a sync code and shows it to you once. Your highlights, your notes, the words you marked, and which days of a reading plan you have finished are then kept on the server as well as on your device, so that another device holding the same code sees them. Nothing else is: not your settings, not what you read, not when you read it.
The sync code is the only identity involved. There is still no account, no email address, no password and no name. The server keeps a one-way hash of the code rather than the code itself, so what is stored cannot be used to find your notes without the code you were given. It is an identifier, though, and we say so plainly: everything in one code's store belongs together.
Two consequences, and both are honest rather than convenient. Lose the code and nobody can give it back to you -- not us, because recovering it would mean holding an account for you to recover it with. Your notes are still on each of your devices and still export to a file; it is the shared copy that becomes unreachable. And 'Stop syncing' deletes that shared copy from the server for good, which is what the words have to mean to be worth printing.
What the server is asked
When you open a passage, search, or look up a word, the app asks the server for that passage, that search or that word. The request carries the reference and the translation. It does not carry a name, an account or an identifier for you, because there is none. Reading, searching and looking up a word are never tied to a sync code even when you have one: sync is its own request, and the server is not told which passages the device holding that code has opened.
Like every web server, it keeps an ordinary request log: the time, the path requested, the response status, and the IP address the connection came from. That log is used to keep the service running and to investigate abuse, and it is kept no longer than it is useful for that. There is no account and no cookie to attach it to, so it is not a profile of anybody.
No cookies are set by this site. No third-party scripts, fonts, tag managers or analytics are loaded, so no other company is told that you were here.
If the app goes wrong
When something inside the app fails -- a screen that will not draw, a list that comes back empty -- the app writes down what happened: the time, which build you are on, which part of the app it was in, the error, and the programmer's stack trace. You can read the whole thing yourself, before anything is sent and afterwards: Sources and licenses, then Diagnostics.
That report is sent to the server automatically, without asking you, the next time the app can reach it. We say so here rather than leaving you to find out, and we say what is not in it: not the passage you were reading, not your highlights or notes, not your settings, and no identifier for you or your device, because there is none to put in it. Two reports from one phone and two reports from two phones cannot be told apart at this end. That is deliberate, and it is also why the number of reports is not a count of readers and is never used as one.
Why automatically rather than asking you first: a stack trace is worth nothing to the person who hit the fault and everything to the next reader who would have hit it. A report that waits for somebody to press send is a report that mostly never arrives, and the fault stays in the app.
These reports are kept only while they are useful for fixing what they describe, and then deleted. You can also send one by hand from the same Diagnostics screen, which is what that screen was for before this was automatic.
The file you export
When you export your highlights and notes, the file is handed to you -- to your share sheet on a phone, or to your downloads in a browser. It does not pass through this server. Where it goes next is entirely your choice, and so is what happens to it there.
Payments
Any payment -- supporting the app, or a subscription if one is ever offered -- is handled by Google Play or the App Store. They take the payment and they hold your payment details. We never see your card number, your name or your billing address.
What the store hands back is a receipt: a token saying what was bought and when it expires. If a subscription exists, that receipt is checked with the store and kept so the app knows what you are entitled to. Supporting the app unlocks nothing, so there is nothing to keep and nothing is kept.
The daily reminder
The reminder is scheduled by your own phone's alarm clock. There is no push service, no Firebase and no server involved, so nothing about when or whether you read leaves the device. The app reads your time zone so that seven in the morning means seven where you are, and that stays on the phone too.
What the Android app asks permission for
Internet access, to fetch the text. Notifications, only at the moment you turn the reminder on. Permission to schedule an exact alarm, so that a reminder set for seven arrives at seven rather than up to an hour later -- you grant it in system settings and you can take it back. Permission to run after a restart, so a reminder survives rebooting your phone. Vibration, for the reminder. Nothing else.
Children
This app asks nobody their age, name or email address, children included, and has no account to attach any of it to. Two things only are ever stored away from your own device. What sync holds, if you switch sync on: your own highlights and notes, under a code and not under a person. And a report of a fault in the app, which carries the error and the build and nothing about who you are or what you were reading.
Changes to this policy
If this policy changes in a way that affects you, the date at the top changes with it. It is a description of what the software actually does, so it changes when the software does.
Contact
Questions about this go to biblestudytoolapp@gmail.com.