Privacy Policy
Last updated: 16 November 2026
Bible Feed has no accounts and no sign-in, and never asks for your name, email address or location. What you read, save and write stays on your device. A few things do leave it: a random install ID and a few facts about your trial or subscription, which go to our own server and to the store you buy from, and app events, which go to Meta so we can measure our ads. This page lists each of them, where it goes and why.
Who we are
Bible Feed and biblefeed.app are run by the publisher of Bible Feed, named as the seller on its App Store and Google Play listings (“we”). We are the controller of the data described here. Questions about this policy or your data go to support@biblefeed.app.
What stays on your device
Your reading position, chosen translation, saved verses and notes, the verses you have read, streaks, progress, challenges, reminders and display settings are stored in the app’s own storage on your device. We never receive them, and deleting the app deletes them. Reminders are scheduled by your phone itself, and the Home Screen widget reads its verse from the app on the same device. Your answers to the onboarding questions are kept on the device too, and are never sent to Meta or to us.
The install ID
The first time it needs one, the app creates a random identifier for this installation (a version 4 UUID). It is made from random numbers, not from your device, your name or any account, and it is not linked to your name or email address: we cannot tell who you are from it. Deleting and reinstalling the app creates a new one. It is used in the three places described next: the onboarding request, the trial report and your purchase.
Our server (biblefeed.app)
- Onboarding. Each time the app shows its onboarding (normally once, on first launch), it asks biblefeed.app which onboarding to show. The request carries the install ID, the platform (iOS or Android), the app’s interface language and which kinds of onboarding screen this version of the app can display. The server answers with the onboarding in your language and does not save the request.
- Trial report. When you start a free trial, the app sends biblefeed.app the install ID, the name of the onboarding you saw, the plan, the price and currency the trial renews at, and the screen you started it from. We store this, with the time it arrived, to learn which onboarding leads to trials. Older versions of the app also reported other onboarding and purchase steps; the server discards those without storing them.
Like any web request, these reach our hosting provider with your device’s IP address, which may appear in its request logs. We do not store IP addresses in our database.
Purchases
The Bible+ subscription and its free trial are sold, billed and managed by Apple (the App Store) or Google (Google Play). We never receive your payment details, your name, your email address or your store account. Those transactions are covered by Apple’s Privacy Policy and Google’s Privacy Policy, and you manage or cancel the subscription in your store account settings.
When you subscribe or start a trial, the app hands the install ID to the store with the purchase (as the purchase’s app account token on iPhone and iPad, and as its obfuscated account ID on Android), so that a purchase can be matched to the onboarding that led to it.
On iPhone and iPad, Apple then sends our server a signed App Store Server Notification each time something happens to the subscription: it starts, renews, changes plan, is cancelled, fails to renew, is refunded or expires. Each one carries the install ID with Apple’s transaction IDs, the product, the price and currency, the dates, and the country of the App Store account. We check Apple’s signature and store these notifications to count trials, renewals and refunds for each onboarding. A short summary of each (what happened, the product, the price and our running trial totals, without the install ID or any transaction ID) is posted to a private Discord channel that our team reads, where Discord keeps it under its own policy. When configured, each notification is also passed on, unchanged, to one other service that receives our App Store notifications. Google Play does not send our server anything about your purchase.
Meta (Facebook) App Events
The app includes Meta’s App Events SDK, which we use to tell whether our ads on Meta’s platforms lead to installs, trials and subscriptions, and to improve those ads. It sends Meta:
- Events the SDK logs itself: that the app was installed and opened, and purchases, trials and subscriptions as the store reports them (the product, price and currency, never your payment details).
- Events from the app: that you began the onboarding; that you finished it, with the translation you chose but never your answers to its questions or any date you gave; that the subscription screen was shown; and that a trial or subscription started, with its plan, price and currency. Each event carries the name of the onboarding you saw.
- Device and app information the SDK collects, such as device model, operating-system version, app version, language, time zone and screen size, and an anonymous identifier the SDK creates for the app on your device.
- On Android: your device’s advertising ID, which the SDK reads so that an install can be matched to an ad. You can reset or delete it in Android Settings › Privacy › Ads.
On iPhone and iPad, Bible Feed asks once, with Apple’s App Tracking Transparency prompt at the end of the onboarding, whether it may track you. If you allow it, the SDK may also send Apple’s advertising identifier (IDFA), so Meta can match your install, trial or subscription to the ad that led to it. If you ask the app not to track, the app tells the SDK so and the IDFA is not available to it; attribution then relies on aggregated methods such as Apple’s SKAdNetwork, which report to advertisers without identifying you. You can change your answer at any time in iOS Settings › Privacy & Security › Tracking.
Meta processes these events as described in the Meta Privacy Policy. If you have a Meta account, you can manage how it uses activity from apps and websites in Meta Accounts Center.
Everything else in the app
When you share a verse, your phone hands the text or image to the app you pick, under that app’s privacy policy. Bible Feed shows no ads and includes no analytics or crash-reporting service other than Meta’s SDK. Every Bible text, the commentary and the prayers ship inside the app, so nothing is downloaded while you read.
This website
biblefeed.app runs no analytics and sets no cookies, and its fonts are served from the site itself.
Our hosting provider receives each visitor’s IP address and browser details in order to serve the pages, and may keep them in request logs. The random verse tool draws verses on our server and stores nothing. The admin pages, where we read the counts and notifications described above, are password-protected and used only by us.
Where it is kept, and for how long
- On your device: until you delete the app or clear its data.
- On our server: trial reports and App Store notifications are kept in our database, run by a cloud provider and possibly in a country other than yours, for as long as we offer Bible Feed and need them to count trials, renewals and refunds. They have no fixed expiry today. We delete them sooner when you ask (see below).
- With Apple, Google, Meta and Discord: under their own policies.
If you are in the European Economic Area, the United Kingdom or Switzerland: we use the install ID, trial reports and App Store notifications to provide the subscription you bought and in our legitimate interest in running the onboarding and keeping accurate subscription records; Meta app events in our legitimate interest in measuring our advertising; and advertising tracking on iPhone and iPad only with the consent you give through Apple’s prompt.
Your rights and choices
Depending on where you live (for example under the GDPR in Europe and the UK, or the CCPA in California), you can ask us to give you, correct or delete the personal data we hold about you, to send you a copy, or to stop or limit how we use it, and you can complain to your data protection authority. Write to support@biblefeed.app. We will not treat you differently for asking.
Because nothing we hold is linked to your name or email address, we can only find your records through the install ID or a purchase. Tell us roughly when you started a trial or subscribed, the plan and your country, and we will look for matching records, delete them and confirm. If we cannot tell which records are yours, we will tell you that. Deleting the app removes everything stored on your device, and a reinstall starts with a new install ID.
On your phone you can also decline or turn off tracking (iPhone and iPad), reset or delete your advertising ID (Android), and turn off Bible Feed’s notifications. For data Meta holds against your Meta account, use Meta Accounts Center; for purchase records, Apple or Google.
We do not sell personal information. Sending app events to Meta to measure our ads may count as “sharing” for cross-context behavioral advertising under California law; the tracking and advertising ID settings above limit it.
Children
Bible Feed is not directed at children under 13, and we do not knowingly collect personal information from children. If you believe a child has sent us information, write to support@biblefeed.app and we will delete it.
Changes
If this policy changes, the new version is posted on this page with a new date.