Privacy

Affelion Bible is an English-language app. This policy covers the App Store version for iPhone and iPad and the Google Play version for Android. Your journal, prayer and reflection text stays in the app’s storage on your device. The app never sends that text to Affelion, RevenueCat, Apple or Google for billing. You choose whether to save your writing and whether to export a copy.

What stays on your device

Your saved writing, pins, follow-up links, linked Scripture references, bookmarks, study progress, reading position and preferences are stored locally. Affelion does not provide end-to-end encryption or an app passcode. Use your device lock, especially on a shared device.

Purchases and access checks

If you have never opened purchase options or tapped Restore purchases, and this device has no recorded purchase activity or confirmed restore, the app does not start RevenueCat or send data to the purchase service. You can read the Bible, complete the first study, pray and use your journal without starting it. Opening Settings alone does not start it.

When purchases are enabled in your build, the app sends purchase-service data only after you open purchase options, start a purchase, or restore. These actions start RevenueCat and may contact Apple for App Store purchases or Google for Google Play purchases. Purchase options include View library access and a locked study’s purchase screen. Before opening the store payment sheet, the app saves a small purchase-activity flag only on this device. Later launches and resumes check purchase status, so a deferred payment approved while the app is closed can give you access when you return. Cancellation keeps this flag. A confirmed restore also sets it; merely viewing prices or a restore that finds no purchase does not. Cached information can sometimes be used while offline.

Once started, the purchase SDK can continue its own requests during that app session, including after returning from the background. Leaving the purchase screen does not shut it down. If you only viewed purchase options and did not start a purchase or confirm a restore, the next cold launch leaves it off until you open purchases or restore again. Erase clears the local flag; fully close and reopen the app to end an already-started purchase session. This purchase-service promise does not cover exports you choose, external links, store/operating-system services or device speech.

Apple handles App Store payments; Google handles Google Play payments. The store you use receives your purchase or restore request and processes its store account, payment, device and connection information under its own privacy policy. RevenueCat receives purchase records to verify access and provide purchase reports to Affelion. These include product and transaction identifiers, receipts, signed transaction records or Google purchase tokens, purchase dates and status, price, currency, store country, and restore or refund information when available. The app does not receive your full card details or store password.

RevenueCat assigns a random app user ID, shown in Settings as your purchase support reference. RevenueCat links purchase records and technical information to this ID. A reinstall or restore can change or link purchase references. The ID contains no writing or email address, but it is not a guarantee that purchase records cannot be linked to you, especially if you send it to support.

Technical information used for purchases

RevenueCat receives the device model and operating system, app version and identifier, SDK versions, language and locale, store country and purchase currency. Requests also include technical details such as whether the app is in the background, whether it is a test build, and request, cache and verification information. RevenueCat records when the purchase profile was created and when it last connected.

On iOS, the SDK also sends Apple’s vendor device identifier (IDFV) and the current tracking-permission status, with its update time. This status check does not request permission or turn on tracking. Affelion does not set email, name, phone, advertising or custom customer attributes in RevenueCat. We explicitly disable the SDK’s optional collection of device identifiers for advertising attribution. The app does not collect Apple’s advertising identifier (IDFA).

On Android, this purchase SDK configuration does not collect Google’s advertising identifier (GAID) or Android ID (ANDROID_ID). During a purchase, Google Play receives a one-way hashed version of the random RevenueCat app user ID as a purchase account reference. It is not your journal or prayer text.

RevenueCat’s servers receive the connection’s IP address. RevenueCat says it derives a country from the address and then drops the address. The country can remain on the purchase profile; the app does not request GPS location.

The app sets purchase diagnostics to off. The installed iOS SDK does not enable its optional diagnostics stream with this setting. The audited Android SDK can override that setting through RevenueCat’s remote configuration. If enabled, it can send diagnostic events containing event and session identifiers, timestamps, Play Store and Play Services versions, product and purchase status, request and cache state, response times, verification results and error codes or messages. The normal technical request information also accompanies those events. These diagnostics do not contain your writing.

How purchase information is used

Purchase-service requests use encrypted HTTPS connections. RevenueCat uses purchase records, the app user ID, country and connection activity for course access, restores, fraud prevention, support and purchase reporting. In Apple’s privacy categories, these purposes are App Functionality and Analytics. The iOS vendor device identifier and remaining technical information support App Functionality. Conditional Android diagnostics support purchase functionality and performance analysis. These records are linked to the purchase profile or device; a randomly assigned ID does not make them unlinked data.

There are no ads in Affelion Bible, and the app does not use purchase data for advertising or tracking across other companies’ apps. Affelion does not send reading, prayer or journal activity to an analytics service. Purchase reporting does not include your personal writing.

Read RevenueCat’s privacy policy (www.revenuecat.com/privacy-policy) and Apple’s App Store privacy information (www.apple.com/legal/privacy/data/en/appstore/) and Google’s privacy policy (policies.google.com/privacy) for their handling of purchase data.

Backups and Erase

An exported backup contains readable personal writing. The destination you choose receives that copy, so save it somewhere private. Large backups have numbered files; keep all parts together when importing. Older single-file backups up to 20 MB are supported.

Erase in Settings removes local writing and app-owned temporary export files only after cleanup succeeds. It does not delete backups you deliberately saved elsewhere or purchase records held by RevenueCat, Apple or Google. On iOS, the app attempts to remove temporary export copies when sharing ends. It also checks for leftover copies when it starts or prepares another export. If cleanup fails, the app reports the problem. On Android, a temporary copy can stay in Affelion’s private cache after the share sheet closes so a receiving app has time to read it. The app attempts cleanup at the next startup or resume when no share is pending, before the next export, and during Erase. If removal fails, the app reports it instead of saying the data was erased.

On launch, the app asks iOS to exclude its writing storage from system backups. On Android, the app disables automatic backup and supplies rules excluding its app storage from cloud backup and device transfer. Keep your own exported backup; do not rely on device backup or transfer to preserve your writing. Browser preview storage belongs to that browser profile. Clearing it or uninstalling can remove your writing.

Support and deletion requests

Contact hello@affelion.com for purchase help or to request access to or deletion of billing information. In Settings, use Copy purchase reference and include it with your request. Before billing has started, the field says “Available after you open purchases”; opening Settings does not create or fetch an ID. Open View library access or use Restore purchases if you need a reference. We receive your email address and the support information you choose to send. For a Google Play refund investigation, we may also ask for the relevant Google Play order ID to find the transaction, without a full receipt screenshot or payment details. Do not send prayer, journal or reflection text, passwords or full payment-card details.

Purchase information is kept as needed to maintain and restore access, resolve support requests, prevent fraud and meet applicable recordkeeping duties. A deletion request is reviewed and verified before eligible RevenueCat records are removed. Apple and Google retain their own store transaction records under their privacy policies. Deleting a RevenueCat profile does not refund a purchase; a later app connection or restore can create records again. Support will explain any records that must be retained. The course is a one-time purchase with no subscription to cancel.

Read aloud and external links

Scripture is read aloud with your device’s voice. Personal writing is never sent to the speech service. Voice availability and network use depend on your device settings. Links to other services open under their own privacy policies.

Public privacy and support pages

Our public privacy and support pages are hosted on Replit. Replit may process visit and connection information, such as IP addresses, browser and device details, and pages viewed, and may use cookies or similar technologies under its own privacy policy. See https://replit.com/privacy-policy.

Contact

Affelion LLC · hello@affelion.com.

Effective October 19, 2026. We will update this page if our practices change.