Bible Awake
Privacy
Effective and last updated September 5, 2026
This policy explains how Bible Awake handles information when you use the Bible Awake iPhone app, its API, and this public website.
Information kept on your device
Your alarm times, labels and schedules, challenge configuration, selected wallpaper and sound, downloaded scripture content, and language preference are stored locally on your device. Removing the app removes that local app data, subject to normal device backups. Removing the app does not cancel an App Store subscription.
Photo of a Cross challenge
With camera permission, a photo is processed temporarily on your iPhone only to confirm that a capture succeeded, then discarded. It is not saved to your photo library or app storage, uploaded, or collected. This version does not analyze whether the photo contains a cross. If capture is unavailable, you can choose a verse challenge instead.
What we collect
For subscription verification and protected content, our server receives a random app-installation UUID, platform and app version, product ID, and Apple-signed transaction information. We validate it with Apple, then retain hashed Apple transaction identifiers, subscription environment and state, expiration, grace-period and revocation dates, and hashed short-lived access tokens. We do not retain raw transaction JWS values or bearer tokens.
Product and reliability telemetry
Bible Awake may send pseudonymous event and session UUIDs, installation UUID, app/build and operating-system versions, platform, time-zone offset, permission state, generated alarm IDs and configuration categories, scheduling and wake outcomes, challenge type, difficulty and timing, and hashed client-error messages. The telemetry schema rejects high-risk fields such as alarm labels, scripture text, contact details, receipts and tokens. Raw telemetry is configured for deletion after 90 days; deidentified aggregate reports may be kept longer.
Website, API and operational logs
Our IIS-hosted website and API may process IP address, requested URL, date and time, browser or device user agent, referrer, content type, request size and correlation IDs in standard server and error logs. Error records may also contain sanitized exception details. The public site does not include an advertising or public-site analytics SDK, but it loads fonts from Google, so your browser sends Google your IP address and ordinary request headers. A language cookie remembers your site language; authenticated administration areas use necessary sign-in and security cookies.
How it is used
We use information to verify and restore subscriptions across your installations, deliver subscribed content, operate and secure Bible Awake, diagnose failures, answer support requests, measure reliability and improve the service. We do not sell personal information or use it for targeted advertising.
When information is shared
Apple processes purchases, billing, cancellation and signed subscription records under Apple's terms and privacy policy. Hosting and infrastructure providers process data to operate the website and API, and Google receives web-font requests as described above. We may disclose information when required by law, to protect users or the service, or as part of a business transfer subject to appropriate safeguards.
Retention
Raw telemetry is retained for up to 90 days under the current server setting. Subscription and installation records are kept while needed to provide access, support restores, prevent fraud and meet legal obligations. Notification idempotency records, aggregate metrics, support correspondence and security/error logs are kept only as reasonably needed for those operational, support, security and legal purposes. Backups may retain deleted records until their normal rotation completes.
Your choices and deletion requests
You can change permissions in iPhone Settings, cancel or manage the subscription through Apple, and remove device-local data by deleting the app. To ask for access, correction or deletion of server-side information, email support. We may need an installation identifier or support details to locate records, and may retain limited information where law, security, fraud prevention or an unresolved transaction requires it. Deidentified aggregate data cannot be linked back to an installation.
Security
We use transport encryption, cryptographic verification of Apple-signed data, certificate-chain validation, hashed tokens and transaction identifiers, access controls, and redaction rules. No system is perfectly secure; contact us promptly if you believe your information or Bible Awake access has been compromised.
Children
Bible Awake is not directed to children under 13, and we do not knowingly collect personal information from a child under 13. A parent or guardian who believes a child provided information should contact us for deletion.
Changes to this policy
We may update this policy as Bible Awake or legal requirements change. We will post the revised policy here and change the effective date; material changes may also be announced in the app.
Contact
Contact Bible Awake support with privacy questions or requests: