BeBible
Last updated August 27, 2026
BeBible ("we", "our", or "the app") helps you build a daily Scripture habit, guard selected apps with Apple's Screen Time tools, and share a daily photo and reflection with private, invite-only Groups. This policy explains the information the app handles, why it is used, where it is stored, and the choices available to you.
BeBible was previously called Altar. It is the same app and developer under a new name.
Your selected applications, categories, and web domains are represented by Apple Family Controls tokens. BeBible stores those tokens in its private App Group so the app and its Screen Time extensions can apply the shields you request. The selection is not uploaded to BeBible, Supabase, RevenueCat, Cloudflare, or OpenAI. Hard Block Mode schedules, temporary unlock state, and related settings also stay on the device and are handled through Apple's Family Controls, Managed Settings, and Device Activity frameworks.
If a Group post cannot finish while its Group day is still active, its two compressed photos and a small retry record may remain in app-private storage. They do not appear in Memories or the BeBible Photos album until the server confirms a post. An expired retry is hidden and is removed after the app can confirm that no post was accepted; an ambiguous offline retry may remain privately until the next reconciliation. These retry files are excluded from device backups.
Before Sign in with Apple, BeBible may create an anonymous Supabase authentication session. It has a random backend user identifier and does not contain your Apple identity. It supports authenticated connectivity, rate limiting, and pre-sign-in product analytics. Reinstalling the app may create a different anonymous identifier.
When you use Groups, Sign in with Apple gives Supabase an app-specific identifier. Apple may also provide your name and either your email address or an Apple relay email, depending on your choices and what Apple has already shared for this app. BeBible uses the account to maintain your session, save your display name, authorize Group access, connect subscription status, apply abuse limits, deliver notifications, and support account deletion. Group members see your display name, not your email address or Apple account identifier. We never receive your Apple password.
Apple processes purchases and payment information. RevenueCat receives purchase and entitlement information from Apple and is linked to your BeBible backend user identifier after you sign in. BeBible and Supabase store the resulting entitlement status, expiration information, environment, update time, and RevenueCat app-user identifiers so paid access can be enforced consistently. We do not receive your full card or bank details.
Groups are invite-only. Free members may belong to one Group total or create one four-person referral Group. Premium members may belong to or create up to ten Groups, and a Premium-owned Group can hold up to 50 members. If a free referral Group is permanently upgraded, that capacity remains available as described in the app.
When you create, join, or use a Group, we store:
Members of the same Group can see its roster and each other's display names. After posting for that Group's current day, a member can see the day's visible posts, photos, shared Scripture and reflection content, comments, and replies. Members cannot see your email, Apple account identifier, Screen Time selections, other Groups, private local history, or content hidden by a block or report rule.
Reporting a post, comment, or reply hides it for the reporter. Reports from two distinct members hide the content from the Group pending review. The reported author is not notified. Blocking prevents both people from seeing each other's posts, comments, replies, profiles, and related notifications in shared Groups; factual membership may remain visible to Group owners for management. The blocked person is not notified.
Leaving a Group removes your access but does not delete the posts and comments you previously shared there; remaining members retain access according to the normal Group rules. If an owner leaves a Group with other members, ownership transfers to the earliest remaining member. If the last member leaves, the Group and its related server content are deleted. Removing a member has the same access effect as leaving.
Deleting a post removes its server capture and every per-Group post and thread attached to that capture. BeBible also requests deletion of its R2 objects, app-private files, cached copies, and matching BeBible Photos assets. R2 cleanup is best effort because the lifecycle rule is the final deletion boundary. Photos cleanup requires current permission and Apple's confirmation; if it cannot complete, an album copy may remain on your device, but BeBible ignores it when no matching server post exists. Deleting your account does not delete recovery copies already saved in Apple Photos.
If you allow notifications, Apple gives BeBible an APNs device token. We store the token with your backend user identifier, platform, app environment, bundle identifier, and last-seen time so we can send Group post, comment, and reply alerts and route a tap to the related content. Notification delivery goes through Apple Push Notification service. Tokens are removed when you sign out or delete your account when that cleanup can be completed; Apple may rotate or invalidate them independently. BeBible also schedules selected reminders locally on your device.
Scan to Unlock first processes the camera image on your device with Apple Vision OCR. It then compares the recognized words with Bible text bundled in the app. The camera image itself is not sent to Supabase or OpenAI. When on-device matching cannot confidently identify the page, the optional AI identification fallback may send the recognized OCR text to our Supabase Edge Function and then to OpenAI.
Other optional AI requests use text only:
Consent defaults to off. The current scan flow does not interrupt the camera with a separate AI warning. Instead, the explicit consent control is the Profile → Account → Privacy → Scan processing toggle, whose label explains that scanned text is sent to OpenAI. This one toggle controls all AI-assisted Scripture features, including the Bible Assistant. The choice is stored for the device and currently remains in effect if you sign out or change accounts on that device. You can turn it off at any time. While it is off, OCR, passage matching, and fallback devotional responses remain on the device, and BeBible does not make an OpenAI request. AI Assistant access is also hidden while consent is off.
When consent is on and you use an eligible AI feature, Supabase verifies your signed-in account and Premium entitlement, applies per-user, per-IP, and global limits, and forwards the permitted text to OpenAI's /v1/chat/completions API. Supabase stores your backend account identifier, request time, prompt character count, and status in an assistant request log; it does not store the prompt body in that table. Those account-linked request rows are deleted when the account is deleted. A separate abuse-control table stores the source IP address, rolling request count, window start, and last-request time. Its count resets after a 24-hour window, but the database currently has no automatic schedule that deletes the IP row.
OpenAI may retain API prompts and responses in abuse-monitoring logs for up to 30 days, unless longer retention is required by law or is reasonably necessary to protect OpenAI's services, users, or third parties from harm. OpenAI states that API inputs and outputs are not used to train its models by default unless the API account owner explicitly opts in to data sharing. BeBible does not request persistent Chat Completions application state. See OpenAI API data controls.
OpenAI returns generated text to BeBible. AI responses may be inaccurate or theologically imprecise and are not professional spiritual, medical, legal, or financial advice. If you choose Report on an AI response, BeBible opens your email app with a portion of that response and space for your explanation; sending the email is your choice and is then handled by your email provider.
BeBible sends a limited set of product-interaction events to its own Supabase backend so we can understand onboarding, paywall, Screen Time, scan, subscription, Group, social, Memories, and Hard Block Mode flows. Analytics are on by default and can be disabled under Profile → Account → Privacy → Help improve BeBible.
Analytics may include an event name, approved scalar properties such as a step or action category, event time, a random install identifier, a per-launch identifier, app version, build number, platform, environment, and whether Premium was active. After sign-in, the event is also associated with your Supabase user identifier. The analytics boundary rejects unapproved properties: it does not send invite codes, Group or post identifiers, names, authored posts, comments, reflections, prayers, scanned Scripture text, photos, or Screen Time selections.
Events may be queued in app-private storage before upload. Turning analytics off stops new uploads and clears the local queue. Uploaded analytics events are automatically deleted after 90 days. Account deletion removes analytics attached to the signed-in account; pre-sign-in events attached to a separate anonymous session expire under the same 90-day rule.
Network requests use HTTPS/TLS. Social database tables use row-level restrictions or service-only access, and feed photos use short-lived signed URLs. iOS protects local app storage according to the device's security settings. No method of storage or transmission is completely secure, so we cannot guarantee absolute security.
BeBible is not directed to children under 13, and we do not knowingly collect personal information from children under 13. The age-band answer collected during onboarding stays on the device and is not attached to the backend account or used for advertising.
We may update this policy as BeBible changes. The date at the top shows the latest revision.
Questions or privacy requests? Email thealtarapp@gmail.com.