Privacy policy

Your account and preferences

Google sign-in provides a name, a verified email address and an account identifier. Bible Guidance saves the name, email, verification status and an identifier derived from the Google account to recognize you. Bible Guidance does not request access to Gmail messages or Google Drive files, and does not store Google access or refresh tokens.

If you choose Kakao sign-in, Bible Guidance receives your account identifier and, if you consent, your nickname. It saves an identifier derived from your Kakao account and any nickname you share to recognize you. It does not request or store your Kakao email, or retain Kakao access or refresh tokens. Google and Kakao accounts are not automatically merged.

Your language and faith tradition are saved in this browser and, when signed in and synchronization is available, in your account. A faith preference may reveal religious beliefs. You can change it in Settings.

Email sign-in

If email sign-in is available and you choose it, we send your email address and a six-digit sign-in code to Resend to deliver the authentication email. After you verify the code, Bible Guidance saves your verified email address, verification status, an identifier derived from the address and a display name based on the part before @. A Google account and an email sign-in account are not automatically merged, even when they use the same address.

Each code is valid for ten minutes and can be used once. Our database stores a secret-keyed hash of the code rather than the code itself, and the app does not log codes. To protect verification and limit repeated sends, temporary records contain hashes of the browser marker and email address, a keyed hash of the network address when supplied by the hosting platform, timestamps and verification-attempt information. Verification records more than 24 hours old are removed when a subsequent code request is processed; they may remain longer if no further request occurs. This cleanup does not delete the verified account or its usage records.

What you share in a conversation

Your text is sent to the server to search Scripture and prepare an answer. For AI answers, the text, recent conversation, selected language and faith tradition, and relevant passages are also sent to OpenAI for processing. Names, nicknames and email addresses collected for sign-in, including email sign-in, are not added to these AI requests. Avoid including names, contact details or other sensitive information that is not needed to explain your situation.

Bible Guidance does not save the text of your questions or answers as a server-side conversation history. They remain in the page’s memory by default. If you enable history, the latest 20 conversation turns are saved in this browser on this device. You can clear them in Settings or clear the browser’s site data. Clearing local history does not delete your account or usage records.

AI requests are sent with response storage disabled. This setting is not a promise that OpenAI or hosting providers keep no data: their own processing, security logs and retention practices also apply.

Usage records and service security

Bible Guidance keeps the records needed for sign-in, account settings, admission, daily and monthly allowances, request status and AI cost accounting. These include timestamps, session-token hashes, account and browser identifiers, and a one-way request fingerprint for detecting duplicate requests. The fingerprint is not a saved copy of the conversation.

To reduce repeated registrations, the app uses a signed browser marker and, where the hosting platform supplies it, a temporary keyed hash of the network address. These controls do not establish that every account belongs to a different person. Application diagnostics record operational information such as request stages, duration and error categories rather than conversation text.

Cookies and browser storage

Essential cookies maintain your signed-in session, protect the sign-in flow and recognize a browser during registration. Browser storage holds preferences and, only if enabled, local conversation history. Blocking or clearing this storage can sign you out, remove your preferences or affect registration. Bible Guidance does not use advertising cookies or sell access to your conversation for advertising.

Services that process information

Google handles Google sign-in. If you choose Kakao sign-in, Kakao handles that sign-in. Resend delivers authentication emails when you choose email sign-in, as described above. OpenAI processes AI requests. The site runs on ChatGPT Sites and Cloudflare infrastructure, which process requests and the technical data needed to host and secure the service. Information may be processed outside your country. Each provider’s own privacy practices also apply. Bible Guidance does not publish your conversations for other users to read.

Keeping and managing information

Account, admission and usage records are retained to operate the service and enforce its limits; signing out does not erase them or reset your allowance. There is no single fixed retention period for every record. You can contact the operator to request access, correction or deletion of account information, including deletion of a Google sign-in account. The operator will explain any records that need to be retained for security or usage accounting.

When Kakao notifies Bible Guidance that you have disconnected the service, we end your app sessions, delete your stored Kakao profile and account preferences, and remove the Kakao identity from admission and usage records. Usage and cost records and registration safeguards may remain, without the Kakao account identifier. Disconnecting does not guarantee a new allowance or another place in the service. Conversation history saved in your browser must be cleared on that device.

Removing the Google connection does not by itself delete information already held by Bible Guidance. You can stop using the service or clear local history at any time. If you contact support, the information in your email is used to respond. This policy may change as the service changes; its current version and update date are shown here.