Privacy Policy

Last updated: October 28, 2026

This policy says what Your Bible App collects about you, why, who else touches it, how long we keep it, and how to make us delete it. It is written in plain English on purpose.

The app is not on the App Store yet: only our own testers use it, and no customer information exists. This policy describes how the app is built to work, and the date above will change if the wording does.

The short version

• We do not sell your information. Not to anyone, for any price.
• We do not currently show adverts in the app, and nothing you do here is used to aim adverts at you anywhere else. We are not promising that forever. If it ever changes, this page changes first and we tell you before it happens, not after. A subscription lists "No ads" as one of its benefits. Today nobody sees ads, whether they subscribe or not.
• We advertise the app, and we measure which adverts lead to downloads. The app never asks to track you and never reads your device’s advertising identifier. See Our adverts.
• Our server never keeps which book or chapter you read in the Bible tab. Your reading history, your favorite verses and what you mark as read are kept on your device only, and are never sent to us. If you press Play to hear a chapter of the BSB, the recording comes from our file storage at Supabase, whose own service log notes which chapter was fetched, and from which internet address, for 7 days. It never carries your account. For the NLT and the NASB 2020, the service that supplies them, API.Bible, learns which chapter was shown, and from which internet address, under a random code that is not your account. See Reading the Bible.
• Your sessions are for you alone. If you write down a Bible study or a sermon in the Sessions tab, it is kept with your account so that you can see it on any device you sign in on. Nobody else sees it in the app. Its place is only ever a name, never your device’s GPS position. See Sessions.
• Friends is off unless you turn it on. If you do, someone can ask to be your friend only by typing your exact username, and nothing is shared until you accept. Your friends see your username, your stars this week, your streak, and your streak together with them. Unless you hide them, a friend who taps your name also sees your stats: your current and best streak, how many units you have completed, how many studies you have finished, how many with Section 1 finished and how many with Section 2 finished, your highest section, how many Section Exams you have passed, your Progress Points and your stars. There is no search list, no contacts, no feed, no comments and no messages. Nothing about you is public unless you choose it. Your stats are public only if you pick Everyone, and so is the username you chose. The app has no public places today.
• We never see your card details. Apple sells the subscription and Apple takes the money.
• You can delete everything we hold about you from inside the app. An anonymous record of any payments stays. See Delete your account.
• You must be 13 or older. The age check below explains how we check, and what happens if the App Store tells us something different.

Who we are

Your Bible App, operated by Joel Malone (sole proprietor), Texas, USA. A sole proprietor is a one-person business. You can reach a person at support@yourbibleapp.com.

What this policy covers

It covers Your Bible App, on every device it runs on, and this website. There is no web version of the app and there is no sign-in on this website.

What we collect

• How you sign in. An e-mail address, a phone number, or a Sign in with Apple or Sign in with Google identity — whichever you choose. There are no passwords in the app at all, so we never hold one. If you use a phone number, it is only for signing you in: it goes to Twilio, which texts you a one-time code, and we keep it and delete it the same way as your other sign-in details.
• Your answer to the age question and the date you answered it. The app asks whether you are 13 or older the first time you open it, and again after anyone signs out on that device. What we store is a yes or a no, that date, and whether Apple's age check confirmed the yes or could not be made — never your age, never your date of birth, never the age bracket Apple reports. Friends asks one more yes-or-no question about your age, described under Friends.
• Your study record. Which studies and units you have studied, the studies you added to your list in the app, when you added each one and when you last chose it, when each unit started and finished, the answers you gave and how long each one took, your scores, stars and streaks, the badges you have earned and the day each was earned, the points you have earned, and how recently you were active. If you take a Section Exam, it also holds when you started and handed in each attempt, whether you left it part-way, your final answer to each question, whether it was right, when you answered it and how many times you changed it, and the attempt's score, stars, result for each part of the exam and whether you passed. If you earned coins while coins were switched on, it also holds those coins and the studies you unlocked with them. Coins are switched off now: no unit earns any, and nothing is locked behind them. This is the part we treat as sensitive; it has its own section below.
• Your energy. Your energy balance and the moment it was last worked out. For each unit, the energy it used and gave back, when it was played, whether a subscription covered it, and whether you stopped because you ran out. For a unit you finished, how long it waited for energy. For each Section Exam you start, when it started, the energy it used, and whether a subscription covered it. Practice rounds are switched off now: the app offers none, so no new one is recorded. For each practice round played before, when our server received it, how many questions it asked, whether you finished it, whether a subscription covered it, the energy it used and gave back, and the day any energy it gave back counted toward. All of it is in Energy and unit times below.
• If you use the Bible tab: a count of how many requests your device made through our server each day, for Bible text or for the list of translations and books. Never which chapter or which translation. All of it is in Reading the Bible below.
• If you write sessions: what you write in each one — its type, when it started and ended, its place, the passages, your notes, and any title and speaker or leader you add — and when you saved and changed it. Sessions need an account. All of it is in Sessions below.
• Your time zone, and when it changed, so that each unit counts on the day you played it — including while you travel.
• Your approximate place: the city, state, zip code and country your internet address points to. Once a lookup has worked, it is not done again for 30 days; if one fails, the app tries again at most once a day until one works. See below.
• Your reminder settings. Whether unit reminders are on; whether offers and announcements are on, and when you last turned them on or off; the reminder time saved for you (a default time if your reminders are Automatic); whether your device allowed notifications from the app, and when the app first asked. The daily reminder itself is set on your device and shown by your device, in your device's own time zone. We do not send it, and nothing about a reminder being shown reaches us. If you open the app by tapping one, the app records that, and whether it was a daily reminder or the note saying reminders will pause. If your reminders are Automatic, which they are unless you pick a time, your device works out the time from when you last finished a unit, and that choice stays on the device. A reminder appears on your lock screen under the app's name, and some reminders give your streak, such as "Day 3 is waiting". Anyone who can see your lock screen can read it; your device's notification settings can hide previews.
• Your subscription. Whether you are on a free trial, paying, lapsed or refunded; the periods Apple has sold you; the identifiers Apple uses for your purchase; and the messages Apple sends us when your subscription renews, fails, is cancelled or is refunded. We never see your card details. Apple takes the payment, not us.
• If you play as a guest without making an account: a random identifier that our sign-in service at Supabase makes for this device and that your device keeps, plus the same study record. It is not linked to your name, your e-mail or your phone number.
• Your device and when you got the app. The app sends our server your device's model, the app's build number, and the date you first downloaded the app from the App Store, and we keep them with your profile. It sends no country from the App Store.
• Crash reports when the app fails (see the next item), and a short, fixed list of usage events. In plain words, these are:
  • the app opening, and the age question being shown and answered yes;
  • which screens of the app you move between, in what order, and how long each was open — never the Friends or Sessions screens: time on either counts as time on the screen you opened it from, and coming back to that screen is not counted as a new visit — and the app going into the background;
  • a request to our servers that failed, or took two seconds or longer: which kind of request it was (such as downloading units), how long it took while the app was open (a request cut off while the app was in the background is not counted as failed), the answer code it got, and the screen it came from — never its address or anything sent in it, never a Friends request or a reading report, and nothing while Friends or Sessions is open;
  • the paywall appearing, and which screen or reason opened it, such as running out of energy;
  • a purchase or a restore starting, being recorded, cancelled, still finishing with Apple, or failing;
  • a free trial starting, and the subscription being checked or changing state;
  • a unit being started, completed, abandoned or repeated;
  • a study opened, a question answered or reported, a game shown, a verse-recall step, and content synced;
  • a question's Scripture section being opened, which game the question was shown as, and whether it was opened before or after answering;
  • your streak starting, growing, breaking or being protected by us;
  • a badge being earned, and your daily unit goal being set or reached;
  • the notification question being answered, the reminder switches and hour you choose, and the app being opened from a reminder;
  • a chapter being shown in the Bible tab;
  • a study being added to your list, and how many studies the list then holds.
  When the app first opens, it records the first screen being shown, and how you left it. In your first three new units it also records:
  • you opening the Learn screen yourself;
  • how many seconds your first answer and each unit took;
  • which question you left a unit on.
  It also records the card under a unit's result being shown or tapped, and signing in, signing out, and asking to delete your account. Here is the whole list, by the names the app uses. It sends no other event, apart from the message that tells PostHog the code described below, and the taps described after this list. PostHog's own library also adds to every event whether the device is a phone or a tablet, the app's version and build number, the device's model (such as iPhone 15 Pro), the name and version of its operating system (iOS), the screen's width and height, the library's name and version, the name of the app screen on show (never Friends or Sessions: our analytics service records nothing while either is open), a random code for the current app session, which it replaces each time the app starts and after 30 minutes without use, and three settings of its own: whether this installation has been sent the code described below yet, whether PostHog keeps a profile for it, and an instruction not to work out where you are from your connection. A tap also says that it was a touch. The app uses no PostHog feature flags, so it never asks PostHog for any and none are added. It does not add your device's language, its time zone or where you are. Nothing at all is sent to PostHog until the age question has been answered 13 or over on that launch.
  • Opening: app_opened guest_session_started age_gate_shown age_gate_passed.
  • Screens: screen_viewed app_backgrounded.
  • Requests to our servers: server_call_failed server_call_slow.
  • First minutes: first_run_shown first_run_start_chosen early_learn_opened early_first_answer early_lesson_finished early_lesson_left after_lesson_card_shown after_lesson_card_tapped.
  • Paying: paywall_shown purchase_started purchase_recorded purchase_failed purchase_cancelled purchase_awaiting_apple restore_started restore_recorded restore_failed subscription_state_changed trial_started entitlement_status_read entitlement_served_from_cache manage_subscription_opened.
  • Units: lesson_started lesson_completed lesson_abandoned lesson_repeated collection_opened item_answered item_reported experience_shown content_synced content_sync_failed recall_started recall_scored recall_near_miss recall_attribution_shown scripture_opened.
  • Streaks, badges and goals: streak_started streak_extended streak_broken streak_freeze_active achievement_earned daily_goal_set daily_goal_met.
  • Reminders: notification_permission_asked notification_toggle_changed notification_time_changed reminder_opened.
  • Signing in and your account: anonymous_sign_in_succeeded anonymous_sign_in_failed bootstrap_blocked profile_ensured sign_in_started sign_in_succeeded sign_in_failed identity_linked sign_out apple_revocation_token_stored apple_revocation_token_not_stored account_deletion_shown account_deletion_requested account_deletion_failed account_deletion_cancelled.
  • Reading: chapter_read.
  • Studies: study_added.
  Each event records that the step happened, the details PostHog's library adds (above), and at most these, nothing else:
  • a state name or an outcome word (for a change, the one before and the one after);
  • a count, or a number of seconds;
  • the hour you chose for a reminder;
  • the name of a badge;
  • the identifier of a unit, study or question;
  • the Bible translation a chapter was shown in: BSB, NLT or NASB2020;
  • the name of a screen, from the app's own fixed list;
  • whether a purchase was an Apple test purchase, yes or no;
  • the kind of a request to our servers, its method and answer code, and a number of milliseconds.
  It never records your name, your e-mail, your phone number, your account, Apple's transaction identifier, your age, whether your "Show the teaching before each unit" switch is on, which book or chapter you read, or anything you typed.
• Your taps. PostHog records each tap in the app, with the names of the parts of the app you tapped, which kind of control it was (by the name our code gives that control's words, never the words themselves, and only when that name belongs to one kind of control), and the screen it was on. To find that name, the app reads on your device the words VoiceOver would say for the control; those words are never sent. It never records the words on the screen, anything you type, or where on the screen you tapped. Taps are not recorded at all on the age question, the welcome screens the app shows before your first unit, Friends and everything it opens, the line on Home about a streak you share with a friend, the Bible tab, signing in, deleting your account, the subscription sheet, the sheets for reporting a question or a problem, the "Show the teaching before each unit" switch, editing your username on Profile, who can see your stats & progress in Settings, an arcade game's play area, a Sort or Related board, or Recall's drag-to-order rows (a swipe, a drag or a tap on the board itself), or in any box you type in. Taps on answer choices, Match tiles and Tap in Order rows are recorded like any other tap: never the words and never where you tapped, though a True or False tap says which of the two buttons it was. The app never records the screen itself: there are no screen recordings.
• Crash reports, freezes and how fast screens load, sent to Sentry. Nothing at all is sent to Sentry until the age question has been answered 13 or over on that launch, and nothing ever from a device that answered under 13, so a crash before that answer is not reported. After it: a record of each time you use the app (when it started, how long it lasted, and whether it crashed), so we can count crash-free use; a report when the app crashes, when it freezes (stops responding for two seconds or more), when iOS closes it because it stopped responding or used too much memory, or when the app could not start because of a problem on our servers (the kind of problem, the server's status number, which step it was, and the first 120 characters of the server's own error message, with any e-mail address, code, key or internet address taken out); and, for every screen you open, how long that screen took to appear and to show its content, how long the app took to start (not measured when the app asked your age first), whether it stuttered, and how long each request to our servers made while it loaded took, by the kind of request only. While you answer questions, Sentry also receives how long the app took to show the result of each answer and to bring up the next question or the unit's results, which kind of question it was, and whether the screen stuttered meanwhile — never which answer you chose, whether it was right, or the question itself. Each report names the app screen it came from and the screens and kinds of request just before it, from the app's own fixed lists — the screen can be Friends, but Friends is never named among the screens before a report — and carries technical details of the device and the app: its model and model code, its processor type and how many processors it has, its iOS version and build and the version of iOS's core, whether it is a simulator, whether it has been jailbroken, how much memory it has and has free, its screen size and which way up it is, whether Low Power Mode is on and whether it is running hot; the app's name, bundle identifier, version and build, when it started, how much memory it was using, whether it was in front, which over-the-air update it runs and on which channel, and technical settings of the app's framework (such as its React Native version and its project code at Expo, the company whose tools build the app). A crash or freeze report also carries the step-by-step state of the app's code when it happened, and the list of code libraries the app had loaded and where on the device they are stored. Sentry also receives three codes: a random code it makes for this installation of the app, so it can tell how many devices a problem touched; a second code worked out from the one your device gives each app maker (Apple's identifier for vendors), the device's model and the app's identifier; and a random code Expo makes each time the app starts. None of them is your account, and none is ever linked to it. Reports made in the part of the app that cannot filter them — crashes, freezes, and iOS closing the app — also carry your device's language and region setting (such as en_US). A freeze report also carries the device's time zone, its calendar, whether it shows a 24-hour clock, the name of every part of the app that was running at the time (its threads), and the names our code gives the views on its screens. Sentry never receives your name, your e-mail, your account, anything you typed (apart from a problem you report, next), or a web address the app visited: the app keeps only the kind of request, such as a unit download, and never records a Bible reading request, a request for a chapter's notes or an article, or a change to your username or who can see your stats & progress, there at all. On Friends Sentry receives the same as on any other screen — how fast it loads, whether it stutters or freezes, its crashes and errors, when the app was in use, and each request Friends makes that fails or is slow, including the app's check for new friend requests, by its kind only (such as reading your leaderboard or reporting a friend), with how long it took and the answer it got (never Friends' own answers such as "sign in first") — and never who your friends are, anyone's username, who asked to be your friend or whom you asked, your leaderboard or streaks, a report's reason or words, what you type or what you tap; the words of an error in the app's own code there are never sent (see Friends).
• A problem you report from Settings ("Report a problem"): the words you type, the screen you came from and the one before it, and the technical details above. It goes to Sentry, never to our analytics service, and it is not tied to your account. There is no box for your e-mail: if you want a reply, write to the support address the sheet shows.
• One code that says "this is the same person as last time". The app sends our analytics service a single random string, so that two visits by one person are not counted as two people. It is the random identifier our sign-in service made for your account — or, if you play as a guest, for this device. Deleting and reinstalling the app does not change it: your device keeps the app's sign-in in its Keychain, so a guest who reinstalls the app on the same device is still the same guest. After you sign out, this device starts again as a new guest, with a new one. If the account on this device changes, for example when a guest signs in to an account they already had, the message that tells PostHog the new code also carries an earlier code from this device, once. This is the one identifier tied to your account that deliberately leaves the device, and it is written here rather than buried in a footnote because it is the exception. The Bible tab's random reading code also leaves the device, but it goes only to API.Bible and is never tied to your account; see Reading the Bible.
• Anonymous totals. How often a question is answered correctly across everyone, and how many requests for Bible text everyone made together each day and each month. No person is attached to these and they cannot be traced back to you.
• A report you send about a question. The question, your answer, and any words you type.
• Which advert, if any, led to your download, once the age question has been answered 13 or over. For an Apple Ads advert, Apple tells us the campaign, ad group, keyword and advert, the country or region, whether it was a first download or a redownload, and whether you tapped the advert or only saw it. AppsFlyer tells us whether it counts your install as organic (not from an advert), and the advert’s source, campaign, ad set and keyword. We keep this with your profile. All of it is in Our adverts below.
• If you turn on Friends: that you turned it on or off and when, which version of the Friends text you agreed to and when, your answer to the Friends age question (a yes or a no), your friends list, the friend requests you sent and those sent to you (who asked whom, and when) until each one ends, when you sent each request (not to whom) for 7 days, the people you blocked, any report you make about a friend with the reason and your words, any report a friend makes about you, and the fact that someone blocked you. If we switch Friends off for you, we keep when and why. All of it is in Friends below.
• Your profile settings. For every player, guests included, we keep who can see your stats & progress (Everyone, Friends or Only me; Friends unless you change it), and a random name such as "Reader 4821" that the app no longer shows. Once you are signed in, the app gives you a username, and you can choose your own; we keep both and when you chose it. To stop anyone testing names, we count how many names you check, and how many you generate, in an hour. We never keep the names you checked. All of it is in Your profile below.

Nothing at all is recorded on our servers when somebody says they are under 13. No event, no row on our servers, no e-mail address. The app refuses on the device itself, and nothing about the answer leaves it. Like every copy of the app, it still checks with Expo for app updates each time it opens (see Expo below); that check says nothing about age. The device itself remembers one thing so it does not have to ask again every time you open it: the date to ask again, about a year later. That date is kept on the device, can be copied into your device's encrypted backups, and is never sent to us.

The app never asks for your device’s location services, except when you tap Use my location in a session, in versions of the app that have that button: that tap is the only thing that can bring up your device’s location prompt, and even then the app keeps only a place name, never the position (see Sessions). Our website host, which already serves our pages, tells our server the city, state, zip code (approximate) and country your internet address points to — often your internet provider’s, not yours. Once that lookup has worked, the app does not ask again for 30 days; if it fails, the app tries again at most once a day until it works. We compare the place with your device’s time zone. If they agree, or if we have no time zone to compare with, we keep the city, state, zip code and country; if they disagree (a VPN, for example) we keep only your time zone’s region and country. We never keep the address itself; our host’s own request log holds it for a short time, as for any page it serves (see Vercel below). We keep one place per account, replace it at most every 30 days, and delete it with your account. We do keep your device’s time zone and when it changed (above). A time zone names a broad region, such as America/New_York, so it shows roughly the region you are in — never where you are within it. If an Apple Ads advert led to your download, we also keep the country or region Apple reports for it. We do not collect your contacts, your photos, your health data or your card number, and the app does not ask for any of those permissions. We do use ad-measurement software, AppsFlyer, to learn which advert brought you here, and AppsFlyer works out roughly where your device is from its internet address; see Our adverts.

Some things stay on your device. Earlier versions of the app had a Settings switch, "Show the teaching before each unit". The app no longer shows it, or any teaching screen before a unit, but a device that set it keeps that setting on the device only, and we never receive it. Earlier versions of the app also asked whether you had studied the Bible before; that answer only set this switch. The switch is never copied into an iCloud or computer backup and never moves to a new device, though it stays on this device if you delete and reinstall the app. The streak target you pick and whether your reminders are Automatic are never sent to us either; they are kept in the app's secure storage, which can be copied into your device's own encrypted backup. The Home Screen widget, if you add one, shows your streak and whether today's unit is done to anyone who can see your screen. The app keeps those two facts, with the date they are for and when they were written, in a small shared space on your device for the widget, whether or not you add one; it is emptied when you sign out, and it can be copied into your device's backups. Nothing extra is sent. The Bible tab keeps your place in the Bible, your Day or Night page choice, the last 10 chapters you opened, your favorite verses and what you mark as read on this device only, never in a backup; see Reading the Bible.

How we collect it

• From you, when you type it into the app.
• From your device: the guest sign-in it keeps, your time zone each time it changes, your device's model, the app's build number and the date you first downloaded the app, and what your device answered when the app asked to show you notifications.
• From Apple: when you start a trial, buy, renew, cancel, or are refunded, Apple tells our server. Apple also answers the age-category question described in the age check below, and, if an Apple Ads advert led to your download, which advert it was.
• Automatically while the app runs: crash reports, freezes and screen load times; usage events and taps; your energy, from the units and Section Exams you play; and, when you choose or read the NLT or the NASB 2020, the daily count of your requests for Bible text.
• From API.Bible: nothing about you. It sends our server the Bible text that was asked for, and our server never tells it who asked.
• From our website host, Vercel: the approximate city, state, zip code and country of the internet address the app’s request came from: once it has worked, not again for 30 days; if it fails, at most once a day until it works. Never the address.
• From AppsFlyer, through the app: whether it counts your install as coming from an advert, and which one. See Our adverts.
• From Apple’s map service, only when you tap Use my location in a session, in versions of the app that have that button: the name of the place your device is at. Never the position itself. See Sessions.

This website collects nothing. See This website below.

How we use it

• To sign you in and keep you signed in.
• To store your study record and show it back to you.
• To decide which unit to put in front of you next, from what you have already answered. That is unit ordering and nothing more: no person and no AI makes any other decision about you, and nothing in this app decides anything about a person automatically.
• To work out your energy: what each unit and Section Exam uses and gives back, and unlimited energy while you subscribe.
• To measure, across everyone and with no person named, how long units take and how often their questions are missed, so we can tune unit length and difficulty.
• To show you the Bible text you open in the Bible tab, the notes, articles and related verses that go with it, and the verses on your Favorite Verses page, to keep reading within the daily limits of our Bible text plan, and to let API.Bible count how often each translation is shown, which its terms require.
• To keep the sessions you write and show them back to you, on any device you sign in on.
• To work out whether you are a subscriber, and to restore a purchase.
• To see roughly where our players are, so we know where the app is used.
• If you turn on Friends: to pass a friend request to the person you asked, to show the friends you connect with what the Friends section lists, and to deal with a report about a friend.
• To show your username to your friends, and your stats and the name you chose to the people your setting allows.
• To answer you when you write to support.
• To find and fix crashes, freezes, slow screens and faults, and to look into a problem you report.
• To see which parts of the app are used, and how people move through them, so we know what to improve.
• To learn which of our adverts lead to downloads, free trials and subscriptions, so we spend on the ones that work. We use it to measure our adverts only, never to aim an advert at you.
• To keep the records a business has to keep, such as records of what was sold.
• To meet a legal duty, or to protect the app, our users, or ourselves from fraud or abuse.

We do not sell your information. We do not use it to aim adverts at you, we do not build profiles of you for anyone else, and we do not send you marketing texts. Its one advertising use is measuring our own adverts, set out in Our adverts.

Your study record, and the agreement we ask for

This is a Bible app, so we have to be straight about this. Using this app does not tell us what you believe. We do not ask your religion, we do not ask you to declare one, and we do not assume one. People study the Bible for many reasons.

What we hold is a record of which studies and units you have studied, and any Section Exams you took, with the answers you gave, how long they took, your scores, your streaks and your badges, tied to your account. We keep it to show your progress back to you, and to decide which unit to put in front of you next. It also works out your energy, because each question you answer in a unit uses some, and so does starting a Section Exam. And, counted across everyone with no person named, its unit times and missed questions tell us how long units take and how hard they are, so we can tune them. If you turn on Friends, or choose to share your stats, what Friends and Your profile below list is worked out from it and shown to the people you chose, and nothing else from it is; see Friends and Your profile below.

We treat that record as sensitive information, because a record of what a named person studies in a Bible app can say something about their beliefs. So we ask you before we collect it, not after. That is the rule we hold ourselves to, and we would rather ask twice than assume.

So we ask before any of it exists. The first screen the app ever shows you is the age question, and under it is the line "By continuing, you agree to our Privacy Policy and Terms of Use." Your study record begins after you confirm your age and continue past the notice on that screen. There is no study record before that moment, because there is nothing to record until you play. Whatever you decide later, these rights stay yours: you can ask us what we hold, ask us to correct it, and ask us to delete all of it, and we will never treat you worse for asking. They are listed under "Your choices and how to change your mind" below.

You can stop it. Delete your account, from inside the app, and the record goes with it on the timetable below. There is nothing else you have to do and nobody you have to write to.

Where it goes. Supabase holds the record itself. PostHog receives the usage events described above — which units were started, completed, repeated or answered — under a pseudonymous code for your profile and a random code PostHog makes for this installation, which are codes that are not your name, never under your name or your e-mail address. Nothing about your study record is sent to any advertiser, any data broker, or any AI service. If you turn on Friends, the friends you connect with see what Friends below lists. If you choose Everyone, anyone signed in to the app may see your stats.

Friends (only if you turn it on)

Friends is off until you turn it on. Nothing in this section happens to you unless you do. You need a signed-in account to turn it on; a guest cannot.

The Friends text. In the app, under the Turn on Friends button, a short note says what the friends you add will see, with a link to Full details: the main points of this section. That note and Full details are the Friends text you agree to when you turn Friends on.

How people connect. You type a person's exact username in the app, and they get a friend request. You become friends only if they accept. That is the only way. There is no search list and nothing to browse, and we never look at your contacts. Only people who have Friends on can be found. If a username does not exist, has Friends off, or belongs to someone who blocked you, the app gives the same answer: not found. If you have both asked each other, you become friends.

Requests and age. An adult cannot send a friend request to anyone 13 to 17. To an adult who types their username, the answer is not found, the same as any other miss, so the answer does not tell them your age. Someone 13 to 17 can send a request to an adult, who can accept it, and people 13 to 17 can send requests to each other. To know who is an adult, the app asks one question when you turn Friends on: "Are you 18 or older?", Yes or No. If you already had Friends on, it asks the next time you open Friends, and it never asks again after you answer. We store your answer as one yes or no, only to decide who can send you a friend request, and it is never shown to anyone, your friends included. Until you answer, Friends treats you as 13 to 17, and you cannot send a request.

What a request shows. Nothing is shared until the other person accepts. The person you ask sees your username, the one your friends would see, and that you asked. Nothing else. You see the username you typed, marked as waiting. Because a request either goes through or is not found, someone who can send you a request and types your exact username can tell that you have Friends on. The Friends button at the bottom of the screen shows how many requests are waiting for you.

How a request ends. The person accepts, and you are friends. They decline, and the request goes away; the person who asked is not told. The person who asked cancels it. Either of you blocks the other, or turns Friends off. Nobody answers for 30 days. Or either account is deleted. There is a limit on how many requests you can send each day and on how many can wait at once.

What your friends see. Your username: the name you chose, if you saved one, or else the name the app made for you, such as "BraveOliveLamp". While "Who can see my stats & progress" is set to Only me, they see the name the app made. The stars you gained this week. Your streak, meaning how many days in a row you have studied. Where you are on their leaderboard. Your friends see your stars and your streak as they were at the end of yesterday. So they can tell on which days you studied. If they check very often, they can also tell roughly when your day turns over, and so roughly which time zone you are in. They also see your streak together. Only me hides your stats and the name you chose, but your friends still see your stars, your streak and your streak together.

Your streak together. For each friend, you both get how many days in a row you have both finished a unit, counting only days since you became friends, and your longest run together. Both numbers include days before you agreed to the Friends text, and days you were hidden (such as a deletion you cancelled), once you are both back. Once you have finished a unit today, you also see whether your friend has finished one on their own day: "Both done today", or "Waiting on" and their username. They see the same about you once they have finished one. So a friend who has already studied today can tell, as soon as you finish, that you studied today, and so roughly when. Unlike your stars and your streak, this is up to date, not as of the end of yesterday.

Your stats, unless you hide them. Unless you set "Who can see my stats & progress" in Settings to Only me, a friend who taps your name in Friends sees a small card with your stats, as they were at the end of yesterday: your current and best streak, how many units you have completed, how many studies you have finished, how many with Section 1 finished and how many with Section 2 finished, your highest section, how many Section Exams you have passed, your Progress Points and your stars. The card shows nothing else about you. While your setting is Only me, it says your stats are private.

What your friends never see. Your e-mail, phone number, or Apple or Google name. The name you chose, while your setting is Only me. Which studies and units you study. Your answers, or your score on any one unit. Which badges you have earned. Your age answers. Whether you pay.

When you are hidden. You leave every friend's leaderboard, your streaks together and your stats are hidden from your friends, and nobody can send you a friend request, while you have asked us to delete your account, if we switch Friends off for you, or, when the Friends text changes, until you agree to the new version. Your friends are not told why.

Why we ask first. Being on a friend's leaderboard tells them you use a Bible study app and how much you studied this week. Your streak together tells them more, and your stats tell them more again, such as how many units and studies you have finished. That can say something about what you believe. So Friends is off until you turn it on, and it shows only what is listed here. When you turn it on we record the date and which version of the Friends text you saw.

Names on Friends. Friends shows everyone by their username. You cannot rename a friend, and a request shows only the username. If the name you chose is your real name, your friends see it, unless your setting is Only me.

Remove, block, report. You can remove any friend, and you both leave each other's leaderboard. Block also ends any request between you and stops that person connecting with you again: to them, your username is not found. Report also blocks them, and sends us the reason you pick and any words you add; only we read them. The person is not told. We look at every report within 24 hours.

What we see about a report. The reason, your words, when you sent it and how long you had been friends, with three counts about the person you reported: their friends, the friend requests they sent in the last 7 days, and the reports made about them, and whether Friends is already switched off for them. If you report a username as offensive, we see that username so we can reset it. Other reports show neither person's username. We may then switch Friends off for that person.

Turning it off removes all your friends and every friend request you sent or received, straight away. People you blocked stay blocked. Your answer to the age question stays, so you are not asked again. If you turn it on again, you start with no friends.

Deleting your account. The moment you ask, you disappear from your friends' leaderboards, and your streaks together and your stats are hidden from them. If you change your mind within the 30 days, you come back. On day 30 your friends list, friend requests, your answer to the age question, blocks and reports are deleted with the rest of your account.

What we tell our analytics service. Nothing about Friends. No usage event is sent when you turn Friends on or off, send, accept, decline or cancel a friend request, remove, block or report a friend, or look at your streaks together, and nothing that happens while Friends is open is sent to it.

What our crash reporter receives. So we can find what is slow or broken, Sentry, our crash reporter, receives the same about Friends as about the rest of the app, from the moment the Friends screen opens, whether or not you turn Friends on: how long the screen took to appear and to show your friends, whether it stuttered or froze, any crash or error while it was open, when the app was in use, and each request Friends made to our servers, including the app's check for new friend requests, by its kind only (such as reading your leaderboard or reporting a friend), with how long it took and the answer it got. It never receives who your friends are, anyone's username, who asked to be your friend or whom you asked, your leaderboard or streaks, a report's reason or words, anything you type, or what you tap. The words of an error in the app's own code on the Friends screen are never sent.

Who else handles it. Friends is kept in our database at Supabase, and Sentry receives only what the paragraph above lists. When a report is waiting for us, our system e-mails our own support mailbox, through SendGrid, soon after the report is made and again each night, to say how many are waiting. About Friends these e-mails carry numbers only: never who reported whom, the reason, or your words.

The rules. Our Terms of Use set the rules for Friends: connect only with people you know, and never use Friends to bother anyone. We may switch Friends off for anyone who breaks them.

Your profile: username and stats

Your stats. Your profile shows these about you: the day you joined, and how many days you have studied; your current and best streak; how many units you have completed, and how many you have played, replays included; how many were perfect, and how many studies you have started; how many badges and stars you have; how many studies you have finished, how many with Section 1 finished and how many with Section 2 finished, your highest section, and how many Section Exams you have passed; your favorite book or topic, and the last one you studied. Your Profile also shows your Progress Points. You always see your own, up to date.

Who else sees them is your choice. In Settings, under "Who can see my stats & progress", you pick one. Only me: nobody else sees them. Friends, which is the setting unless you change it: while you have Friends on and have agreed to the current Friends text, a friend who taps your name sees a card with your current and best streak, how many units you have completed, how many studies you have finished, how many with Section 1 finished and how many with Section 2 finished, your highest section, how many Section Exams you have passed, your Progress Points and your stars, and nothing else (see Friends). Everyone: your friends see that card too, and anyone signed in to Your Bible App may see your stats, but the app has no place that shows them to anyone but your friends today. Anyone but you sees them as they were at the end of yesterday. Nobody else sees them while you have asked us to delete your account, or if either of you has blocked the other. You need to be signed in to share them. A guest cannot share their stats or see anyone else's.

Why we ask. Your stats come from your study record, which we treat as sensitive. Your favorite book or topic, and the last one you studied, are shown to nobody but you: Friends never see them. Only Everyone would show them to anyone else, and the app has no public place today. Everyone is never chosen for you.

Your username. Once you are signed in, the app gives you one made of three words, sometimes followed by two digits, such as "BraveOliveLamp", shown at the top of your Profile. To change it, tap the edit button, type a name (3 to 20 letters, numbers or underscores) or tap "Generate Random Name" as many times as you like, up to 60 an hour, then Save. Your friends see the name you chose unless your setting is Only me; then they see the name the app made. They also see the name the app made while we have turned sharing off for everyone. Public places, such as leagues if we add them, show the name you chose only if your setting is Everyone; the app has none today. Every username is different, so anyone signed in who tries a name can find out it is taken, and so that someone uses Your Bible App under it. We limit how many names one person can try in an hour. If you change the name you chose, someone else can take the old one straight away. A name the app made is never given to anyone else, even after your account is deleted. If we reset a name you chose after a report, nobody can take that name again.

What we see. We can see a list of accounts with each one's User ID, username (and whether it is the one the app made or one you chose), whether you are signed in, when the app was first opened, downloaded and last used, when you last finished a unit, progress (streak, stars and Progress Points), number of friends, device type and model, app version, approximate location and time zone, plan (and whether it is a trial) and amount paid, and how you came to the app: an advert (with Apple’s or AppsFlyer’s campaign details when they send them), a friend request or friend code in your first week, or no advert found. If your username is reported as offensive, we also see that report and any reset.

What we tell our analytics service. Nothing about your profile. No usage event is sent when you generate, choose or change a username, or change who can see your stats & progress.

Deleting your account. The moment you ask, your stats are hidden from everyone else, and public places show only the name the app made. While your deletion is waiting, you cannot choose or generate a new username. On day 30 the name you chose and your choices are deleted with the rest of your account, and the name you chose becomes free. The name the app made stays on our list of used names, tied to nobody, so it is never given out again.

Reading the Bible

The Bible tab has the whole Bible. The Berean Standard Bible (BSB) is stored in the app on your device. It opens without a signal, and reading it asks API.Bible and our server for no Bible text. The NLT and the NASB 2020 come from API.Bible, a service run by American Bible Society, through our own server.

What our server does. When you open a chapter of the NLT or the NASB 2020 that is not saved on your device, your Favorite Verses page or a session's Notes needs a verse from one, the app asks our server for that chapter, and our server asks API.Bible. Our server never tells API.Bible who you are, and it does not keep which chapter you asked for.

Notes on each chapter. When you open a chapter, in any translation, the BSB included, the app asks (at most once a day for each chapter) our database for what goes with it: the big idea, notes, articles and related verses. The request carries the book, the chapter and the translation inside it, never in its web address. When you open an article, the app asks for that article the same way. All of this comes from our own database. Nothing about it goes to API.Bible, and nothing the app sends to our analytics or crash-report services names the book, the chapter, the translation or the article. Our database looks the chapter up and writes nothing down. Supabase's own service log notes each request, with your account, your internet address, a line naming the app and your iOS version, and the time, for 7 days on our current plan. The book, the chapter, the translation and the article travel inside the request, which that log does not keep.

Search in the Bible tab. A reference you type, such as John 3:16, never leaves your device. Other words of two or more letters or numbers, a book's name included, are sent to our database to find the people, places and topics whose names match them. The words travel inside the request, never in its web address, and our database writes nothing down. Supabase's service log notes the request as above, but not the words. The app keeps what it finds only in its memory, never in your device's storage, and nothing the app sends to our analytics or crash-report services contains what you typed.

Listening to the BSB. The Play button, shown only for the BSB, reads the chapter aloud: Bob Souer's recording, which is in the public domain. The recordings are not stored in the app. When you press Play, your device fetches that chapter's recording, and a small file saying when each verse starts, from our file storage at Supabase; while it keeps playing, it fetches the next chapter's the same way. The address of each file names the book and the chapter. Like any request on the internet, each one carries your device's IP address, its language setting, and a line naming the app or your device's audio player and the iOS version. It never carries your account, your name, your e-mail or a cookie. Supabase's own service log notes each request, with that address, for 7 days on our current plan; we do not copy it anywhere else, and we do not use it to see what anyone listens to. When you press Play your device also reads a list of all the chapters' files (once it has it, at most once an hour); that list names no chapter. Our analytics hears nothing about listening (a chapter the reading turns to is counted like any chapter you open, by translation only), and a crash or screen-speed report can say only that a file was fetched from our storage, never which one. The app keeps no record of what you listened to; iOS may keep the small verse-timing files in its own download cache, which it clears by itself.

What our server keeps: a daily count. Our Bible text plan allows only so many requests a month. So our server counts how many requests each person, and each guest, makes through it in a day: getting a chapter that is not saved on your device is one, and so is fetching the list of translations or of books, at most once a day. It keeps the number only, never which chapter or which translation. Our server's own log notes which translation was served, never the chapter, and Supabase keeps that log for 7 days on our current plan. Past a daily limit, new chapters open again after midnight UTC; if the month's allowance for everyone is used up, they open again when our plan's month resets, and chapters already saved on your device still open. Each count covers one day, by UTC time, and is deleted automatically two days later. It is also deleted with your account, and a backup copy can hold it for up to 7 days more.

What your device tells API.Bible. API.Bible's terms require a usage report each time its Bible text is shown, so that the publishers can count how often their translation is read. So each time a chapter of the NLT or the NASB 2020 appears on your screen, whether it came from the internet or from your device's saved copy, your device sends API.Bible one short report. The same goes for your Favorite Verses page and for a verse you open from a session's Notes: each time they show verses of the NLT or the NASB 2020, your device sends one report for each chapter those verses come from. A report carries:

• the report token API.Bible sent with that chapter. It stands for that chapter of that translation, so API.Bible can tell which chapter was shown;
• a random reading code, made on your device for these reports alone. It is not your account and is never linked to it. It is kept on this device only, never in a backup. The app makes a new one when you sign out, when someone else signs in on this device, and when you delete your account;
• a random session code, made new each time the app starts, when you come back after 30 minutes or more away, and whenever the reading code is replaced;
• as with any request on the internet, your device's IP address, a line naming the app, its build number and your iOS version (the "User-Agent"), and your device's language settings (the "Accept-Language").

It never carries your account, your name, your e-mail or a cookie. So API.Bible can see which chapters were shown under one random code, and from which internet address, but it is never told who you are. If a report cannot get through, your device keeps it and tries again, at most 5 times over at most 7 days, and then drops it. We do not know how long API.Bible keeps these reports.

What stays on your device. Chapters of the NLT and the NASB 2020 that you have read, or that your Favorite Verses page fetched, are saved on your device, so they open again without a signal. At most 499 verses of each translation are kept, and none for more than 30 days, as API.Bible's terms require. If the device's clock is turned back while the app is closed, the app notices when it next opens and deletes the saved chapters, as long as the clock was turned back by more than five minutes plus the time the device spent asleep in between, and the device was not restarted. Otherwise a saved chapter can stay longer, by as much as the clock was turned back, until the app next hears from our server. They are kept in a part of the device that is never backed up. The notes and articles the app was sent for a chapter are kept there too, so the chapter opens with them at once: those for up to 200 chapters and 200 articles, each for at most 30 days from when it was fetched, by the device's clock. If that clock is turned back, they can stay longer, by as much as it was turned back. They show which chapters were opened on this device, in any translation. Your place in the Bible, your Day or Night page choice, your reading history (the last 10 chapters you opened, and when), your favorite verses (which verses, in which translation and when you saved each, never their words) and what you mark as read are kept on this device only, never in a backup, and are never sent to us. When you sign out, when someone else signs in on this device, and when you delete your account, the app wipes the saved chapters, the saved notes and articles, your place, your reading history, your favorite verses, what you marked as read, any report still waiting and the reading code. Deleting your account also wipes your page choice.

What we tell our analytics service. Each time a chapter is shown in the Bible tab, the app sends PostHog one usage event, named chapter_read, with the name of the translation and nothing else of ours (PostHog's library adds the details listed under What we collect): never the book, never the chapter. Your reading history, your favorite verses and what you mark as read send it nothing. Neither do the notes and articles shown with a chapter, apart from a request for them that fails or is slow (see Crash reports, next).

Crash reports. Nothing the app sends to Sentry records a Bible request, a request for a chapter's notes or an article, or a reading report, and no tap on the Bible tab is recorded by us or by any service we use. What you save there yourself (a favorite verse, or a verse or chapter marked as read) stays on your device. The part of the app that cannot filter its own reports no longer records web addresses at all; earlier test versions of the app could include the web addresses the device used just before a crash, and one of them could be a reading report, with its random codes. Crash reports are never tied to your account. If a request for Bible text fails or is slow, our analytics service counts it as a request to our Bible service, with how long it took — never the book or the chapter. If a request for a chapter's notes or an article fails or is slow, it counts it by the request's name, with how long it took — never the book, the chapter or the article.

Why we are careful. What someone reads in the Bible can say something about what they believe, so we treat your reading as carefully as your study record. Our server uses the chapter you ask for only to fetch it and the notes that go with it, and keeps no record of it, and nothing the app sends to our analytics service names a book or chapter you read. Nothing in this section is sent to any advertiser, any data broker or any AI service.

Sessions: your notes on studies and sermons

What it is. In the Sessions tab you can write down a Bible study, a sermon, or your own time with the Bible: its type, when it started and ended, where it was, the passages it covered, your own notes, and, if you want them, a title and the name of the speaker or leader. Sessions are free. They need an account, so the app asks a guest to sign in first. Nothing in this section happens unless you write a session.

What we keep, and why. Everything you write in a session, and when you saved and changed it, is kept with your account in our database at Supabase, so that you can see your own sessions on any device you sign in on. That is all we use them for: they do not choose your next unit and are not part of your stats. The app also keeps a copy on your device, so you can write without a signal; it reaches your account the next time the device is online. That copy is kept in the app’s ordinary storage on your device, so it can be included in your device’s own backups: an iCloud backup, which Apple keeps under your Apple Account, or a backup to your computer. When the app first moves a session to separate notes, we keep the session’s earlier notes, as they were before the move, as a backup until we have checked the move, then delete that backup. Until then, words you later delete from a note can still be in it.

If two devices change the same session. If a device tries to save changes made on an out-of-date copy, our server refuses that save. The device takes the latest version and adds its own new words as a clearly marked note next to the note they came from, so nothing anyone wrote is lost. If those words would not fit (a session’s notes have size limits), or the session was deleted on another device, the app keeps them as a new session instead. The device shows a short notice and keeps it until you have seen it.

Who sees them. In the app, only you. Sessions are not shared with your friends, not shown on your profile and never public. Like the rest of your account, they are stored in our database, which the people who run the app can reach with our own tools. We use that access only to run the service and keep it secure, to answer a request you make, such as asking what we hold about you, and to meet a legal duty. Your notes on a sermon or a study can say a great deal about what you believe, so we treat your sessions as sensitive information, as we do your study record.

The place. A session’s place is only ever a name, such as a church, a street or a town. You can type it, or, in versions of the app that have the button, tap Use my location in the session. That tap is the only thing in the app that can bring up your device’s location prompt. The app asks only to use your location while you are using the app, never “Always”, and never in the background. Your device asks your permission the first time you tap the button (and again later if you chose Allow Once). If you allow it, your device works out where it is and sends that position to Apple’s map service, which sends back the name of the place. The app fills in that name: the place’s own name, such as a church, or, for an address, the street without its house number, then the town or area (only the town and its region if you have turned off Precise Location for the app). Only that name is saved with the session, just as a place you type is saved, and you can change it at any time. Your device’s position itself is never saved by the app and never sent to us, to our analytics service or to our crash reporter. If you say no, or never tap the button, you type the place yourself.

What other services receive. Sessions sends nothing to our analytics service or our crash reporter: not what you write, not your taps, and not whether a save worked. Nothing in a session is sent to any advertiser, any data broker or any AI service. Supabase’s own service log notes each time your device sends or fetches your sessions, with your account, your internet address, a line naming the app and your iOS version, and the time, for 7 days on our current plan. What you wrote travels inside the request, which that log does not keep.

How long we keep them. Until you delete the session, or your account. When you delete a session, its words are erased from our database as soon as your device reaches our server. If another device saved newer words to it first, nothing is erased: the newer version comes back to your list with a short notice, and you can delete it again. A marker with nothing you wrote in it (only the session’s random code and its times) stays for up to 180 days, so your other devices learn that it was deleted, and is then removed. A backup copy can hold the session for up to 7 days more. Deleting your account deletes every session, marker included, on the timetable on the Delete your account page. When you sign out, the app first tries to send any unsent changes; if some cannot be sent, it warns you, and if you sign out anyway they are removed from this device with the rest of your Sessions. If a different account signs in on this device without the previous one having signed out, the app removes the previous account’s Sessions from the device, except changes that had not yet reached our server (for example, the previous person’s sign-in had expired). Those stay on the device, hidden from the new account, which cannot open or see them, and are sent the next time that previous account signs in on this device; nothing else of theirs is kept except the app’s unread notices about them. When you delete your account, all of your Sessions are removed from this device, including changes not yet sent. While an account deletion is waiting, Sessions can be read but not changed; whatever reached your account stays there until it is deleted.

Energy and unit times

Units and Section Exams use energy. Each question you answer in a unit uses some (a board you match or sort counts as one question, and a missed question asked again at the end of the unit is free), a Section Exam uses a set amount when you start it, and energy refills over time. A run of right answers in a unit, and finishing a unit, can give some back. Practice rounds use energy too, but they are switched off now: the app offers none. How much each question uses, how much an exam uses, how much a run or a finished unit gives back, whether a finished practice round adds any, how many practice rounds a day can add energy, and how fast energy refills, are settings we can change. While you subscribe, your energy is unlimited. Energy has no cash value: it cannot be bought on its own, sold, swapped or paid out.

What our server keeps. Your energy balance, and the moment it was last worked out. For each unit: when it was played, the energy it used and gave back, whether a subscription covered it, and whether you stopped because you ran out. For a unit you finished, how long it waited for energy, so that the wait is not counted as time spent on the unit. For each Section Exam you start: when it started, the energy it used, and whether a subscription covered it. Practice rounds are switched off now, so no new one is recorded. For each practice round: when our server received it, how many questions it asked, whether you finished it, whether a subscription covered it, the energy it used and gave back, and the day any energy it gave back counted toward, in your own time zone, so that we can count the practice rounds that added energy on each day.

Why. The balance is kept on our server so that it is the same on any device where you are signed in. The record of each round makes sure a round your device sends us twice is never charged or rewarded twice. It also tells us how often people run out of energy in a unit, which is part of how we tune unit length and difficulty.

Unit times. Your study record holds when each unit started and finished, and how long each answer took. We use those times, counted across everyone, to see how long units take and how often their questions are missed, so that we can tune unit length and difficulty. The report we read counts units, not people: it names no one.

How long we keep it. For as long as your account exists. When you delete your account, it is deleted with the rest of it on day 30, and a backup copy can hold it for up to 7 days more. A guest's goes when the guest profile is deleted.

What we tell our analytics service. No usage event carries your energy balance or what a round used. The only event that mentions energy is the paywall appearing, which says when running out of energy opened it.

Our adverts

We advertise the app, or plan to, on Apple Ads, Google, Meta and AppLovin. To learn which adverts work, we use a measurement company, AppsFlyer, and Apple’s own ad measurement. The app never asks to track you. It never reads your device’s advertising identifier: we use the version of AppsFlyer’s software that has no way to read it.

Nothing is sent for ad measurement before the age question. AppsFlyer is not started, and the app does not ask Apple about an advert, until the age question has been answered 13 or over. If the app asks your age again, AppsFlyer stops, and starts again only after an answer of 13 or over.

What AppsFlyer receives. A random code its software makes for this installation of the app; technical details of the device and the app, such as the device’s model and its iOS version; your device’s internet address, as any request on the internet carries; when the app was installed and each time it is opened; and, once our server has checked Apple’s signed record of it, that a free trial or a subscription has started. Nothing else you do in the app is sent to it. It never receives the price, your name, your e-mail, your phone number, your username, your account, or Apple’s identifier for vendors (the app switches that off). From the internet address, AppsFlyer works out roughly where the device is, which its own help pages say can be as close as a city or a postal code. We have turned on AppsFlyer’s IP masking, so the address itself is left out of the reports AppsFlyer gives us. Masking only hides it in those reports: AppsFlyer still receives the address and still works out the location from it, so the country and city still appear. So each of these is sent only once for this installation, the app keeps a short note on your device of which ones it has already sent, such as that a free trial started. The note is never sent to us, is deleted with the app, and can be copied into your device’s backups.

What Apple tells us. If an Apple Ads advert led to your download, Apple tells our server which campaign, ad group, keyword and advert it was. The keyword is one we chose to advertise on, not the words you searched for. Apple also says the country or region, whether it was a first download or a redownload, and whether you tapped the advert or only saw it. Apple says this answer does not identify you or your device.

What we keep with your profile. Apple’s answer, and AppsFlyer’s: whether it counts your install as organic (not from an advert), and the advert’s source, campaign, ad set and keyword. Only we can read it, and we use it to count which adverts lead to downloads, free trials and subscriptions. We never keep your internet address, your device’s advertising identifier, Apple’s identifier for vendors, or AppsFlyer’s code for your device. It is deleted with your account.

What ad networks see. Every time the app starts, before AppsFlyer is switched on, the app tells AppsFlyer to share nothing about your install with any ad network. If that instruction fails, AppsFlyer is not started at all. We do not put AppsFlyer’s links in our adverts on AppLovin or similar networks. Apple’s own ad measurement may send the network whose advert you saw a note, signed by Apple, that the advert led to a download and, when Apple allows, a small, coarse value for what happened next, such as whether a free trial or a subscription started. Apple says the note carries nothing about you or your device, and it gives less detail when few people are counted. So ad networks such as Google, Meta and AppLovin learn about this app’s installs from Apple’s anonymous notes, not from us or from AppsFlyer. Apple also sends us a copy of each note, which goes to AppsFlyer for us.

What AppsFlyer does with it. AppsFlyer works for us, and its policies call it our data processor. Its privacy policy also says that it uses what it receives to match the devices one person uses and to detect fraud, so that its measurement is more accurate for all the companies that use it, and that it uses anonymous totals, which name no one, for its own research and to improve and market its service. It keeps what it receives about your device for up to 24 months. AppsFlyer is an Israeli company, and the companies it names for storing data are in the European Union.

The age check

You must be 13 or older to use Your Bible App. Two things settle that, and this is the order they run in.

1. The app asks you the first time you open it, and again after anyone signs out on that device, because the next person to use it starts fresh. Under the question is the line "By continuing, you agree to our Privacy Policy and Terms of Use."
2. The app asks the App Store for the age category Apple holds for your Apple Account — only after you answer yes, and only on a device with iOS 26 or iPadOS 26 or later. Apple shares it only when an app asks, and you or your parent can decline to share it.

If Apple gives us a category and it disagrees with your answer, Apple's category is the one we use. That is a duty and not a preference: Texas law requires us to read and act on the age category the App Store reports, and we apply the same rule to everyone in the United States rather than only in Texas.

If Apple gives us nothing — because the sharing was declined, because your device is too old for the feature, or because Apple holds no category for your account — your own answer stands, and we record that the check could not be made.

What we store about your age is a yes or a no, the date you answered, and whether Apple's check confirmed it or could not be made. We do not store your age, your date of birth, or the age bracket Apple reports. We keep that yes-or-no for as long as your account is active, and it is deleted with everything else when your account is. If you turn on Friends, we also keep your one yes or no to the Friends question about being an adult (see Friends), in the same way.

The App Store age rating for the app is 13+ for the same reason the terms say 13: Apple requires the store rating to match the minimum age our terms set.

If you are 13 to 17

Everything on this page applies to you the same way it applies to an adult, apart from one Friends rule below, and we collect nothing extra about you because of your age (the Friends question about being an adult is asked of everyone who turns Friends on).

• The same events, the same code. The usage events and the pseudonymous codes are the same for a 15-year-old as for a 40-year-old. No age property is ever attached to any event, and your age answer never leaves our own database.
• No parental controls in the app, and none pretended. There is no parent-facing screen in this app, and we do not claim there is one. Apple's own Ask to Buy and Screen Time controls sit outside our app, on the device, and we cannot see whether a family has switched them on.
• The subscription is a real agreement. The terms and the subscription apply to a 13 to 17 year old the same way they apply to anyone else. Apple is the seller and Apple takes the money.
• Friends has one extra rule for you. It is off until you turn it on. There is no search list (anyone signed in who tries a username can learn it is taken; see Your profile). An adult cannot send you a friend request: to an adult who types your username, the answer is not found. You can send a request to an adult, who can accept it, and you can send requests to, and get them from, other people 13 to 17. Nothing is shared until a request is accepted, and you can remove, block or report any friend at any time. There is no messaging and nothing to post. There are a few ways to share, and each one is your choice: a Share button on a badge you have earned, on a three-star unit result, or on a streak celebration, which opens your device's own share sheet with one line of text and our web address; and in the Bible tab you can select verses and use your device's own Copy or Share. Nothing leaves your device unless you choose where to send it. Your profile works the same for you too. A friend who taps your name sees your stats unless you change that, and public places show the name the app made for you unless you pick Everyone.
• Same rights. Everything under "Your choices and how to change your mind" is yours at 13 exactly as it is at 30.

Who else handles your information

We use other companies to run the service. Each one only handles what it needs for the job named here, and none of them is allowed to use your information for their own purposes. There are two exceptions to that last sentence. The reading reports your device sends API.Bible are for API.Bible and the Bible's publishers themselves, to count how their text is used, under API.Bible's own terms. And AppsFlyer's privacy policy says it uses what it receives to match the devices one person uses and to detect fraud, for all the companies that use it, and anonymous totals for its own research; see Our adverts.

Where it is stored. Your information is stored in the United States, with one exception. Every company above except AppsFlyer is a United States company, and apart from AppsFlyer we have chosen no service that we know stores your information outside the United States. AppsFlyer is an Israeli company, the companies it names for storing data are in the European Union, and its policy says it may move data between countries. If anything else has to change, this page changes first. One gap, said plainly: API.Bible is run from the United States, but it has not told us where it stores the reading reports it receives.

Legal process. We will hand over information if the law requires it — a court order, a subpoena, or a lawful demand we cannot refuse.

If the business changes hands. This policy contains no clause allowing your information to be sold or transferred to a buyer of the business, because no such arrangement has been decided. If one ever is, this page changes before it happens.

Text messages

The only text message the app sends is a one-time sign-in code, through Twilio, and only when you ask for one by signing in with a phone number. We do not send marketing texts, and we never will without telling you first.

We do not share, sell, or provide your mobile phone number or messaging consent data to third parties or affiliates for marketing or promotional purposes.

Message and data rates may apply. You only get a text when you ask for a code — so there is no list to unsubscribe from.

One rule holds whichever way you sign in: your account keeps the verified way in you made it with. The app has no way to remove a sign-in method, so you cannot lock yourself out of your own progress.

How long we keep your information

Every period below is either a setting in our own database or a property of how our database host keeps its backups. None of them is a guess, and the right-hand column is the rule that decides it.

The Friends periods above are enforced by our nightly job, so a row can outlive its period by up to about a day, and a backup copy can hold it for up to 7 days more.

The daily reading counts are deleted by the first Bible request of each new day, and by our nightly job on a day when nobody reads. A backup copy can hold one for up to 7 days more.

So the honest total is this: deletion from the live service completes 30 days after you ask, and the last backup copy expires up to about 38 days after you ask. We do not promise 30 days end to end, because that would not be true.

What the other companies keep. PostHog keeps the usage events we send it for 1 year on our free plan, and then deletes them; the person record PostHog builds from those events runs on the same clock, because PostHog publishes no separate period for it. Sentry keeps the crash and error reports we send it for 30 days on our free plan. AppsFlyer's policy says it keeps what it receives about your device for no more than 24 months, unless we tell it otherwise or the law requires or allows longer. Vercel keeps the ordinary web server log for 1 day on our current plan. Supabase keeps its own sign-in, service and file-storage logs for 7 days on our current plan, and backs up our database once a day, keeping each backup for 7 days on that plan — those are the backups in the table above. API.Bible has not told us how long it keeps the reading reports your device sends it. Twilio keeps its own record of each sign-in code it sends, with the phone number it went to; we can look those records up for 30 days, and we have not yet confirmed how long Twilio keeps them after that. Expo's privacy policy gives no fixed period for the install id, crash message or launch details described above; it says it keeps what it collects only for as long as it reasonably needs it, under applicable law.

Deleting your account

You can ask for deletion from inside the app, and guests can delete their data too. The whole process, including what a purchase during the grace period does, is on the Delete your account page.

When an account is deleted, we keep an anonymous record of its payments for our financial records, including renewals Apple charges after the deletion: for each payment, the amount, the day, the plan and whether it was refunded, and a random code that keeps the payments made before the deletion together, but no name, account, device or contact details.

One thing worth repeating here: deleting your account does not cancel your Apple subscription. You have to cancel that separately, in your device's subscription settings, or Apple will keep billing you.

Your choices and how to change your mind

• Stop us keeping your study record. Delete your account. That is the way out of it, it is in the app, and it takes the record with it on the timetable above.
• Delete everything about you from inside the app, or by writing to support@yourbibleapp.com from the address on your account.
• Ask us what we hold. There is no self-service download button. Write to support and we will answer you.
• Ask us to correct something. Write to support.
• Stop sharing with friends. Turn Friends off in the app. Your friends list and every friend request you sent or received go straight away.
• Choose who sees your stats. In Settings, "Who can see my stats & progress" goes to Only me whenever you like, and on your Profile you can change the name you chose whenever you like.
• Clear what the Bible tab keeps on this device. Sign out. The saved chapters, the saved notes and articles, your place, your reading history, your favorite verses, what you marked as read, any reading report still waiting and the reading code go, and the next report uses a new code. You can also remove a favorite verse, or mark a verse or chapter as unread, at any time.
• Delete a session in the app, whenever you like. Deleting your account deletes all of them.

We will never treat you worse for asking. Nothing in this list changes the price you pay or what the app gives you, except where that is the direct point of the request.

We will ask you to prove who you are before we delete or hand over anything, and if we cannot tie the request to a verified way into the account, we will refuse it. Refusing is the safer mistake: the other one destroys the wrong person's work.

If we say no, you can appeal. Reply to our answer, or write again to support@yourbibleapp.com with the word APPEAL in the subject line. A person — not a machine — looks at it again, and we write back within 60 days with the decision and the reason for it. If you are still not satisfied, you can complain to the Texas Attorney General's consumer protection division, at texasattorneygeneral.gov.

There are two ways to make any of these requests: from inside the app, or by e-mail to support@yourbibleapp.com. You do not need an account with us to ask about a request you have already made.

Children

Your Bible App is for people aged 13 and over. It is not designed for or directed at children under 13. If you tell the app you are under 13, or the App Store's age category says you are, it stops there: no new account is made and nothing about you is recorded, no sign-in is offered, and there is nothing to buy. Nothing about that answer reaches us — no row on our servers, no analytics event, no e-mail address. Our crash reporter, our analytics service and our ad-measurement service, AppsFlyer, are not even started on that device until the question has been answered 13 or over, so they receive nothing from it, not even a crash report, and the app does not ask Apple whether an advert led to the download. Like every copy of the app, it still checks with Expo for app updates each time it opens (see Expo above); that check says nothing about age. The device itself keeps one marker so it does not have to ask again every time the app opens: the date to ask again, about a year later. It is never sent to us; it can be copied into the device's encrypted backups. If you believe a child under 13 has given us information, write to support@yourbibleapp.com and we will delete it. You do not have to prove anything to us first.

Keeping it safe

Your information travels encrypted between your device and our servers, and it is stored encrypted at rest by our database host. There are no passwords in this app, so there is no password of yours to steal. The keys our servers use are held by the services that run them and are never in the app on your device.

Nobody can promise that a system on the internet will never be broken into, and we do not. What we can say is what we have done, which is above.

Where this applies

Your Bible App is offered in the United States only. It was not built for use elsewhere, and this policy does not try to describe rights under the laws of other countries. One rule applies everywhere in the United States: we do not vary what we collect, or how we behave, from state to state.

This website

This website is a handful of pages of plain text. It sets no cookies, runs no JavaScript, has no analytics, no tracking pixels, and no forms. It loads nothing from any other company — no fonts, no images, no scripts from anywhere else — and the server is configured to refuse to load any of those even if someone added them by mistake.

The only record of your visit is the ordinary web server log kept by our host, Vercel, described in the table above. There is no cookie banner on this site because there are no cookies to consent to.

An old Friends invite link opens one page here, yourbibleapp.com/invite, which says how to add a friend by username. The page learns nothing about who sent the link.

Changes to this policy

If this changes, the date at the top changes with it, and the current version is always on this page. If we change something that matters — what we collect, who gets it, or what we do with it — we will tell you in the app before it takes effect, rather than quietly changing the date.

How to contact us

support@yourbibleapp.com
Your Bible App, operated by Joel Malone (sole proprietor), Texas, USA.