Privacy
Your reading stays yours.
The short version: your reading record never leaves your device, there is no account, and the only things the app sends are anonymous usage counts — one part of which waits for your explicit yes.
What the app keeps, and where
BibleRing stores your reading record — which chapters you have marked as read, on which day, any notes you write, your reading plan, your display name and an optional photograph — in a database on your device. It is not uploaded anywhere. There is no account and no sign-in. A small projection of your progress (a percentage, the next passage, the run) is written to a shared container on the device so the widgets can show it; it goes no further.
Deleting the app deletes the record. Settings › Data › Erase all reading data does the same without deleting the app. A normal device backup includes it.
The daily note
The one-line note on Home is written by the app itself and, where Apple Intelligence is on and supports your language, refined by Apple’s on-device model. Nothing about your reading is sent to a server for this.
Usage analytics
The app measures itself in two ways, and they are gated differently on purpose.
Aptabase — on for everyone, with an objection switch
Aptabase counts events such as “a screen was opened” or “a reading was logged”, with the app version and the device model. It keeps no identifier, writes nothing to your device, and cannot connect two sessions to one person. Because it touches nothing on the device, no permission is needed under §25 TDDDG; it runs on our legitimate interest in knowing which parts of the app are used (Art. 6(1)(f) GDPR). You can object at any time in Settings › Privacy, and it stops immediately. The data is processed in the EU.
PostHog — only after you say yes
PostHog can show how the app is used across sessions: which features are found, where people stop, whether a change helped. To do that it stores a random identifier on your device, and that is why it is not started at all until you agree on the consent sheet (Art. 6(1)(a) GDPR; §25(1) TDDDG). The sheet appears once, after your first reading, and never over another screen. Declining is the same size as accepting, and swiping it away is a decline. You can withdraw in Settings › Privacy: the identifier is removed from the device and nothing further is sent. PostHog is hosted in the EU. Feedback you send from the app travels the same route, with the note you typed, the app version and nothing else.
Neither service ever receives what you read or wrote: no note text, no book names, no display name, no photograph. A finished book is reported as its division and its length, not its name.
Purchases
The Supporter unlock and tips are handled by Apple’s App Store. The app reads your purchase state from Apple to decide which covers are unlocked; it never sees your payment details. Refunds are Apple’s.
Notifications
The daily reminder is scheduled on your device, by the app, from your own reading habit. No server is involved and nothing about the time you read is sent anywhere.
This website
This site is static. It sets no cookies, loads no third-party scripts or fonts, and keeps no analytics. The hosting provider may keep ordinary server logs (IP address, time, page) for a short period to keep the service running.
Your rights
Under the GDPR you may ask what personal data we hold about you, have it corrected or deleted, restrict or object to its processing, and receive a copy. Because the reading record never leaves your device, the honest answer for most of these is that we hold nothing that identifies you. For the analytics described above, withdrawing consent or objecting in the app is the effective route; anything already received by PostHog under your consent can be deleted on request. You also have the right to complain to a supervisory authority.
Contact
Jonathan Müller, JTechPro, Germany ·[email protected]