One ChapterSign in

One Chapter · Your information

Privacy policy

One Chapter is a Bible-reading community with automatic membership for signed-in users unless access is restricted. This policy covers shared discussions, prayers and reading activity, account information, optional on-device Devotion Mode, and three separate texting choices.

Last updated November 9, 2026

Private devotion time and optional iPhone blocking

Devotion time tracking is available on the website and in the iPhone app. It does not require Screen Time permission and does not block apps. In supported One Chapter iPhone apps, you may separately enable Apple Screen Time and choose apps, categories or websites to set aside during a session. Blocking is optional; setup does not start blocking, and you may end a session early or revoke access in iPhone Settings. Selected items stay restricted until the scheduled end unless you pause or end the session, sign out, or revoke permission. Leaving One Chapter pauses recorded devotion time, not scheduled restrictions.

App-selection tokens and native restriction settings stay in Apple-managed storage on your device. App identities and Screen Time usage outside One Chapter are not sent to our servers. Devotion preferences, goals and time history are stored locally in the browser or on the device where you use them, separately for your account; website and iPhone data do not sync with each other. They are not sent to One Chapter servers, the host, friends, groups or analytics. Local data may be lost if browser or app data is cleared or the app is removed. Anyone with access to your unlocked device or browser may see it. You can clear local devotion data in Profile; active restrictions are released before clearing.

This does not change how prayers are stored. “Only me” prayers are private under the existing prayer-access rules, not a promise that prayers are stored only on your phone. Ordinary reading activity and shared community content still follow the rest of this policy. A devotion timer records time, not proof of attention or completed reading.

Information we use

The host can see which Bible translations you view and your display counts for reading, translation comparisons, and saved text. Other members cannot see this report. These records contain your account identifier, translation, view type, and time—not Scripture text, passage references, or the contents of your private Saved verses collection. We retain them for up to 30 days and delete them with your account. Display counts do not prove you finished reading.

  • Your profile name (we ask for your full name so friends can recognize you), optional bio, account identifier, membership or moderation status, phone-search preference, and whether you dismissed the initial text-setup reminder.
  • Optional profile and group photos. We crop and resize saved photos and strip embedded metadata, including location metadata.
  • Your comments, replies, likes, friend requests and accepted friendships, latest visible app-opening time (to skip unnecessary daily reminder texts), daily Today-page activity, and any historical self-reported reading records.
  • Groups you create, invitations and membership responses, and accepted group tags. Pending invitations and declined membership do not appear as profile tags.
  • Prayer titles and details, request-to-praise explanations and original requests, sharing choices, expiration dates, and who joins in prayer or celebrates.
  • When phone authentication is enabled, your verified phone number and Auth0 account identifier. During the transition, existing accounts may retain their legacy Clerk identifier; Clerk also handles information supplied through its login screens.
  • Your chosen daily reminder time and timezone, separate reminder and nudge preferences, consent and withdrawal records, notice versions, and delivery statuses. Optional texts use your own verified number, never a number supplied by another member.
  • Essential session cookies and operational information processed by the hosting and authentication services, such as request, device, network, delivery, and security records.

You choose what to put in your profile and comments. These may reveal religious beliefs or personal information. Anyone who signs in can join. New comment settings initially select your accepted friends and groups, with Public off. Review the audience before sharing sensitive information.

Why we use it

We use this information to verify access, show daily readings and shared activity, save profiles, discussions, likes and friendships, moderate the community, and investigate technical or security problems. Moderation may privately retain a banned verified number to enforce access restrictions.

A requested verification text is for login or phone-account linking only. Verifying your number is not consent to daily reading reminders, invitations, or marketing messages.

Daily reminders and friend nudges have independent, default-off checkboxes in Profile. Daily reminders use your saved time and timezone. Friend nudges may arrive when requested, at most one across the community per group day. You can withdraw either choice independently of requested codes.

After successful phone verification, we keep a private login-only consent audit: the notice version, request and verification times, and verified identity. If you are linking an existing account, the audit also identifies the authenticated account that began the request. The audit contains no phone number or verification code and is not a delivery receipt.

What other members can see

Accepted friends can browse each other’s accepted friends to find people they know and send friend requests. Your name and optional photo may appear in a friend’s list when viewed by that friend’s accepted friends. This does not require a separate permission setting. These lists exclude pending connections and blocked or inactive accounts, and do not show phone numbers, private activity, or private content. A request does not grant friendship or access to private posts until accepted.

The host can see when each member joined, a chart of how the group has grown, and a map of current accepted friendships. This map shows who is friends now, not who invited whom or when a friendship began, and it never includes pending requests, Identity boards, identity encouragement, or Only me prayers.

When you use the iPhone app while signed in, we record its installation identifier, your latest app-opening time, last reported notification permission, and whether you dismissed the notification setup prompt. The host can see that you used the app and your last known notification setup status, but not device tokens or installation identifiers. These records cannot confirm an unopened download, a current installation, or delivery of an alert. This does not give access to your private prayers or callings.

For new accounts, we save which welcome steps you reviewed or skipped so you can finish optional setup later. Moving through the welcome guide does not enable text messages or app notifications; those choices use their separate consent and save controls.

The host can see how many shared requests and praises each member has created, review shared prayer content without a report, and remove shared prayers when necessary. This includes past shared prayers. Shared-prayer counts exclude “Only me” prayers and joining someone else's prayer.

Identity boards are private. Your callings, their order, and your pin choices are visible only to you, never to the host or other members. An identity encouragement is visible only to its sender and recipient. The host cannot browse encouragements, but a recipient can deliberately share an individual message and note with the host by reporting it. The sender never sees whether it was pinned or any of your callings. If the recipient dismisses it, the sender still keeps it in their sent history, and encouragement already delivered stays with the recipient after an unfriend. Encouragements are delivered in the app only, never by text message.

Prayers are never public and start private. Authors choose individual accepted friends and specific groups using two recipient selectors. Only selected friends and accepted members of selected groups can access a shared prayer, along with the host for moderation. Selecting nobody makes it “Only me”: visible only to the author, never the host. Previously shared prayers stay private until their authors select recipients. Members who can access a shared prayer can see the names of people joining in prayer or celebrating. Joining adds that same prayer to your personal list without copying it or granting new access. If you are deselected, a friendship or group access ends, or the author removes all recipients, you lose access even if you previously joined. Answered and expired prayers leave active shared lists; authors can retain their own past prayers, and past shared prayers remain available for host moderation only while recipients remain selected. You can leave your participation without deleting someone else's prayer.

Names of people who react to a comment and their chosen reactions are visible to members who can access that comment. Account email addresses are not public: the host can view the primary login email, when available, alongside participation and friendship counts for community administration. Phone-only accounts may have no email address.

Phone-number search is off by default. You can enable it in Profile so active, signed-in members who enter your complete phone number can find your profile name and send a friend request. Search results never display your number, and enabling search does not accept friends or enable texts. You can turn it off at any time. An empty result does not tell the searcher whether an account exists or opted out. We do not upload your contacts or provide partial-number search, and searches are rate limited.

For account support and administration, the active host can view your verified number even when phone search is off. The member-management list displays only the last four digits until the host deliberately selects Reveal for support. We log the host and member identifiers for this action, not the number itself. Other members cannot access this control.

Choosing a church is optional. If you choose one, your selected church is visible to other signed-in One Chapter members, who can see your name and optional photo on that church's member list and send you a friend request. We store only the church's Google place identifier, never its address or other listing details. You can change or remove your church in Profile at any time.

Photos are optional and are not private like Identity boards. Your profile photo can appear beside your name in signed-in community views. Group photos can appear on group cards, invitations and visible group tags. You can replace or remove your own photo in Profile; group creators and the community host can manage group photos. Uploaded images are stored privately and served only to authorized signed-in members under the existing profile and group visibility rules. Others may still copy or screenshot a photo they can see.

Signed-in members can see profiles, discussions, whether you opened Today, your streak, and your total days. Opening a visible, signed-in chapter page records participation for its displayed date, once per date. Using Previous to catch up on a past chapter adds that earlier day and can repair a streak. Today changes at 4 a.m. in the group's timezone. Background polling and visits to other pages do not count. A visit does not confirm that you read the chapter. Historical marked-reading days remain part of your activity history.

Everyone, Friends only, and Friends + groups filter your view independently of post privacy. For new comments, select individual accepted friends and groups, or explicitly choose Public to share with the signed-in community. Selected groups include all their current accepted members, even if you deselect an individual friend. The host follows the same audience rules as other members and has no automatic access to restricted comments. With Public off and no recipients, the comment is Only me, including from the host. Pending requests and invitations grant no restricted access. Existing posts keep their selected audiences; host status does not override them.

Your last successfully posted audience is saved as the starting point for your next comment. Newly accepted friends are automatically selected for future drafts; newly joined groups must be selected after your first saved choice. Changing these defaults does not edit posted recipient lists. Removing a friendship or leaving a group withdraws the corresponding access.

Accepted group names appear on profiles and member listings. Accepting a group makes its members eligible to view your Friends + groups posts; leaving or removal withdraws that group-based access. Accepting a friend request grants friend-based access; removing a friend withdraws it for both members. Replies to restricted posts inherit the original parent's audience and verse links and cannot widen them. Joining a group does not automatically add friends or enable texts.

Verse highlights are shared with the signed-in community. We store verse references and who highlighted them, not Bible text. Your highlighted references also form your private Saved verses collection, visible only to you. Removing a saved verse removes your personal highlight too. Saved verses can reopen their chapter text on request, without access to historical discussions or reading credit. The selected discussion view limits whose highlights contribute to its displayed counts. A member counts only once per verse. Verse-linked comments use the same recipient choices as other comments. Replies to a restricted post inherit its audience and cannot widen it. Community reading and discussion access is limited to Today and Yesterday; older records remain retained for reading totals, security, and deletion or moderation requests.

Your own eligible comments appear in both feeds. If access to a restricted parent is withdrawn, its replies are hidden too, including replies you wrote. Reading activity and profile information remain shared. Phone numbers are excluded from the directory and Friends feed. Favorites are personal selections, not a public contact list.

You can report a comment, reply, shared prayer, received encouraging word, member, or group. A report voluntarily shares only that item (as a snapshot taken when you report) and your optional note privately with the host, along with your name and the reason. It never shares your whole Identity board, prayer list, or other content. The reported member is not told who reported. Reports do not automatically ban, block, or delete anything; the host reviews them and records a status. Snapshots may remain in the host review queue after the original content is edited or removed. You can block a member: this removes your friendship and pending requests and hides interactions both ways, including public and group posts and invitations. Blocked members are not notified, and blocking is not a site-wide ban and does not remove either person from shared groups. Only you see your blocked list; unblocking does not restore friendship. Reports you filed or that concern you, and blocks you made or received, are deleted when either related account is deleted. Notifications already submitted to SMS or push providers before a block cannot be recalled.

The host may delete comments or ban access. Other members can copy or screenshot content. User-initiated sharing uses your device's Share or copy-link feature; One Chapter does not upload contacts or automatically text invitations.

Service providers and sharing

Help understand is optional. Only when you choose Generate explanation do we send the selected Bible reference and verse numbers to OpenAI through Replit AI Integrations. We do not include your name, phone number, profile, prayers, Identity board, or discussion comments. We do not store the generated explanation or Bible text in the AI usage records; we retain account-linked request dates, status and estimated costs to enforce daily and monthly limits. Generated explanations stay in the current dialog, are not reviewed by OneChapter, and may contain errors. AI service providers may retain their own operational records under their policies.

“Bible links · AI” is off until you explicitly accept its OpenAI/Replit disclosure and select “Allow and remember.” Your choice is saved to your account for future comments and replies across devices; posting, closing an editor or changing readings does not require you to accept again. After permission, a four-second typing pause sends your draft—including private text—and the current chapter label to OpenAI through Replit AI Integrations to suggest Bible-reference hashtags. This can happen before you post. Turn it off in a comment editor or Profile to stop future checks on your account; text already sent cannot be recalled. Changes must save successfully to apply on other devices. We retain your latest choice, disclosure version, acceptance time and last-change time until account deletion; another account does not inherit your permission. Material changes to the provider or processing purpose require renewed permission. There are up to three automatic checks per draft, with an optional manual check afterward, subject to daily and shared monthly limits. Anything you type in the draft is included; we do not attach your profile, phone number, recipient list, parent discussion, or other members’ comments. We do not save drafts or suggestions in AI usage records; only account-linked request dates, purpose, status, and estimated costs are retained for limits. AI suggestions are not reviewed by OneChapter and can be wrong. You choose any links to include; we never change the sharing audience. Sharing never waits for AI, and you can post without links or when AI is unavailable. AI service providers may retain operational records under their own policies.

Church search and listings use Google Maps Platform. When you search, the text you enter (such as a ZIP code, city, or church name) is sent from our server to Google to find churches; we do not store your search text or ZIP code. Church details shown in the app are fetched from Google when needed and are not stored by One Chapter. If you open the optional map, your browser loads Google Maps directly, and Google may receive ordinary network information such as your IP address under its own privacy policy.

Replit provides hosting, database services, and the secure Twilio connection. Clerk provides the existing login, and Auth0 processes phone authentication when configured. Twilio delivers verification messages through Auth0 and optional daily reminders and friend nudges from One Chapter. These services process information needed for their functions under their own terms and privacy policies.

We do not sell personal information or share mobile information with third parties or affiliates for marketing or promotional purposes. SMS opt-in information and consent are not shared for those purposes. Necessary authentication and message-delivery processing is separate from marketing use.

The optional embedded reader fetches licensed Bible text from API.Bible. When you open it, API.Bible receives a passage-view token and random device and session identifiers for required Bible-usage reporting. Device identifiers are stored in this browser and session identifiers in this tab. One Chapter does not send names, emails, phone numbers, comments, or account identifiers in these reports. API.Bible can also receive ordinary network information, such as your IP address. This reporting is for licensing, not advertising. See API.Bible's privacy information.

Your translation preference is saved for your account in this browser. It does not change the shared chapter or your discussion audience. You can use the external Bible App/YouVersion link instead of the embedded reader; its own privacy practices apply there.

Cookies and security

Personal invite links use a random public code to identify the inviter, not to sign in or grant access to private content. On reading and Connect pages, a signed-in member’s copied browser address may include their own invite code. Share those links only with people you intend to invite.

When you open an invite link, its code may be saved in this browser for up to 30 days so it can survive sign-in. You can skip the friend-request offer. New members who choose to continue send a request only after finishing profile setup; existing members must confirm sending. Invitation records and choices are associated with your account and removed when the account is deleted.

Essential cookies maintain authenticated sessions. The phone integration uses encrypted, HttpOnly server-session cookies; passwords and SMS codes should never be posted in discussions or sent to the host.

The MVP does not include advertising or marketing trackers. Infrastructure providers may maintain their own operational records. No online service can guarantee absolute security.

Retention and your choices

Account and discussion data are retained as needed to operate the group and support security and moderation. The MVP does not have an automatic account-data expiration schedule.

Private login-only phone-consent evidence is kept while your community account exists, including if access is blocked. When your account is deleted, its matching login-consent evidence is deleted with it. If a successful phone verification is not associated with a community account, its evidence becomes eligible for deletion 30 days after verification. Cleanup runs when the API starts and hourly while it is running; overdue records are removed on its next successful run. This housekeeping period is not a legal retention requirement. These records do not enroll you in daily texts, and deleting them does not unlink an existing community account.

You can edit your profile and delete your own comments. When automatic account deletion is enabled, use “Delete my account” in Profile and confirm your account name. This permanently removes your One Chapter profile, authored comments, prayers, Identity content, reading history, friendships, owned groups, and reminder and push registrations. Other authors’ replies are preserved with their existing access restrictions. Account access and new reminders stop when deletion is accepted; a durable cleanup job then removes associated Auth0 login identities, any linked Clerk identity, and uploaded photo files. The deletion receipt distinguishes processing from completed cleanup. Provider outages delay cleanup and are retried automatically; completion is not claimed until all of these steps succeed. Existing photo-upload links must expire before final photo cleanup. Contact the host if deletion is unavailable or remains pending. A sole active host must arrange another host before deleting their account.

Deletion processing temporarily retains only the login identifiers and photo identifiers needed for cleanup, then erases those fields when cleanup succeeds. A receipt without member information is retained for 35 days after completion. Non-reversible login-subject hashes remain for 35 days to reject old signed-in sessions; they are not phone bans. Independent moderation bans are not removed by deletion. Authentication, messaging and infrastructure providers may retain separate security, delivery or backup records under their own policies; account deletion does not erase messages already delivered to recipients or copies they made.

Turn off daily reminders or friend nudges in Profile, or reply STOP to stop texts from the sender. STOP can also prevent login-code delivery when the programs share a sender. Follow the sender’s instructions to opt back in. Do not send sensitive information in support requests.

Phone-search limit records store only the searching member’s identifier and request time, never the searched number. Records older than 24 hours are removed during subsequent phone searches; deleting an account also removes its search-limit records and contact preferences. A dismissible setup reminder is not SMS consent.

Removing or replacing a photo immediately removes its reference from the app. Unused uploads and old photo files become eligible for deletion after one hour. Cleanup processes up to 100 unused uploads at API startup and hourly while it runs; failed deletion attempts and larger backlogs are retried on later runs. Referenced photos remain while in use. Storage providers and backups may have their own retention policies.

Questions and updates

For privacy questions, account requests, or SMS help, email Rmuzljakovich@gmail.com. Never include a password or verification code.

If the way One Chapter uses information changes, this policy will be updated before the new use is introduced.