Privacy Policy

Effective date: October 30, 2026

Remember (“Remember,” “the app,” “we,” “us”) is a Bible journaling app operated by an independent developer. This policy explains what information the app collects, how it collects it, why, who processes it on our behalf, and the choices you have. If anything here is unclear, email us at elizabeth.rememberapp@gmail.com and we will answer plainly.

The short version. Your journal is private: no other user can ever see your entries. We collect only what the app needs to work: your account details, the content you create, and usage statistics that never include what you write. We do not show ads, do not track you across other apps or websites, and do not sell your data. If you turn on AI transcription, your voice recordings and their transcripts are processed by the AI providers named below, solely to provide that feature. Typed notes never go to any AI service, and searching your journal happens on your device.

1. Information we collect

Account information

Name and email address. You can create an account with an email address and password, or by signing in with Google. On iOS you can also use Sign in with Apple, which lets you hide your real email address; we support that. We use your email address to sign you in and to send account emails such as password resets, and your name (if you provide one) so the app can greet you.
A random account identifier created for you by our backend.

Content you create

Journal entries. The text you write, its formatting, and the Scripture references detected in it, collected when you write or record and synced to our backend so your journal follows you across devices.
Voice recordings. Audio you record in the app when you choose to use voice journaling. Audio is captured by the microphone only while you are actively recording in the foreground; the app never records in the background. A recording that has not yet finished transcribing is kept on your device, not on our servers. On Android it is kept for up to 30 days and then deleted. On iOS it is kept until you resolve it: retry the transcription, keep the note as written, or delete the note.

Purchase information

Subscription status and purchase history for the app’s premium recording subscription, processed by RevenueCat (our subscription infrastructure) together with Apple’s App Store or Google Play, depending on your device. RevenueCat identifies your subscription by your account identifier. We never see or store your payment card details; payment is handled entirely by Apple or Google.
Recording usage time (how many minutes of transcription you have used), which we track to enforce the free allowance and fair-use limits.

Usage and diagnostic information

Product analytics via PostHog: events such as “a note was created” or “the paywall was viewed.” These events never include the content of your journal, your searches, your name, or your email; only counts, on/off values, and fixed category names. That includes your answers to the questions asked during onboarding, which are chosen from fixed options and are never free text. These events include subscription activity, such as starting, completing, or restoring a purchase and whether you have a subscription, which we use to understand how the subscription is used. Events are recorded under a random analytics identifier rather than your name or email.
Crash and performance diagnostics via Sentry. If the app crashes, stops responding, is terminated by the operating system, or encounters a bounded operational failure, Sentry receives technical diagnostics needed to identify and fix the problem: crash or hang details, the technical error message and stack trace generated at the moment of the problem, app and operating system versions, device model, bounded event categories and counts, and a random installation identifier that changes every 30 days. These diagnostics are not linked to your account and are not used for tracking. We never attach your journal or Scripture text, transcripts, audio, screenshots, or a view hierarchy, and we do not record your taps or navigation as breadcrumbs.
Time zone identifier, captured when you create a note and stored with it, including on our servers when the note syncs, so that dates and reminders behave correctly where you live. Reminders themselves are local notifications, computed and scheduled entirely on your device from your own journal; no reminder content passes through our servers.
Device integrity signals. Apple’s App Attest on iOS and Google’s Play Integrity on Android, used only to check that requests to our transcription and Scripture services come from a genuine copy of the app. These checks describe the app and the device, not you personally. On iOS they involve a device attestation key that our server keeps while your account exists (Section 6 explains what happens to it when you delete your account).
A one-time free-minutes marker. The free transcription minutes we give you are meant to be claimed once, not repeatedly. On iOS this uses Apple’s DeviceCheck: Apple stores two yes/no bits for us and tells us nothing else, and we use this only to prevent abuse of the free allowance, never for advertising or tracking. On Android, the app currently includes the device’s Android ID (a device-scoped identifier called the SSAID) in the one-time request that activates your free minutes; today our server does not store or use that identifier, and the free allowance on Android is tied to your account instead. If we begin using it to prevent repeat claims from the same device, we will update this policy first.
Operational and security records. Our backend keeps small technical records needed to run the service safely: a log of free-minutes activations (your account identifier, platform, outcome, and timestamp), rate-limit counters, and short-lived challenge codes used by the device integrity checks. Our server logs may also record technical details of a request, and if our ESV Scripture service fails over to the King James Version, the search phrase involved can appear in those logs. These records are used only to operate, secure, and debug the service.
Support emails. If you contact us for help, the app pre-fills your device model, operating system version, region, language, app version and build number, subscription plan, and a short account reference (the first eight characters of your account identifier, so we can find your account if you ask us to) into the email before you send it. You can see and edit this information before sending, and nothing is sent unless you choose to send the email yourself.

2. How your content is processed (including AI providers)

Voice journaling uses third-party AI services. When you allow AI transcription, your voice recording and its transcript are shared with ElevenLabs, Anthropic, and Google, and used only to turn that recording into a written journal entry: transcribing your voice, formatting the transcript, and finding the Scripture references you mention. Notes you type are never sent to any AI service.

A recording stays on your device until you allow AI transcription. After each recording, the app shows a prompt asking whether to transcribe it with AI; nothing is sent to any AI provider until you tap I Agree. That prompt appears again after every recording until you allow it. You can turn AI Transcription off at any time with the Enable AI Transcription switch on the Me tab. On iOS, a recording you choose not to send is transcribed on your device instead by Apple’s on-device speech recognition, and nothing is transmitted. Android has no on-device transcription, so there the recording simply stays on your device until you choose to transcribe it, keep the note as written, or delete it. Typed notes never go to any AI service, on either platform.

All of this processing happens through our own secure backend. The app never sends your content directly to these providers, and provider credentials are never present on your device. Your audio is never written to storage on our servers: it is held in memory only for the duration of the request. None of our AI providers uses your recordings or transcripts to train their models, and each is bound by API terms that protect your data at least as strongly as this policy. Providers may retain what we send them for a limited period under their standard API terms, solely to monitor for abuse; we do not ask for or extend that retention. The transcript and the formatted entry are kept in our own transcription records on the server, which lets an interrupted request recover and prevents a retry from being billed twice; those records are deleted with your account. You can withdraw consent at any time with the Enable AI Transcription switch on the Me tab.

Verse lookup and Scripture search send only the reference or search phrase you type (never your journal text) to our own backend. When ESV text is needed, that phrase is forwarded to Crossway’s ESV API; King James Version passages are served entirely from our own backend and are not sent to any third party. Crossway is a Scripture service, not an AI service.

Searching your journal itself happens entirely on your device. Your journal searches are never sent to us or to anyone else.

When a note has a web link on a line of its own, your device loads a preview of that page, such as its title and image, directly from the website (and any image host it uses), so that website can see your device’s IP address. Remember’s servers are not involved, and the preview is kept only on your device.

3. Service providers we rely on

Supabase: authentication, database, and cloud sync. Your account and journal data are stored here so they can sync across your devices.
ElevenLabs: speech to text for voice journaling. Receives your audio recording only to return the transcript. We have opted out of ElevenLabs using the recordings we send to train its models.
Anthropic: receives the transcript to format it into a journal entry and find the Scripture references you mention. We use Anthropic’s API, whose terms state that API data is not used to train its models.
Google (Gemini API): used when another AI provider cannot process a request; it may then receive the audio recording or the transcript. We use Google’s paid API tier, whose data is not used to train its models. Gemini never receives the notes you type.
RevenueCat: subscription management, identified by your account identifier as described in Section 1.
PostHog: product analytics, as described in Section 1.
Sentry: crash, app-hang, watchdog-termination, and bounded operational diagnostics. Sentry receives no journal content, audio, or account identity from the app.
Crossway (ESV API): Scripture text and Scripture search.
Apple and Google: sign-in, payment processing, and device-integrity checks (App Attest and DeviceCheck on iOS, Play Integrity on Android).

Each of these providers processes your data only on our behalf and only to provide its service to us. We share data with a provider only when a feature needs it, and only the minimum that feature requires. Before we rely on a provider, we review its terms and privacy commitments and require that it protect your data with safeguards at least as protective as the ones described in this policy, including encryption in transit, no selling of your data, and no use of it for advertising. If a provider cannot meet that bar, we do not send it your data.

4. What we do NOT do

We do not sell your personal information. Not to anyone, not ever.
We do not show advertising and do not share your data with advertisers or data brokers.
We do not track you across other companies’ apps or websites, and the app contains no advertising identifiers.
We do not use your journal content to train AI models, and we do not permit our providers to sell it or use it for advertising.
No other user of Remember can see your journal or anything else you create in the app.

5. Where your data lives and how it is protected

The app works offline-first: your entries are stored on your device and synced to our cloud backend (Supabase) so they survive device loss and sync across devices. Our Supabase database is hosted in Seoul, South Korea. The service providers named in Section 3 process data on their own infrastructure, which may be located in other countries, including the United States; wherever your data is processed, it travels over encrypted connections (HTTPS/TLS) and is used only for the purposes described in this policy. Sensitive server credentials (such as AI-provider keys) exist only on the server, never in the app.

6. Retention and deletion

Your journal data is retained for as long as you keep your account, so it remains available to you.
You can delete individual entries at any time in the app.
Voice audio is never stored on our servers at all; it is processed in memory and passed to the transcription provider. The transcript and formatted entry from each transcription request are kept in our server-side transcription records until your account is deleted, as described in Section 2.
You can delete your entire account from inside the app: open the Me tab and tap Delete Account. This permanently deletes from our servers your account (name, email, and account identifier), your journal entries with their Scripture references and tags, your transcription records (including any stored transcripts), your entitlement and free-minutes records, and your sign-in tokens. If you signed in with Apple, we also ask Apple to revoke the app’s sign-in permission. See Delete Your Account for step-by-step instructions.
A few records survive account deletion, and here is exactly what: anonymous usage statistics and crash diagnostics, which are recorded under random identifiers rather than your account; subscription and purchase records, meaning RevenueCat’s record of any subscription you had and Apple’s or Google’s own purchase records, kept as long as accounting and tax rules require; and, on iOS, a device security record, the device attestation key used to confirm requests come from a genuine copy of the app, kept with its link to your account removed so old security credentials cannot be replayed against us.

7. Children

Remember is not directed at children under 13 (or the equivalent minimum age in your jurisdiction), and we do not knowingly collect personal information from them. If you believe a child has created an account, contact us and we will delete it.

8. Your rights

Depending on where you live, you may have rights to access, correct, export, or delete your personal information, or to object to certain processing. The app itself gives you the two that matter most: reading everything you have stored, and deleting your account entirely. For anything else, email elizabeth.rememberapp@gmail.com and we will honor your request as required by applicable law.

9. Changes to this policy

If we change this policy in a meaningful way, we will update the effective date above and, for significant changes, tell you in the app. Continued use of the app after a change means you accept the updated policy.

10. Contact

Questions, concerns, or requests: elizabeth.rememberapp@gmail.com