Trust, privacy, and corrections
How bibleverse handles privacy, account deletion, church presentation, rights concerns, legal concerns, corrections, and support contact.
Trust detail
How trust decisions are made and corrected.
Trust notes bring together the working method behind privacy choices, account deletion, source corrections, religious-content boundaries, support contact, and beta availability.
Visitors do not have to infer whether Bibleverse sells data, uses ads personalization, claims endorsement, replaces pastoral care, or hides how source and correction decisions are handled.
Method
Public claims are kept close to implemented behavior: beta availability, no-ad posture, consent-gated analytics, visible source labels, and support routes are named without implying third-party validation.
Release NotesPrivacy choices
Optional analytics stay consent-gated, ad storage remains denied, and the privacy policy names account, progress, signup, support, diagnostics, notification, and deletion data.
Privacy PolicySource handling
Bible text, media, canon context, and tradition labels are documented through public source notes so readers and rights holders can see what is being used and where review is still needed.
SourcesCorrections
Source, rights, attribution, legal, and tradition-content concerns go through support with the passage, URL, visible label, expected correction, and public reference needed for review.
Support messageDeletion
Account deletion is available in app settings and through a public deletion request when someone cannot sign in.
Account DeletionBoundaries
Bibleverse is a scripture and prayer companion in limited beta. It does not claim official church endorsement or replace a Bible, parish life, pastoral care, counseling, legal advice, medical care, or emergency help.
FAQWhat to know
Trust starts with plain language and visible correction paths.
Trust is built from small visible choices: no ad posture, consent-gated website analytics, account deletion routes, support contact, source corrections, and careful tradition language. Bibleverse keeps those choices in public view so readers do not have to infer the product boundaries.
The practical choices stay separate: Method, Privacy choices, and Source handling. From trust notes, 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 privacy-conscious readers, parents, pastors, and source-conscious readers. For trust notes, 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 privacy, ads, source correction, deletion, religious endorsement, and support boundaries. Trust notes should answer that question directly before asking anyone to join a list, send a message, or assume a store link is ready.
Method
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.
- Method
- Privacy choices
- Source handling
How it helps
Review the specific trust page that matches the concern.
Method
Public claims are kept close to implemented behavior: beta availability, no-ad posture, consent-gated analytics, visible source labels, and support routes are named without implying third-party validation.
Public claims are kept close to implemented behavior: beta availability, no-ad posture, consent-gated analytics, visible source labels, and support routes are named without implying third-party validation.
Source handling
Bible text, media, canon context, and tradition labels are documented through public source notes so readers and rights holders can see what is being used and where review is still needed.
Optional analytics stay consent-gated, ad storage remains denied, and the privacy policy names account, progress, signup, support, diagnostics, notification, and deletion 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.
Next
Review the specific trust page that matches the concern.
Privacy choices
Source handling
Join the beta list.
Bibleverse is in limited beta. Join Android tester interest or get launch updates while public Android launch work continues; iOS is planned later.