Why Urdu Bible collects no data at all
Urdu Bible collects nothing. No account, no analytics, no crash reports, no advertising identifiers, no record of which passages you opened.
That is not a promise in a privacy policy. It is a declaration filed with the app stores, and you can read it without taking our word for anything.
In short
- The store listing declares no data collected and no data shared, which is a formal statement to Google rather than marketing copy.
- The app has no mechanism to collect anything, because it never makes a network request while you read.
- Collecting nothing costs us something specific, and it costs us every time a bug ships.
What does "no data collected" actually mean?
It means the declaration in the store's data safety section says so. Google requires every developer to complete that section, describing what the app collects, what it shares, and why, and it appears on the listing next to the download button.
That matters because of who the statement is made to. A privacy policy is a document a company writes about itself; a data safety declaration is a representation to the platform, and misdeclaring it is a policy violation with consequences for the developer account. Google explains how to read one on its Data safety help page, and the App Store publishes equivalent labels.
So the useful instruction here is not "trust us." It is: open the listing, scroll to data safety, and read it. If it ever says anything other than no data collected and no data shared, we have broken something.
How can an app collect nothing?
By having nowhere to send it. Urdu Bible reads entirely offline, so opening a chapter is a local file read and there is no request in which anything could travel.
This is the part worth understanding, because it turns the promise from a policy into a property of the build. An app that streams its text has a server, and a server necessarily observes something: which chapters were requested, from which IP, at what time. The data exists, and then somebody has to decide what to do with it. An app with no server has no such record.
The absences reinforce each other. No account means no identity to attach behaviour to. No advertising means no third-party SDK, which is where a great deal of quiet collection actually happens in free apps. No ads at all removes the commercial reason to want the data in the first place.
What does collecting nothing cost you?
Nothing, which is the point. What it costs us is the more interesting half.
We have no crash reporting. When the app fails on a device or an Android version we do not own, we do not find out. There is no dashboard showing a spike; there is an email, days or weeks later, from somebody who took the trouble to write. Every other studio our size runs a crash reporter, and they are right to, and we gave it up on purpose.
We also have no analytics, so we do not know how the app is used. We cannot tell you which books are read most, whether anyone uses search, or whether the Roman line is the one people follow. Those would be useful when deciding what to build next, and we decide without them.
Here is the cost we promised, stated plainly: we are the only people who can find our own bugs, and we are slower at it than a crash reporter would be. That is the price of the declaration, and it is paid in defects that live longer than they should.
Is collecting nothing the right trade for every app?
No, and it would be silly to claim otherwise. Most software is better for knowing how it is used, and a team that measures nothing is guessing.
The reason it fits here is what the data would be about. A record of which passages a person read, how long they stayed, and which verse they returned to is not neutral information, and in some places it is genuinely unsafe information to have collected about somebody. A Bible app is one of the few products where the most valuable analytics are also the ones you would least want to exist.
So the trade is specific to this app rather than a principle we apply everywhere. Our commercial work measures plenty.
FAQ
How can I verify Urdu Bible collects no data?
Open its Google Play or App Store listing and read the data safety section or privacy label. Both stores require developers to declare collection and sharing, and both display it publicly, so the claim is checkable independently of anything we say.
Does the app need an account or sign-up?
No. There is no account, no email address to give and no sign-in of any kind. You install it and start reading, which is also why there is no identity for any behaviour to be attached to.
If it collects nothing, how do you fix bugs?
From email. Without crash reporting we rely on readers telling us something broke, which is slower and less reliable than automated reporting, and it is the deliberate cost of collecting nothing.
If you would rather your reading left no record anywhere, Urdu Bible has all 66 books in Urdu and Roman Urdu and never opens a connection. Free, offline, no ads.
