Privacy Policy

Effective date: October 3, 2026. Last updated: October 31, 2026. This policy is issued by Westeresch B.V. and covers the Sacred Feed app for iPhone and the website sacredfeed.com.

The short version

  • There is no account and no sign-in. We never ask for your name, email or password to use the app.
  • Your reading history, bookmarks, likes, notes, streaks, reminder time and the faith tradition you choose stay on your iPhone. We do not receive them. Your faith tradition is never sent anywhere, not even to our usage statistics.
  • The built-in Bible and every Deep Study work offline. The app goes online to play audio, to load the licensed translations (NLT, CSB, NKJV) if you choose one, to check its settings and your subscription, and to send a small amount of technical data to a few service providers: usage statistics tied to a random ID (never to your name or reading history), crash reports and, only if you tap Allow in the iOS tracking prompt, an advertising identifier used to see which ads bring new readers.
  • We do not sell or share your personal information. No personal data is ever sent to any artificial-intelligence system.
  • You can export or delete all app data in the app's Settings at any time. To delete data held by our service providers, email .
  • The website sets no cookies.

1. Who we are

Sacred Feed is made by Westeresch B.V., a private limited company registered in the Netherlands. On the App Store the app is listed under the developer name “Lira AI”; that listing is ours, and the seller is Westeresch B.V. Under the EU General Data Protection Regulation (GDPR) we are the controller of the personal data described in this policy. We have not appointed a data protection officer because the law does not require one for a company of our size and activity. For any question about privacy, write to .

Sacred Feed is marketed in the United States first. Because we are established in the European Union, the GDPR applies to everything we do with your data, wherever you live. If you live in the United States, the state-law rights in section 12 also apply to you.

2. No account

You do not create an account to use Sacred Feed. We do not collect your name, email address, phone number, contacts, photos, precise location or payment card details through the app. Because there is no account, there is nothing to log in to and no password that could leak. The only time you give us contact details is when you choose to email us.

3. What stays on your device

Everything personal about how you read stays on your iPhone and is never transmitted to us or to anyone else:

  • your reading history and current position;
  • bookmarks, likes and saved verses;
  • notes you write;
  • streaks and reading-plan progress;
  • your reminder time and notification settings;
  • the faith tradition and Bible translation you choose.

Our commitment about your faith tradition. The tradition you pick during setup reveals your religious beliefs. That is sensitive information under the GDPR (Article 9) and US state privacy laws, and we treat it that way. It is used only on your device, to choose a default translation and the order of the books, and it is never sent anywhere. The app also leaves out anything that would give it away indirectly, such as the number of books in your Bible or switching to a Catholic translation. Earlier versions had an optional switch, “Share my tradition in analytics”. If you turned it on, the current version deletes that information from our analytics the first time it opens.

If you use the app's export feature, the file is created on your device and goes only where you send it. If you delete the app, this data is deleted with it.

4. What we collect

4.1 Through the app

The app sends a limited set of technical data to the service providers listed in section 6. In the category wording used by California law, this is:

CategoryWhat exactlyWho receives it
IdentifiersApple's identifier for vendors (IDFV), a random app-user ID created by our subscription provider, a random device ID created by our analytics provider, a Firebase installation ID, a random reading-report ID used only when you read NLT, CSB or NKJV, and the advertising identifier (IDFA) only if you tap Allow in the iOS tracking promptAdapty, Amplitude, AppsFlyer, Google Firebase, American Bible Society (API.Bible)
Commercial informationApp Store transaction and receipt data: which subscription you have, when a trial or subscription started, renewed or ended. We never see card numbersAdapty, Apple, AppsFlyer (trial start and purchase events)
Internet or other electronic network activityProduct events such as screens viewed, number of verses read, features opened; app version, iOS version, device model and language; crash reports with stack traces and app state at the time of the crash; which chapters of the NLT, CSB or NKJV were displayed (a view count the publishers require, with no reading history attached)Amplitude, AppsFlyer, Google Firebase, American Bible Society (API.Bible)
Geolocation data (coarse only)Country, and for attribution the city, derived from your IP address at the time of the request. The IP address itself is not kept by us; precise location is never collectedAmplitude (country), AppsFlyer (city)
Sensitive personal informationNone. Your faith tradition, reading history, notes and bookmarks never leave your device—
InferencesNone. We do not build profiles about you—

We do not collect your contacts, photos, microphone, camera, health, financial or precise location data, and the app does not ask for permission to.

4.2 Audio and licensed translations

Audio recordings come from our own server, audio.sacredfeed.com. Chapters of the NLT, CSB and NKJV come from our own server, bible.sacredfeed.com, which fetches them from API.Bible without passing on anything about you. Both run on Cloudflare, which processes your IP address and the file requested to deliver it; we do not keep request logs.

The NLT, CSB and NKJV are part of Premium, and their publishers do not allow the text to be copied in bulk. So before bible.sacredfeed.com sends a chapter, the app proves it is a genuine copy of Sacred Feed with Apple's App Attest: a key kept in your iPhone's secure hardware, which Apple confirms belongs to our app. The app also sends your Support ID, and the server asks our subscription provider, Adapty, whether that subscription is active. For each device the server keeps only a random key ID, the key's public half, a counter, a one-way hash of the Support ID and whether a subscription was active. It deletes this record automatically 90 days after it was last used.

Separately, while you read one of those three translations, the app reports to API.Bible which chapters were displayed, together with a random reading-report ID and a random ID for the current session. API.Bible's license requires this so that publishers can count how often their text is read. The reading-report ID is not linked to any other identifier, and Delete my data replaces it. If you never pick NLT, CSB or NKJV, nothing is sent to API.Bible.

4.3 Through the website

  • Server requests. Our host, Cloudflare, processes the IP address, requested page, time and browser of each request to deliver the website and protect it from attacks. We do not keep request logs ourselves.
  • Visitor statistics. We use Cloudflare Web Analytics, which does not use cookies or local storage and does not fingerprint your browser. It records the page URL, referrer, browser type and country.
  • Cookies. This website sets no cookies, first-party or third-party.

5. Why we use this data and on what legal basis

The GDPR requires us to name a legal basis for each purpose. Here they are.

PurposeData usedLegal basis (GDPR Art. 6)
Unlocking Premium, restoring purchases, keeping your subscription in syncTransaction data, IDFV, app-user IDPerformance of a contract, Art. 6(1)(b)
Keeping accounting and tax records of salesTransaction dataLegal obligation, Art. 6(1)(c)
Understanding which features help people keep reading, so we can improve the appUsage events tied to a random device ID, device and app version, countryOur legitimate interest in improving the app, Art. 6(1)(f). Our analytics is set up to have little impact on your privacy: it does not record your IP address, city or Apple's device identifiers, and the data is not shared with anyone for their own purposes. You can object at any time (section 9)
Delivering audio and the licensed translations you chooseIP address, requested file or chapterPerformance of a contract, Art. 6(1)(b)
Reporting views of licensed translations to their publishersReading-report ID, session ID, displayed chaptersLegitimate interest in keeping the license that lets us offer these translations, Art. 6(1)(f)
Changing app settings remotely, for example turning a feature on or offFirebase installation ID, app versionLegitimate interest in a working app, Art. 6(1)(f)
Sending occasional notifications from us, such as a seasonal reading plan or a nudge after a few days awayFirebase installation ID, Apple's push token, and the groups the app joins: subscription status (free, trial, premium) and the date you last opened the appYour permission for notifications in iOS; legitimate interest in keeping you reading, Art. 6(1)(f)
Finding and fixing crashesCrash reports, device model, OS, app stateLegitimate interest in a working app, Art. 6(1)(f)
Measuring which advertising brings new readers (attribution)IDFV, install and purchase events, IP-derived city; IDFA only with your permissionIn the EU, the EEA, the United Kingdom and Switzerland: only with your consent, Art. 6(1)(a), given by tapping Allow in the iOS tracking prompt; without it nothing is sent to AppsFlyer. Elsewhere: consent through the iOS tracking prompt for the IDFA; otherwise legitimate interest, Art. 6(1)(f), limited to counting installs
Answering your questions and fixing reported mistakesYour email address and messageLegitimate interest in helping you, Art. 6(1)(f); contract where it concerns your subscription
Keeping the website secureServer logsLegitimate interest in security, Art. 6(1)(f)
Complying with the law, including age-range signals from Apple (section 14)Only what the law requiresLegal obligation, Art. 6(1)(c)

We do not make any decision about you by automated means that has a legal or similarly significant effect on you. There is no profiling.

6. Who receives your data

We do not sell personal information. We do not share personal information for cross-context behavioral advertising. We work with a small number of service providers (processors) that act only on our instructions and under written contracts. Each is bound to protect your data at least as well as this policy and Apple's App Store guidelines require. Two recipients in the table are not our processors: Apple, which sells and bills the subscription, and the American Bible Society (API.Bible), which licenses the NLT, CSB and NKJV. Each handles the data it receives as an independent controller under its own privacy policy.

ProviderRoleData it receivesRetentionPrivacy page
AdaptySubscription infrastructure, including confirming an active subscription before NLT, CSB or NKJV chapters are sentApp Store receipt and transaction data, purchase history, IDFV, a random app-user ID, device type and locale, and the analytics and attribution IDs (so a Support ID can be matched to them), plus the ad campaign name AppsFlyer reports for the installFor the life of the subscription, then 7 years for accountingadapty.io
AmplitudeProduct analyticsRandom device ID, events such as screens viewed and verses-read count, app version, iOS version, coarse country from IP24 months, then deleted automaticallyamplitude.com
AppsFlyerInstall attributionIDFV, IP-derived city, install and in-app events such as trial start and purchase; IDFA only if you tap Allow in the iOS tracking prompt. In the EU, the EEA, the UK and Switzerland, AppsFlyer receives nothing at all unless you tap AllowRaw user-level data 90 days; aggregated data 25 monthsappsflyer.com
Google Firebase (Crashlytics, Remote Config, Cloud Messaging)Crash reporting, remote app settings and delivering notificationsStack traces, device model, iOS version, app state at the crash, Firebase installation ID, Apple's push token, notification groups (subscription status, date you last opened the app), app version. Crash reports are not linked to your Support ID or any other identifier of yoursCrash reports 90 days; installation data per Google's Firebase termsfirebase.google.com
American Bible Society (API.Bible)Licensed Bible text (NLT, CSB, NKJV) and the view reports its license requiresOnly if you read one of those translations: a random reading-report ID, a session ID, which chapters were displayed, and your IP address as part of the requestPer the American Bible Society's policyamericanbible.org
AppleApp Store billing and distributionYour purchase, handled entirely by Apple under Apple's own privacy policy. We receive transaction records, never card numbersPer Apple's policyapple.com
CloudflareWebsite hosting, delivery of audio and licensed Bible chapters, DNS and cookieless web analyticsIP address and request details while serving the website and app downloads; page URL, referrer, browser type and country for statisticsRequest data is not stored by us; statistics are aggregatedcloudflare.com

We may also disclose data if the law requires it, to protect our rights or someone's safety, or to a buyer if our company is sold, in which case this policy continues to apply.

7. No data is sent to AI

Deep Study notes in the app are written in advance, checked, and shipped inside the app. The app never sends your prompts, your reading, your notes or any personal data to any artificial-intelligence service, ours or anyone else's. Read how our studies are made.

8. International transfers

Our service providers are based in, or process data in, the United States. When personal data leaves the European Economic Area we rely on the EU–US Data Privacy Framework for providers certified under it, and otherwise on the European Commission's Standard Contractual Clauses, with supplementary measures where needed. You can ask us for a copy of the relevant safeguards at .

9. Tracking and your choices

App Tracking Transparency

Soon after you start the app, iOS asks whether Sacred Feed may track you across other companies' apps and websites. If you tap Allow, the app shares Apple's advertising identifier (IDFA) with AppsFlyer so we can learn which ad brought you here. If you tap Ask App Not to Track, no IDFA is shared and attribution is limited to counting installs. If your App Store country is in the EU, the EEA, the United Kingdom or Switzerland, the app goes further: AppsFlyer stays switched off until you tap Allow, and switches off again if you later turn tracking off. Nothing in the app depends on your answer. You can change it at any time in iOS Settings › Privacy & Security › Tracking.

Analytics

Usage statistics are tied to a random device ID, not to your name, and never include your reading history, notes or faith tradition. If you want us to delete the statistics tied to your device, write to us from the app with Settings › Contact support: the email includes your Support ID, which is also shown under Settings › Data & legal › Support ID. You can also use Delete my data in Settings. It gives you a new Support ID, a new analytics device ID and a new reading-report ID, and removes your notification registration. Two identifiers cannot be reset by the app: Apple's identifier for vendors (IDFV) and the AppsFlyer ID; both change only when you delete the app. If you want the data linked to them deleted as well, email us with your Support ID before you tap Delete my data.

Reminders and notifications

Daily reminders are optional, scheduled on your device, and controlled in the app's Settings or in iOS Settings › Notifications. We may also send a few notifications ourselves through Google Firebase Cloud Messaging, for example a seasonal reading plan or a short note if you have not opened the app for a while. They only reach you if you allowed notifications and keep Daily reminder on; turn it off and the app leaves every notification group. They never contain your reading history. Delete my data also removes this registration. No feature requires notifications.

Do Not Track and Global Privacy Control

Our website does not track you across other sites, sets no cookies and uses no third-party advertising. There is therefore nothing to opt out of, and we do not change our behavior in response to a browser's Do Not Track signal. We nevertheless treat a Global Privacy Control signal as a valid request not to sell or share personal information, which we never do in any case.

10. How long we keep data

DataKept for
Everything on your device (reading, notes, tradition, settings)Until you delete it or delete the app
Subscription and transaction records (Adapty)Life of the subscription, then 7 years for accounting and tax law
Analytics events (Amplitude)24 months, then deleted automatically
Attribution data (AppsFlyer)Raw data 90 days; aggregated data 25 months
Crash reports (Crashlytics)90 days
Chapters of NLT, CSB and NKJV on your deviceUp to 30 days after you open them, then refreshed or deleted
View reports for licensed translations (API.Bible)Per the American Bible Society's policy
Device check for licensed translations (bible.sacredfeed.com): random key ID, public key, hash of the Support ID, subscription status90 days after it was last used, then deleted automatically
Website requests (Cloudflare)Not stored by us; Cloudflare processes them to serve and protect the website
Support messages and emailsUntil answered, then deleted within 12 months unless we need them for an open issue or a legal reason
Aggregated statistics with no personal dataIndefinitely

11. Your rights

Under the GDPR you have the right to:

  • access the personal data we hold about you and get a copy;
  • correct inaccurate data;
  • erase your data ("right to be forgotten");
  • restrict processing or object to it, including to processing based on legitimate interest;
  • port your data in a machine-readable format;
  • withdraw consent at any time, for example by turning off tracking in iOS Settings. This does not affect processing that happened before you withdrew it.

How to exercise them. Email . Because we hold no account, the only way we can find data about you with our providers is your Support ID, shown in the app under Settings › Data & legal › Support ID (tap it to copy). Writing from the app with Settings › Contact support includes it automatically. If you plan to use Delete my data, copy the Support ID first: deleting replaces it with a new one. We will answer within 30 days. We may ask a question to confirm that the request really comes from the device owner. We never charge for a request unless it is clearly excessive.

Much of your data you can handle yourself, instantly: Settings › Export my data gives you a copy of everything stored on your device, and Settings › Delete my data erases it and replaces the identifiers described in section 9. See Privacy Choices for step-by-step instructions.

Complaints. If you believe we have handled your data unlawfully, you can lodge a complaint with the Dutch data protection authority, the Autoriteit Persoonsgegevens (autoriteitpersoonsgegevens.nl), or with the supervisory authority where you live or work. We would appreciate the chance to resolve it first.

12. Your US state privacy rights

If you live in California, Colorado, Connecticut, Virginia, Oregon, Texas or another US state with a comprehensive privacy law, you have the right to know what personal information we collect and how we use it; to access it; to delete it; to correct it; to opt out of its sale, sharing or use for targeted advertising; to limit the use of sensitive personal information; and not to be discriminated against for exercising these rights.

  • We do not sell or share personal information as those terms are defined in the California Consumer Privacy Act, and we do not use it for targeted advertising. We have no reason to believe we sell or share the personal information of anyone under 16.
  • Sensitive personal information. We do not collect it. Your faith tradition never leaves your device.
  • Categories collected in the last 12 months are listed in section 4; sources are you and your device; purposes are in section 5; the service providers that receive them are in section 6.
  • How to make a request. Email with the subject "Privacy request" and include the Support ID from Settings › Data & legal › Support ID; writing from the app with Settings › Contact support includes it automatically. We confirm receipt within 10 business days and answer within 45 days, extendable once by a further 45 days with notice. An authorized agent may act for you if they show written permission.
  • Appeal. If we decline your request, we will tell you why. You may appeal by replying to our decision within 60 days; a different person will review it and answer within 45 days. If you remain unsatisfied, you may contact your state attorney general.
  • California "Shine the Light" (Civil Code §1798.83). We do not disclose personal information to third parties for their direct marketing.
  • Global Privacy Control. We honor it as an opt-out of sale and sharing (section 9).

13. Children

Sacred Feed is a general-audience app, suitable for all ages, and is not directed at children. A child reads it the same way as anyone else: there is no account, and reading, notes and faith tradition stay on the device. We do not knowingly collect personal information from children under 13, or under 16 in the European Union, beyond the basic usage statistics and crash reports described in section 4. On Apple accounts for children, iOS normally switches off tracking requests, so no advertising identifier is shared and, in the EU, the EEA, the United Kingdom and Switzerland, AppsFlyer receives nothing. If you are a parent or guardian and want data linked to your child's device deleted, email with the Support ID from Settings › Data & legal › Support ID and we will delete it.

14. Age-range signals from Apple

Where the law requires it (for example the Texas App Store Accountability Act), Apple may make the age range of the account holder available to apps. Sacred Feed does not read this signal today. If we start to, we will use it only to comply with the law, for example by disabling analytics and attribution for younger users, we will not store it beyond what is needed to do so, and we will update this section first.

15. Security

All data sent by the app and the website travels over encrypted connections (TLS). We hold no account database and no payment details, so there is very little to steal. Our providers maintain independent security audits (such as SOC 2). No system is perfectly secure; if we ever learn of a breach affecting you, we will inform you and the authorities as the law requires. To report a security problem, email .

16. Changes to this policy

When we change this policy we update the "Last updated" date at the top. If a change is material, we will tell you inside the app before it takes effect and keep the previous version available on request. We review this policy at least once a year.

17. Contact

Westeresch B.V.
Onlandweg 9
9482 TC Tynaarlo
The Netherlands

See also: Privacy Choices, Terms of Use (EULA), Support, How our studies are made.