Privacy Policy

Information we collect

Account information

New accounts require a contact email address and phone number with country code. New accounts verify their phone through a Twilio Verify text code and then verify email through a code. We store both verification statuses, the agreement version and acceptance time, and account timestamps. Existing accounts can sign in by email and verify their phone from their profile. Providing or verifying a number is not marketing consent. Prior accounts may retain identity information from a previously available sign-in provider. New account signup uses email and phone, not social login.

Study and Program information

We store notes, verse highlights, chapter bookmarks, Apple Pencil vector markups, Program enrollments, progress, reminder preferences, and related timestamps.

Service Desk requests

When you submit a support ticket, feedback, or feature request while signed in, we store its type, topic, subject, messages, status, priority, assignment, handling history, timestamps, and your account link. Authorized support administrators can read and respond; they may add internal handling notes that are not shown in your ticket view. We use this information to answer and manage your request, investigate issues, and improve Saint Bible. Ticket-number email notices may be sent through our email provider, but do not contain the request text. Ticket records are removed with your account, subject to limited backups and any legal retention obligation. Do not put sign-in codes, payment-card details, private prayer notes, or other sensitive information in a request.

Technical information

Our hosting and security providers may process IP address, browser and device information, request metadata, error information, and security logs. A secure session token identifies a signed-in browser. On your device, local storage remembers display preferences, reading position, and unsaved note drafts. A random first-party guest ID also stays in local storage so we can distinguish repeat visits from the same browser. A separate random group-prayer device identifier helps prevent duplicate seats in a gathering. Neither identifier is used across other websites or for advertising.

Content activity

We count openings of Reader sections, Bible books, prayers, and Programs in a daily aggregate table. Anonymous content openings are also associated with the browser's guest ID and time so we can understand repeat use and journeys. A guest ID identifies a browser, not a person; clearing site data or using another browser creates a new ID. When you sign in to a verified account, that browser's guest ID is associated with the account. Signing in on another device can associate its different guest ID with the same account; we do not assume two otherwise anonymous devices belong to one person. Signed-in readers also have an account-linked activity history: sign-ins; sections, books, chapters, and Programs opened; Program start, completion, reopening, and leaving; the fact that a note, highlight, or bookmark was saved or removed; and group-prayer starts or joins. These records include event type, public content reference, guest ID or account ID, time, and whether the visit occurred as a guest, free account, or paid member. They do not contain note text, private prayer selections, call media, or IP address. For content visits after geographic reporting began, we also store approximate country, region, city, and coordinates derived by our host from the request's IP address, associated with the guest browser ID or verified account ID by day. Coordinates are rounded; they are not GPS or a precise device location. We do not store the IP address in these activity records or request device-location permission. Authorized Serverbin administrators can review guest-browser, account-level, membership-category, and approximate geographic activity in a read-only dashboard to operate and improve Saint Bible. We do not use an advertising cookie or cross-site identifier for this measurement. Hosting providers may still process ordinary request metadata in operational logs.

Diagnostic events and presence

We also record when a reader or guest browser requests narration or visual contemplation and, for signed-in readers, the exact public verse or reflection sentence when playback begins. To diagnose app and third-party service failures, we record the time, affected feature and public content reference, provider, HTTP status, error code, and a shortened, filtered error message. Browser software errors are recorded using only their error type, same-site script path, and line number, not the full browser error message or stack. A signed-in account or guest browser ID may be associated with an event. While the app is visible, a short-lived presence record holds the latest section and content reference so administrators can see approximate live usage; it is removed after 24 hours. We do not intentionally store API credentials, private notes, prayer text, generated audio, or full request and response bodies in these diagnostic records. Authorized administrators can inspect these records in the Control Center.

Content requests

When narration must be generated, the requested public Scripture or companion-reflection text may be sent to our audio provider. Generated verse audio may also be sent to a transcription service to check that the spoken words match the source text. We do not intentionally include your name, email, phone number, notes, or markups in those requests.

Optional Google Analytics

On the public website, you may choose to allow Google Analytics to measure visits. The Google tag is not loaded until you agree. It can use analytics cookies and process page-view, browser, device, and approximate location information under Google’s own terms. Our explicit page-view events use shortened public paths. We do not intentionally include account identifiers, names, email addresses, phone numbers, private studies, prayer text, call information, invitation tokens, or payment details in those events. We disable Google advertising signals and personalization in our tag. Declining does not limit reading or account access. You can change your choice from the Cookie Policy; the iOS app and Control Center do not load this website tag.

Live group prayer

When you organize or join a group gathering, we store group names, member email addresses and roles, schedules, selected prayers, invitation links, participant display names, and technical connection signals needed to establish the call. Participants in a gathering can see and hear the media you choose to share. Calls use browser-managed WebRTC media encryption (DTLS-SRTP) over direct connections between participant devices when available; signaling travels to our service over HTTPS. Google STUN servers may receive connection requests and participants may learn one another’s network addresses. These transport protections do not independently verify another participant’s identity.

Saint Bible does not record, store, or analyze the audio or video of group calls, including with visual AI. Other participants may use their own device or software to make a recording outside Saint Bible. Camera and microphone access begins when you choose to join, can remain active while you read elsewhere in the same app, and ends when you leave the call or close the page. Muting or turning off the camera prevents others from hearing or seeing you, but may not immediately release the device permission indicator.

If you report another participant through the in-call Safety control, we store the two account IDs, gathering reference, reason, optional details you provide, review status, and time. Blocking stores the two account IDs and prevents those accounts from sharing an active call connection. Authorized administrators can review reports in the Control Center and may receive a report-number email alert; the alert does not contain your report details or call media. On room entry, connection signals older than ten minutes are deleted; a scheduled daily cleanup also removes older signals. Reports and blocks are removed when either account is deleted, subject to limited backups and legal retention. For concerns after a call, contact our published support address.

How we use information

• create and secure accounts and verify email addresses and phone numbers;
• save and synchronize studies, markups, reading progress, and preferences;
• connect group-prayer participants and coordinate prayer schedules;
• generate and cache requested audio;
• send necessary service messages and requested Program reminders;
• record separate email and text offer choices, and deliver authorized marketing where permitted;
• measure aggregate, guest-browser, and signed-in account activity to operate, debug, protect, and improve Saint Bible;
• respond to questions, rights requests, and legal obligations; and
• prevent fraud, abuse, or security incidents.

How we disclose information

We disclose information only as reasonably needed to operate the service, comply with law, protect rights and safety, or complete a transaction you request. Current categories of processors include:

• Vercel for hosting, delivery, and operational logs;
• Neon for managed database storage;
• Twilio Verify and SendGrid for phone verification, email verification and requested reminder email;
• Google or Apple for historical sign-in authorizations retained by existing linked accounts;
• Google Analytics for optional public-site page-view measurement after consent;
• OpenAI and ElevenLabs for generated narration, transcription checks, and scheduled illustration generation;
• Stripe for Saint Bible web billing and subscription records where applicable; and
• professional advisers or authorities when legally required.

We do not sell personal information or share it for cross-context behavioral advertising. We do not use third-party advertising cookies.

Cookies and device storage

Saint Bible uses a strictly necessary, secure sign-in cookie and limited browser storage. Details, names, purposes, and retention are in the Cookie Policy.

Your choices and rights

You may change available display preferences; turn the profile Reminders switch on or off; use email unsubscribe links; or delete individual saved items. To permanently delete your account, open your profile and choose Delete my account. Verify the code sent to your existing email address and confirm in the app; contacting support is not required.

Deletion removes account-linked studies, Program progress and reminders, activity/location records, group memberships and Family Groups you own. Other members keep their accounts and previously granted Plus access. Guest identities linked exclusively to your account and their histories are removed; a shared-browser identity also linked to another account is unlinked from yours rather than deleting that other reader’s history. Sessions are revoked on all devices. This device’s saved account data and scheduled device reminders are cleared; another offline device cannot receive a remote wipe and clears its account cache when it next connects and checks its session.

Any Saint Bible web billing customer is removed and its subscriptions cancelled before account removal. Payment providers may retain historical invoices or records required by law. Sign in with Apple authorizations are revoked; older Apple-linked accounts may first need to reconnect Apple sign-in so that revocation can be completed.

For access, correction, export, or help exercising other rights, email sebastian@serverbin.io. Depending on where you live, law may provide rights to know, access, correct, delete, restrict, object, receive a portable copy, or appeal a decision. We may verify a request before acting. We will not discriminate against you for exercising an applicable privacy right.

Because we do not sell or share personal information for behavioral advertising, there is no sale or targeted-advertising opt-out to process at this time.

Device reminders in the iPhone and iPad app

The single Reminders switch in your profile controls optional Scripture, Saints, prayer, reading, enrolled-Program and Family Group session-update reminders. Local iOS notifications also require Apple’s notification permission. Morning Scripture, midday Saints and evening prayer alerts recur daily; reading and active-Program reminders depend on your activity. The system chooses reminder timing; no per-Program or category controls are offered. Device reminders are scheduled locally and the app does not register an APNs push token or receive remote push campaigns. The account-wide reminder preference is stored with your account, and local scheduling data stays on the device. The daily reading or Program email is limited to one message per day; separate Family Group schedule updates follow group activity. Email requires a verified address and network connection. Direct group invitations and necessary account messages remain separate. You can turn reminders off in your profile or use the unsubscribe link in a reading or Program email; you can separately deny device notifications in iOS Settings. A change on another device applies when this app next connects; already-scheduled offline notifications cannot be remotely recalled.

Retention

Email sign-in links and codes expire after 15 minutes and are deleted after use or replacement. Phone-code challenges expire after 10 minutes; the subsequent email-verification phase expires after 15 minutes. Completed challenges are consumed once. Expired phone challenges and hashed phone/IP rate-limit records are periodically removed after their retention window, generally within two days. Twilio may retain verification records under its own service policy. Browser sessions are configured for up to 30 days. Anonymous guest activity events and approximate geographic activity are deleted after 13 months; guest IDs without an account link are deleted after 13 months of inactivity. Guest IDs linked through a verified sign-in remain associated with the account while it is active. Account-linked activity events are retained while the account is active and removed with the account; the dashboard normally displays the most recent 7, 30, or 90 days. Diagnostic error events are deleted after 90 days. Account and study data are retained while your account is active and as reasonably needed to provide the service, resolve disputes, meet legal obligations, and protect the service. Backups and security logs may remain for a limited period after deletion.

Security

We use administrative, technical, and organizational safeguards designed for the nature of the information, including secure cookies, hashed session tokens, access controls, and encrypted transport. No system is completely secure; do not store highly sensitive personal, medical, financial, or confidential information in notes or shared links.

Underage privacy and safety

Users below legal adulthood need parent or guardian permission. Saint Bible is a general-audience service, is not directed to people under 13 and does not offer accounts for that age group. A responsible adult must supervise underage participants present with them in a private family gathering. Do not submit personal information for a person under 13 or allow them to join independently. Not recording a live call does not eliminate privacy obligations. If you believe underage personal information has been supplied or an unsafe interaction has occurred, contact sebastian@serverbin.io so we can investigate, restrict access and handle deletion as appropriate.

International use

Saint Bible is operated from the United States. If you use it elsewhere, information may be transferred to and processed in the United States and other locations where service providers operate, subject to applicable safeguards.

Changes and contact

We may update this policy as the service, providers, or law changes. Material changes will be communicated where reasonably appropriate.