← IEUM

IEUM Privacy Policy

IEUM is operated by AboutUsAgency, Inc. This policy explains how we handle information when you read Scripture, save reflections or audio, choose to share content, and, if you agree separately, use Through Their Eyes (AI) and its subscription. Contact us at support@aboutusforyou.com.

Effective October 27, 2026

Nothing in the English version of this policy is new in IEUM app 1.0.16, 1.0.12 or 1.0.11. The check newly described in this version, which the app may make with our server before you agree to Through Their Eyes (whether the feature and its subscription can be opened; our server stores nothing from it), applies from IEUM app 1.0.10 (marked “From app 1.0.10” in the text). App 1.0.9 and earlier don’t make it. The records added in app 1.0.9 that are kept on this device and not sent to our server (how much of a chapter you heard when listening was cut off, records for a month’s book, lines to look at again, listening sets, small gallery cards, the record of reminder suggestions the app makes on its own, Lines you kept and Highlight dates) apply from app 1.0.9, and notifications from people (reading circle and friend news) are a Korean edition feature. Sending your device’s date (for the free-reply letter), payment and trial totals that also carry the name of the place that opened the payment screen, and the items added to usage totals in 1.0.8 are features of app 1.0.8 and later; app health information (error reports), Bible narration (the AI-generated voice “Eunha”) and downloaded narration, install source totals and usage totals, 1-month and 1-year passes, and the free-reply letter of app 1.0.7 and later; and Through Their Eyes (AI), its subscription, and recent searches of app 1.0.6 and later. The policies for apps 1.0.9, 1.0.8, 1.0.7 and 1.0.6, and records kept only by app 1.0.5 and earlier (when a pause in rating requests after a helpline notice ends), are in the previous versions. Previous version (effective October 26, 2026, app 1.0.9) · Earlier version (effective October 21, 2026, app 1.0.8) · Older version (effective October 16, 2026, app 1.0.7) · Even older version (effective October 7, 2026, app 1.0.6) · Oldest version (effective October 4, 2026, app 1.0.5 and earlier)

Reading and information on your device

You can read the available Scripture and explore scenes without creating an IEUM account. Reading preferences, the order you chose for search results, your recent searches (up to 10 words or references you looked for), your phone’s text size, the day the app first opened on this device and when it last asked for a rating, guest verse marks, and downloaded public content can remain on your device. With the rating request, the app also keeps the app version it asked in and when you last tapped “Send feedback.” To choose when to ask, it also keeps, on this device only, the last three days you listened to a chapter to its end and up to three days you opened a Through Their Eyes letter. Recent searches stay on this device; the app does not upload Bible search terms as a saved search history.

An unsaved draft or recording is not the same as a saved account record. Until you choose to save or share it, it stays in the current app experience. Leaving that screen or closing the app may discard unsaved work. Downloads and files you export are controlled by your device and the apps you choose to receive them.

While you write a reflection in the app, “Keep a draft on this device” is on by default, so the reflection and prayer you are writing are saved as a draft on this device until you save them to your account. On a shared device, turn this option off or delete the draft. Drafts written while signed in are removed from this device when you sign out or delete your account. When a sign-in ends because it expired, its draft stays on this device so the writing is not lost; the next time someone signs in, the app shows only its passage and date and asks whether to keep writing it or remove it. Drafts written while signed out, My Verse Book (its title and the locations of the verses you chose), guest highlights, and your last reading place are not linked to your account, so they stay on this device after account deletion. However, a draft you were writing while signed out moves to that account’s drafts if you sign in without closing the app, and guest highlights and underlines that you move with “Move to my account” after signing in are saved to your account and removed from this device. When a stored My Verse Book cannot be read and is repaired or started again, a copy of the original record is set aside on this device; up to five copies are kept, and the oldest is removed first. Whether or not you are signed in, “On this device” in Account and privacy (the gear) lets you choose records kept only on this device and clear them: your reading record, reading plans, church year readings (the seasons you chose to read daily, the days you checked, season cards you closed, and the church days you set aside), prayer notebook, reflection drafts, Recent searches (the words and references you looked for), My Verse Book and its set-aside copies, guest highlights and journey progress, your last reading place, listening settings and where you last listened, Reminder time (reminder times), Scripture Memory (the verses you’re learning and when each comes back), Through Their Eyes (conversations, letters, letter notes, kept cards, consent, and settings), and App hints (your search result order, the day the app first opened here and when it last asked for a rating, the listening and letter days kept to choose when to ask, and your phone’s text size). Cleared records cannot be restored. “Clear them from this device too,” on the screen that confirms account deletion, clears them the same way, except that Scripture Memory, Recent searches, App hints, and drafts written while signed out stay until you clear them here and the prayer notebook goes only if you tick it there. Removing the app removes them from its local storage on the current device. Previously exported files and earlier operating-system backup copies are managed separately through the files and operating-system backup settings. Whether you agreed to the Community Guidelines and your reminder settings are also stored on this device.

While you are signed in, this device keeps a copy of the verse marks (highlights and underlines), bookmarks and reading place last loaded from your account, so you can still see them without a connection. Offline, this copy can be viewed but not changed. Each sign-in also stores a random tag made for that sign-in and the time the server says the sign-in ends, so the app can tell you before it ends and can tie your Community Guidelines agreement to that sign-in only. This information is not sent to our servers. It is removed when you sign out or delete your account, and after a sign-in expires it is removed or replaced at the next sign-in.

Sermon notes (date, church and preacher, passage, title and note text) and reading settings are stored on this device. We do not automatically send or analyse sermon notes on our servers. “Move to a new phone” lets you export reading records, plans, prayer and sermon notes, reading settings and other supported device records into one file and import it into the same language edition. This file contains the records as written; keep it somewhere private. Account reflections, audio and bookmarks, sign-in credentials and drafts you are writing are excluded. Records present before an import are set aside on this device for seven days so you can undo the import. Clearing device records also removes that copy.

From app 1.0.7, if you use Listen (the Eunha narration), your listening settings (speed, continuing to the next chapter, following along, counting chapters you hear as read, showing the verse on the Lock Screen) and where you last listened are stored only on this device. Narration you download stays in the app’s storage on this device, is excluded from iCloud and device backups, and can be deleted book by book or all at once in Settings › Listen › Downloaded narration. When “Count listened chapters as read” is on, a chapter you hear to the end is added to this device’s reading record. The narration is not a human recording: it is an AI-generated voice (named “Eunha”) reading the Bible text as written.

Text typed while copying is only compared with the passage on this device and is never stored or sent. Only which verses you finished, how much you chose to write today when writing on paper, and the days you marked as written on paper (how many chapters each day) stay on this device, and you can delete them in Settings › Account and privacy › On this device.

From app 1.0.7, these records also stay only on this device; they are not sent to our server and are left out of “Move to a new phone” records files and Android device backups: the quiet week record of Listen to the Bible in a Year (how many weeks and days you have been with the Word so far, counted from your reading history) and whether you closed the New Year listening card, the verse where listening stopped on a sleep timer (book, chapter, verse and time — used only for the next morning’s Resume card), your place on the listening shelf (the next stop on each life you follow and the stops you heard to the end, where a whole book stopped, which multi-voice episodes you opened, and which story you were in, kept to choose what Continue shows), your break dates, each church season’s days with the Word and listening time (for the season look-back), and when the reminder suggestion was seen and your answer. You can delete them in Settings › Account and privacy › On this device; deleting your reading history also deletes the weeks and days counted from it. If you choose to clear this device too when deleting your account, these records are cleared as well (how much you chose to write on paper and the days you wrote stay, like your copied verses). From app 1.0.9, how much of a chapter you heard when listening was cut off (the last three days) is kept the same way, only on this device; it is used only to count a chapter heard in parts as one chapter, and is cleared with the reading record.

From app 1.0.9, these records also stay only on this device and are not sent to our server: the records you chose for a month’s book (where each record is, their order and the cover color — no copy of the words is kept), the lines you chose to look at again and the day for each, your listening sets (name, chosen chapters and their order, cover, and where you last listened), and the recipes for cards in your small gallery (verse, chosen line, background and size — no image files are kept). These four go into “Move to a new phone” records files and Android device backups. To keep the reminder suggestions the app makes on its own (asking whether to set a reminder time after you finish reading or listening, or after you keep a line) to one a day and three in seven days, the app also keeps on this device the kind of each suggestion, when it was shown and whether you took it up. Only the last 30 days are counted, and older entries are removed the next time one is written; after two in a row are not taken up, the app suggests less often. This suggestion record is left out of records files and Android device backups, and notifications at times you set yourself are not counted. You can delete all of these in Settings › Account and privacy › On this device (the suggestion record is part of App hints); they stay on this device after account deletion until you delete them there.

From app 1.0.9, Lines you kept and Highlight dates also stay only on this device and are not sent to our server. A line you keep holds the verse you held (chapter, verse and translation) and what you left with it (words you typed, words you spoke in the Korean edition, or your answers to questions together with each question), when you kept it and last changed it, which screen you kept it from, the color you chose, the feelings you chose (up to three), and the names you added to say who a line is for (up to three — picked from your prayer notebook or typed yourself; your prayer notebook is not changed). Speaking a line turns your words into text on this device only, and only when you tap it; the sound is not kept. Highlight dates are the day you first highlighted or underlined each verse; for highlights saved to your account while signed in, the date still stays only on this device. Both go into “Move to a new phone” records files and Android device backups, and on iPhone they can be included in iCloud or computer backups. Lines you kept are not locked, so anyone who shares this device may see them. You can delete both in Settings › Account and privacy › On this device (copies set aside because they could not be read go with them). Lines you kept are not linked to your account, so they stay on this device after you sign out or delete your account until you delete them there; Highlight dates are cleared as well if you choose to clear this device too when deleting your account.

Account and sign-in information

When you sign in, we use an identifier from your sign-in provider to recognize your IEUM account and protect access to its records. Depending on the provider and the information you authorize, the sign-in service can also supply your name and email address. You can choose a separate display name for a group or invitation.

The native app uses a session credential to access your account. A native session expires after 30 days unless revoked earlier. The temporary code used to finish native sign-in expires after 2 minutes and can be used once. You may need to sign in again when a session expires. These validity periods describe access credentials, not a retention period for your notes.

You can also sign in with a separately issued invited account. We store its assigned username, display name, and a securely hashed password. We do not store or log the plaintext password. Account deletion removes the login record and password hash. Invited accounts have the same ordinary permissions to save, share, and delete their records.

Information you choose to save

Saved content can include your written reflections and prayers, passage references, narrator and recipient labels, voice recordings or uploaded audio, bookmarks, verse highlights, reading position, journey progress, drafts of journeys you create, and revisit settings or replies. We associate these records with your account so you can return to them.

Prayers and reflections can reveal religious beliefs and other personal information. You choose what to write or record. Avoid including information about another person without permission. We use your saved content to provide the features you request, rather than to generate a live AI conversation. Messages you send yourself in Through Their Eyes, and letter notes, are handled as described in “Through Their Eyes (AI)” below.

Records that may reveal religious beliefs

Because IEUM is a service for reading and reflecting on Scripture, the prayers, reflections, and recordings you save, and the notes you share, can reveal your religious beliefs. Laws such as the GDPR and Korea’s Personal Information Protection Act treat religious beliefs as sensitive information, so we handle this content as follows.

IEUM does not ask about your religion, denomination, or faith and does not collect it as a separate field. Such content appears only in records you choose to save or share. Writing and recordings you have not saved, and records kept only on this device such as your recent searches, reading record, reading plans, the verses you copied out and the days you marked as written on paper in Scripture Writing, church year readings, and the verses you are learning in Scripture Memory, are not sent to our servers. From app 1.0.9, Lines you kept (what you wrote or spoke, your answers to questions, the feelings you chose and the names of others a line is for) and Highlight dates are also kept only on this device in this way and are not sent to our servers. The exception is what you write yourself in Through Their Eyes, which is handled under the separate consent for sensitive information described in “Through Their Eyes (AI)” below.

Saved records are used only to keep them for you, show them again when you ask, and deliver the shares you choose. We do not analyze them to infer your religious views, use them for advertising, or show them to other users automatically. Content reaches a group, a published journey, or an invitation only when you choose the record and where it goes. You can delete saved records at any time.

Through Their Eyes (AI)

Through Their Eyes is an AI text conversation feature that imitates the way of speaking of figures recorded in the Bible. It is only for people 18 and over who agree to it separately, and nothing is sent to IEUM’s server or an AI provider because of it until you finish the age check and agree. Bible reading and everything else in IEUM work without it. From app 1.0.10, before you agree, the app may still check with IEUM’s server whether this feature and its subscription can be opened; that request sends only the app, the edition, the app version, and the platform, and IEUM’s server stores nothing from it.

After you agree, each time you send a message we send what you just wrote, the recent part of the conversation (up to the last 12 messages), the figure and scene you chose, where you started the conversation and, if you started from a Bible verse, its location, and your device’s date. Text that looks like a phone number, email address, ID number, or card number is masked on this device before sending. For the crisis response, we also send two category flags: whether the device found words about self-harm, suicide, violence, or abuse before sending, and whether a help notice was shown on this device in the last 24 hours. From app 1.0.8, when you open the conversation screen the app sends only the chosen figure and the usage pass, once, so the server can prepare that figure’s fixed opening (instructions and the figure’s record); no conversation text is sent then.

While you have a subscription (including a trial) and the daily letter is on, the first time you open the app each day (after 4 a.m.) we send your chosen figure, your device’s date, the location of the day’s verse, and whether a help notice was shown in the last 24 hours, to receive the letter. Only if you separately turn on letter personalization and agree, when a conversation ends (you tap “Wrap up,” switch figures, or come back after more than 10 minutes) we send up to its last 12 messages to receive a note of up to 200 characters, keep that note on this device, and send the notes from the last 7 days (up to 10) with your next letter request. No note is made from a conversation that had a crisis notice, and for 7 days after a notice no notes are made or sent.

We don’t send your name, contacts, IEUM account, or other records such as reflections, your prayer notebook, sermon notes, or reading record. Through Their Eyes requests carry no IEUM sign-in credential, so conversations are not linked to your IEUM account.

What you send is used only to write replies, letters, and notes, to check them for safety, and to prevent abuse. IEUM’s server (Vercel, Tokyo, Japan) receives the request and sends it to Claude models from Anthropic, PBC (USA; privacy contact privacy@anthropic.com); depending on our operating settings, it may be relayed through Vercel Inc.’s AI Gateway (USA; privacy@vercel.com). The recipients, their contacts, countries, and retention are listed under “Where your information is processed” below. Model requests carry a pseudonymous value that our server hashes again, not your install key or account. We don’t allow your conversations to be used for model training or send them to the provider as feedback, and every request uses an encrypted connection (HTTPS).

IEUM’s server does not keep the text of conversations, letters, or notes in a database, log, or file; it handles them only while processing a request (reports, below, are the exception). Server logs keep only fixed event names and short code values. Anthropic deletes the inputs and outputs it receives within 30 days. If content is automatically flagged for a safety-policy violation, inputs and outputs may be kept up to 2 years and safety scores up to 7 years, and content may be kept longer where the law requires.

Conversations stay on this device. By default, a conversation is cleared 30 days after you last talked in it; you can choose 7 days, keep, or don’t keep in Settings › Through Their Eyes. Daily letters are cleared 7 days after they arrive and letter notes 7 days after they are made, with at most 10 notes kept. This cleanup runs when you open the app (when it starts and when you bring it back to the front), and also when you open a Through Their Eyes conversation or change how long to keep conversations. Records past their period can therefore remain on this device until you next open the app. The cards you keep at the end of a conversation (a verse to hold, the small steps you chose, a line of prayer) stay until you delete them. These records are not included in the “Move to a new phone” records file or in Android backups. On iPhone, the app’s storage is not separately excluded from operating-system backups, so it can be included in iCloud or computer backups. You can clear each kind under “On this device,” and deleting the app removes them from this device.

The first time you send, we ask for two separate agreements: one for sending what you write to Anthropic (USA) to write replies and check safety, including transferring personal information abroad, and a separate one for processing sensitive information, such as faith or health, that your writing may contain, for the same purposes. Neither box is checked in advance, and both are needed to send. Everything else in IEUM works as usual if you don’t agree. Letter personalization is turned on and agreed to separately in Settings. If the consent notice changes, we ask again.

Through Their Eyes and its subscription are only for people 18 and over. If your device provides an age signal (iOS Declared Age Range or Google Play Age Signals), we use its result; otherwise we ask for your birth year (because the birthday is unknown, you pass only if this year minus that year is 19 or more). We don’t store your birth year; this device keeps only the result, how it was checked, and the date, and IEUM’s server receives only how it was checked. If you are under 18, we won’t ask again for 30 days, and if a conversation suggests you may be under 18, the feature pauses on this device for 30 days.

This feature is not offered in EU or EEA member states or Switzerland. The app hides the feature based on your store country, and IEUM’s server checks the country again from the request’s IP address. The country is not stored.

When the app gets a usage pass, it sends a hash of a random install key made on this device (never the key itself), the result of App Attest on iPhone or Play Integrity on Android, the consent version, how your age was checked, your store country, your device’s date (from app 1.0.8, used only to see whether a free-reply letter is ready that day, and not kept), and the number of crisis notices shown on this device while offline (a number only). To run free replies, daily limits, subscriptions, and abuse prevention, IEUM’s server keeps the following with irreversible hashes: daily use and attempt counts by install-key hash and by IP-address hash (deleted three days after that day), free-reply counts per install and the date it received the free-reply letter (one year from first use), iPhone attestation public keys (60 days after last use), subscription status and the installs using it (90 days after the subscription ends), 1-month and 1-year passes and the installs using them (90 days after the pass ends), and hashes of store notifications (30 days). Combined with other information, these values could single out a device, so they are pseudonymous, not fully anonymous. The number of crisis notices shown and of replies is kept only as numeric totals by date, edition, and type for 3 years (for reports required by law and for operations); these totals contain no writing or install hashes. The usage pass travels in a request header (X-IEUM-Pass) with each request for this feature.

The time a crisis notice was shown and an under-18 result stay on this device for that period (24 hours and 30 days), even if you withdraw consent or clear the settings; only the time is kept, never what you wrote or why.

If you report an AI reply or letter, we receive the text of that one reply (or letter), the figure and scene details, the reasons you chose, anything you add under “Anything else” (up to 200 characters), the app version, model name, and request number, plus your previous message only if you turn that on. Reports are kept for 90 days so we can review them, and then deleted.

If you turn the feature off in Settings › Through Their Eyes, sending stops right away and your consent, age check, and usage pass records are removed; you can also clear the conversations, letters, notes, and kept cards on this device. The install key stays so that turning the feature off and on does not restart free replies. What was already sent follows the retention rules above. Send requests to access, delete, or stop processing to support@aboutusforyou.com. Because our server holds only hashes, without names or accounts, we may need to work out with you how to identify the device. The subscription is separate: cancel it in the App Store or Google Play. The Terms of Use explain the subscription’s price, trial, automatic renewal, and cancellation.

From app 1.0.7, if an install has used the free replies, then while this feature is on it can receive one letter, once, the first time the app is opened on a day from the day after the first free reply through the seventh day. We send only the chosen figure, your device’s date, the location of the day’s verse, and whether a help notice was shown in the last 24 hours — not your conversation or notes. The server keeps only the date that install received this letter, with the hashed install key, in the free-reply record (deleted after one year), and sends no notification.

From app 1.0.7, to show payment notices only once and to ask for the free-reply letter only a set number of times a day, this device keeps these marks and dates: whether the server reported a payment problem and whether pass purchases are hidden, whether a free-reply letter may be requested today and on which day that was given, the day you first used the free replies, the day and number of free-reply letter requests and whether it arrived, whether the payment-problem notice, the pass-ending notice and the line at the end of the free-reply letter were shown, and whether you closed the “welcome back” card. The words of your conversations and letters are not kept here. These values are not sent to our server and are deleted with your other records when you turn Through Their Eyes off or delete its records in Settings.

From app 1.0.8, to learn where the payment screen was opened, five payment events (paywall_shown, purchase_started, trial_started, pass_verified, and entitlement_verified_paid for a subscription started without a trial) are also counted under a name that joins the event, with two underscores (__), to the place that opened the payment screen (seven places: taste_end, letter_line, story_locked, settings, today_card, locked_card, return_card) — for example paywall_shown__settings. The app sends that place name with the payment-screen and purchase-start counts, and with the subscription check request when you buy from the payment screen. We also count paywall_shown__taste_end__a, paywall_shown__taste_end__b, purchase_started__taste_end__a and purchase_started__taste_end__b, which compare two versions of the screen shown when the free replies run out; trial_day_open__d1 through trial_day_open__d7, the day of the trial on which the Through Their Eyes screen was opened; and letter_open_lag__lt1h, letter_open_lag__1to6h, letter_open_lag__6to24h and letter_open_lag__gt24h, how long after a letter was ready it was opened. These names contain no conversation or letter text, no figure, episode or verse, and no install source, and like the other usage counts they are kept only as numbers by date, edition and kind.

Private records and content you share

Your personal library is private in the app unless you choose a sharing action. Private means that ordinary access is limited by account permissions; notes and audio are processed by the service and its storage providers and are not end-to-end encrypted.

When you share a note in a group, group members can see the chosen text and your group display name. The separate narrator and recipient fields are not added to the group post, but anything you wrote inside the note is visible. Attached audio is shared only when you select that option.

Published journeys can expose their title, guide name, description, commentary, questions, and selected audio to anyone with the link. Invitation pages can expose the name and message you enter, alongside the selected scene and Scripture. Your private reflections and voice recordings are not automatically added to an invitation.

Links can be forwarded. Recipients can save content or make copies. Withdrawing a link or deleting your IEUM copy does not remove screenshots, exported files, or copies held by other people.

Microphone, files, and reminders

The microphone is used when you choose to record and grant the device permission. You can write instead or select an audio file. Saving or sharing audio sends the selected recording to the online service.

Export and share actions send the selected content to the destination you choose. A calendar file you import is handled by your calendar app; IEUM does not need to read your calendar to create that file. Revisit settings show a saved reflection on a later visit. They do not by themselves send a push notification.

If you turn on daily verse reminders, your reminder time and the Bible verses for the next 30 days are scheduled as local notifications on your device. Your device delivers them; they do not pass through our servers. When you open the app near the end of that period, the reminders are scheduled again at the same time, and turning reminders off cancels all scheduled reminders. You can change notification permission in your device settings.

If you add the home screen widget, it shows the same verse of the day as the app on your home screen (and, on iPhone, the Lock Screen). The widget reads only the verses that come with the app, does not connect to the network, and does not read or send your information, such as your records, verse marks, or account. You can remove it at any time from your device’s widget editing screen.

On supported Android devices, when you allow operating-system backup or device transfer, a separate file of supported device records may be transferred. Google cloud backup is allowed only when the operating system confirms encryption capabilities; device-to-device transfer follows separate operating-system rules. Restoration depends on Android version, manufacturer and backup settings. Sign-in tokens, sessions, device identifiers and the full WebView store are excluded. IEUM servers do not receive this device backup file. On iPhone, records on this device (such as the prayer notebook, sermon notes, and reading record) can be included in iCloud or computer backups; IEUM servers do not receive those backups.

“Keep screen on while reading” applies only to Bible reading, copying out and focus reading. It releases when that screen closes, the app goes into the background, or there has been no interaction for 30 minutes. This setting collects no personal data and sends none to a server.

Notifications from people (Korean edition)

Notifications from people, such as reading circle news, circle invitations, and friend requests, are a Korean edition feature; how they handle information is set out in the Korean version of this policy. The IEUM app (English edition) does not offer them.

Install source totals

From app 1.0.7, when you open a newly installed IEUM for the first time, the app checks once whether the install came from an ad or a link. On iPhone, it uses Apple’s ad attribution feature (AdServices) to learn only whether the install came through Apple Search Ads and, if so, the campaign number. Your device asks Apple directly; IEUM’s server never receives the value used for this check. On Android, it reads from the install link that Google Play passes to the device only the source, medium and campaign name, whether an ad click number was present, and a marker IEUM adds for which screen that link points to. The click number and everything else are discarded on the device; the screen marker (a chapter or a reading invitation you received) is used only to open that screen on the first launch and is never sent to the server.

IEUM’s server then receives only the week the app was first opened, the app version, the edition, the operating system, the install source (an Apple Search Ads campaign number, a link tag, or “no source”), and one of “first opened,” “opened again the next day,” or “opened again on day 7.” The server only checks the app version without storing it, and adds one to the total for the other values. No install key, device identifier, advertising identifier (IDFA or advertising ID), ad click number, account, notes, or Bible location is sent. These totals are used only to measure how well ads and links work; they are not combined with other companies’ data, not given to advertising companies, and not linked to usage totals.

Nothing is sent after the day-7 check (anything that could not be sent is retried for up to 14 days from its day), and once eight days have passed since the first open with nothing left to send, this device’s install-source record is deleted. Apps updated from an earlier version and test builds send nothing. Turning off “Share usage totals” in Settings stops sending and deletes this device’s record right away. Totals on the server are deleted after 400 days. To prevent abuse, daily request counts are kept only under the first part of an irreversible hash of the requesting IP address mixed with a value that changes every day, and are deleted after three days.

Usage totals

From app 1.0.7, on this device, the app counts only numbers about each day’s use: the days, weeks and months you opened it, minutes on screen, minutes of Bible narration and whether they passed 5, 15, 30 or 60, how many chapters you finished reading or listening to (not which ones), the kind of plan you started (listening year, M’Cheyne, topical, season or other), how often you opened and completed the share sheet (verse card, verse text, chapter listening, plan, scene invitation, reading invitation, season invitation or “listened today,” and whether it went to KakaoTalk, Messages, Instagram or elsewhere), whether you opened the app from a widget, the Lock Screen, a notification, a shortcut or a link, and whether you came back after some days away. From app 1.0.8, it also counts, as numbers only, taps on the Today screen shortcuts (today_tools_tap — not which one), once a day on a device that shows today’s part on the shortcuts (today_tool_status_on), tasks finished from a notification button (notice_action — only which kind: verse, plan, listen or recite), how often reminders paused themselves (notice_rest), how often a reminder kind was turned off (notice_off), the set chosen in “My time with the Word” (timetable_preset — dawn, commute, lunch, night or sunday), how often a custom-range plan was started (plan_custom_start — not the range or books), journey finish cards (journey) and plan finish cards (plan_done) among share sheet kinds, and the verse card frame used (vcard_frame — paper, forest, dawn, storm, nets, night, hold, today, book or photo_paper, plus square for a square card).

It also counts, as numbers only, how often listening was started and finished from the listening shelf (before-sleep sets, a whole book, following a life), today’s verse chapter, season readings and “Listen from this verse” in copying (not which set, book, person or chapter), how often the reminder suggestion was seen and a time chosen, how often a reading invitation was started, how often a pause was turned on, how often a season look-back was seen, and the days you copied a passage or marked it as written on paper. Minutes heard while a before-sleep set plays are counted apart from other listening minutes.

IEUM’s server receives only these numbers with the date, app version, edition, operating system, and a range of days since the app was first opened on this device (first day, next day, days 2–6, day 7, days 8–29, day 30, after day 30). No device identifier, install key, account, advertising identifier, chapters or verses read, or any of your writing (prayers, reflections, Quiet Time, sermon notes, memos, searches), and no Story Companion conversation is sent. The prayer book, reflection, Quiet Time and sermon note screens have no counting of their own, so nothing you do there is counted; time spent on them is added only to the app’s overall screen minutes, without recording which screen it was. Notification buttons (notice_action) are counted only on verse, reading, listening and memorizing reminders; buttons on prayer and sermon note reminders are not counted (opening the app from a notification is counted app-wide, without which notification). Nothing links one report to another. The server only adds the numbers to totals. The totals are used only to improve the app and measure how its features work; they are never used to profile anyone’s religious views or for advertising, never given to other companies, and never combined with install-source totals.

Reports are sent when the app goes to the background and when you open it next, no more than four times a day. Numbers that could not be sent are discarded on the device after 7 days (at most 30 days if the device clock was changed). Turning off “Share usage totals” in Settings stops sending and immediately deletes unsent numbers and “already counted” marks on this device. Totals on the server are deleted after 400 days. To prevent abuse, daily request counts are kept only under the same irreversible daily IP hash used for install-source totals, never stored with the totals, and deleted after three days.

When narration is played on a shared link page at ieumbible.com, only the number of plays started, passed halfway and finished is counted by date, edition and link tag, without cookies.

App health information

From app 1.0.7, to find and fix errors such as the app stopping, a screen failing to draw, or Bible narration audio failing to play or download, while “Send error reports” is on, the app counts that day’s errors by type on this device and sends them to IEUM’s server once, the next day. Each report covers at most 20 kinds of errors. Only the iOS and Android apps do this; IEUM opened in a web browser neither counts nor sends errors.

Only the following is sent: the app version and build number, the language edition (Korean or English), the operating system (iOS or Android) and its major version, the date of the errors (not the time; for an app crash or a reloaded blank screen, the date the app next ran and learned of it), the type of error (an error in the app’s code, a screen that failed to draw, a blank screen the app had to reload, an app crash, or Bible narration audio that failed to play, download, or verify), the error’s type name (such as TypeError, sent only when the name set by the app’s code or the operating system is on a fixed list or fits a fixed pattern; for an app crash, the exception or signal name or the exception class name the operating system reports; for Bible narration, the failure code and the audio source), where in the app’s code the error happened (the name of an IEUM app file with line and column numbers, or numbers that point to a place inside the app’s executable; at most 5), a signature that groups the same error (an irreversible hash of the error type, name, and location), the kind of screen it happened on (a name such as Today, Bible reader, or Settings), and how many times that error happened that day.

The report itself does not contain the error message (neither its first line nor any other part), install keys, advertising identifiers or other device identifiers, the device model, your IEUM account or sign-in details, the passage you were reading, anything you write such as reflections, prayers, or notes, search terms, or the exact time and time zone. When something other than an error object is thrown, the app does not read that value and counts it only as “not an error object.” These reports carry no IEUM sign-in credential, so they are not linked to your IEUM account. As with any online request, technical connection information (your IP address, and the user-agent value your browser adds along with its summary of the browser name and version, whether the device is mobile, and the operating system name; on Android the user-agent value can include the device model) and the time the server receives the request are processed in transit, but IEUM’s server does not store them as app health information.

IEUM’s server keeps only totals by date, app version, edition, operating system, error type, and signature, and deletes them after 90 days. For each signature, it keeps one sample of the error type name, code location, screen type, and major operating-system version for 30 days. To prevent abuse, the requesting IP address is hashed irreversibly with a value that changes every day and counted only as that day’s number of requests, which is deleted three days later; the IP address itself is not stored.

Error records waiting to be sent stay on this device for at most 7 days, and a day’s records, along with any older ones, are removed when they are sent. If sending fails, they are discarded, not sent again. They are not included in the “Move to a new phone” records file or in Android device-record backups, and you can also clear them yourself in Settings › On this device.

In app 1.0.7 and later, “Send error reports” is on by default, and you can turn it off in Settings › App health. When it is off, the app neither counts nor sends errors, and it removes the records already gathered on this device right away. Separately, crash reports that Apple and Google collect at the operating-system level (App Store Connect and Xcode, and Google Play Android vitals) reach us only if you agreed in your device settings to share them with app developers, and you can turn that off in your device settings.

Services that help operate IEUM

The release app uses Vercel for server hosting and private audio storage, and Turso for database storage. Server functions and the database are provisioned in Japan (Tokyo); audio storage is provisioned in the United States (Washington, D.C. region). Apple handles authentication. These providers process the identifiers, saved content, and technical information needed to deliver the features you request. Our server host (Vercel) handles the access and usage records created as it runs the service (operational information such as request times and addresses) under its own policies. External Bible sources, calendar apps, and sharing destinations have their own privacy practices.

From app 1.0.7, Bible narration files (audio and verse timings) are delivered from Cloudflare’s storage and network in the United States. While delivering them, Cloudflare processes technical connection information such as the requested address and your IP address; IEUM does not receive or store these request logs. The setting that turns narration on or off and the file address are fetched from ieumbible.com without any identifier or sign-in information.

If you buy a tip, the App Store or Google Play processes the payment. For tips, IEUM’s servers do not receive your payment details, receipts, or purchase history, and the app keeps no record of tips on your device. Apple’s or Google’s privacy policy applies to the payment.

To confirm a Through Their Eyes subscription, IEUM’s server receives the transaction information signed by the App Store or Google Play (such as the product, purchase and expiry times, and the original transaction number or purchase token) and checks the subscription status with Apple’s or Google’s servers. The original transaction number and purchase token are stored only as irreversible hashes and are deleted, with the status and expiry time, 90 days after the subscription ends. We do not receive your payment method, name, or email address. From app 1.0.7, 1-month and 1-year passes with no automatic payment are checked the same way (Apple: hashed transaction number, purchase time, pass length and refund status; Google: hashed purchase token and expiry time), and whether the store reported a payment problem (grace period or hold) is kept with the subscription status. Pass records are kept until 90 days after the pass ends (or after a refunded transaction’s original end date), then deleted.

If you contact support, we receive the contact information and content you send. Reports can include the reported content, account or content identifiers, your reason, and information needed to review the issue. Blocking requires recording the relationship between the accounts. We use this information to respond to requests and operate safety controls.

The IEUM app includes the fonts it uses to display text, so showing an app screen does not send a request to an outside font service. Invitation pages shared from the app display text in the system fonts already on the viewer’s device and do not load fonts from elsewhere.

On ieumbible.com, the app information page and the store buttons count only how many times they are tapped, by date and route. Nothing that could identify the person who tapped is stored. Verse, scene and invitation pages shared from the app are counted the same way, only as daily totals by page type, and nothing that could identify the person who opened them is stored. From app 1.0.7, “Send this chapter to listen to” sends a link to the chapter and its first verse through the app you choose; we do not record who sent what. That chapter link can be listened to on ieumbible.com. The narration file is fetched from the narration storage (Cloudflare R2) only when Listen is tapped, and the device’s connection information (such as its IP address) reaches that storage provider. The page uses no cookies or analytics; opens and store-button taps are counted only as daily totals. Reading invitation, today’s portion, this week’s portion, season and church schedule pages likewise count only openings and narration starts, halfway points and finishes by date, edition and link tag, without cookies, and do not record which plan was opened. When IEUM is installed on Android from the Google Play button of a shared link, the link’s chapter or plan start date is passed along in Google Play’s install information so the first launch can open it. The value is used once on the device, then discarded, and never sent to our server. Topic plans are never passed.

Online requests also involve technical connection information needed to deliver and secure the service. Please contact us about the handling of your information or the services involved.

Pastor tool and church pages

The pastor tool at ieumbible.com/pastor is offered only in Korean, to invited pastors; how it handles information is set out in the Korean version of this policy. The IEUM app (English edition) does not use it.

Where your information is processed

We use the providers below to operate IEUM, or your device communicates with them directly. Information is sent over encrypted network connections when you use the app or website, so it can be processed outside your country, including in Japan and the United States.

Recipients’ contacts: Vercel Inc. (privacy@vercel.com), ChiselStrike Inc. (Turso, support@turso.tech), Apple Inc. (privacy contact form at apple.com/legal/privacy/contact), Anthropic, PBC (privacy@anthropic.com), Google LLC (Privacy Inquiry form at support.google.com/policies/contact/general_privacy_form), and Cloudflare, Inc. (privacyquestions@cloudflare.com).

If you do not want your account and records processed in these locations, you can choose not to create an account or request account deletion. Features that need an account, such as saving and sharing, are then unavailable. If you do not want Through Their Eyes messages processed abroad, don’t turn it on, or turn it off in Settings › Through Their Eyes. If you do not want Bible narration files delivered through Cloudflare, don’t play or download narration in the app; reading the Bible text works as usual.

Providers and locations
RecipientCountry or locationInformationPurposeWhen and howRetention
Vercel Inc.US company. Server functions run in Japan (Tokyo, hnd1); audio storage is in the United States (Washington, D.C. region)Account identifiers, saved and shared records and audio files, Through Their Eyes requests and app health reports (only while processing), usage-total and install-source requests (only while processing), and technical connection informationServer hosting, private audio storage, and relaying Through Their Eyes AI requests (AI Gateway, depending on operating settings)Sent over the network whenever you use the app or websiteSame as the retention periods in the next table
ChiselStrike Inc. (Turso)Japan (Tokyo region)Account information, saved and shared records, reports and blocks, Through Their Eyes hashed values, counts, subscription status and passes, and AI reports, and app health totals and samples, and usage and install-source totals with abuse-prevention request countsDatabase storageSent over the network when our server handles a requestSame as the retention periods in the next table
Apple Inc.United StatesSign in with Apple credentials and identity tokens, a revocation request when you delete your account, and signed Through Their Eyes subscription transactions, and a one-time value for checking Apple Search Ads attribution on iPhone (sent by the device directly to Apple)Sign in with Apple and revoking it, and confirming a Through Their Eyes subscription, and checking whether an install came from Apple Search AdsWhen you sign in with Apple, delete your account, or a subscription is confirmed, or when a newly installed app is first opened (retried a few times within 24 hours)Under Apple’s privacy policy
Anthropic, PBCUnited StatesMessages you send in Through Their Eyes and up to the last 12 messages of the conversation, figure, scene, and verse locations, your device’s date, crisis-word category flags, letter notes and the day’s verse location (when you use letters or personalization), and a pseudonymous value made by our serverWriting Through Their Eyes replies, letters, and notes, and safety checks (including checking for signs of crisis)Each time you send a message or request a letter or note after agreeing, over an encrypted connectionDeleted within 30 days; if flagged for a safety-policy violation, inputs and outputs up to 2 years and safety scores up to 7 years, or longer where the law requires (to refuse, don’t turn it on, or turn it off in Settings › Through Their Eyes)
Google LLCUnited StatesProduct and purchase token of a Google Play subscription, and Android attestation (Play Integrity) tokensConfirming a Through Their Eyes subscription and checking app attestationWhen a subscription or usage pass is checked on AndroidUnder Google’s privacy policy
Cloudflare, Inc.US company. Narration files are stored in Cloudflare R2 and delivered from a nearby location of Cloudflare’s networkFor each Bible narration file requested, the request address (which chapter’s file) and technical connection information such as the IP addressStoring and delivering Bible narration files (AI-generated voice)When narration is played or downloaded in the app, over an encrypted connectionUnder Cloudflare’s privacy policy. IEUM does not receive per-request records and sees only the totals Cloudflare reports

Information, purposes, and retention

The table below lists the information our servers process, why we process it, and how long we keep it. Drafts, your reading record, reading plans, and church year readings, your prayer notebook, your Scripture Memory cards (the verses you’re learning and when each comes back), My Verse Book and its set-aside copies, guest highlights you have not moved to your account and your guest reading place, the copy of your signed-in verse marks, bookmarks, and reading place, the sign-in tag and end time, your search result order and recent searches, when the app last asked for a rating (with the app version it asked in and when you last tapped “Send feedback”) and the day it first opened on this device, your phone’s text size, your Community Guidelines agreement, reading preferences, and reminder settings stay on your device and are not sent to our servers, so they are not listed. The listening days (the last three) and letter days (up to three) kept to choose when to ask for a rating also stay on your device and are not sent. They are removed when you clear them on the device or remove the app.

What we process, why, and for how long
InformationPurposeRetention
Sign-in provider identifier, the name and email the provider supplies if you allow it, and an invited account’s username, display name, and password hashRecognizing your account, signing you in, and protecting access to your recordsUntil you delete your account
IEUM session credential and temporary sign-in codeKeeping you signed in and finishing sign-inA session lasts 30 days unless revoked earlier; the code lasts 2 minutes and works once
Encrypted Sign in with Apple tokensValidating sign-in and revoking Apple authorization when you delete your accountUntil account deletion and Apple revocation are complete
Saved reflections and prayers, passage references, narrator and recipient labels, audio, bookmarks, verse highlights, reading position, journey progress, drafts of journeys you create, and revisit settings and repliesKeeping the records you save and showing them againUntil you delete them or your account
Group name and passage, your group display name and the notes or audio you share, your part in group activities (Pilgrimage together, Row together), published journeys, and the name and message on invitationsDelivering the shares you chooseUntil you remove the share, the group is closed, or you delete your account. Revoking an invitation or withdrawing a journey closes only the public link; remaining stored copies are deleted with your account
Contact details and messages you send to supportResponding to your requestAs long as needed to resolve the request; you can ask us to delete it
Reported content, account or content identifiers, and reasons, and the accounts you blockReviewing reports, acting on them, and operating blockingReports: as long as needed to review and act on them. Blocks: until you unblock or delete your account
Minimal account deletion marker, without reflection text or audioPreventing delayed requests from recreating deleted recordsAs long as needed for this protection
Technical connection information such as IP address and device or browser detailsDelivering and securing the serviceAs long as needed to deliver and secure the service
Through Their Eyes subscription status (hashes of the original transaction number or purchase token, product, status, whether a trial, whether it renews, whether the store reported a payment problem (grace period or hold), expiry time, and whether a test purchase) and hashes of the install keys using itConfirming the subscription and managing how many devices use it (up to 5)Until 90 days after the subscription ends
Through Their Eyes passes (Apple: hashed transaction number, purchase time, pass length (1 month or 1 year), refund status; Google: hashed purchase token, expiry time) and the hashed install keys using the passConfirming passes and managing the number of devices using a pass (up to 5)Kept until 90 days after the pass ends (or after a refunded transaction’s original end date), then deleted
Daily use and attempt counts by Through Their Eyes install-key hash and IP-address hashDaily limits and preventing abuseDeleted three days after that day
Free-reply counts by Through Their Eyes install-key hash, and the date the free-reply letter was receivedManaging free replies and the one free-reply letterOne year from first use
iPhone app attestation public keys (with the install-key hash)Checking app attestation and preventing abuse60 days after last use
Hashes of store subscription notificationsNot applying the same notification twice30 days
Reported AI replies or letters, the reasons chosen and anything added, and your previous message if you turned that onReviewing reports and improving the feature90 days
Numeric totals of crisis notices and replies by date, edition, and typeReports required by law and operations3 years
App health information (error type, error type name, code location, signature, screen type, and count, with the app version, edition, operating system and its major version, and date) and request counts by IP-address hash for abuse preventionFinding and fixing app errors, and preventing abuseTotals: 90 days. One sample per signature: 30 days. Request counts by IP-address hash: deleted three days after that day
Install source totals (first-open counts and next-day and day-7 reopen counts by first-open week, edition, operating system and install source)Measuring how well ads and links work400 days
Usage totals (counts and minutes of fixed items by date, app version, edition, operating system and days-since-first-open range)Improving the app and measuring how features work400 days
Narration plays on shared link pages (by date, edition and link tag)Measuring how sharing works400 days
Daily request counts per IP address hash for install-source, usage-total and shared-link play requestsPreventing abuseDeleted three days after that day

Keeping and deleting information

Saved account content remains available while it is stored in IEUM. You can delete individual notes and their attached audio, remove your own group shares, leave groups, and request deletion of your IEUM account. Revoking an invitation or withdrawing a journey closes its public link; that action alone is not a request to erase every stored version.

Account deletion removes your account-associated saved records and the shared content controlled by IEUM, including your uploaded audio. Groups you own are closed; other members retain their own original private notes. Access credentials are revoked. If deleting an audio file fails temporarily, a deletion task is kept for retry and deletion remains pending until that work is complete.

Support messages and safety reports are used to resolve the request or issue for which they were provided. Contact us if you want to request access, correction, or deletion of information in that correspondence. We may need to verify that the request concerns your account.

Deleting IEUM data does not delete your account with Apple or another sign-in provider, or files and calendar events you exported to another app. The account-deletion page explains the available controls.

App health information (from app 1.0.7) is gathered on this device for a day and sent the next day, and records waiting to be sent are removed within 7 days. On our server, totals are deleted after 90 days and samples after 30 days. Turning off “Send error reports” in Settings › App health removes the records gathered on this device right away.

How we protect information

Connections between the app and our servers are encrypted (HTTPS). Access to records and audio is limited by account permissions, and audio files are kept in private storage. Sign in with Apple tokens are encrypted on the server, invited-account passwords are stored only as hashes, and your device keeps the IEUM session in its protected credential storage. Records are not end-to-end encrypted, so the service and its storage providers can process them.

Your choices and questions

You can read without signing in, choose what to save, decline microphone access, decide what to share, and remove saved content. For privacy requests, account-access problems, or a concern about a child’s information, contact support@aboutusforyou.com. Please do not send passwords or sign-in codes.

We update this policy when our data practices change. The published version and its update date are available on this page.

Your privacy rights

Depending on where you live, you may have the right to access your personal information, correct it, delete it, receive a copy of it, object to or restrict certain processing, and withdraw consent you have given. In the European Economic Area and the United Kingdom, these rights come from the GDPR and the UK GDPR, and you can also complain to your local data protection authority. California residents have the right to know what personal information we collect, use, and disclose, and to ask us to delete or correct it. We will not treat you differently for exercising these rights.

We do not sell personal information, and we do not share it for cross-context behavioral advertising.

To exercise these rights, use the in-app controls to view or delete your records, remove your shares, or delete your account, or email support@aboutusforyou.com. An authorized agent can also make a request for you. We may need to verify that the request concerns your account, and we respond within the time required by applicable law.

IEUM does not ask your age at sign-up and is not designed for young children. If you believe a child’s information was saved without a parent’s permission, contact support@aboutusforyou.com. Through Their Eyes (AI) and its subscription are only for people 18 and over; age is checked with the device’s age signal or by asking for a birth year.

Privacy contact

AboutUsAgency, Inc. is the controller of the personal information processed through IEUM. For privacy questions, requests, or complaints, contact AboutUsAgency, Inc. at support@aboutusforyou.com.

Deletion protection

A minimal account deletion marker is kept to prevent delayed requests from recreating deleted records. It does not contain your reflection text or audio.

Sign in with Apple

You can sign in with Apple in the app. We verify Apple’s signed identity token, application identifier, and one-time nonce on our server. Apple email is used only when verified. Apple authorization tokens are encrypted on the server and used to validate or revoke authorization. Your device stores an opaque IEUM session in its protected credential storage.

Deleting your account also requests revocation of Apple authorization. If Apple is temporarily unavailable, encrypted revocation information remains only for cleanup; return to the deletion screen to retry. If a token exchange ended without a recoverable token, we explain how to revoke the app in Apple account settings. A minimal deletion marker is retained to prevent an in-flight request from recreating deleted data.

Previous website accounts

The release app uses a separate service. Records in the earlier OpenAI-hosted website are not automatically copied or linked to the new app. We preserve that website and its data; access to or migration of those records depends on restoring access to the original service. Korean and English app accounts and records are separate.