Privacy Policy
Privacy Policy
This page summarizes the public app-store privacy information for Faith Garden, the website’s behavior, and the app’s current analytics and advertising-attribution setup.
Overview
This Privacy Policy describes how the Faith Garden website and app may handle information.
It is based on the public App Store privacy information for Faith Garden, the behavior visible in this website codebase, and the app-side attribution and analytics implementation visible in the local christian_app project as of August 1, 2026.
Because this policy is derived from code and public disclosures rather than a complete internal data map, it should be updated whenever the app’s backend, advertising, analytics, or support workflows materially change.
Information we collect
According to the App Store privacy label, Faith Garden may collect contact information, user content, and identifiers for app functionality, personalization, analytics, and developer marketing.
The app code also indicates use of analytics and ad-attribution tooling that may process limited device, campaign, deep-link, and account-linked identifier data to understand installs, sign-ins, subscriptions, donations, and other high-level app events.
If you use the support form on this website, the site opens your email app with a pre-filled message instead of storing that message in the website itself.
Account information and sign-in methods
The app code uses Firebase Authentication and supports account sign-in flows that include email and password, Google Sign-In, and Sign in with Apple.
Depending on the sign-in method you choose, Faith Garden may receive account details such as an email address, display name, profile photo, provider identifier, or authentication tokens needed to create, access, or secure your account.
If you contact support about account access, deletion, billing, or privacy, related correspondence may also become part of your support history.
How information may be used
App-store privacy information indicates that collected app data may be used for functionality, personalization, analytics, and developer marketing.
The app implementation shows Firebase Analytics for in-app product analytics and AppsFlyer for marketing attribution, including measurement of campaign performance and install or re-engagement flows from partners such as Meta Ads and TikTok Ads.
Support emails may be used to respond to questions, troubleshoot issues, and follow up on account or privacy requests.
Advertising attribution and campaign measurement
The app code in the christian_app project includes AppsFlyer-based marketing attribution. Based on that implementation, Faith Garden may use AppsFlyer to measure which campaigns, media sources, or deep links led to installs, opens, sign-ups, subscription starts, completed subscriptions, donations, and certain other high-level app events.
The code also shows that the app may set an AppsFlyer customer user ID after sign-in and may process attribution fields such as campaign and media source. This page does not claim that every available AppsFlyer feature is enabled in production, but it does reflect that attribution and campaign-measurement support has been implemented in the app code.
Tracking permission and device identifiers
On iOS, the app code requests App Tracking Transparency permission when needed and includes a tracking-permission message stating that limited device data may be used to measure ad performance and improve the experience after install.
The Android app configuration also declares the Google Play advertising ID permission. Where supported by the platform and applicable law, advertising or attribution identifiers may be used for analytics and campaign measurement rather than to collect prayer or journal content.
Sensitive faith content
The website is not designed to collect prayer entries, journal text, or other sensitive free-form faith content through website analytics.
The app analytics service in the christian_app project explicitly filters out a range of sensitive fields such as journal text, private notes, search text, names, emails, and raw user IDs from ordinary analytics-event parameters before logging them. That does not rule out other app data flows entirely, but it does indicate a code-level effort to avoid sending sensitive free-form spiritual content through routine analytics events.
Subscriptions, purchases, and donations
The app code includes subscription and purchase handling through RevenueCat, along with app-store billing flows on supported platforms.
If you start or complete a subscription or donation flow, Faith Garden and its service providers may process plan identifiers, product identifiers, purchase status, renewal state, entitlement status, transaction-linked metadata, and limited revenue or currency information needed to verify access, manage billing state, prevent abuse, and measure purchase-related events.
Actual payment processing, refunds, renewals, and certain billing records may also be handled by Apple, Google, RevenueCat, or other payment-related partners under their own terms and privacy practices.
Notifications and reminders
The app code includes push notifications, local reminders, notification-permission prompts, and notification-preference syncing.
If you allow notifications, Faith Garden may process device push tokens, reminder preferences, notification-permission status, check-in schedules, affirmation reminders, journey reminders, and related operational delivery data needed to send or manage notifications.
Notification services may involve Expo, Apple, Google, Firebase, or similar infrastructure depending on device and build configuration.
Crash reporting, monitoring, and operational logs
The app code includes Crashlytics-based monitoring and non-fatal error logging for operational reliability.
Based on the implementation, Faith Garden may process technical diagnostics such as app environment, platform, error messages, limited operational attributes, and hashed user identifiers for crash reporting and debugging.
The monitoring code also shows an effort to filter out sensitive free-form fields such as prayer content, names, emails, notes, and raw user IDs before sending ordinary monitoring attributes.
Website analytics and cookies
This website can use Google Analytics for basic traffic and download-click measurement when analytics is enabled and you choose to allow analytics cookies.
The website analytics setup is separate from the app’s mobile attribution and analytics tooling described above.
Storage, backend services, and infrastructure
The app code references Firebase services for authentication, Firestore database usage, cloud storage, serverless functions, analytics, and related app infrastructure.
Based on that implementation, user account data, app content, attachments, subscription state, and operational records may be processed through Firebase-backed services and connected infrastructure used to run Faith Garden.
This website repository does not expose the complete production backend schema, storage inventory, or server-side retention rules, so this policy should not be read as a full technical data map.
Third-party services
Depending on how you use Faith Garden, third-party service providers visible in the codebase may include Firebase, Google Sign-In, Apple Sign-In, RevenueCat, AppsFlyer, Expo notification infrastructure, Apple App Store services, Google Play services, Meta Ads, and TikTok Ads.
These providers may process information under their own privacy terms when they act as independent platforms or service providers. Faith Garden’s use of their SDKs or services does not replace their own privacy notices.
Data retention
This repository does not expose the app’s backend storage systems or a full retention schedule for app data.
Support emails and account-related correspondence may be retained for as long as needed to respond, keep records, comply with legal obligations, resolve disputes, or enforce the service terms. Attribution, analytics, and campaign-measurement retention may also depend on configured third-party provider settings such as Firebase Analytics, AppsFlyer, Apple, Google, Meta, or TikTok.
If more specific backend retention details or provider-specific retention settings are published later, this page should be updated.
Security and access controls
The app code shows use of platform authentication, biometric protection messaging, and account-based access flows intended to help protect private areas of the app.
No public statement on this website should be read as a guarantee of perfect security, encryption scope, zero-knowledge architecture, or breach prevention unless those claims are separately documented and verified.
User rights
Depending on your location, you may have rights to request access to, correction of, or deletion of personal information associated with your use of Faith Garden.
To make a privacy-related request, contact support@faithgarden.online and include enough information for the team to identify your account or prior communication.
Children’s privacy
The App Store listing rates Faith Garden 16+ and notes that the app may include messaging and chat, user-generated content, and health or wellness topics.
Faith Garden is not directed to children under 13. If you believe information from a child has been submitted in error, contact support so the team can review the request.
Contact information
For privacy questions or data requests, contact support@faithgarden.online.
If you need help with account deletion, support, billing questions, or app access, the support and account-deletion pages on this website may also help point you to the right next step.