Privacy Policy
Last updated: 4 October 2026
Your reading and reflections are personal. This policy explains what Biblic processes, why it is needed and the choices available to you.
1. Scope and contact
The Sanctity Church, based in California, United States, operates Biblic and is responsible for the information practices described here. This policy covers biblic.app and its account, study, support and giving features. Other websites, including thesanctity.org, and payment providers have their own privacy notices. The payment recipient is also displayed during checkout.
Contact us through Biblic support or hello@biblic.app. Include your account email or payment reference when relevant. Do not send passwords, full payment-card details or security codes.
2. Information we process
- Account information: name, email address, password hash, verification status and account settings. Authentication records may include session times, IP addresses and browser/device information.
- Study information: saved passages, notes, highlights, collections, lesson answers and progress you choose to save or synchronize. Reflections may reveal religious beliefs or other sensitive details; avoid including information you do not want stored.
- Support messages: your name, email, selected topic, message, reference number and staff responses.
- Giving records: email, amount, currency, purpose, consent, transaction and subscription identifiers, status, receipt and related reconciliation records. Historical physical orders may also contain recipient and shipping information.
- Resource downloads: the email address you enter as a guest, or your account email when signed in, the resource requested, whether you were signed in, and the request date. We use these records to manage access and resource requests. A download does not subscribe you to marketing emails. A short-lived download cookie lets your browser retrieve the file for ten minutes. Contact us to request removal of your download records.
- Technical records: requests, errors, security events, administrative audit records, email delivery metadata and identifiers used to prevent abuse or duplicate processing. Hosting providers may maintain their own access and security logs.
Payment-card entry occurs on Authorize.Net’s hosted page. Biblic’s payment flow does not collect or store full card numbers or card security codes.
3. Why we use information
We use information to operate accounts, synchronize requested study work, restore access, process and reconcile contributions, manage subscriptions, send service emails, respond to support, protect the service and maintain necessary financial and operational records. We do not sell personal information or use private study content for targeted advertising. The app does not submit your notes or lesson answers to an AI service for processing or training.
4. Cookies, device storage and offline content
Necessary authentication cookies maintain sign-in and security. Browser storage holds preferences, guest study drafts, progress, payment-access references and cached public content. Session storage helps you return securely to payment status. These features are functional rather than advertising tools; Biblic’s application does not include advertising pixels or a behavioral advertising system.
Guest study data stays in that browser unless you explicitly merge it into an account. Signing in alone does not import it. Cached chapters are not a complete offline library. Clear cookies or site storage through your browser to remove local copies; doing so can sign you out and permanently remove unsynchronized work. Account deletion does not automatically erase copies on every device or exports you downloaded.
5. Who can access information
Private notes and answers are not published in public verse shares, and support administrators are not given a study-note browsing feature. They are not end-to-end encrypted; authorized infrastructure operators may technically access stored records when necessary to run, secure or repair the service.
We use service providers for hosting/database operations (including Hostinger), transactional email (including SMTP2GO or the configured mail provider) and payments (Authorize.Net). They receive information required for their function: for example, email providers process recipient addresses and service-message content, while payment providers process payment details and billing information.
Authorized staff access relevant support, financial, fulfillment and operational records according to their roles. Information may also be disclosed where legally required or reasonably necessary to investigate abuse, protect rights or address a security incident. We do not publish donor identities or a recipient’s contact details as part of a sponsorship.
6. Service emails and external links
We send account verification, password reset, support and payment/subscription messages as needed. This release does not offer a marketing mailing-list subscription. Provider acceptance of an email does not guarantee that it reaches your inbox.
When you follow an external link or proceed to hosted checkout, that service can collect information under its own policy. Review those policies before entering information. Never send passwords, full card numbers or security codes in a support message.
7. Retention and deletion
Account and synchronized study data are kept while needed to provide the account’s features. You can delete saved material and request account deletion. Transaction, subscription-consent, receipt, support, security and audit records may need to be retained for reconciliation, dispute handling, fraud prevention or legal obligations after account deletion. Deleting an account is not a request to reverse a payment.
Payment-record retention: true
We do not promise that deleting active records immediately removes every backup or provider copy. Backup and provider retention can differ. Ask us about a specific record or deletion request; we will explain applicable limits rather than treat account deletion as erasure of all financial history.
8. Your choices and requests
Use Account to update your name, export saved study data, review/revoke sessions or delete your account. My Learning provides an export of lesson responses. Use Manage Giving for contributions and monthly plans. Cancel or resolve outstanding monthly plans before account deletion; an owner account also requires ownership transfer.
You may contact us to request access, correction or deletion of personal information, or to ask about other rights available where you live. We may need proportionate identity verification to protect your data. Applicable rights can include portability, objection or restriction and contacting your local privacy regulator; availability and lawful exceptions depend on your location. We do not charge or impose conditions contrary to applicable law.
9. Security and international processing
We use password hashing, session controls, access restrictions and protected connections as part of safeguarding information. No online service or device is completely secure. Protect your email account, sign out on shared devices and keep independent exports of work you need.
Hosting, email and payment services may process information in countries other than where you live, whose laws may differ. Contact us for information relevant to your request. This policy does not claim that storage is confined to a particular country or that a specific regulatory certification has been obtained.
10. Children and policy changes
Account, support and payment features are not intended for children under 13. Do not submit a child’s personal information through these features. If you believe we have collected such information, contact us so we can investigate and address removal as appropriate.
We will update the date on this page when practices change. Material changes will be identified on the service or communicated through an appropriate available channel. Where applicable law requires consent for a new use, a policy update alone does not replace that consent.
Contact us through Biblic support or hello@biblic.app. Include your account email or payment reference when relevant. Do not send passwords, full payment-card details or security codes.