Privacy Policy

Version: Current

Current
September 28, 2026 to October 8, 2026

Daily Christians: Privacy Policy

Last Updated: October 8, 2026
Effective Date: October 8, 2026

We at SIMPLISIO INNOVATION SRL (together with our affiliates, “Daily Christians”, “we”, “our” or “us”) respect your privacy and are strongly committed to keeping secure any information we obtain from you or about you. This Privacy Policy describes our practices with respect to Personal Data that we collect from or about you when you use our mobile application and services (collectively, “Services”).

In short

We never sell your data or use it for advertising.
Your private faith life stays private. Your trackers, prayers, journal entries and Bible notes are visible only to you in the app.
Your conversations never train AI. The AI companies we use may not use them for training, and we have switched off every training and data-sharing setting available to us.
We protect the community. Automatic checks keep spam, scams, harassment and hate out of groups, and a photo check, which we are switching on step by step, keeps photos appropriate for everyone, including younger members.
You stay in control. You can export or delete your data at any time from the app.

The full details follow.

1. Data Controller

If you are located in the European Economic Area (EEA), Switzerland, or the United Kingdom, SIMPLISIO INNOVATION SRL is the controller responsible for the processing of your Personal Data as described in this Privacy Policy.

Company: SIMPLISIO INNOVATION SRL
Address: Bucharest, Sectorul 3, Strada Nerva Traian, Nr. 27-33, Birou 6, Bl. B, Etaj 1, Ap. 6, Romania
Registration: Nr. Registrul Comertului: J40/14613/2021, CUI: 44791098
Contact: [email protected]

2. Religious Data & Your Consent

Daily Christians is an app designed to support your Christian faith and daily growth. By its nature, the app processes data that may reveal your religious beliefs, including prayer content, Bible study activity, habit tracking, and faith-related conversations with our AI Bible Assistant.

Under GDPR Article 9, data revealing religious beliefs is considered a “special category” of personal data requiring explicit consent.

By creating an account, you explicitly consent to the processing of data related to your faith and daily practices as described in this Privacy Policy.

Any content you voluntarily submit (messages, prayers, notes, journal entries) is processed based on your active choice to provide it. You can withdraw consent for specific content at any time by deleting it within the app. Most content is deleted immediately; deleted community messages are hidden at once and removed completely when you delete your account (Section 12). You can withdraw consent entirely by deleting your account.

3. Data We Collect: By Feature

Data minimization: Most features are optional, and we only collect the data described below if you actually choose to use that feature. Account & Profile data (Section 3.1) and basic analytics and crash diagnostics (Section 6) apply regardless of which features you use, since they support the app itself. If you use the app in Guest Mode (Section 9), your content stays on your device and is never sent to us; Section 9 lists the few technical exceptions.

3.0 Pre-Launch Mailing List

If you sign up to be notified about our launch (before the app is available), we collect:

Email address: to send you a notification when the app launches and occasional updates about the app’s development
IP address: for fraud prevention (detecting spam signups)
Consent timestamp: recording when you gave consent (GDPR compliance)

Your email is stored securely and used for launch notifications and occasional updates about Daily Christians. You can unsubscribe at any time via the unsubscribe link in any email or by contacting us. We do not share your email with third parties for marketing purposes. After launch, your pre-launch email is not linked to any app account unless you choose to create one with the same email.

3.1 Account & Profile

When you create an account, we collect:

Email address: for sign-in, account management, and password reset
Username and display name: chosen by you. You need a username to join or start a community, so members can recognise each other.
Profile photo: optional, uploaded by you. Our automatic photo check applies to it as we switch it on (Section 3.12)
Denomination: selected during onboarding, so the app and the AI Bible Assistant can reflect your tradition. If you ask to join a community that is tagged with a tradition, its leaders and moderators see yours (Section 3.6)
Referral source: how you found the app (if provided). If you were referred by another user, your account may be linked to theirs for referral tracking, which may support a future ambassador rewards or commission program (see Section 3.10)
Preferences: such as language, theme, the hour your day starts, and your calendar and Bible tradition settings

We also store your account creation date, timezone, and subscription status.

Sign-in security: Our sign-in provider (Supabase) records the IP address and device type of each signed-in session, to keep your account secure. This record is removed when you sign out or delete your account.

Age: When you create your account (or the first time the app needs it), you tell us your age and we check it against the minimum age for your country (Section 9). Your exact age stays on your device and is not stored on our servers. When you use the AI Bible Assistant, a rough age range is sent with your message so answers are appropriate for your stage of life (Section 3.5).

3.2 Trackers (Habit Tracking)

When you use the habit tracking feature, we collect:

Tracker definitions: name, type, icon, target values, frequency, whether the habit is positive or negative
Daily logs: date, completion status, value/quantity, notes, and journal entries
Trigger descriptions: if you choose to record what triggered a behavior (e.g., for addiction recovery trackers)
Streak data: current streak, longest streak, total successful days
Goals and goal history: your targets and how they changed over time
Challenges: solo goals you set with start/end dates and progress. For challenges shared with other users, see Section 3.9 (Social Challenges)
Reminders: times, days, and custom messages for your reminders

Sensitivity note: Tracker data may reveal religious practices (e.g., prayer frequency) or health information (e.g., addiction recovery). Trigger descriptions are particularly sensitive. This data is stored securely and only you can see it in the app.

Deleted trackers: When you delete a tracker, it stays in “Recently deleted” for 30 days so you can restore it if you change your mind, and is then permanently removed.

3.3 Prayer

When you use the prayer feature, we collect:

Prayer subjects: categories you create to organize your prayers
Prayer intentions: the content of your prayer requests, answer status, and testimony
Prayer journal entries: your personal reflections linked to prayers
Prayer check-ins: session dates, duration, which intentions you prayed for, and reflection notes
Prayer statistics: aggregated data such as streaks, total check-ins, and total time spent in prayer

All prayer data is stored securely and only you can see it in the app. If you add a prayer widget to your home screen, see Section 3.14.

3.4 Bible Reader

Bible text is read locally on your device (SQLite database). The World English Bible comes with the app; other translations are downloaded from our storage when you choose them. The Bible text itself is never sent to our servers
Bookmarks, highlights, and notes: your annotations on Bible passages, including verse references, colors, labels, and personal notes. These are synced to our servers so you can access them across devices
Custom labels: label names you create to categorize Bible passages
Device identifier: a device ID is associated with each annotation to enable multi-device sync

3.5 AI Bible Assistant

When you use the AI Bible Assistant, we collect:

Your messages: the questions and prompts you send to the assistant
AI responses: the replies, stored so you can return to your conversations
Conversation details: titles, creation dates, message counts, and usage amounts

How your questions are answered: To respond, the assistant sends your message, together with the conversation so far, to an AI model through OpenRouter, a service that provides access to models from companies such as Anthropic, OpenAI and Google.

Answers suited to you: Together with your message, we send your Christian tradition, so that answers reflect its language and practice (for example, the Mass for Catholics or the Divine Liturgy for Orthodox Christians), as well as your language, your local time, a rough age range, and whether you have turned on Gen Z Mode. We never send your name, email address, or account details. OpenRouter also receives a technical usage identifier, derived from your account, so we can apply your plan’s usage limits.

Your permission: Before your first message to the AI Bible Assistant, the app asks your permission. If you decline, nothing is sent.

No training on your conversations: None of these companies may use your conversations to train AI, and we have switched off every training and data-sharing setting available to us. Some may retain requests for a limited period under their own privacy policies (Section 10), as is common practice among AI providers.

Safety: Your questions and the assistant’s answers go through our automatic safety check (Section 3.12), so that every answer remains safe and helpful. We do not read your AI conversations; our team can open stored data only when needed to run the service or fix a problem (Section 15).

Your conversation history: Your conversations are stored in our own database (Supabase) so that you can return to them. You can delete any conversation at any time, and it is deleted permanently.

AI providers: We may add or change AI providers in the future. Every provider we use states that it does not use your content to train AI models. This applies to the AI Bible Assistant and to our automatic safety checks (Section 3.12). Section 10 explains what they receive and how to ask us which companies they are.

Important: AI-generated responses are not professional counseling, therapy, or medical advice. They are provided for informational and inspirational purposes only.

3.6 Community & Groups

When you take part in community groups, we collect:

Group memberships: which groups you belong to, your role (member, moderator or leader), and join date
Groups you create: the group’s name, description, welcome message, photo and language
Messages: text messages you send in group chats, including replies and mentions
Shared images: photos posted in group conversations by verified group hosts
Poll responses: your votes on group polls
Reactions: emoji reactions you add to messages
Blocks: people you choose to block, so their messages and notifications are hidden from you
Reports: if you report a message, a person or a group, the report reason and status
Reading position: which messages you have read in each community, so your unread count works on all your devices. Only you can see it.
Pins and group count: Communities you have pinned, and how many communities you have started (there is a limit), are stored so they work on all your devices.
Subscription tier badge: if you subscribe to Pro or Max, a badge showing your tier is displayed next to your name in group chats, feedback ideas, and update posts

Visibility: Community messages, images, polls, reactions, and subscription tier badges are visible to other members of the group.

Invite links and codes: the name, description, photo, number of members, language and tradition of a community are visible to anyone who has its invite link or code, including on our website before they have an account. The person who starts a community chooses what to write there.

Link previews: When someone posts a link, our server opens the page once to build a preview in the chat, so the website sees a request from our server. If the preview has a picture, each member’s phone loads that picture directly from the website, so that website can see the phone’s internet address, as with any picture on the web. Previews are only built for well-known approved websites.

If you report content, your identity is not shared with the person you reported.

Keeping groups safe (automated and human): Our groups are a place to pray for one another, so we protect them carefully:

Before posting: messages go through our automatic safety check (Section 3.12), which screens out spam, scams, harassment and hate before others see them.
After a report: an automatic review assesses the reported message together with the report, and either removes it when a violation is highly likely, keeps it when it is clearly fine, or refers it to our team when the case is unclear. If a message is reported as a possible threat to someone’s life or safety, it may be hidden at once while our team looks; hiding it is not a decision about the person who posted it. If it is a possible threat to someone’s life, a copy may be kept as evidence, even after you delete your account (Section 12).
Restrictions: repeated or serious violations can lead to a temporary restriction from the community (posting, reacting, reporting, joining or starting groups, the feedback board, and challenges), from 30 minutes to 30 days, sometimes until our team has reviewed the case, or to a permanent one after repeated violations or a single very serious one. Your personal features (trackers, prayer, Bible reader, AI Bible Assistant) remain available during any restriction. You can ask us to review any restriction by writing to [email protected].
When someone may be struggling: messages in which someone shares a personal struggle, including thoughts of self-harm, are never removed, because the community is there to support them. When the check sees such a message, the person who wrote it is offered support resources, and our team receives a private alert. The alert does not contain your words; the team opens the message in the app to see it. These alerts are delivered through the notification services described in Section 4.
Moderation records: we keep a record of strikes and community pauses on your account: what happened, when, how it was decided, and any note you write to our team. Strikes expire after 90 days to a year and are deleted a year after that. The rest of the record is deleted when you delete your account (apart from what Section 12 lists). When a leader removes someone from a group, or asks our team for help, that is recorded too.
Held-back messages: if a held-back message is serious enough to count as a violation, we keep its words together with that record, so you can see what it was and our team can review it. They are deleted when that record is deleted (about 15 months for lighter violations, up to two years for serious ones) or when you delete your account. If the automatic check can’t decide, our team may look at the held-back message; we keep it for at most 30 days, or until they decide. Other held-back messages are not kept. Held-back words are included in your export.
Starting a group: when you start a group, the app confirms to our server that you are an adult; your age itself is not sent.
Joining: when you ask to join a community that needs approval, the people who run it (leaders and moderators) can see your name, username and photo until they answer. Communities can ask to be found in the app: our team reviews them first (see Public groups below), then people can find them and ask to join. When your request is answered, you get a notification that names the community.
Asking to join: If you ask to join a community that is tagged with a Christian tradition, the people who run it (its leaders and moderators) see your own tradition next to your name while your request is waiting. The app tells you this before you send the request.
Public groups: a group leader can let people find their group in the app. Before our team makes such a group public, a member of our team may read the group’s messages from the last 30 days, to make sure it is a safe and welcoming place for new people. This happens only in groups whose leader turned this on, only for that decision, and the group’s members are told in the group chat when the leader turns it on (legal basis: our legitimate interest in keeping public groups safe for everyone who joins them).

Deleted messages: When you delete a message, it disappears from the group at once. We keep its text and any photo until you delete your account, so that our team can still review reports about it.

Edited messages: you can edit a message for a short time after posting. Members see only the new text, marked “edited”. We keep the earlier versions until you delete your account, so a report can be judged on what was actually written. Edits go through the same safety check as new messages.

3.7 Journey (Lessons & Paths)

When you use the learning journey feature, we collect:

Progress data: which lessons and action plan items you have completed, and when

3.8 Feedback & Updates

When you use the feedback board or app updates, we collect:

Feature ideas: title, description, and category of ideas you submit
Comments: your comments on feature ideas
Upvotes: which ideas you upvoted
Update reactions: your reactions to app update posts

Your display name and profile photo are shown alongside your feedback contributions. Because others build on them, ideas you post stay on the board after you delete your account, without your name or photo. Your comments and upvotes are deleted with your account.

3.9 Social Challenges

When you create or join a challenge with friends, we collect:

Challenge details: goal type, start/end dates, and (for rolling challenges) recurring period settings
Challenge text: the name, description, goal label and commitment note you write, and the name of a custom tracker you bring into a challenge, because it becomes visible to other participants. Before others see this text, our automatic safety check (Section 3.12) reviews it and recognizes its language, so public challenges are shown to people who speak that language. If the check blocks it, we keep a short copy so our team can review the decision. If the check cannot run for a moment, the text stays hidden from others until it has been checked
Participation: who joined, your progress, and whether you completed each period
Connections: accepting a challenge invite from another user creates a mutual “connection” record between your accounts, so you can be invited to future challenges more easily
Sharing choices: you control whether your name and your specific goal are shown to other participants, using per-challenge visibility settings. A challenge creator can also make a board fully anonymous, so only “Someone” is shown instead of participant names
Encouragements: “praying for you” style taps sent between named participants
Reports: if you report a public challenge for inappropriate content, the report reason and status

Visibility: on a shared challenge board, other participants can see your name (unless you’ve chosen anonymity) and your streak/progress (unless you’ve chosen not to share your specific goal). Public challenges may be visible to users beyond your immediate friends.

Sensitivity note: certain goal categories (e.g., addiction-recovery goals) are never stored in a form that could reveal the specific struggle to other participants, even when identity/goal sharing is enabled.

Anti-cheat measure: while a tracker is committed to an active challenge, certain edits to that tracker are temporarily locked to preserve the integrity of shared progress. This does not involve any additional data collection beyond what’s described above.

3.10 Ambassador Program & Referrals

Ambassador applications: if you apply to become an ambassador or to host a community group, we collect what you enter in the application: your name, email address, social media profiles, a short description about you, your country and language, your photo, and the group you propose. We also record the IP address the application was sent from and the result of a spam-protection check (Cloudflare Turnstile), to keep automated spam out. Applications are private to you and our team, and are deleted with your account; if you applied without an account, write to us to have your application deleted.
Referral/commission tracking: if you are an ambassador and someone you referred subscribes to a paid plan, we record the referral relationship, subscription tier, and a calculated reward amount, to support a potential future ambassador rewards or commission program. We do not currently have an active commission payout system; this data capture exists to support one if/when it launches.
Ambassador directory: An ambassador’s name, username, photo and group are shown to people choosing who referred them.

3.11 Verse of the Day

Read status: whether you’ve opened a given day’s verse
Likes: verses you’ve liked, which contribute to an aggregate (non-identifying) like count shown to all users

This engagement data is used to power your personal experience (e.g., marking verses as seen) and is not shared with other users individually.

3.12 Keeping the community safe: automatic safety checks

Our groups are a place to pray for one another and share honestly. To protect them from spam, scams, harassment and hate, an automatic AI check reviews:

Community messages, before they are posted, when you edit them, and again if a message is reported
Usernames and display names, so that every name in the community is respectful
Challenge texts, including the name of a custom tracker you bring into a challenge, because they are visible to other participants
Feedback board posts, because they are visible to all users
AI Bible Assistant conversations, so that every answer remains safe and helpful
Profile and group photos, so that they are appropriate for everyone, including younger members
Community names, descriptions, welcome notes and tab names, before they are saved

The check can also tell which language a message is in and whether it is about a topic the community has switched off (such as politics or war), because leaders can set these for their community. Sharing a personal struggle is never held back for that.

What the check receives: only the text or photo being reviewed, never your email address or account details. For reports, it also receives the report reasons, how many reports there are, and the community’s name, description and rules, so the message can be judged in its setting. The check runs through OpenRouter on AI models provided by other companies (Section 10). None of them may use this content to train AI. Some may retain it for a limited period under their own privacy policies, as is common practice among AI providers.

When something is blocked: a message that clearly breaks the rules is not posted. Before it is dropped, a second automatic look confirms it; if it is a close call, or the first check was unavailable, another AI check from the AI services we work with decides, and if that can’t decide, our team does. Nothing is posted in the meantime. A held-back message that clearly breaks the rules can count as a violation (see Section 3.6). Feedback posts wait for our team to review them instead.

Photos: profile and group photos are checked by an automatic AI check so they are appropriate for everyone, including younger members. We are switching this check on step by step, so a photo uploaded before it reaches you may be checked later, and a photo that doesn’t pass is taken down. A photo that doesn’t pass is never shown to others, and your previous photo stays. We keep a record of each decision together with a digital fingerprint of the photo (not the photo itself), so the same photo doesn’t need to be checked twice. We delete a photo that doesn’t pass. If a photo may involve a child, we delete it at once, we do not keep a copy of it, and we keep only a written record of the decision so our team can act. If someone reports a photo, our team may look at it for that review.

Photo limits: to prevent misuse, repeatedly uploading photos that don’t pass, or uploading a seriously inappropriate photo, can pause your ability to change photos, from a day up to 90 days, or until our team has reviewed it. The automatic check usually limits only photos. When a photo appears seriously harmful, or may involve a child, your community access may also be paused until our team has reviewed it, to protect other members in the meantime.

Sharing personal struggles: sharing a personal struggle is never treated as a violation (Section 3.6).

If you disagree with a decision: write to [email protected] and a member of our team will review it.

3.13 Bible Reading Plans

When you follow a Bible reading plan, we store which plans you follow, the chapters and days you complete, and your plan reminders, so your progress syncs across your devices. Your reading progress is private: only you can see it. When you mark a chapter as read in one plan, it is also marked in your other plans that include it. If you restart or leave a plan, we keep your earlier progress as history; it is removed when you delete your account.

3.14 Widgets

If you add Daily Christians widgets to your home screen (or, on iPhone, a verse widget to your lock screen), the app saves what the widget shows on your device so it can display it: for example your tracker names and streaks, the names of the people and subjects you pray for, your challenge progress, or a verse. Recovery trackers appear under a discreet name or not at all, and prayer intentions are never shown. You choose what each widget shows; please keep in mind that anyone who can see your screen can see it. We store your widget settings on our servers so they can be restored, and record when a widget was first and last shown, to understand how widgets are used.

4. Notifications

Push notification token: your device’s Expo push token, stored to deliver notifications. Collected only with your permission.
Device name, platform and time zone: stored alongside your push token, so notifications arrive at the right time of day
Notification preferences: your settings for each kind of notification (reminders, verse of the day, streak alerts, weekly summary, challenges, quiet hours, sound, vibration) and for each group

What notifications can show: so you can follow along at a glance, some notifications include a little content:

Group messages: the group name, the sender’s name and the beginning of the message
Join requests (for group leaders): the name of the person asking to join
Challenges: the challenge name and, for example, the name of a friend who joined or checked in, or of a participant who could use a prayer
Reminders: reminders are created on your device and can show your tracker’s name
Your own restriction: a notice when your community access is paused or comes back.
Reports you made: a notice that our team reviewed it. Neither contains the message.

Notifications sent from our servers never contain your private prayers, prayer journal, tracker details or AI conversations. A prayer request you post in a community is a group message, so its beginning can appear in other members’ notifications like any group message. Notifications are delivered through Expo’s push service and Apple’s or Google’s notification services (Section 10). You can turn off all notifications at once in Settings (this includes community notifications), or turn each kind off separately, and change notifications for each group in that group’s settings.

5. Subscriptions & Payments

Subscription status: whether your subscription is active, cancelled, or expired
Purchase history: processed and stored by RevenueCat (our subscription management provider). RevenueCat assigns your device an anonymous identifier before you sign in, so a purchase can be linked to your account when you do
Payment information: we never collect or see your credit card, billing address, or payment details. All payment processing is handled entirely by Apple (App Store) or Google (Play Store)

6. Analytics & Diagnostics

App usage analytics: screen views, feature interactions (for example, joining a group), and session data, collected via Firebase Analytics to understand how the app is used and improve it. Analytics are tied to your device, not to your account. You can switch them off at any time in Settings. They are switched off for anyone who tells us they are under 18. Legal basis: Legitimate interest with opt-out available.
Crash reports: error details, device model, operating system version and app version, collected via Firebase Crashlytics so we can find and fix problems. Crash reports use a random identifier that is not linked to your account, and they are switched off for anyone who tells us they are under 18. Legal basis: Legitimate interest.

7. Country Detection & Embargo Enforcement

We determine your country using Cloudflare’s infrastructure-level geolocation, to comply with applicable sanctions laws and to apply the right minimum age for your country. This works as follows:

When you open the app for the first time, and when you sign in or create an account with email, the request passes through our Cloudflare service
Cloudflare uses your IP address to determine a 2-letter country code. Our Cloudflare service does not store your IP address, and our app never receives it
The country code is used to check against sanctioned countries and to set the minimum age for creating an account (Section 9)
This check is performed at sign-in and periodically when the app is opened. Sign in with Apple and Sign in with Google connect directly to our sign-in provider

If you are located in a sanctioned region (currently: North Korea, Iran, Syria, Cuba, Russia), you will be unable to use the service.

Age-gate use: If you enter an age below your country’s minimum threshold during onboarding (see Section 9), the detected country code is also kept on your device solely to calculate how long until you can create an account. This country code is never transmitted to our servers and is removed when you meet the age requirement or delete/uninstall the app.

Legal basis: Legal obligation (sanctions compliance); legitimate interest in protecting minors (age-gate).

8. How We Use Your Data

We use your Personal Data for the following purposes:

To provide the Service: processing your data to deliver habit tracking, prayer, Bible reading, the AI Bible Assistant, community, challenges, reading plans and journey features
To improve the Service: analyzing usage patterns and crash data to fix bugs and develop new features
To communicate with you: sending push notifications (with your permission), subscription updates, and important service announcements
To keep the community safe: automatic safety checks, reviewing reports, and preventing spam and misuse (Sections 3.6 and 3.12)
To comply with the law: sanctions enforcement. We may also disclose your data if required by law, court order, or governmental request, or if we believe disclosure is necessary to protect our rights, your safety, or the safety of others

We do not sell your Personal Data. We do not use your data for advertising. We do not share your data with data brokers.

Business transfers: If we are involved in a merger, acquisition, or sale of assets, your Personal Data may be transferred as part of that transaction. We will notify you before your data becomes subject to a different privacy policy.

9. Children & Guest Mode

Age Requirements

The minimum age to create an account depends on your country:

13 years: United States, United Kingdom, Canada, and others
14-15 years: Austria, France, Italy, Spain, and others
16 years: Germany, Romania, Netherlands, Poland, and others
18 years: India, Brazil, South Africa, Turkey, and others. If we cannot determine your country, or it is not on our list, we use 18, the strictest threshold

When you create your account, you tell us your age and we check it against the minimum for your country. See our full age threshold list in the app.

Guest Mode

Users who do not meet the minimum age, or who choose not to create an account, can use the app in Guest Mode:

Your content stays on your device: trackers, prayers, notes and everything else you create are stored only on your device and never sent to our servers
No account and no personal information: no name, email or account is created
A few technical things still leave your device, because the app needs them to work: the country check (Section 7), the anonymous purchase identifier (Section 5), Bible translations you download (Section 3.4), the list of reading plans, the check for a newer app version, the check for policy updates, and anonymous analytics (unless switched off) and crash reports, which are switched off for anyone who tells us they are under 18 (Section 6)
Guest data may be lost if the app is uninstalled or device data is cleared

Guests cannot use the community, the AI Bible Assistant, social challenges or the feedback board, which all require an account.

Managing Guest Data

Although guest content never reaches our servers, under GDPR we are still considered the data controller for data processed through our app. You have full rights to export and delete your guest data:

Export your data: Settings > Data Management > Export My Data. Your data is generated on-device in JSON or CSV format and shared via your device’s native share sheet.
Delete your data: Settings > Data Management > Delete Account. All guest content (trackers, prayers, Bible annotations, journal entries) is permanently removed from your device. This requires device authentication (biometric or passcode) and a two-step confirmation.
What is preserved after deletion: your language preference, theme, Bible tradition selection, and age-verification status (for legal compliance) are kept so you can continue using the app without re-configuring it. Everything else is wiped.
Uninstalling the app: also removes all local guest data permanently (equivalent to deletion).

No server-side request is required for guest data deletion, because no server copy exists.

Data Migration

When a guest user later creates an account, their locally stored data can be migrated to our servers. This requires your explicit consent, and you are informed what data will be migrated before confirming.

COPPA Compliance

In compliance with COPPA (US), GDPR Article 8 (EU), and the UK Age Appropriate Design Code, we do not knowingly collect personal information from children under 13 (or the applicable age in your country). Users below the minimum age are limited to Guest Mode, where their content stays on their device, and analytics and crash reports are switched off for anyone who tells us they are under 18. If we discover we have inadvertently collected information from a child below the minimum age, we will delete it promptly. If you believe a child has provided Personal Data to us, please contact us at [email protected].

10. Third-Party Services

We use the following third-party services to operate the app. Each receives only the data necessary for its purpose:

Supabase (database, storage & sign-in)

Receives: All user data listed in this policy, and the IP address of each signed-in session (Section 3.1)
Purpose: Backend database, sign-in, file storage
Data is encrypted at rest and in transit
Privacy: https://supabase.com/privacy

OpenRouter (AI processing)

Receives: AI Bible Assistant messages, the conversation context described in Section 3.5, conversation titles, a technical usage identifier, and the text and photos sent for automatic safety checks (Section 3.12)
Purpose: Generating AI responses and running safety checks
OpenRouter itself does not store your messages or use them for training. It passes them to the AI model providers described below.
Privacy: https://openrouter.ai/privacy

AI model providers (through OpenRouter)

Receive: what OpenRouter passes on for the AI Bible Assistant and the safety checks (Sections 3.5 and 3.12). Never your name, email address or account details
Purpose: Running the AI models behind the AI Bible Assistant and our safety checks
None of them may use your content to train AI models. Some may retain it for a limited period, as described in their own privacy policies
Which companies: these change as better AI models come out, so we don’t list them here. Write to [email protected] and we’ll tell you which ones process your data

Apple (Sign in with Apple)

Receives: Sign-in request. If you choose “Hide My Email,” Apple generates a private relay email address that forwards to your real email
Purpose: Secure sign-in without creating a password
Privacy: https://www.apple.com/legal/privacy/

Google (Sign in with Google)

Receives: Email address and display name from your Google account
Purpose: Secure sign-in without creating a password
Privacy: https://policies.google.com/privacy

RevenueCat (subscription management)

Receives: An anonymous identifier (linked to your account once you sign in), subscription status, purchase history
Purpose: Managing subscriptions across iOS and Android
Privacy: https://www.revenuecat.com/privacy

Firebase Analytics (usage analytics)

Receives: App usage events and a device identifier. Never your account ID
Purpose: Understanding how features are used to improve the app
You can opt out in app settings; switched off for anyone who tells us they are under 18
Privacy: https://firebase.google.com/support/privacy

Firebase Crashlytics (crash reporting)

Receives: Crash and error details, device information, and a random identifier
Purpose: Finding and fixing problems
Data is not linked to your identity; switched off for anyone who tells us they are under 18
Privacy: https://firebase.google.com/support/privacy

Expo (notification delivery & app updates)

Receives: Your push token and the content of notifications sent to you (Section 4); requests from the app to check for updates
Purpose: Delivering notifications and app updates
Privacy: https://expo.dev/privacy

Apple Push Notification service / Firebase Cloud Messaging (notification delivery)

Receives: The notifications sent to your device
Purpose: Delivering notifications on iPhone and Android
Governed by Apple’s / Google’s privacy policies

Amazon Web Services (email delivery)

Receives: Your email address and the content of emails we send you (for example, sign-in emails and replies to applications)
Purpose: Sending service emails
Privacy: https://aws.amazon.com/privacy/

Cloudflare (country check, network security & spam protection)

Receives: Your IP address, used to determine your country; email sign-in requests, which pass through on their way to our sign-in provider; and, for applications, a spam-protection check (Turnstile)
Purpose: Sanctions compliance, age thresholds, network security, spam prevention
Our Cloudflare service does not store your IP address
Privacy: https://www.cloudflare.com/privacypolicy/

Apple App Store / Google Play Store (payments)

Receives: Your payment information (we never see this data)
Purpose: Processing in-app purchases and subscriptions
Governed by Apple’s / Google’s privacy policies

11. Legal Bases for Processing (EU/UK Users)

Under GDPR, we process your data on the following legal bases:

Explicit Consent (Article 9) + Contractual Necessity (Article 6(1)(b))

Data that reveals religious beliefs (prayer content, Bible annotations, habit tracking, AI Bible Assistant conversations about faith, community discussions, denomination) is processed under both Article 9 explicit consent and Article 6(1)(b) contractual necessity. Article 9 consent is required in addition to the Article 6 basis because this data falls under GDPR’s “special categories.”
You provide Article 9 consent when creating your account. You can withdraw it by deleting your account.
Content you voluntarily submit is processed based on your affirmative action of providing it. You can withdraw consent for specific content by deleting it.

Contractual Necessity (Article 6(1)(b))

Account data (email, username, profile): Required to create and manage your account
Subscription data: Required to fulfill your subscription

Legitimate Interest (Article 6(1)(f))

Analytics (Firebase Analytics): Improving app functionality and user experience. You can opt out.
Crash reporting (Firebase Crashlytics): Identifying and fixing bugs to maintain service quality
Community safety: automatic safety checks, held-back messages, report reviews, photo checks, strikes and pauses and their records, to keep the community safe for everyone, including younger members
Sign-in security: recording the IP address of signed-in sessions to protect your account
Ambassador applications: reviewing applications and keeping spam out
Referral tracking: recording referrals for a possible future ambassador rewards program

Explicit Consent (Article 9(2)(a)) for safety checks

Where safety checks, report reviews or support alerts involve content that reveals your faith or health, we rely on the explicit consent you give when creating your account. We also rely on this consent for showing your tradition to the people who run a community you ask to join.

Consent (Article 6(1)(a))

Pre-launch mailing list: you can unsubscribe at any time

Legal Obligation (Article 6(1)(c))

Country-level geolocation: sanctions compliance
Accounting records of payments we receive from Apple and Google

12. Data Retention

Active account data: kept until you delete your account
AI Bible Assistant conversations: kept until you delete a conversation or your account
Tracker, prayer and Bible data: kept until you delete individual items or your account. Deleted trackers stay in “Recently deleted” for 30 days, then are removed
Community messages: kept until deleted by you or a group administrator. Deleted messages are hidden at once, and their text and any photo are kept until you delete your account, so that our team can still review reports. Earlier versions of edited messages are kept until you delete your account. If you leave a group, your messages stay visible to its members unless you delete them
Sign-in sessions: each session record (including its IP address) is kept until you sign out or delete your account
Safety check records: records of automatic decisions are kept until you delete your account. A short copy of blocked challenge text is kept for our team’s review and deleted with your account. For photos, see Section 3.12. Strikes and pauses, with your notes to our team: see Section 3.6.
Reading-plan progress and its history: kept until you delete your account
Reports you file: reports you file are kept after you delete your account, without your identity, so moderation decisions stay consistent
Reports: reports other people made about your messages stay in our moderation record, without your name, after you delete your account, so moderation decisions stay consistent.
Threats to life: If a message is reported as a possible threat to someone’s life, we keep a copy so our team can act and, where the law requires, preserve it: the message and its earlier versions, the reports about it, and your username, name, email address and account creation date at that moment. If it turns out to be a false alarm, we delete the copy at once. Otherwise we keep it until our team has decided and then normally for 90 days, for up to a year if the authorities were informed, and longer if the law requires. We keep it even if you delete your account.
Held-back messages: the words of a held-back message that counts as a violation are deleted when its record is deleted (about 15 months for lighter violations, up to two years for serious ones) or when you delete your account. A held-back message waiting for our team’s decision is kept for at most 30 days, or until they decide (Section 3.6)
Refused messages: a short log of chat messages the app refused to send (the reason, the community and the time, never the words), kept for 90 days to tune our limits and deleted with your account.
Policy notices: we keep a record that you were shown a notice about a policy update and what you tapped, to show we told you in time. It is deleted with your account.
Content others build on: ideas you posted on the feedback board, and groups, polls and challenges you created that others still use, stay after you delete your account, without your name
Referral and reward records: Referral and reward records for the ambassador program are kept without the link to your account.
Ambassador applications: kept until you delete your account or ask us to delete them
Pre-launch mailing list: kept until you unsubscribe or request deletion
Purchase records: kept by Apple, Google and RevenueCat under their own policies; our copy of your subscription status is deleted with your account
Analytics data: kept for up to 14 months, according to our Firebase Analytics settings
Crash reports: kept according to Firebase Crashlytics defaults (typically 90 days)
Photos that don’t pass, or that may involve a child: deleted at once; only a written record of the decision (no image) is kept.
Photo fingerprints: a digital fingerprint of each checked photo, with the result, is kept so the same photo doesn’t need checking again; it can’t be turned back into the photo.
Our accounting records: records of payments we receive from Apple and Google are kept as long as Romanian accounting law requires
Backups: our database provider keeps encrypted backups for a short period; deleted data disappears from them as they are replaced

13. Your Rights

All Users

You can exercise these rights directly in the app:

Delete your account: Settings > Data Management > Delete Account. Requires device authentication (biometric or passcode). Your personal data is deleted immediately and permanently, apart from the few things Section 12 lists, and why. This cannot be undone.
Export your data: Settings > Data Management > Export My Data. Choose JSON or CSV format. The export includes your own moderation record: your community pauses and strikes, the notes you wrote to our team, messages that were held back before posting and counted as a violation, earlier versions of messages you edited, and the reports you filed. It leaves out our team’s private notes, the automatic checks’ scores, and who reported you, to protect the people who report content. You can ask us by email for anything not included.
Delete specific content: Delete individual trackers, prayers, AI conversations, Bible notes, and community messages within the app (deleted community messages are hidden at once, and their text and any photo are kept for report review; see Section 12).
Edit your data: Update your profile, tracker settings, and other information at any time.

EU/UK Users (GDPR Rights)

In addition to the above, you have the following rights under GDPR:

Right to access: View and export your data (see above), or ask us for anything not included in the export
Right to rectification: Correct inaccurate data via the app or by contacting us
Right to erasure: Delete your account and data (see above)
Right to data portability: Export your data in JSON or CSV format (see above)
Right to restrict processing: Contact us to limit how we process your data
Right to object: Object to processing based on legitimate interests, such as analytics
Right to human review: Some decisions are made automatically, such as removing a message, restricting your access to groups, or pausing photo changes. You can ask a member of our team to review any of them
Right to withdraw consent: Delete content or your account at any time
Right to lodge a complaint: Contact your local data protection authority

Supervisory authorities:

Romania: ANSPDCP (Autoritatea Nationala de Supraveghere a Prelucrarii Datelor cu Caracter Personal)
Your local EU/EEA data protection authority
UK: Information Commissioner’s Office (ICO): https://ico.org.uk

For requests not available through the app, contact us at [email protected]. We will respond within 30 days.

US Residents (State Privacy Rights)

If you are a resident of California, Virginia, Colorado, Connecticut, or Utah:

Right to know: What data we collect and how we use it (this policy)
Right to delete: Delete your account and data via the app (see above)
Right to correct: Edit your data via the app
Right to data portability: Export your data via the app
Right to opt out of sale: We do not sell your personal data
Right to non-discrimination: We will not treat you differently for exercising your rights
Right to appeal: If we deny a request, you can appeal by contacting us

We do not sell personal data. We do not share personal data for cross-contextual behavioral advertising.

For requests, contact us at [email protected]. We will respond within 45 days.

14. International Data Transfers

Your data may be transferred to and processed in countries outside the European Economic Area (EEA), Switzerland, and the United Kingdom, including the United States.

When transferring data outside these regions, we rely on safeguards approved under GDPR, such as:

The EU-US Data Privacy Framework, for recipients certified under it
Standard Contractual Clauses (SCCs): approved by the European Commission under Article 46(2)(c) GDPR
The UK Addendum or International Data Transfer Agreement: for transfers from the UK

Our third-party processors (Supabase, OpenRouter and the AI model providers it uses, RevenueCat, Firebase, Expo, Amazon Web Services, Cloudflare) maintain their own data transfer safeguards. For details, see Section 10.

For a copy of the safeguards we use, contact us at [email protected].

15. Security

We implement commercially reasonable technical, administrative, and organizational measures to protect your data:

All data is encrypted in transit (TLS/HTTPS)
Database data is encrypted at rest (Supabase default encryption)
Row Level Security (RLS) ensures that, in the app, you can only access your own private data
Authentication uses industry-standard protocols (OAuth 2.0, bcrypt password hashing)
We use standard encryption only (TLS/HTTPS), with no custom cryptographic implementations
Our team can access data only when needed to run the service, fix problems, review reports, or decide whether a group can become public (Section 3.6)

No system is 100% secure. If you discover a security vulnerability, please contact us at [email protected].

Data breach notification: In the event of a data breach that poses a risk to your rights, we will notify affected users and the relevant supervisory authorities in accordance with applicable law (within 72 hours for GDPR).

16. Changes to This Policy

We may update this Privacy Policy from time to time. When we do, we will:

Publish the updated version with a new effective date on this page
Tell you in the app (or by email) about significant changes
For material changes to how we process your data, we will seek your renewed consent where required by law
Your continued use of the Services after changes take effect constitutes acceptance of non-material changes

17. Contact Us

If you have questions about this Privacy Policy or want to exercise your privacy rights:

Email: [email protected]
Company: SIMPLISIO INNOVATION SRL
Address: Bucharest, Sectorul 3, Strada Nerva Traian, Nr. 27-33, Birou 6, Bl. B, Etaj 1, Ap. 6, Romania

Previous versions

September 28, 2026 to October 8, 2026