Privacy Policy
What stays on your phone. What leaves it.
1. The short version
On iPhone: Tracking for ad measurement happens only if you allow it: on a fresh installation iOS shows Apple's tracking prompt once, and only if you tap Allow does With Him send Meta an advertising identifier and limited app and device information so we can measure which Meta ads led to installs. If you decline, nothing is sent to Meta and no feature is limited. Optional usage analytics through PostHog are off by default for each account and require your explicit consent while signed in; you can turn them off in Settings at any time. Using the iPhone app requires Sign in with Apple; finishing a verse reading to stop an alarm or lift the Focus Shield never waits on it. Your reading progress, reading history, alarms and settings are kept in your With Him account so they come back after a reinstall or on a new device; with With Him Plus, your notes, highlights, bookmarks and saved sermon notes are kept there too. When you use Ask, the conversation and your denomination stay on your device, but the latest context needed for each answer is sent through our authenticated Supabase service to Microsoft Azure. If you choose AI sermon processing on iPhone, an authenticated service sends your selected sermon recording, written notes and metadata to Microsoft Azure to prepare a draft for your review. Feedback also reaches our services when you choose to send it.
On Android: Google sign-in and With Him Plus are required to use the main app. Google Play and RevenueCat handle subscriptions. Manage Screen Time reads actual app package names, categories and foreground timing locally, not screen content, and does not send those app identities or usage times to us. English verse recognition uses on-device Vosk; Android's system recognizer, used for Korean and eligible fallback, may stream audio to its provider only after your explicit consent for that session. Sermon recording can continue with the app hidden or screen off, and saving an audio draft sends the recording through Supabase to Microsoft Azure for transcription and summary. Ask sends limited recent conversation context and an optional tradition through Supabase to Azure OpenAI. Optional PostHog analytics are off by default per account. Android has no ads, advertising-ID collection or Meta SDK. See the Android details below and account-deletion instructions.
This website collects an email address only if you choose to type it into the Android waitlist form, so we can write to you once when an Android version is available. The form creates no app account. See Android waitlist in section 5.
The rest of this page is the same statement said precisely enough to be relied on.
The Android app
The Android app differs from the iPhone app in the ways below. Apple-specific descriptions elsewhere on this page apply only to iPhone; these Android descriptions apply instead where the platforms differ.
Google sign-in, account sync and Plus
Android requires Google sign-in to create or access your With Him account, and a With Him Plus subscription to use the main app. Google provides an identity token and account information, including your Google identifier, email address and available name, which we use through Supabase for authentication and account management. Your account ID links your progress, reading history, alarms, settings and eligible Plus library content to your account. Notes, highlights, bookmarks and confirmed sermon notes, including saved writing and sermon information, sync separately from AI processing.
Google Play handles Android payments; we do not receive your card details. RevenueCat receives purchase records and tokens, subscription status, your With Him account ID, an SDK-generated installation identity and limited technical device information to provide and verify Plus access. This subscription infrastructure is not controlled by the optional PostHog analytics switch. RevenueCat's documentation describes country information from transactions or an IP-country fallback; the app does not request device-location permission. Manage or cancel a Play subscription in Play Store → Payments & subscriptions → Subscriptions → With Him.
Manage Screen Time: Accessibility service and Usage access
If you enable Manage Screen Time, With Him uses an Android Accessibility service to observe the real package name when the foreground app changes, compare it with the apps and Android categories you choose, and measure elapsed foreground time to decide when to show a verse gate. The app picker reads launchable-app package names, labels, categories and icon/update information. With Usage access, it reads package-level usage events and timestamps on this device to calculate foreground intervals, current usage and recent comparisons, and optional usage nudges.
Observed app identities, your selected packages and categories, exclusions, and measured usage and timing stay on this device. They are not sent to With Him, Supabase or PostHog. Only general shield settings such as the enabled state, schedule and thresholds sync to your account. The service does not retrieve screen content, text, taps, passwords, messages, screenshots, browser history or web addresses. With Him is not an accessibility tool for disabilities. Enabling this local package-level use requires a separate disclosure and affirmative consent before Android Settings; you can decline or revoke access there. It is a best-effort interruption, not an immutable device lock.
Verse-reading speech
English verse reading uses the Vosk recognizer on the device; that recognition path does not upload microphone audio. The English model is bundled; if it is missing, the app may download it from Alpha Cephei over HTTPS without sending audio. Korean uses Android's system recognizer, and English can use it as an eligible fallback. Before a system-recognition session that may use the network, the app asks for explicit, session-only consent: Allow this time or Keep typing. Android's regular speech service may stream microphone audio and verse-vocabulary hints to its installed provider. With Him does not record that verse-reading audio. The provider depends on your device; its handling and retention are governed by its own terms. You can type instead.
Sermon recording and AI processing
Android sermon recording continues while With Him is hidden or the screen is off, using a microphone foreground service and an ongoing notification. Starting recording alone does not upload it. Saving or finishing a draft containing audio starts processing: only the recording, together with the authentication and technical job information needed to process it, is sent through private Supabase storage and our service to Microsoft Azure Speech for transcription and Azure OpenAI for a summary. Android does not include your written note, title, church, speaker, service, date or Scripture references in that AI input. Saved writing and sermon information can still sync to your account as part of the confirmed note.
When processing succeeds, Android automatically confirms the summary, deletes the local recording and acknowledges the result for backend cleanup; it does not wait for a separate review-and-confirm tap. You can edit or delete the saved note. Record only with the necessary permission. Local draft audio and temporary provider content follow section 9; Microsoft's separate abuse-monitoring retention also applies.
Ask messages and operational records
Ask is optional and requires consent before the first send. Each authenticated request sends up to eight recent user and assistant turns in total, including your new message, optional Christian tradition or denomination, an attached passage reference if chosen, Bible edition, language and relevant response/safety context through Supabase to Microsoft Azure OpenAI. This content can reveal religious beliefs or contain other personal information you enter. With Him does not store the conversation or selected tradition on its servers; conversation history and the tradition preference are stored on your device and are not account-synced. Ordinary sign-out does not erase the local history; confirmed account deletion purges that account's local history on the device.
The backend does retain daily quota counters associated with your user ID and content-free operational request metrics, such as duration, status, error class, token counts and safety/tool metadata. These records support access limits, reliability and safety and are separate from optional PostHog analytics. Microsoft states that Azure OpenAI inputs and outputs are not used to train foundation models without permission, but may retain and review content flagged for abuse monitoring. We have not established that this service is exempt from that monitoring; do not assume end-to-end zero retention.
Optional analytics, updates and network connections
As on iPhone, PostHog usage analytics are optional and off by default for each account. Signed-in consent is required, and you can withdraw it at Profile → Settings → Privacy → Share usage data. Events use account-linked pseudonymous identifiers and limited app/device context, not verses, notes, audio, Ask messages, tradition, selected app packages or usage durations. Turning the switch off stops future PostHog events and discards unsent events; provider erasure of previously sent events is asynchronous. Android requests that PostHog disable IP-based location lookup; server-side IP logging and retention depend on the provider configuration.
Google Play In-App Updates checks for eligible updates and handles installation through Google's system flow after you choose Update. Google processes technical update information such as device metadata, app version and this app's installed modules or asset packs; this is not your installed-app inventory. Android contains no ads, does not collect the advertising ID and does not use Meta. All network requests made by the With Him Android app use HTTPS, including account, subscription, analytics, artwork and AI-processing requests. This is encryption in transit, not end-to-end encryption. The separately installed system speech provider controls its own network service and transport.
Android feedback includes what you type and app/Android version information. No account identifier is attached, but our backend uses an IP-derived, one-way security identifier to limit abuse before sending feedback to our development tracker. Avoid including private information you do not want stored there.
To delete your account, use Profile → Settings → Account → Delete account. Android also offers Account from the required subscription screen without paying. You can instead request deletion by email without reinstalling the app: see Delete your With Him account.
Android 앱 개인정보 안내
Android의 기본 앱 이용에는 Google 로그인과 With Him Plus 구독이 필요합니다. Google의 계정 식별자, 이메일과 제공된 이름을 Supabase 인증에 사용하며, 진행 상황·읽기 기록·알람·설정과 Plus 보관함은 계정에 동기화됩니다. 결제는 Google Play가 처리하고 RevenueCat은 구매·구독 상태, 계정 ID, 설치 식별자와 제한된 기기 정보를 처리합니다. 구독 취소는 Play 스토어 → 결제 및 정기 결제 → 정기 결제 → With Him에서 할 수 있습니다.
스크린 타임 관리의 접근성 서비스와 사용 정보 접근 권한은 실제 앱 패키지 이름, 선택한 Android 카테고리, 전면 앱 변경과 이용 시간을 기기에서만 처리합니다. 앱 목록과 관측한 이용 시간은 전송하지 않으며, 화면 내용·문자·탭·비밀번호·메시지·스크린샷·방문 기록·웹 주소를 가져오지 않습니다. 일정·제한·활성화 여부 같은 일반 설정만 계정에 동기화됩니다. 별도 안내에 동의한 뒤 권한을 켤 수 있으며 Android 설정에서 언제든 철회할 수 있습니다.
영어 말씀 읽기는 기기 내 Vosk를 사용합니다. 한국어와 필요한 영어 대체 인식은 Android 시스템 음성 서비스를 사용하며, 네트워크 인식이 필요하면 매 세션마다 이번만 허용 또는 계속 입력하기를 선택하게 합니다. 허용하면 설치된 음성 제공자에게 마이크 음성과 구절 어휘 정보가 전송될 수 있습니다. With Him은 이 말씀 읽기 음성을 녹음하지 않으며, 제공자의 처리·보관 조건은 해당 제공자가 정합니다.
설교 녹음은 앱을 벗어나거나 화면이 꺼져도 포그라운드 알림과 함께 계속됩니다. 녹음이 있는 초안을 저장하거나 마치면 녹음과 처리에 필요한 기술 정보만 Supabase를 거쳐 Microsoft Azure Speech와 Azure OpenAI로 전송됩니다. 작성한 메모와 설교 정보는 Android의 AI 입력에 포함되지 않지만, 완성된 노트로 계정에 따로 동기화될 수 있습니다. 처리가 성공하면 요약이 자동 확정되고 기기의 녹음은 삭제됩니다.
Ask는 동의 후 새 메시지를 포함해 총 최대 8턴의 최근 대화와 선택한 신앙 전통, 구절 참조 및 응답에 필요한 정보를 Supabase를 거쳐 Microsoft Azure OpenAI로 보냅니다. 대화와 신앙 전통은 With Him 서버에 저장하지 않지만 계정별 일일 한도와 내용 없는 요청 운영 지표는 보관하며, 선택적 PostHog 분석과는 별개입니다. Microsoft는 오용 감시에서 표시된 내용을 보관·검토할 수 있습니다.
PostHog 사용 분석은 iPhone과 마찬가지로 계정마다 기본적으로 꺼져 있고, 로그인 후 동의해야만 전송됩니다. Android에는 광고·광고 ID 수집·Meta SDK가 없습니다. 앱의 네트워크 요청은 HTTPS를 사용하지만 별도 시스템 음성 서비스의 통신은 해당 제공자가 관리합니다. Google Play 인앱 업데이트는 앱 버전 등 기술 정보를 처리합니다. 계정 삭제는 프로필 → 설정 → 계정 → 계정 삭제에서 할 수 있고 구독 화면의 계정 메뉴에서도 결제 없이 가능합니다. 이메일 요청과 보관 기간은 계정 삭제 안내를 참고해 주세요.
2. Your voice
On iPhone, verse-reading audio stays on your device and is not recorded or retained. Apple's on-device speech recogniser checks the reading. Sermon recording is a separate, optional feature with its own recording and processing controls. Android speech and sermon behavior is described in The Android app.
What the app keeps from a spoken reading is the outcome, not the sound: that a verse was completed, when, and by which method (spoken or typed). That record is stored on the device and, when you are signed in, in your account, and it is what the reading history and the alarm's own logic are built from.
The microphone is used for verse reading or when you start a sermon recording. iOS displays its microphone indicator while capture is active. On iPhone, sermon capture pauses when the app leaves the foreground; it does not add background recording. Obtain permission to record when required by the speaker, venue or applicable rules. Declining microphone access does not prevent manual note taking.
On iPhone, choosing AI processing sends your manual writing, optional sermon metadata and recording through encrypted transport to our authenticated Supabase backend and Microsoft Azure. Azure transcribes the recording and prepares a note, with your writing treated as the primary source. You can edit the result and must confirm it before it becomes a completed sermon note. We do not log recordings, transcripts, note bodies or prompts containing your content.
3. What stays on the device
The following is held in the app's own storage. When you are signed in, the items noted below are also kept in your With Him account — see What we do collect. Sermon content is sent to our AI processing service only when you choose that action:
- Highlights, notes and bookmarks — also kept in your account with With Him Plus.
- Your reading position, your daily-verse progress, your reading history and which passages have been completed — also kept in your account.
- Alarms and their schedules — also kept in your account. The record of which alarms were answered stays on the device.
- Focus Shield settings — the schedule and limits are also kept in your account; the apps you selected stay on the device.
- Reading preferences: theme, text size, translation, language — also kept in your account.
- Your Ask conversations and denomination or tradition preference. They are not synced to your account. The latest context needed to answer is transmitted when you send an Ask message, as described below.
- The Bible text itself, which ships inside the app and needs no network at all.
On iPhone, some of this is shared between the app and its extensions through a private App Group container on the device, which is what lets the shield and the alarm agree with the app about what has been read. That container is local; it is not a sync service.
4. Screen Time data
On iPhone, the Focus Shield uses Apple's Screen Time (Family Controls) framework. When you choose which apps to shield, iOS hands the app opaque tokens rather than the identities of the apps — by Apple's design we cannot see which apps you picked, and the selection cannot leave the device. Usage figures shown in the app are rendered by a sandboxed Apple extension that is not permitted to return data to us either. Android uses actual package identities locally through Accessibility and Usage access, as described above.
5. What we do collect
The following content reaches our services only through the corresponding feature you choose.
Feedback you type
On iPhone, Settings → Send feedback turns what you write into an issue in our development tracker. No identifier is attached, so it is not linked to you or to your device. Do not put anything in that box you would not want stored — including your email address, unless you want a reply and are content for it to be recorded. Android feedback also includes app/OS version information and connection-based abuse protection, as described above.
Identity
Using the iPhone app requires Sign in with Apple. It provides an Apple user identifier, an email address — Apple's private relay address unless you share your real one — and the name Apple supplies on first authorisation. Android requires Google sign-in through Supabase, as described above. AI processing requests are authenticated and therefore associated with your account while they are handled; their religious content must not be treated as anonymous or unlinked. Ordinary highlights, bookmarks, alarms and reading positions are not sent to the AI service.
Your reading progress, reading history and settings
When you finish a verse reading — to open an alarm, to lift the Focus Shield, or reading a passage aloud in the Bible — the app records that reading so it can tell you how many times you have now read that passage. Each reading is one record: which passage it was, where it came from, whether you read it aloud or traced it, and when. If you answer the optional question about how much the verse touched you, that answer — a position on a scale, with no number shown to you — is stored on the same record. Reading-completion sync sends references, not Bible text; the text already ships inside the app. Android's system speech service may receive verse-vocabulary hints as described above.
When you read aloud in the Bible, or through a book in the read-through, the app also keeps which verses you read each day and the hour of the day you read each one, so the verse count on Home and your History show the same numbers on every device. It keeps only verse references, days and hours — never the words you spoke or any audio.
If you are signed in, these records are stored in our Supabase backend and linked to your account, so the count follows you to a new phone or a reinstall. The same account also keeps your daily-verse progress (which passages each day held and how far you got), your place in each Thread, the verses you read aloud each day, your Bible reading position, your alarms and their schedules, your reading and routine preferences, whether you have finished the app's introduction, and your Focus Shield schedule and limits. Our server only reads and writes the records of the account whose sign-in token accompanies the request; the app holds only your own short-lived access token and has no credential that could reach anyone else's records.
If you are not signed in, or you are offline, nothing is sent. The reading is recorded on your device, the count you are shown comes from the readings on your device, and the mission completes normally — an account is never required to finish a reading, stop an alarm, or lift the shield. Records made before you ever sign in are attributed to the first account you sign in with on that device, and are then sent. Records belonging to one account are never sent or counted under another account on the same device.
With With Him Plus, your notes, highlights, bookmarks and saved sermon notes are also kept in your account, so they come back on a new phone or after a reinstall. Without it they stay on the device. Notes you attach when you keep a passage as a highlight are part of that library, exactly as any other note is.
Sermon content you choose to process
On iPhone, we process the selected audio, your written note, optional title, church, speaker, service, date and Scripture references, the resulting transcript, and the generated draft solely to provide the sermon-note feature. Android AI processing takes the recording and technical job information, not your written note or sermon metadata; saved notes sync separately. This content can include personal reflections or religious information that you choose to write or record. Do not include material you do not want processed by these services.
Ask conversations you choose to send
Ask is a With Him Plus feature. When you send a message, the app sends up to eight conversation turns in total, including the message you just sent, together with your selected Christian tradition or denomination, the Bible edition and the app language (Korean or English), through encrypted transport to our authenticated Supabase service and Microsoft Azure. These details can reveal religious beliefs and can include any personal information you put in the conversation. Do not include content you do not want these services to process.
The complete conversation and your denomination or tradition preference are kept only on your device. With Him does not retain or log Ask conversation text or the selected tradition on its servers. We keep the account, Plus entitlement and server-side daily usage-count metadata needed to authenticate access and enforce the daily limit; that metadata does not contain the conversation text or selected tradition. Android also produces content-free operational request metrics as described above.
Android waitlist on this website
The landing page has an optional form for people who want to hear when an Android version of With Him is available. If you submit it, our Supabase database stores your email address, the date, which button you used (near the top of the page or near the bottom) and the date of this wording, which is what you agreed to. We use the address only to write to you once, when an Android version is available. We do not add it to any other list, and we do not share it or sell it.
To limit abuse, the form counts attempts from each connection using a one-way hash of the network address. The address itself is not stored. The form is on the website only, not in the iPhone app, and the website does not use it to track you. You can ask us to remove your address at any time: see section 13.
6. Purchases
On iPhone, payment is processed entirely by Apple. On Android, it is processed by Google Play. We never see, receive or store your card details, billing address, or any other payment instrument.
To know whether a subscription is active, the app uses RevenueCat, a subscription-infrastructure provider. On iPhone, RevenueCat receives the App Store purchase record and an anonymous identifier it generates for the installation, and returns whether the subscription is entitled. That identifier is not linked to your name or email unless you have signed in and we associate it. Android's Google Play purchase records, account linkage and technical information are described in The Android app.
7. Optional analytics, tracking and advertising
Usage analytics are optional and off by default for each account. We send usage events to PostHog to improve the app only while you are signed in and after you explicitly opt in through a signed-in onboarding or consent prompt, or the usage-data switch in Settings (Profile → Settings → Privacy → Share usage data; in earlier versions, Settings → Your privacy → Help improve With Him). You can withdraw consent at any time by turning that switch off. Declining or withdrawing consent does not limit the app's features. No PostHog usage events are collected while signed out or before consent, and actions from before consent are not sent later. Necessary subscription processing and content-free operational request records are separate from this optional usage analytics.
Events cover app usage, onboarding completion after consent, reading completion, paywall interactions, purchase or restore outcomes, and requests for an AI sermon summary together with how each request ended (for example, completed or stopped by a failed upload). They include event timestamps and limited app and device metadata (such as app version, operating-system version, device model and app language), together with SDK session identifiers. Your stable Supabase account ID (UUID) is used as a pseudonymous identifier. PostHog also receives a random installation identifier when linking the SDK identity to your account, only after signed-in consent. These identifiers link events to your account; the data is not anonymous. Reading-completion events do not identify the book, chapter or verse you read. Sermon-summary events carry only the kind of request and its outcome, never the note, the recording, its length or any error text. Like other network services, PostHog receives your IP address when handling requests. For iPhone analytics, our PostHog project is set to discard it so it is not stored with events, and IP-based location lookup (GeoIP) is turned off. Android explicitly requests GeoIP be disabled; provider-side IP logging and retention depend on its configuration.
We do not send PostHog your name, email address, survey answers, denomination or tradition, Scripture references or text, recordings, transcripts, sermon content, notes or conversation text. Session replay and automatic interaction capture are disabled.
PostHog is not used for advertising. We do not sell personal information for money or share it with data brokers.
iPhone ad measurement through Meta, only if you allow tracking
On a fresh installation only, shortly after you first open the app, iOS shows Apple's App Tracking Transparency prompt once. Existing users who only update the app are not asked. The app requests this permission and reads your device's advertising identifier (IDFA), but only after you tap Allow.
If you tap Allow, the Meta (Facebook) SDK for iOS starts and, each time the app opens, sends Meta an "app activated" event. Meta receives your device's advertising identifier (IDFA), Meta's own anonymous app-instance ID, and limited app and device information that the SDK attaches, such as app version, operating-system version, device model, language, time zone, screen size and similar details. Our purpose is to measure which Meta ads led to installs and app opens (ad attribution and measurement). Meta may also use the data as described in Meta's privacy policy. Meta processes data in the United States and elsewhere.
If you tap Ask App Not to Track, or later turn tracking off for With Him in iOS Settings → Privacy & Security → Tracking → With Him, the Meta SDK is not started and nothing is sent to Meta. Declining or withdrawing never limits any feature of the app. For data Meta already holds, use Meta's own controls; we cannot erase it from Meta.
Automatic event logging, automatic in-app-purchase logging and the SDK's metadata and screen-title collection are turned off. The app logs only the one "app activated" event.
We never send Meta Scripture references or text, readings or reading history, notes, highlights, recordings, transcripts, sermon content, Ask conversations, survey answers, denomination, name, email address, your Sign in with Apple identity, your Supabase account ID, or purchase or subscription data. We do not combine Meta data with PostHog analytics.
8. Who else is involved
These providers and independently operated platform services have specific roles:
- Apple — the App Store, payment, Sign in with Apple, on-device speech recognition, alarms and Screen Time, under Apple's own privacy policy.
- Microsoft Azure — sermon transcription, AI note preparation and Ask responses, under Microsoft's applicable Azure AI data privacy terms. Under the provider's policy, prompts and responses are not used to train foundation models without permission. Azure may retain content flagged by automated abuse monitoring under its own terms; we have not established that content logging is disabled for this service.
- Google — Android Google sign-in, Google Play Billing and In-App Updates, under Google's privacy policy and the applicable Google Play terms. Google Play, not With Him, handles your payment instrument.
- RevenueCat — subscription purchase records, identifiers, entitlement verification and related technical information, as described above; see RevenueCat's privacy policy.
- Supabase — authentication for Apple and Google sign-in, the progress, reading history and settings kept in your account, your library if you have With Him Plus, temporary private sermon uploads and processing jobs, authenticated relay, daily quota counters and content-free operational metrics for Ask, and the email addresses given to the Android waitlist form on this website.
- PostHog — optional, consent-based usage analytics processed in the United States as described above. Its policy permits use of aggregated or de-identified customer content for its own product/model development unless the customer opts out or agrees otherwise; we have not established a project-specific exemption. See PostHog's privacy policy and privacy control documentation.
- Android's installed speech-recognition provider — system speech recognition that may send verse-reading audio to its provider after explicit per-session consent. The provider and its retention terms depend on your device; this is distinct from on-device Vosk.
- Alpha Cephei — hosts the English Vosk model if a fallback model download is needed; no microphone audio is sent to that model host.
- GitHub — hosts this website and the development tracker that receives feedback you choose to send.
- Meta Platforms, Inc. (Facebook SDK for iOS only) — optional ad measurement, only if you allow tracking: the Meta SDK for iOS receives an "app activated" event, your advertising identifier and limited app and device information, processed in the United States and elsewhere as described above. Android does not use Meta. See Meta's privacy policy.
Apart from the iPhone Meta ad measurement described in section 7, which happens only after you allow tracking, nothing is rented or shared for anyone's marketing purposes, and we do not sell personal information for money.
9. How long anything is kept
Your original writing and saved sermon note remain until you delete them. Local recordings are excluded from device backup and kept while a draft is active or needs retry; confirming or deleting the note removes its local audio. Draft audio unused for 7 days is removed on a subsequent library cleanup, while written notes remain. An abrupt app termination may leave the current recording incomplete, without removing your saved writing.
Backend audio is deleted after a durable transcript is available. Abandoned uploads expire after 24 hours; failed processing artifacts and unacknowledged transcripts or drafts have a maximum seven-day retention window. Cleanup runs on a schedule and retries provider failures, so outages can delay actual erasure. Azure Speech jobs request a 48-hour expiry and are deleted after their results are copied. Confirming the note acknowledges the processing result so temporary backend content can be removed sooner; Android automatically confirms and acknowledges successful summaries and deletes their local audio. Provider-operated safety or abuse monitoring is governed separately by Microsoft's applicable terms; the 48-hour Speech-job expiry is not a retention promise for Azure OpenAI safety copies. Provider backup-retention periods have not been established here.
Your reading history, progress and settings are kept in your account for as long as the account exists, because their whole purpose is to follow you over the years and across devices. They are small and they do not contain Scripture text.
Deleting your account permanently deletes everything kept in it — reading history and any answers about how a verse landed, progress, alarms, settings, notes, highlights, bookmarks and sermon notes — from our servers and from the device you delete it on. It also cancels the account's processing jobs and schedules removal of temporary sermon content. Earlier versions of the app also kept reading progress and library content in your private iCloud account; we cannot read that data or delete it from our servers, and you can remove it in your Apple Account's iCloud storage settings. Feedback is kept while the issue it created remains useful.
After temporary content is erased, we retain minimal operation identifiers and a one-way input digest until account deletion to prevent an old request from triggering another paid processing job. Cleanup identifiers may remain longer during a service outage until erasure can be verified; they do not include the erased note or transcript.
Ask conversations and the selected tradition remain on your device until you delete them there; on Android, confirmed account deletion also purges that account's local Ask history on the device. With Him does not keep their text or the selected tradition on its servers, but account, Plus-entitlement and daily usage-count metadata remain under the retention periods for those records. Android's content-free request metrics are also retained for operation and safety; a fixed retention period for those metrics has not been established here. Deleting a local conversation does not mean that any provider-operated safety or abuse-monitoring copy is deleted immediately. Any such retention and deletion are governed by Microsoft's applicable terms.
Turning analytics off stops future analytics collection and discards unsent events; it does not by itself erase events already sent. You can request deletion of your PostHog profile and associated events by contacting us. Deleting your With Him account also starts an asynchronous request to erase that account's PostHog profile and associated events. Provider processing may take time; analytics erasure is not immediate.
An Android waitlist address is kept until we have sent the one email saying an Android version is available, and is then deleted. If you ask us to remove it sooner, we delete it. If no Android version is released, we delete the list.
말씀 읽기 기록 개인정보 안내
알람을 끄거나, 집중 보호막을 해제하거나, 성경에서 구절을 소리 내어 읽는 말씀 읽기를 마치면, 그 구절을 지금까지 몇 번 읽었는지 알려 드리기 위해 읽기 기록이 저장됩니다. 한 번의 읽기가 한 개의 기록이며, 어떤 구절이었는지, 어디에서 읽었는지, 소리 내어 읽었는지 따라 썼는지, 그리고 언제였는지가 담깁니다. 그 말씀이 마음에 얼마나 와닿았는지 묻는 선택 질문에 답하시면, 숫자로 표시되지 않는 그 답도 같은 기록에 함께 저장됩니다. 읽기 기록 동기화에는 성경 본문이 아니라 구절 참조가 전송됩니다. 본문은 앱 안에 들어 있으며, Android 시스템 음성 서비스의 구절 어휘 전송 가능성은 위 Android 안내를 참고해 주세요.
성경이나 통독에서 소리 내어 읽으면, 날마다 어떤 구절을 읽었는지와 각 구절을 읽은 시간대도 함께 기록됩니다. 홈의 읽은 구절 수와 기록 화면이 모든 기기에서 같은 숫자를 보여 주기 위해서입니다. 구절 위치와 날짜, 시간대만 남으며, 말한 내용이나 음성은 남지 않습니다.
로그인한 상태라면 이 기록은 인증된 Supabase 서버에 계정과 연결되어 저장되며, 기기를 바꾸거나 앱을 다시 설치해도 읽은 횟수가 그대로 이어집니다. 같은 계정에는 오늘의 말씀 진행 상황(날마다 어떤 구절이 주어졌고 어디까지 읽었는지), 묵상별 진행 위치, 날마다 소리 내어 읽은 구절, 성경 읽던 위치, 알람과 그 일정, 읽기 및 일과 설정, 앱 소개를 마쳤는지 여부, 집중 보호막의 일정과 제한 설정도 함께 저장됩니다. 서버는 요청과 함께 온 로그인 토큰의 계정 기록만 읽고 쓰며, 앱에는 본인의 단기 접근 토큰 외에 다른 사람의 기록에 닿을 수 있는 자격 증명이 없습니다.
로그인하지 않았거나 오프라인이면 아무것도 전송되지 않습니다. 읽기는 기기에 기록되고, 화면에 보이는 횟수는 기기에 있는 기록으로 셉니다. 미션은 평소대로 완료되며, 말씀 읽기를 마치는 일, 알람을 끄는 일, 보호막을 해제하는 일에는 계정이 필요하지 않습니다. 로그인 전에 쌓인 기록은 그 기기에서 처음 로그인한 계정의 기록이 되어 전송되며, 한 계정의 기록이 같은 기기의 다른 계정으로 넘어가거나 합산되는 일은 없습니다.
읽기 기록과 계정에 저장된 진행 상황, 설정은 계정이 유지되는 동안 보관됩니다. 오랜 시간 여러 기기에 걸쳐 이어지는 것이 그 목적이기 때문입니다. 계정을 삭제하면 이 모든 기록과 마음에 와닿은 정도에 대한 답변이 서버와 삭제한 기기에서 즉시 영구 삭제됩니다. 이전 버전의 앱은 진행 상황과 노트를 개인 iCloud에도 보관했습니다. 저희는 그 데이터를 읽거나 서버에서 지울 수 없으므로, Apple 계정의 iCloud 저장 공간 설정에서 직접 삭제하실 수 있습니다.
설교 노트 개인정보 안내
iPhone에서는 설교 노트 작성과 원본 저장에 녹음이 필요하지 않습니다. 녹음을 시작하기 전에 필요한 허락을 받아 주세요. iPhone에서 앱을 벗어나거나 화면을 잠그면 녹음은 일시 정지됩니다. AI 정리를 선택하고 전송에 동의할 때만 작성한 메모, 선택한 설교 정보와 녹음이 인증된 Supabase 서버와 Microsoft Azure로 전송됩니다. AI는 직접 쓴 메모를 우선하며, 결과는 검토하고 확인 후 저장해야 완성된 노트가 됩니다. Android는 백그라운드 녹음·녹음만 AI 입력으로 전송·성공한 결과 자동 확정 방식이며, 위 Android 안내가 적용됩니다.
원본 메모와 저장한 노트는 직접 삭제할 때까지 기기에 남으며, With Him Plus를 이용하면 확인 저장한 노트는 계정에도 보관되어 새 기기나 재설치 후에도 돌아옵니다. 기기의 녹음은 노트 확인 저장 또는 삭제 시 지워집니다. 7일 동안 사용하지 않은 초안의 녹음도 다음 정리 시 삭제되지만, 작성한 메모는 유지됩니다. 앱이 갑자기 종료되면 진행 중이던 녹음 파일은 복구되지 않을 수 있습니다.
서버의 녹음은 대화 내용이 안전하게 저장되면 삭제합니다. 완료되지 않은 업로드는 24시간 후, 실패한 처리 자료와 확인되지 않은 결과는 최초 처리 후 최대 7일 이내에 정리 대상으로 전환됩니다. Azure 음성 작업에는 완료 후 48시간 만료를 설정하고 결과를 가져온 뒤 삭제를 요청합니다. 서비스 장애 시 실제 삭제가 늦어질 수 있어 재시도하며, Microsoft 자체 보안 및 오용 감시는 해당 약관을 따릅니다. 계정을 삭제하면 계정에 보관된 노트와 처리 작업, 임시 서버 자료가 함께 삭제됩니다.
Ask 개인정보 안내
Ask 대화 전체와 선택한 교단 또는 신앙 전통은 기기에만 저장되며 계정에 동기화되지 않습니다. 다만 메시지를 보낼 때마다 방금 보낸 메시지를 포함한 대화 최대 8턴, 선택한 교단 또는 신앙 전통, 성경 번역본과 앱 언어(한국어 또는 영어)가 암호화되어 인증된 With Him Supabase 서비스를 거쳐 Microsoft Azure로 전송됩니다. 이 정보는 종교적 신념을 드러낼 수 있으며, 대화에 직접 입력한 개인정보도 포함될 수 있습니다.
With Him 서버는 Ask 대화 내용이나 선택한 교단 또는 신앙 전통을 보관하거나 기록하지 않습니다. 접근 권한 확인과 하루 사용 한도 적용에 필요한 계정, With Him Plus 이용 권한, 서버의 일일 사용 횟수 메타데이터는 보관되지만 대화 내용이나 선택한 신앙 전통은 포함하지 않습니다. 요청은 로그인한 계정으로 인증되어 처리되므로 종교 관련 내용이 익명 또는 계정과 분리된 정보라고 보지는 않습니다. Android는 내용 없는 요청 운영 지표도 보관하며, 선택적 PostHog 사용 분석과는 별개입니다.
Microsoft의 해당 정책에 따르면 허락 없이 프롬프트와 답변을 기반 모델 학습에 사용하지 않습니다. 다만 자동 오용 감시에서 표시된 내용은 Microsoft 약관에 따라 보관될 수 있으며, 이 서비스에 콘텐츠 로깅이 비활성화되었다고 확인된 상태는 아닙니다. 기기에서 대화를 삭제하면 기기 사본은 삭제되지만, 제공자의 보안 또는 오용 감시용 사본이 즉시 삭제된다는 뜻은 아닙니다.
선택적 사용 분석 개인정보 안내
사용 분석은 선택 사항이며 계정마다 기본적으로 꺼져 있습니다. 로그인한 상태에서 온보딩이나 동의 안내 화면, 또는 설정의 사용 정보 공유 스위치(프로필 → 설정 → 개인정보 → 사용 정보 공유, 이전 버전에서는 설정 → 개인정보 보호 → With Him 개선 돕기)를 통해 직접 동의한 뒤에만 앱 개선을 위한 사용 이벤트가 PostHog로 전송됩니다. 설정에서 언제든 사용 분석을 끄고 동의를 철회할 수 있으며, 동의하지 않거나 철회해도 앱 기능 이용에는 제한이 없습니다. 로그인하지 않았거나 동의하기 전에는 분석 이벤트를 수집하지 않으며, 동의 전에 한 동작을 나중에 소급하여 보내지도 않습니다.
분석 대상은 앱 사용, 동의 후의 온보딩 완료, 읽기 완료, 구독 안내 화면에서의 동작, 구매 또는 구매 복원 결과, 그리고 AI 설교 요약 요청과 그 요청이 어떻게 끝났는지(예: 완료, 업로드 실패로 중단)입니다. 이벤트 발생 시각, 앱 버전·운영체제 버전·기기 모델·앱 언어 등 제한된 앱 및 기기 정보와 SDK 세션 식별자가 포함됩니다. 변경되지 않는 Supabase 계정 ID(UUID)를 가명 식별자로 사용합니다. SDK 식별 정보를 계정에 연결할 때에는 임의로 생성한 앱 설치 식별자도 PostHog로 전송되며, 이 역시 로그인한 상태에서 동의한 뒤에만 이루어집니다. 이 식별자들로 이벤트가 계정에 연결되므로 익명 정보는 아닙니다. 읽기 완료 이벤트에는 읽은 성경의 책·장·절이 포함되지 않습니다. 설교 요약 이벤트에는 요청 종류와 결과만 담기며, 노트, 녹음, 녹음 길이, 오류 내용은 포함되지 않습니다. 다른 네트워크 서비스와 마찬가지로 PostHog는 요청을 처리할 때 IP 주소를 받지만, With Him의 PostHog 프로젝트는 이를 폐기하도록 설정되어 있어 이벤트와 함께 저장되지 않으며, IP 주소를 이용한 위치 조회(GeoIP)도 사용하지 않습니다.
이름, 이메일 주소, 설문 답변, 교단이나 신앙 전통, 성경 구절 참조나 본문, 녹음, 녹취록, 설교 내용, 노트 및 대화 내용은 PostHog로 보내지 않습니다. 세션 다시 보기와 사용자 동작 자동 수집 기능은 비활성화되어 있습니다. PostHog를 광고 목적으로 사용하지 않습니다. 저희는 개인정보를 금전적 대가를 받고 판매하지 않으며 데이터 중개업체에도 제공하지 않습니다.
사용 분석을 끄면 이후 수집이 중단되고 아직 전송되지 않은 이벤트는 폐기되지만, 이미 전송된 이벤트가 자동으로 삭제되지는 않습니다. 연락처로 요청하시면 PostHog의 계정 프로필과 연결된 이벤트의 삭제를 요청할 수 있습니다. With Him 계정을 삭제할 때에도 해당 계정의 PostHog 프로필과 연결된 이벤트를 삭제하는 비동기 요청이 시작됩니다. 제공자의 처리에는 시간이 걸릴 수 있으며, 분석 데이터가 즉시 삭제되는 것은 아닙니다.
PostHog는 동의한 사용자의 선택적 사용 분석을 담당하며, 이 데이터는 미국에서 처리됩니다. 자세한 내용은 PostHog 개인정보 처리방침과 개인정보 보호 제어 문서를 참고해 주세요.
Android는 PostHog 요청에 IP 기반 위치 조회 비활성화를 명시하며, 서버의 IP 보관 여부는 제공자 설정에 따릅니다. 위 iPhone 프로젝트 설명을 Android 서버 설정 검증으로 보지는 않습니다. PostHog 정책상 별도 거부나 약정이 없다면 집계·비식별화한 고객 콘텐츠가 자체 제품·모델 개발에 쓰일 수 있으며, With Him에 대한 예외는 확인되지 않았습니다.
광고 성과 측정 및 앱 추적 개인정보 안내
iPhone 앱을 새로 설치한 경우에만, 처음 실행한 직후 iOS가 Apple의 앱 추적 투명성(App Tracking Transparency) 안내를 한 번 표시합니다. 앱을 업데이트만 한 기존 사용자에게는 묻지 않습니다. 앱은 이 권한을 요청하며, 허용하신 뒤에만 기기의 광고 식별자(IDFA)를 읽습니다. Android에는 이 Meta SDK나 광고 ID 수집이 없습니다.
'허용'을 선택하면 Meta(Facebook) iOS SDK가 시작되며, 앱을 열 때마다 Meta로 "앱 활성화" 이벤트를 전송합니다. Meta는 기기의 광고 식별자(IDFA), Meta가 자체적으로 부여하는 익명의 앱 인스턴스 ID, 그리고 SDK가 덧붙이는 제한된 앱 및 기기 정보(앱 버전, 운영체제 버전, 기기 모델, 언어, 시간대, 화면 크기 등)를 받습니다. 목적은 어떤 Meta 광고를 통해 앱이 설치되고 실행되었는지 측정하는 것(광고 성과 귀속 및 측정)입니다. Meta는 이 데이터를 Meta 개인정보 처리방침에 설명된 대로 사용할 수도 있습니다. Meta는 데이터를 미국 및 그 밖의 지역에서 처리합니다.
'앱이 추적하지 않도록 요청'을 선택하시거나 나중에 iOS 설정 → 개인정보 보호 및 보안 → 추적 → With Him에서 추적을 끄시면 Meta SDK는 시작되지 않으며 Meta로 아무것도 전송되지 않습니다. 허용하지 않거나 철회해도 앱 기능 이용에는 어떤 제한도 없습니다. 이미 Meta가 보유한 데이터는 Meta가 제공하는 자체 설정으로 관리해 주세요. 저희는 그 데이터를 Meta에서 삭제할 수 없습니다.
자동 이벤트 기록, 자동 인앱 구매 기록, SDK의 메타데이터 및 화면 제목 수집은 모두 꺼져 있습니다. 앱이 기록하는 이벤트는 "앱 활성화" 하나뿐입니다.
성경 구절 참조나 본문, 읽기 및 읽기 기록, 노트, 하이라이트, 녹음, 녹취록, 설교 내용, Ask 대화, 설문 답변, 교단, 이름, 이메일 주소, Sign in with Apple 신원 정보, Supabase 계정 ID, 구매 또는 구독 정보는 Meta로 보내지 않습니다. 저희는 Meta 데이터를 PostHog 사용 분석과 결합하지 않습니다.
Meta Platforms, Inc.(Facebook SDK)는 추적을 허용한 사용자의 선택적 광고 성과 측정을 담당하며, 이 데이터는 미국 및 그 밖의 지역에서 처리됩니다. 자세한 내용은 Meta 개인정보 처리방침을 참고해 주세요.
10. Your rights
Depending on where you live, you may have rights to access, correct, export or erase personal data we hold, to object to or restrict processing, and to complain to a supervisory authority. On Android and iPhone, Profile → Settings → Account → Delete account removes the account and everything kept in it, and starts cleanup of its temporary processing content. Android also provides Account access on the required subscription screen without paying. You can edit or delete sermon notes in the Notes library. For a copy of data or help with a request, contact us.
Delete your With Him account without reinstalling the app: email kipackjeong@devitall.co from your account's Google or Apple sign-in email address with the subject Delete my With Him account. We handle requests within 30 days. See the deletion and retention details. Deleting an account does not cancel a Google Play or App Store subscription.
For California residents: we do not sell personal information for money. Ad-measurement data goes to Meta only after you allow tracking in the iOS prompt, and you can stop it at any time in iOS Settings → Privacy & Security → Tracking → With Him; see section 7.
11. Children
The app is not directed at children under 13 and we do not knowingly collect personal information from them. If you believe a child has created an account, write to us and it will be deleted.
12. Changes
If this policy changes, the date at the top changes with it. A change that widens what is collected will be announced in the app before it takes effect — not left in a document nobody re-reads.
13. Contact
Write to kipackjeong@devitall.co, or use Settings → Send feedback inside the app.