Reading the Bible offline, without an account
Why most Bible apps want you signed in, what they actually sync, and the honest list of what a purely local app can and cannot do for you.
You install a Bible app, and before you have read a sentence it wants an email address. It is a strange thing to be asked for by a book, and it is common enough that people assume it is simply how apps work now. It is not. There are specific reasons, they are worth understanding, and once you know them you can tell from the outside which apps will work on a plane and which will not.
Why Bible apps ask you to sign in
The translation is licensed
This is the reason nobody mentions and it is often the first one. Modern translations — the NIV, the ESV, the NASB and most others published in the last seventy years — are under copyright, and an app carrying them holds a licence from the publisher. Those licences commonly favour serving the text from a server over shipping it as a file the reader keeps, because a file that has been handed over cannot be withdrawn if the licence lapses.
If the text has to be fetched, the app needs a connection. If it has to know which texts you are entitled to, it needs a way to recognise you. The account arrives as a consequence of the licensing arrangement, before anyone has designed a single feature for you.
Sync
The honest reason. People highlight passages, write notes, keep bookmarks and follow plans, and losing all of that when a phone is replaced is genuinely painful. Syncing it needs a server, and a server needs to know whose data is whose. This is a real benefit being offered in exchange for a real thing.
The business model
The third reason is that an identified user is worth more than an anonymous one. An account supports subscriptions, retention email, personalised recommendations, advertising, and the analytics that make all of it measurable. None of this is unique to Bible apps. It does mean the sign-in screen is often doing several jobs at once, only one of which is for your benefit.
What actually gets synced
Worth being concrete, because "sync" is vague and the items differ a lot in how sensitive they are.
- Bookmarks and highlights — which verses you marked, and often when.
- Notes — free text you wrote, which can be the most personal thing on your phone.
- Reading plan progress, and the streaks and completion records built on it.
- Which translations you have opened, and how often, which is straightforwardly a record of your reading.
- On social features, anything you shared, followed or commented on.
The reading history is the one people underestimate. A timestamped record of which passages someone opened, and when, is a fairly intimate document. Whether that matters to you depends on where you are and who you are, and for some readers it matters a great deal.
What a purely local app can do
Quite a lot, as it turns out, because reading is not an online activity to begin with.
- Show you any passage instantly, because the text is on the device and a lookup is a local database query rather than a request.
- Work identically on a plane, in a basement, abroad without roaming, on a phone with no SIM, and during the provider’s outage.
- Keep working years from now, since there is no server that can be switched off and no session that can expire.
- Ask nothing of you — no email, no password, no verification code, no consent dialog for tracking you were not going to be subject to.
- Hold nothing that can be breached, because there is no account database anywhere with your name in it.
- Search, favourite, take notes and export a verse as an image, all locally.
What it cannot do, and this is the real cost
A page that only listed the advantages would not be worth reading. Here is the other side, for this app specifically.
- No sync across devices. Notes made on a phone are not on a tablet. There is no mechanism and there is no plan to fake one.
- No restore. Delete the app and its notes and favourites go with it; a new phone starts empty. In this app there is currently no export either, which is the sharpest edge of the trade.
- No shared or social features — no comparing highlights, no group plans, no comments.
- No content updates without an app update. Because the text is compiled into the download, a correction ships as a new version rather than appearing quietly.
- A larger download than an app that fetches chapters on demand. You pay the install size once instead of paying for the network forever.
If cross-device sync of your notes is the thing you need most, a local-only app is the wrong tool and you should use one with an account and go in knowing what it collects. That is a legitimate choice, not a failure of nerve.
Practical advice either way
If you go local, handle the backup problem yourself
The gap is real, so treat it as one. Anything you write that you would be sorry to lose should exist somewhere else too — copied into a notes app, emailed to yourself, written in a paper notebook. A whole-device backup may carry an app’s files along with everything else, but that is a property of the phone rather than a feature the app offers you, and it is not something to lean on for text you care about. Until an export exists, the reliable answer is a second copy you made deliberately.
How to check an app before you install it
- Read the App Store privacy card first. "Data Not Collected" and a long list of collected data are very different products, and the card is a declaration the developer had to make.
- Look for whether the translations named are copyrighted ones. If the list is NIV, ESV and NASB, expect a connection and an account. If it is the KJV and other public-domain texts, offline is at least possible.
- After installing, turn on airplane mode and open a chapter you have not visited. This is the only test that cannot be argued with.
- See whether the first screen asks for an email before showing you any text. An app that reads first and asks later, or never, has made a decision about your relationship to it.
- Check whether there is an export for notes. If there is not, decide in advance where your own copy lives.
Where this app stands
Verses is on the local side of that line, and the reasoning is the same chain as above, run backwards. It carries public-domain texts — the King James Version and the Chinese Union Version in both simplified and traditional characters — so there is no licence to enforce. With no licence to enforce there is nothing to check, so there is no server, so there is no account, so there is nothing to sign in to and no email screen to get past.
Concretely: the whole text is compiled into the download and unpacked once on first launch, so the very first chapter you open works in airplane mode. There is no sign-in anywhere in the app. There is no analytics SDK, no advertising SDK, no crash reporting and no tracking identifier — not as a policy commitment but because no such code is in it. Favourites, notes, settings and reading history are stored on the device and nowhere else.
And the cost, without softening: nothing is backed up and nothing is synced, there is no export yet, and deleting the app deletes your notes. That is the price of the rest of it, and you should know it before you start writing anything in there rather than after.
Frequently asked questions
Is there a Bible app that works completely offline?
Yes, and the reliable indicator is which translations it carries. An app built on public-domain texts such as the King James Version can compile the whole Bible into the download and never make a request. Verses does exactly that, including on first launch.
Why does a Bible app need my email address?
Usually for some combination of three things: verifying your entitlement to a copyrighted translation, syncing your notes and highlights across devices, and supporting subscriptions, marketing and analytics. Only the second is a benefit to you, and it is available only if you want it enough to accept the other two.
What do Bible apps collect about my reading?
Where an account exists, typically bookmarks, highlights, notes, reading-plan progress, and which passages you opened and when. The last of those is more revealing than people expect. Check the App Store privacy card, which the developer is required to fill in.
If there is no account, what happens to my notes when I get a new phone?
In a purely local app they do not travel. In Verses specifically there is no sync and no export at present, so notes live on the device that made them and are deleted with the app. Keep a copy of anything you would be sorry to lose.
Read it without signing in
Verses carries the King James Version and the Chinese Union Version — both public domain — compiled into the app itself. Book list, chapter grid, and a reader that renders a chapter as continuous text with the verse numbers still there. Free, no account, no ads, no analytics, and no network requests at all.