← Back to Bible Seal

Legal

Privacy Policy

Effective: August 23, 2026 Last updated: August 23, 2026
Contents
  1. Scope and controller
  2. Information we process
  3. Information kept on-device
  4. Screen Time information
  5. Bible Chat information
  6. Analytics and diagnostics
  7. How and why we use information
  8. How we disclose information
  9. International processing
  10. Retention
  11. Security
  12. Your choices
  13. Your privacy rights
  14. Age restriction
  15. Changes
  16. Contact

1. Scope and controller

This Privacy Policy explains how personal information is processed when you use the Bible Seal iOS application, Bible Chat, our website at biblesealapp.com, and related support and subscription services (collectively, the “Service”).

The data controller is the individual developer identified as the provider or seller of Bible Seal on its Apple App Store product page, established in Latvia (“Bible Seal,” the “Operator,” “we,” “us,” or “our”). Apple’s product page provides the applicable trader identification details. You can contact the controller at support@biblesealapp.com.

This Policy does not govern Apple or another third party acting independently under its own privacy policy.

2. Information we process

We process the minimum categories reasonably needed for the features you use. Some information is stored only on your device; some is transmitted to service providers.

Category Examples Main purpose
Account and service identifiers Pseudonymous Supabase user ID, Adapty profile ID, app-install or keychain-based identifier/hash, authentication tokens, request IDs Account continuity, authentication, security, subscription access, abuse prevention
Subscription and transaction information Product and access level, purchase and renewal state, original transaction ID, trial or offer type, expiration, refund, grace-period and cancellation status Provide paid access, restore purchases, handle billing events, resolve disputes and prevent fraud
Onboarding and personalization What you ask us to call you; optional age range and stated gender; Bible-reading habits, goals, obstacles, screen-time estimate, faith-related topics or challenges, chosen translation and reading plan; onboarding progress and feature reactions Personalize the app and paywall, select a reading experience, understand audience segments and improve onboarding
Bible Chat content Your current message, bounded recent conversation context, attached Scripture text and reference, and the generated response Generate and return a Bible Chat answer
Usage and interaction information App launches, screens or flow stages, feature actions, completion counts, streak or practice events, selected plan/translation identifiers, video watch duration, paywall and purchase events, feedback and survey responses Operate and improve the product, understand conversion and reliability, provide support
Diagnostics and technical information App and OS version, device type, timestamps, network request metadata, IP address received by infrastructure providers, performance, crashes, errors, provider/model used, token counts, latency and cost Security, debugging, capacity, cost control, rate limiting and service reliability
Support and communications Email address or other contact details you choose to provide, support category, message, attachments and feature requests Respond to you, troubleshoot, and improve the Service
Website request information IP address, browser and device information, requested pages, referring page, timestamps, and security or server logs Deliver and protect the website and understand technical performance

You do not need to provide your legal name to create Bible Seal’s pseudonymous app account. Apple processes your payment method; we do not receive your full payment-card number.

Because Bible Seal is a Christian application, optional onboarding answers or chat messages may reveal religious beliefs, personal struggles, wellbeing information, or other information considered sensitive in some jurisdictions. You decide what to provide. To the extent an optional answer is legally treated as sensitive data, we process it because you deliberately provide it for requested personalization or support and as otherwise permitted by applicable law. Do not provide more detail than necessary.

3. Information kept on your device

Bible Seal is designed so that substantial personal content remains in local app storage. This can include:

  • full saved Bible Chat threads and generated answers;
  • reading history, plan progress, streaks and completion records;
  • saved verses, highlights, notes, memorization items and practice progress;
  • notification schedules, theme and app preferences;
  • on-device copies of onboarding answers; and
  • selected Screen Time applications/categories and blocking schedules.

We do not currently sync this local Bible library or full chat history to our own cloud database. It may be included in device-level backups controlled by Apple or by you. Deleting your online Bible Seal account does not delete information stored only on the device. To remove local data, use available in-app deletion controls or delete Bible Seal and its data from the device.

4. Screen Time and selected apps

When you grant Screen Time or Family Controls authorization, Apple allows Bible Seal to apply restrictions to the applications and categories you select. Bible Seal stores Apple-issued selection tokens and schedule settings in a shared app container so the app and its blocking extensions can work together.

We do not transmit your selected-app list or ordinary browsing history to our servers. We may collect general analytics such as the number of selected applications or categories, whether protection is enabled, schedule configuration events, and whether a blocking or unlock flow completed. Those analytics do not include Bible Chat text and are not intended to identify the names of selected apps.

Apple processes information through its operating system and frameworks under Apple’s own terms and privacy policy.

5. Bible Chat information

Do not send information you would not want processed by third-party service providers. Avoid exact addresses, passwords, financial details, government identifiers, private health records, confidential material, or personal information about another person.

When you send a Bible Chat message, Bible Seal transmits the current question, a limited amount of recent chat context, and any attached Scripture reference/text to our Cloudflare-based backend. The backend authenticates a pseudonymous account, verifies paid access and usage limits, builds the request, and sends the prompt through OpenRouter to an available model provider. The selected provider may vary from request to request because of availability, capability, rate limits, and routing configuration.

The prompt sent for model processing does not need your legal name, email address, Bible Seal user ID, or Apple transaction ID. Your full historical chat thread remains on-device; only the bounded context needed for the current answer is transmitted.

Our production backend is configured not to write Bible Chat prompt or response text to our Supabase database or include that text in ordinary production application logs. We retain operational metadata such as a pseudonymous user ID, request ID, timestamps, status, model/provider identifiers, token usage, cost, duration, and error information.

We configure OpenRouter routing to deny endpoints it identifies as collecting prompt data for training or retention. We do not enable private prompt logging for normal production use and do not use Bible Chat messages to train our own model. However, Bible Seal does not promise that every request is processed under a formal zero-data-retention (“ZDR”) commitment. OpenRouter and the selected model provider process message content under their own technical and legal practices, which may change and may allow temporary processing, security or abuse review, legal retention, or human review. Provider location can also vary.

More information is available in OpenRouter’s Privacy Policy and data-collection documentation. OpenRouter links to the current policies of its model providers.

6. Analytics and diagnostics

We use PostHog to collect pseudonymous product events and error information so we can understand onboarding, purchases, feature use, retention, failures, and product quality. Analytics can include the usage and diagnostic information described above and may be linked to your pseudonymous Bible Seal user ID.

PostHog does not receive your Bible Chat conversation text through our analytics events. We have disabled automatic screen capture, element autocapture, and session replay. We also avoid sending the text of notes, saved verses, and highlights as analytics properties.

You can turn off future usage analytics in Bible Seal under Settings → Account & Privacy → Analytics. Turning analytics off does not disable essential authentication, subscription verification, security, billing, or aggregate service-usage records needed to operate paid features. It also does not automatically erase events collected before the change; you may contact us to request deletion where applicable.

7. How and why we use information

We use information to:

  • provide, personalize, maintain and secure Bible Seal;
  • authenticate pseudonymous accounts and preserve access across normal app use;
  • verify subscriptions, restore purchases and administer paid access;
  • process Bible Chat requests and enforce fair-usage and rate limits;
  • save choices and generate relevant reading plans or onboarding experiences;
  • send local notifications you authorize;
  • diagnose failures, prevent abuse and fraud, and protect users and providers;
  • measure onboarding, conversion, engagement, performance and feature usefulness;
  • respond to support, feedback, privacy requests and disputes;
  • comply with law, tax/accounting duties, platform rules and legal process; and
  • create aggregate or de-identified statistics that no longer identify an individual.

Legal bases for users in the EEA, United Kingdom, and similar jurisdictions

Depending on the activity, we rely on:

  • Contract: processing needed to provide requested app, subscription, personalization, account, support, and Bible Chat functions;
  • Legitimate interests: securing and improving the Service, preventing abuse, understanding product performance, controlling costs, and maintaining reliable operations, balanced against your rights;
  • Consent: where required for optional analytics, notifications, optional sensitive information, or another clearly voluntary feature; and
  • Legal obligation and legal claims: processing needed for accounting, consumer, privacy, regulatory, court, or law-enforcement requirements and to establish, exercise, or defend claims.

Where we ask for information to perform a requested feature, not providing it may prevent that feature from working. Optional onboarding questions may be skipped where the interface permits, or answered without using your legal identity.

8. How we disclose information

We do not sell personal information, rent it to data brokers, or use it for cross-app behavioral advertising. Bible Seal does not display third-party advertising.

We disclose information only as reasonably necessary to the following categories:

Recipient Role and typical information
Apple App distribution, StoreKit purchases and refunds, subscription management, Screen Time frameworks, device backups, and Apple-provided diagnostics. Apple processes data under its own policy.
Supabase Pseudonymous authentication, account/profile records, subscription linkage, billing-event records, and aggregate AI-usage counters.
Adapty Paywalls, onboarding, subscription status, purchase/profile identifiers, selected onboarding fields, offers, attribution and refund-related analytics.
PostHog Pseudonymous product analytics, surveys, diagnostics and error events. Session replay and automatic screen/element capture are disabled.
Cloudflare Backend execution, network delivery, rate limiting, security and operational logs; may receive IP address and request metadata.
OpenRouter and model providers Bible Chat prompt content and generated responses, plus technical model-request metadata. The available model provider can change.
Tally Embedded support and feature-request forms, including the contact details and message you choose to submit.
Google Fonts Font delivery on the website; Google may receive normal web-request information such as IP address, browser and requested font.

Where a provider processes personal information on our behalf, we require it—through applicable terms, configurations, or agreements—to protect that information consistently with this Policy and applicable law and not to use it for unrelated advertising or other unauthorized purposes. Third parties acting as independent controllers, such as Apple, provide protection under their own terms and privacy policies.

Providers can use subcontractors and may update their infrastructure. We may replace a provider with another service performing a similar function. We will update this Policy if that materially changes how we process personal information.

We may also disclose information:

  • when reasonably necessary to comply with applicable law, a valid legal request, court order, or regulatory obligation;
  • to protect rights, safety, security, users, the public, or the integrity of the Service;
  • to investigate fraud, abuse, or a violation of our Terms of Service;
  • to professional advisers who owe confidentiality duties; or
  • in connection with forming a company to operate Bible Seal, financing, reorganization, merger, sale, or transfer of the business, subject to appropriate safeguards.

9. International processing

The Operator is based in Latvia, but our providers operate infrastructure in the European Economic Area, the United States, and other countries. Bible Chat in particular can be routed to model providers in different jurisdictions depending on availability. We do not promise that Bible Chat content will remain in Latvia or the EEA.

Countries outside your home jurisdiction may have different privacy laws or government-access rules. Where applicable law requires a transfer mechanism, we rely on an adequacy decision, contractual safeguards made available by the provider, or another recognized legal basis. You may contact us for more information about safeguards relevant to your data.

10. Retention

We retain each category only for as long as reasonably necessary for the purposes described in this Policy, including to provide an active account or subscription, maintain security and usage limits, resolve support or billing issues, comply with tax/accounting or legal duties, and establish or defend claims.

  • On-device content remains until you remove it, reset the relevant feature, or delete the app and its local data.
  • Account, subscription, billing and usage records generally remain while your account or the Service is active and may remain longer where needed for transaction history, refunds, fraud prevention, disputes, accounting, legal compliance, or de-identified reporting.
  • Bible Chat content is processed to answer the request and is not intentionally stored as message text in our Supabase database. OpenRouter and model-provider retention is governed by their current policy and routing status. Operational request metadata may be retained for reliability, cost, security, and usage-limit purposes.
  • Analytics and diagnostics are retained according to our configuration and the provider’s retention controls, or until no longer reasonably needed. Turning analytics off stops future optional collection but does not itself delete historical events.
  • Support communications remain while needed to resolve the request and for a reasonable period afterward for quality, dispute, abuse, and legal purposes.

When you delete your Bible Seal account, we initiate deletion of the active Supabase account and associated Adapty profile data under our control. Certain billing or webhook records may be deleted, redacted, de-identified, or retained where reasonably required. Deletion from backups and downstream provider systems may take additional time and remains subject to legal exceptions and provider capabilities.

11. Security

We use reasonable technical and organizational measures designed for the nature of the Service, including encrypted network transport, pseudonymous accounts, access controls, request validation, rate limiting, bounded chat context, restricted production logging, and separation of local content from cloud account records.

No application, network, or storage system is completely secure. We cannot guarantee that unauthorized access, loss, or disclosure will never occur. You should secure your device, use current operating-system updates, and avoid placing confidential or unnecessary personal information in Bible Chat, notes, or support forms.

12. Your choices

  • Analytics: Turn optional usage analytics off under Settings → Account & Privacy.
  • Notifications: Change notification permissions in iOS Settings and adjust Bible Seal reminders in the app.
  • Screen Time: Change selected applications, schedules, or authorization through Bible Seal and supported iOS settings.
  • Local content: Delete individual chats, notes, saved items, or other content where the app provides controls; deleting the app and its data removes local storage from that device.
  • Account deletion: Use Settings → Account & Privacy → Delete Account. Remember that this does not cancel an Apple subscription.
  • Subscription: Manage or cancel through Apple.
  • Bible Chat: Do not use the feature if you do not want message content processed by AI providers.

The public website does not currently use advertising or product-analytics cookies. Hosting, security, and font providers still receive the technical request data needed to serve a page.

13. Your privacy rights

Depending on where you live and subject to legal exceptions, you may have rights to:

  • request access to and a copy of personal information;
  • correct inaccurate information;
  • request deletion;
  • restrict or object to processing;
  • receive certain information in a portable format;
  • withdraw consent for future processing where consent is the basis; and
  • complain to a data-protection or consumer authority.

To exercise a right, email support@biblesealapp.com. Because the account is pseudonymous, we may need information available in the app to locate the correct records and reasonably verify that the request concerns you. We will not ask for more verification data than reasonably necessary.

Withdrawing consent does not affect earlier lawful processing. We may retain information where law permits or requires, including for security, billing records, disputes, or legal claims. If we cannot identify data as relating to you, some rights may be limited.

Users in the EEA may complain to their local supervisory authority or Latvia’s Data State Inspectorate (Datu valsts inspekcija). You may contact us first, but you are not required to do so.

14. Age restriction

Bible Seal is not intended for anyone under 16, and we do not knowingly allow children under 16 to use the Service. If you believe a person under 16 has provided personal information, contact us so we can investigate and take appropriate action.

15. Changes to this Policy

We may update this Policy as the Service, providers, or law changes. The “Last updated” date identifies the current version. If a change materially affects how we use previously collected personal information, we will take reasonable steps to notify you through the Service, website, or another available channel and seek consent where required.

16. Contact

Bible Seal is operated from Latvia by the individual developer identified as the provider or seller on the Bible Seal App Store product page. Apple’s product page provides the applicable trader identification details.

Privacy questions and requests
support@biblesealapp.com

Read the Terms of Service Return to Bible Seal