Eterniseed Privacy Policy
Version 2026-10-03.1 · effective October 3, 2026
Effective Date: October 3, 2026 (revision 1)
Controller: Eterniseed™, Eterniseed LLC (Georgia, USA).
Contact: [email protected]
Eterniseed is a Bible reading, study, and learning app for families and churches. We take the trust you place in us seriously. This policy explains what we collect, why, how long we keep it, and the choices you have (written in plain language, with the legal citations inline where they matter).
If you are a parent managing a child profile inside Eterniseed, there is a dedicated section for you below: Children's Privacy (COPPA).
1. Information We Collect
When you create an account. Your email address, display name, date of birth (used for age-gating, not stored as a birthday reminder), a hashed password (we never see or store the plaintext), and your accepted Terms of Service version. Optionally, if you choose to provide it, your gender.
When you sign in with Google or Apple. If you choose social sign-in, we receive your email address, your name as shared by the provider, and a provider account identifier, and we use them only to create and sign you into your account. With Apple you may hide your email; the private relay address Apple generates is then the only email we see.
When you use the app. Which chapters you have read, which lessons you have completed, which personas you have chatted with, which Bible translation you prefer, which narrator voice you have chosen, your notes and saved passages, your prayers, your community posts, and your reading-streak and progress metrics. We treat this as devotional data and protect it accordingly.
When you add a child profile. The child's display name, date of birth, optional gender, preferred AI Guide persona, and an optional 4-6 digit PIN that you control. Child profiles live inside your account; children do not create their own logins.
Photos you choose to upload. If you set a profile picture (avatar), attach a screenshot to a feedback report, or share an image with your community, we store the image you upload so it can be shown as you intended; feedback screenshots are reviewed by our support team, and community images are safety-screened before they are stored (see Section 3). We only ever receive a photo you deliberately select and upload; we do not access your photo library, camera, or microphone in the background.
When you pray or journal. Prayer requests and journal entries you save are stored on our servers so they are available on all your devices, until you delete them or delete your account.
When you talk to the AI Guide. The text of your conversations, which we process to generate replies and to enforce scriptural safety guardrails. We keep these as part of your account history (see Retention below).
When you subscribe. Your subscription tier, billing status, renewal dates, and the customer and transaction identifiers assigned by the payment processor. On the web (including Android, which purchases through our website), payments are processed by Stripe, and we never see, store, or transmit your credit card number; it goes directly from your browser to Stripe. On iOS, subscriptions are purchased through Apple In-App Purchase: Apple processes the payment under its own terms and privacy policy, and we receive a signed transaction record tied to your account, never your card details.
When you call our toll-free line. If you call +1 (888) 887-9793 and leave a message, we collect your phone number, the approximate location (city/region) reported by the phone network, your audio recording, and a machine-generated transcript, so we can hear your message and respond.
Analytics and diagnostics (mobile app). In our Android and iOS apps we use Google Firebase to understand how the app is used and to keep it stable. Firebase Analytics records app-usage events such as app opens, which screens you view, and which features you use. Firebase Crashlytics records crash reports and diagnostic information when the app encounters an error, so we can fix it. (For child profiles, Firebase Analytics is switched off entirely; see Section 4.) Firebase Analytics does not receive your device's mobile advertising identifier. We switch off advertising-ID collection and ad-personalization signals on both platforms, and our Android app ships with the advertising-ID permissions removed entirely, so the identifier is never available to us or to Google through this app. We use this only for our own first-party, aggregate analytics: to measure usage and improve the app. We do not use it to serve you ads, to build an advertising profile, or to track you across other companies' apps and websites.
Push notifications (mobile app). If you allow notifications, your device registers a push token (a Firebase Cloud Messaging identifier and a Firebase installation ID) that lets us deliver reminders and updates you have asked for. You can turn notifications off at any time in your device or app settings.
Technical information. IP address, user-agent string, rough device type, and timestamps of logins and key actions. Used to fight abuse, investigate incidents, and keep the service reliable.
What we do NOT do. We do not serve advertisements in the app. We do not build advertising profiles about you, and we do not share or sell your information for third-party advertising or cross-app tracking. We do not buy or augment your profile from data brokers. We do not access your contacts. We do not access your camera, microphone, or photo library except for a photo you deliberately choose to upload (see "Photos you choose to upload" above). If you turn on biometric unlock for your notes and journal, your device checks your face or fingerprint locally and simply tells the app yes or no; we never receive or store your biometric data. We use precise location only when you ask us to: if you tap "near me" in the church directory or set a church's location, your browser or device asks your permission first, and we use the coordinates only for that search or listing. We never track your location in the background. Our mobile analytics also records the general region a session came from (derived from your IP address by Google Firebase, at roughly city or state level), so we can see where the app is being used. This is not linked to your account and is not precise location.
2. How We Use Your Information
We use the information above only to:
- Provide the app and its features: reading, lessons, narration, guided conversations, scheduling.
- Personalize your experience: remember your translation, voice, reading progress, and which Guide you prefer.
- Authenticate you and keep your account secure.
- Bill you correctly if you are on a paid tier.
- Enforce our Terms of Service and community standards, including keeping the AI on-topic and age-appropriate.
- Communicate with you about account activity, essential service changes, and (if you have opted in) occasional devotional or product updates, including push notifications you have allowed.
- Measure aggregate usage and diagnose crashes so we can keep the app reliable and improve it (first-party analytics and diagnostics only).
- Comply with legal obligations (audit trails, tax, subpoena responses).
We do not use your information to train AI models, sell to third parties, or target advertising. That is a hard line.
3. Third-Party Service Providers
We use carefully selected providers, each bound by a Data Processing Addendum or equivalent contract. They process data on our behalf only:
- AI processing providers (currently Anthropic, OpenAI, Google and xAI). We use them for these purposes, and no others: (a) to generate replies in AI Guide conversations (your conversation text is sent to them); (b) to safety-screen community image uploads before they are stored; (c) to transcribe voicemail left on our toll-free line; (d) to translate posts and messages shared in community spaces so members reading in another language can follow along; and (e) to help prepare our content library. Our AI providers are bound by contract not to use Eterniseed traffic to train their models. The current provider list is available on request at [email protected].
- Google (Firebase): provides analytics (Firebase Analytics), crash and diagnostics reporting (Firebase Crashlytics), and push notifications (Firebase Cloud Messaging) for our mobile apps. Used for our own first-party analytics, stability, and notification delivery, not for advertising.
- Google Workspace (Gmail SMTP): delivers transactional email (verification links, password resets, receipts, notifications). We send the recipient email and message body.
- ElevenLabs: generates narrated audio for chapters and stories. We send scripture text and voice selection.
- Stripe: processes web subscription payments. Payment details are entered directly into Stripe's PCI-certified systems; we receive only a customer token and billing status.
- Apple: processes iOS in-app purchases under Apple's own terms and privacy policy; we receive signed transaction records, never your payment details.
- Twilio: connects our toll-free line (+1 888 887-9793): voice menus, caller voicemail, and operational text alerts sent to our own administrators. Twilio receives phone numbers and message content as needed to connect them.
- Backblaze B2 + Cloudflare: store and deliver app assets, coloring pages, uploaded avatars, community and church media, documents churches send us when they register, intro videos, and cached narration audio, and provide aggregate, cookie-less web traffic measurement. Screenshots you attach to a feedback report are stored on our own application servers, not with these providers.
- Vultr: hosts our application servers and managed databases in Atlanta, Georgia.
These providers act as our processors. We do not sell your information to them or to anyone, and none of them receive your data for their own advertising. A full list is available on request at [email protected].
4. Children's Privacy (COPPA)
Eterniseed is safe for children to use only through a parent-managed profile inside a parent's adult account. Children under 13 do not create or own their own Eterniseed account. Eterniseed LLC is the only operator that collects or maintains children's personal information through the service.
Before a child profile is added or used, we obtain verifiable parental consent under the Children's Online Privacy Protection Act (15 U.S.C. §§ 6501-6506) and its regulations (16 C.F.R. Part 312). Consent is given in one of two ways, depending on your plan. On a paid or trialing plan we rely on the payment method on the parent's subscription (a card or other online payment system that tells its holder about each transaction), and the consent is given inside your authenticated adult account when you create the profile. On our free plan we email a one-time confirmation link to the verified address on your account, and the child profile is not created until that link is opened and confirmed. Either way we record the method, the date and time, and the IP address of the confirmation. Separately, and per child, we ask again before AI features are enabled for that child, because AI features send the child's conversation text to the providers named below. You may consent to the profile without consenting to AI features, and you may withdraw either at any time in Settings → Family.
For a child profile, we collect only what is needed to provide age-appropriate content and the features the parent enables: display name, date of birth (for reading-level and content-comfort gating), optional gender, optional persona preferences, the parent-set PIN (stored only as a secure hash), the child's activity inside the profile (reading progress, completed lessons, earned badges, saved colorings), and (if the parent has consented to AI features) the text of the child's conversations with the AI Guide, which is sent to our AI processing providers (currently Anthropic, OpenAI, Google and xAI; see Section 3) to generate replies and enforce safety guardrails. Those providers act as our service providers under contracts that limit them to processing on our behalf and prohibit them from using a child's conversation text to train their models.
We share a child's personal information only with the service providers in Section 3 that operate the features you enable: the AI providers (only if you enable AI features), Google Firebase for crash reporting in our mobile apps, and the providers that host and store our systems, each under a written contract that limits them to processing on our behalf and requires them to keep the information confidential and secure. We do not sell, rent, or otherwise disclose a child's personal information to anyone else, except where the law requires it.
In our Android and iOS apps we also receive crash reports through Google Firebase Crashlytics when the app fails on a child's profile, including a Firebase installation identifier assigned to that app install. We keep Crashlytics on for children deliberately, so that a crash on a child's screen can be found and fixed. Firebase Analytics is switched off entirely on children's screens: no screen views, no usage events and no user identifier are sent to Google from a child profile.
The Firebase installation identifier that travels with a crash report is a persistent identifier in COPPA's sense. We collect it for one internal operation only: finding and fixing crashes on children's screens. Google processes it for us as our service provider under Firebase's data-processing terms, and neither we nor Google use it to contact a specific child, to build a profile of a child, or for advertising of any kind. It is scoped to that installation of the app, and it cannot identify a child by name. On the web, our own first-party measurement script runs on children's pages and records page views, which Bible chapter and translation was opened, and AI Guide usage; each record carries a random identifier that exists only for the current browser tab, is never stored with the child's name or account, and is not stored with an IP address. We do not collect a child's email, phone number, precise location, physical address, photographs, or contacts, and we do not use a child's information for advertising of any kind.
Parents have the right, at any time, to:
- Review the information associated with their child's profile (Settings → Family Profiles → the child).
- Correct or update that information.
- Delete the child's profile. The profile is hidden immediately and permanently erased 30 days later (so you can undo an accidental deletion), and you can ask us to erase it sooner at [email protected]. Two things deliberately survive: the record that you gave consent for that child, which we keep as proof that we obtained it, and anonymous counts of activity with every link back to your child removed.
- Refuse further collection or use of their child's information.
- Consent to the collection and use of their child's information without consenting to its disclosure to third parties. The one feature that requires a disclosure to a service provider is AI conversations, which cannot work without sending the child's messages to our AI providers, which is why we ask for that consent separately, and why the profile works without it.
For families in the EU/EEA/UK, consent for a child's profile is given and exercised by the holder of parental responsibility, consistent with Article 8 of the GDPR. The age at which a child may consent to an online service for themselves varies by country under Article 8 (from 13 to 16); because an Eterniseed account requires its holder to be an adult, a child always uses Eterniseed through a profile a parent creates and controls, whatever the local age.
The AI Guide persona used in Kids mode is bound to Bible-centered educational content and cannot discuss topics outside that scope. It does not ask children for personal information and is rate-limited and monitored for safety. Before a child's first question it says, in simple words, that it is a computer helper and not a real person.
Children's data retention policy. We keep personal information collected from a child only as long as it is reasonably necessary for the purpose it was collected for, and we delete it on this schedule:
- Display name, date of birth, gender, persona and reading settings, and the PIN (as a hash): kept while the child profile is active, to run the profile and gate content by age; when the parent deletes the profile (or the parent's account), the profile is hidden immediately and this information is permanently erased 30 days later.
- Reading progress, completed lessons, badges, and saved colorings: kept while the profile is active so the child can see their progress and the parent can review it; erased on the same schedule as the profile.
- AI Guide conversations (only where the parent has consented to AI features): kept while the profile is active so the child can return to them and the parent can review them; erased on the same schedule as the profile.
- Crash reports (Firebase Crashlytics, mobile apps only): kept for the time Google Firebase retains crash data, which we do not extend; never linked to the child's name or account.
- The record of parental consent: kept as proof that we obtained it, including after the profile is deleted.
- Anonymous counts of activity: kept after deletion with every link to the child removed.
A child profile is never suspended or deleted because a parent's paid subscription lapses. The child keeps their profile and everything in it and uses Eterniseed at the free level; the kid features that belong to paid plans stop opening for the child until the plan is restored. A child's information is deleted only when the parent deletes the profile, or the parent's account, on the schedule above. Residual copies of erased information can persist in our encrypted backups for up to 90 additional days before they age out. We delete children's information with reasonable measures against unauthorized access during deletion, and a parent may ask us to erase a child's information sooner at [email protected].
Information-security program. We maintain a written information-security program for children's personal information, with a designated coordinator, safeguards suited to the sensitivity of the data, testing and monitoring, an annual risk assessment, and written assurances from each service provider that receives children's data that it will keep the information confidential and secure.
Operator: ETERNISEED LLC, 8735 Dunwoody Place, STE N, Atlanta, GA 30350, USA · +1 (888) 887-9793 · [email protected]
Questions about our COPPA practices: [email protected], subject line "COPPA request."
5. How We Share Information
We share personal information only in these limited circumstances:
- Service providers (described in Section 3), under written contract, for the sole purpose of operating Eterniseed.
- Legal compliance: if we receive a lawful subpoena, court order, or other legally binding request. We narrow our response to what the law requires and, where legally permitted, notify you.
- Safety: if we reasonably believe disclosure is necessary to protect someone from imminent harm.
- Business transfer: if Eterniseed is ever acquired or merged, your information may transfer to the successor under the same privacy commitments; we will notify you before any change of controller.
We do not sell personal information, and we do not share it for cross-context behavioral advertising or targeted advertising, as those terms are defined under the California Consumer Privacy Act (Cal. Civ. Code § 1798.140) and the other U.S. state privacy laws that apply to us.
No mobile information will be shared with third parties or affiliates for marketing or promotional purposes. Text messaging originator opt-in data and consent will not be shared with any third parties. All the above categories exclude text messaging originator opt-in data and consent; this information will not be shared with any third parties.
6. Data Retention
- Active account data: kept while your account is active.
- Sign-in attempt logs: the email address used and the originating IP address are kept to detect account-takeover attempts. These are kept separately from your account and are not removed by account deletion.
- If a paid subscription lapses: content that belongs to paid tiers (your notes, your saved AI conversations, and community circles that have gone dormant) is deleted thirty (30) days after the lapse. Child profiles are not affected (see Section 4). We email you before that window closes, and resubscribing within it preserves everything. The rest of your account data is kept until you delete your account (Settings → Delete My Account and Data).
- Billing records: retained for seven (7) years after the last transaction to comply with Georgia and U.S. tax and accounting requirements, then deleted. These are tamper-evident financial records: the transaction detail, including the email address the transaction was billed to, is preserved unchanged for that period even if you delete your account, because we cannot alter a financial record after the fact.
- Audit and security logs: kept as append-only, tamper-evident records so that administrative actions and security events can always be accounted for. When your account is deleted we remove the link between these records and your account. Where an action was recorded against your email address at the time it happened, that address stays in the record, because these logs cannot be altered after the fact. We keep a minimal record of the deletion itself as proof it was carried out.
- AI conversations: kept as part of your account history so you can return to them; removed when your account is deleted, or thirty (30) days after a paid-tier lapse as described above.
- Prayer journal entries: retained until you delete them individually or delete your account.
- Voicemail on our toll-free line: recordings and transcripts are kept while we work your message and for our records, and you may request deletion at [email protected].
- Analytics and crash-diagnostics data: retained per Google Firebase's default retention windows for aggregate analytics and crash reports.
Deletion and backups. When you delete your account, we delete or unlink the above within thirty (30) days, except for records we are legally required to retain and the sign-in attempt logs described below, which are kept separately from your account. Residual copies can persist in our backups for up to ninety (90) additional days before they age out. Our off-site backups are held in private, access-restricted storage and are automatically destroyed on that schedule; our database provider also keeps its own short-term backups of the same database for disaster recovery. Backups are used only for disaster recovery, and if we ever restore from one, we will re-apply account deletions made after that backup was taken.
7. Your Rights
You have meaningful control over your data. Depending on where you live, these rights are guaranteed by GDPR (EU/EEA/UK), CCPA/CPRA (California), VCDPA (Virginia), CPA (Colorado), CTDPA (Connecticut), UCPA (Utah), and similar state laws:
- Access: request a copy of the personal information we hold about you.
- Portability: receive your data in a structured, commonly used, machine-readable format (Settings → Privacy → Export My Data) and, where it is technically feasible, have it sent to another provider.
- Correction: fix inaccurate information.
- Deletion: delete your account and its associated data (Settings → Privacy → Delete My Account).
- Opt-out: turn off reminder emails and push notifications at any time in Settings → Notifications. Essential account and security messages (password resets, billing failures, and notices about your account) are always sent. To stop all non-essential email, write to [email protected].
- Restriction: ask us to pause our processing while a concern about the accuracy or lawfulness of your data is resolved.
- Objection: object to processing we base on our legitimate interests.
- Withdraw consent: where we rely on your consent, withdraw it at any time; this does not affect processing already carried out before the withdrawal.
- Non-discrimination: we will never charge you more or give you a worse experience for exercising a privacy right.
To exercise any right not available in-app, email [email protected]. We respond within thirty (30) days.
EU/EEA/UK: legal bases and where to complain. You may lodge a complaint with your local data-protection supervisory authority at any time. Where the GDPR applies, each purpose has its own Article 6 basis: creating and running your account, providing the features you request, and billing: performance of a contract (Article 6(1)(b)); adding and operating a child profile: consent of the holder of parental responsibility (Articles 6(1)(a) and 8); AI Guide conversations, push notifications, and any optional marketing: consent (Article 6(1)(a)), each of which you may withdraw at any time; keeping the service secure, preventing abuse, and diagnosing crashes: our legitimate interests in a secure and stable service (Article 6(1)(f)), balanced against your rights; and tax, accounting, and audit retention: legal obligation (Article 6(1)(c)). We do not make automated decisions about you that have legal or similarly significant effects. The AI Guide generates replies to your questions with large language models, but a reply is information for your reflection, not a decision about you; the content shown to a child profile is filtered by the age the parent set, which is a safety feature, not profiling. Your reading history, prayers, and devotional AI conversations can reveal religious or philosophical beliefs, which are a special category of data under Article 9 of the GDPR. We process this devotional data only with your explicit consent (Article 9(2)(a)), given when you create your account and use these features, and you may withdraw that consent by disabling the relevant feature or deleting your account.
8. Security
- All data in transit is encrypted with TLS 1.2 or higher.
- Passwords are hashed with bcrypt (cost 12); we cannot see your plaintext password, even with root database access.
- Data at rest in our managed Postgres is encrypted by the hosting provider.
- Access to production systems is limited to a small number of operators, reachable only over a private network or from a small list of approved addresses, and authenticated with SSH keys rather than shared passwords. Administrative web surfaces additionally require single sign-on through our identity provider.
- We log administrative actions and review logs periodically.
No system is perfectly secure. If we learn of a breach affecting your personal information, we will notify you as the law requires and without unreasonable delay (our aim is within seventy-two (72) hours of confirming it), allowing for the legitimate needs of law enforcement and for the time it takes to establish what happened.
9. Cookies, Analytics, and Similar Technologies
On the web we set a small number of first-party cookies, all of them necessary to run the service: a session cookie (eterniseed_session: HttpOnly and Secure; SameSite=Lax in a browser, and SameSite=None inside our mobile apps, which need it to keep you signed in) that keeps you logged in for 7 days, or 30 if you choose “Remember me”, or 90 on a device you have set up as a child's own; a language cookie (eterniseed_lang) that remembers the language you chose; a mode cookie (eterniseed_session_scope) that records whether this device is currently in Kids mode; and two ten-minute cookies (oauth_state, oauth_state_apple) used only to protect the Google and Apple sign-in round trip.
We also store data on your device so pages load quickly and keep working offline. Downloaded Bible chapters, coloring pages and other offline content are kept in your browser's IndexedDB database and in the app's offline cache, and anything you change while offline waits there until you reconnect. Your browser's local storage separately holds your display preferences, a copy of your account profile so pages can appear before the server replies, a record of which Terms and Privacy versions you accepted, and (on a device set up for a child) that child's first name. In our mobile apps the same information, and your sign-in token, are stored by the app on the device. All of it stays on your device; you can remove it by signing out and clearing your browser's or the app's stored data. None of these are advertising or cross-site tracking cookies, and we do not use advertising or cross-site tracking cookies anywhere on the web.
Our pages load their typefaces from our own servers. No page of ours, including the children's pages, makes a font or styling request to a third party.
We do not show a cookie banner, because we set no advertising or cross-site tracking cookies. Because we do not sell personal information, do not share it for cross-context behavioral or targeted advertising, and set no advertising or cross-site tracking cookies, a browser “Do Not Track” or Global Privacy Control signal has nothing to switch off here; we do not act on those signals, and there is no in-app switch for our own web measurement. You can clear everything we have stored on your device by signing out and clearing your browser's site data for eterniseed.com, and you can remove the records held on our side by deleting your account (Settings → Privacy → Delete My Account).
We measure web traffic in two ways. Cloudflare gives us aggregate, server-side, cookie-less figures. We also run our own first-party measurement script on our pages (including the children's pages), which records page views, which Bible chapter and translation was opened, and narration and AI Guide usage. Each record carries a random identifier your browser holds for the current tab only; it is not an advertising identifier, and we do not store your IP address with it. We keep these records to diagnose problems and to understand which parts of Eterniseed are used.
In our Android and iOS apps we use Google Firebase Analytics for first-party usage analytics, Firebase Crashlytics for crash diagnostics, and Firebase Cloud Messaging for push notifications you have allowed (see Section 1). Firebase Analytics is switched off entirely on every Kids screen; no analytics event is sent to Google from a child's screen. Crashlytics stays on there, so that an app which crashes for a child still gets fixed; a crash report carries the app's Firebase installation identifier and technical diagnostic details, and never a child's name or content. We do not collect your device's mobile advertising identifier. On Android the advertising-ID permission is stripped from the app we ship and advertising-ID collection is switched off; on iOS the app is built without advertising-identifier support and declares no tracking. Firebase recognises your installation only by an app-scoped installation identifier, which cannot be used to identify you in another company's app.
10. International Users
Eterniseed is operated from the United States. If you access it from outside the U.S., you understand that your information will be transferred to and processed in the U.S. Where applicable, we rely on the EU Standard Contractual Clauses (Module 2, controller to processor), supplemented by the UK Addendum for transfers of UK personal data, for transfers of personal data out of the EU/EEA and UK.
We have not yet appointed a representative in the European Union under Article 27 of the GDPR or in the United Kingdom under Article 27 of the UK GDPR; we will appoint both before we begin serving a church or organization outside the United States, and this policy will then name them. Until then, enquiries from residents of the EU/EEA or the UK go to [email protected].
11. Changes to This Policy
We may update this policy as Eterniseed grows. We will post the new version in-app with its effective date. For material changes, we will ask you to re-acknowledge before continued use.
12. Contact Us
Privacy questions: [email protected]
General support: [email protected]
Mail: ETERNISEED LLC, 8735 Dunwoody Place, STE N, Atlanta, GA 30350, USA
Phone: +1 (888) 887-9793
This policy is governed by the laws of the State of Georgia, U.S.A., without regard to its conflict-of-law principles. Nothing in that choice of law displaces a data-protection law that applies to you because of where you live, including the GDPR, the UK GDPR, or a comparable national law.