Privacy Policy
Privacy policy for bibleverse account data, progress sync, diagnostics, optional analytics, and deletion rights.
Plain-language summary
What the app collects and why.
The privacy summary stays short and concrete: it names the data used for accounts, progress, signups, support, diagnostics, and optional analytics.
Account and progress data support app functionality, signup data supports launch communication, and optional website analytics remains consent-gated.
Account data
Name, email, user ID, preferences, progress, reminders, favorites, and deletion requests exist to run the account and sync the devotional experience.
Signup data
Tester, newsletter, and future support forms collect only the fields shown on the forms and the consent/source details required to manage those lists.
Analytics choices
Optional analytics do not load until they are allowed, and you can change your choice from Privacy choices in the footer. Ads personalization is not part of the public site.
What to know
Privacy language is clearer when it follows the data.
Privacy wording should stay connected to the actual data flow. Bibleverse distinguishes account and progress data from signup forms, support messages, diagnostics, and optional website analytics, then explains deletion and contact routes so readers know where to act if something needs review.
The practical choices stay separate: Account data, Signup data, and Analytics choices. From privacy choices, a reader can move to a related feature, source note, privacy note, update list, or support path without guessing where the question belongs.
That matters for readers and testers checking how account, progress, signup, support, and analytics data are handled. For privacy choices, the answer should be plain enough to act on without treating a signup as access, a reminder as obligation, or app content as a substitute for the right human help.
A visitor may be asking about plain-language privacy choices behind the legal policy. Privacy choices should answer that question directly before asking anyone to join a list, send a message, or assume a store link is ready.
Account data
bibleverse does not present itself as an official Church, parish, diocesan, or denominational product. It does not replace a Bible, worship, confession, pastoral care, counseling, medical care, legal advice, or emergency support.
- Account data
- Signup data
- Analytics choices
How it helps
What the app collects and why with a clear next step.
Account data
Name, email, user ID, preferences, progress, reminders, favorites, and deletion requests exist to run the account and sync the devotional experience.
Name, email, user ID, preferences, progress, reminders, favorites, and deletion requests exist to run the account and sync the devotional experience.
Analytics choices
Optional analytics do not load until they are allowed, and you can change your choice from Privacy choices in the footer. Ads personalization is not part of the public site.
Tester, newsletter, and future support forms collect only the fields shown on the forms and the consent/source details required to manage those lists.
bibleverse does not present itself as an official Church, parish, diocesan, or denominational product. It does not replace a Bible, worship, confession, pastoral care, counseling, medical care, legal advice, or emergency support.
Next