Privacy Policy

1. Operator and contact

Bible Notetaker is operated by 51 Pegasi Fund, based in Puerto Rico. References to we, us, and our mean that operator. For privacy questions or requests, email privacy@biblenotetaker.com or use /contact and select a privacy-related subject. Signed-in users can request account deletion and download their data in Settings.

2. Information we process

Account details include your email, name, username, profile image, biography, authentication-provider identifiers, and preferences. Study data includes annotations, replies, forum posts, saved collections and notes, reading progress when enabled, and AI conversations you save. Information you provide may reveal religious beliefs or other sensitive details; avoid including information about other people without permission.

We process security and operational records such as IP address, browser/device information, login events, request logs, and abuse reports. Previously collected device fingerprints may remain in security records; the app no longer automatically generates browser fingerprints. Payments and rewards may involve Stripe customer/subscription identifiers, transaction records, payout contact information, contributions, and fraud-review records. Payment providers handle payment credentials.

3. Public and private information

Forum contributions and enabled public annotations are visible to others, including visitors and search engines. Turning off Public Annotations hides your annotations from other users in the app. The Public Profile setting controls your profile page; your name or username can still appear beside public forum posts, rewards activity, and other contributions. Hiding a profile does not delete those contributions.

Collections are private unless you publish them. New AI conversations are private unless you choose to share them. As part of this update, older AI conversations have been made private because earlier versions defaulted to public sharing. Owners can share them again. Public material may already have been copied, indexed, quoted, or cached outside our control.

4. Purposes and service providers

We use information to provide sign-in, save your work, answer AI requests, deliver messages, process subscriptions and rewards, moderate content, prevent fraud, resolve disputes, and meet legal obligations. Where applicable privacy law requires a lawful basis, the basis depends on the purpose: providing a requested service, legal obligations, proportionate security/operational interests, or consent. Processing sensitive information may require an additional legal condition; agreeing to the Terms is not blanket permission to use it for unrelated purposes.

Providers may process information for hosting and delivery (including Cloudflare for content delivery and security), authentication (including Google), email (Resend), billing (Stripe), support communications (including Slack), optional analytics (PostHog), AI, and speech generation. AI requests include your submitted messages, relevant conversation history, and selected Scripture context. The configured AI services may include OpenRouter and its model providers, Google Gemini, Groq, or Hetzner; fallback processing can send a request to another configured provider. Provider retention and model-training practices depend on the service and account configuration. We do not promise that all providers have zero retention. Do not submit confidential material that you do not want processed by these services.

We do not sell personal information or share it for cross-context behavioral advertising. We do not use your private notes or chats to train our own general-purpose AI models. Sharing with a provider to answer a request is distinct from training. Any materially different future use requires appropriate notice and, where required, a separate choice. We may disclose information when legally required, to protect rights and safety, or in a business transfer subject to applicable safeguards.

5. Analytics and storage choices

Optional PostHog product analytics are off until you allow them in Cookie preferences. We disable session recordings, automatic click capture, and account identification, and exclude search text, chat text, verse details, and full page URLs from analytics event properties. Global Privacy Control or Do Not Track disables optional analytics in this app. Essential cookies and local storage support sign-in, language, reading preferences, and your privacy choice. See /legal/cookies.

6. iOS app and offline notebooks

The iOS app connects to the same Bible Notetaker account and private collections as the website. Downloaded Scripture, reading position, display preferences, cached notes, and pending edits are stored on your device. Session credentials use iOS secure storage. Notes sync with our server when you connect and use Sync; reconnecting or returning to the app can also trigger a sync. This pilot keeps reading position on the device and does not send that position to the server.

The native reader does not include advertising or product-analytics SDKs. Website pages opened for sign-in, support, or legal information follow the website cookie choices described above. Signing out removes the current account’s cached notebook after pending edits have been synced or resolved. Downloaded books can be removed in Settings. Removing the app or its data can lose unsynced drafts; export anything you need to keep first. Local app data may be included in device backups according to your Apple settings. Export opens the device share sheet; information goes to the destination you choose.

7. Retention, security, and international processing

We retain account and study information while needed to provide your account and until deletion is fulfilled, subject to necessary legal, payment, fraud-prevention, and dispute records. Retention depends on the record's purpose and applicable obligations, not an unlimited right to retain everything. Backups, provider-held copies, and external search caches may take longer to expire. A deletion response will identify applicable limitations.

We use measures such as HTTPS and authenticated access controls, but no system can guarantee complete security or uninterrupted availability. We do not represent that independent security audits occur on a fixed schedule. Providers may process data outside Puerto Rico or your country; where applicable law requires transfer safeguards, those must be established for the relevant service.

8. Your requests and controls

Settings provides a downloadable account/study-data export, reading-history controls, profile/annotation visibility controls, and a tracked account-deletion request. A deletion request is not immediate deletion: we must review and fulfill it, including relevant providers and billing records. It does not itself cancel a subscription; use Manage billing to cancel renewal. You may also request access, correction, deletion, portability, restriction, objection, or withdrawal of consent through /contact, as available under applicable law. We verify identity proportionately and respond within applicable legal deadlines, including permitted extensions. You may complain to the relevant data-protection authority. We will not unlawfully discriminate for exercising privacy rights.

Turning off reading-history tracking stops new server-side reading records; it does not erase earlier history or reading preferences stored on your device. Essential storage can be removed using browser controls, which may sign you out. Withdrawing analytics consent stops future optional collection but does not automatically delete previously received events.

9. Age eligibility and changes

Accounts are intended for people aged 16 or older. We do not offer an under-13 parental-consent registration program. If you believe a child has provided personal information contrary to this policy, contact us so we can investigate and take appropriate action. An age statement alone does not replace duties that apply when we learn a child is using the service.

This update explains new privacy controls and makes AI conversations private by default. Future material changes will be highlighted through the service or another appropriate notice. We will not treat a policy edit as retroactive permission for a materially different use of previously collected information.