Privacy Policy
Last updated October 18, 2026. Policy version 2026-10-18.
This page explains the personal data Kingdom Habits collects, why it is collected, how it is shared, and how to make privacy requests. This policy should be reviewed by legal counsel before it is treated as final legal compliance language.
What We Collect
Account data
Name, email address, Supabase Auth identifiers, profile photo URL, onboarding status, faith statement status, zip code, church search selections, group placement details, and billing customer identifiers when applicable.
Group and activity data
Group membership, roles, invitations, disciple relationships, module progress, reflections, memorization activity, notifications, and related timestamps.
Support and communications
Support chat messages, admin replies and notes, AI support context, waitlist name/email, waitlist consent evidence, invitation emails, and transactional email delivery metadata.
Payment data
Stripe customer, checkout, subscription, and billing portal records. Kingdom Habits stores Stripe customer identifiers and subscription status, while Stripe processes payment card details.
Technical data
Authentication cookies, request metadata, error reports, rate-limit keys, device/browser metadata, and security logs needed to operate and protect the service.
Product analytics
When enabled, PostHog receives a distinct ID; for signed-in users, the Supabase user ID, role, and the IDs of their church organization and group; redacted page views and page leaves; the referring site and campaign tags (such as UTM parameters) of a visit; and named product events sent from the browser and from our servers. Events describe actions, such as that a reflection was posted or a verse was practiced. They never include the text of reflections, comments, answers, notes, messages, prayers, or support conversations, nor group placement answers, church names or locations, or gift amounts. Autocapture, session recording, performance capture, and advertising-style tracking are disabled.
Why We Use Data
We use personal data to create and secure accounts, place users in groups, run app features, provide support, process donations and billing, send transactional messages, manage waitlist invitations, prevent abuse, and meet legal or security obligations. Waitlist and launch emails require explicit opt-in. Marketing or optional communications are not pre-checked.
Cookies And Tracking
The app currently uses essential Supabase Auth cookies and local preferences needed to keep users signed in and operate the product. When analytics is enabled, PostHog uses a distinct ID and captures redacted page views, page leaves, the referring site and campaign tags of a visit, and named product events, with autocapture, session recording, performance capture, and advertising-style tracking disabled. Browser analytics requests are sent through our own domain and are not sent when the browser sends a Do Not Track signal; product events recorded by our servers when an action is saved do not depend on browser settings. When error monitoring is enabled, Sentry receives error reports from the browser and from our servers. Data collection is limited: user details, cookies, request headers and bodies, and URL query strings are not collected, and events are scrubbed of personal content such as reflections, messages, and invite links before they are sent. Sentry session replay is not used. The current codebase does not include Google Analytics, Google Tag Manager, Meta pixels, or Vercel Analytics. Optional marketing or advertising trackers must be blocked until consent is collected for users where consent is required.
Sharing And Processors
- Supabase for authentication, database, storage, realtime, and local auth cookies.
- Vercel for hosting, edge routing, deployment logs, and request metadata.
- Stripe for checkout, recurring donations, customer records, invoices, and payment processing.
- Resend for transactional email and waitlist invitation delivery.
- OpenAI for support AI tooling when users interact with support chat.
- PostHog for product analytics when analytics is enabled, with autocapture and session recording disabled. Browser analytics requests are relayed to PostHog through our own domain.
- Sentry for error monitoring in the browser and on our servers when error monitoring is enabled. Data collection is limited, events are scrubbed of personal content before they are sent, and session replay is not used.
- Google Maps and Places for optional church search in profile settings.
- Apple App Store and Google Play services if the app is distributed through mobile app stores.
Retention
Account and group records are kept while an account is active. Deleted accounts are deleted or anonymized where appropriate, while limited records may be retained for security, fraud prevention, payment, tax, support history, or legal reasons. A daily job deletes the following records automatically:
- Notifications once they expire; otherwise read notifications after 90 days and all notifications after 12 months.
- Waitlist entries 12 months after the last update to a pending or declined entry, 12 months after an invitation that was not used, or 12 months after signup completes.
- Invitation records 90 days after the invitation was used, revoked or expired.
- Support conversations, with their messages, 24 months after the last activity on a resolved conversation. Open conversations are kept.
Logs and analytics-like operational metadata follow our providers' retention settings and are removed when no longer needed.
Your Privacy Requests
Signed-in members can download a copy of their app data at any time from Settings, under Privacy, with “Download my app data”. The JSON file contains your profile and the records tied to your account: group and church memberships, module answers and notes, reflections, comments and likes, chat messages you sent (including in groups you have since left) and your reactions, memorization progress, notifications, follows, referrals, any account deletion request you made in the app, and, if your account is left out of our platform reporting totals, that fact and the reason. It leaves out your sign-in identity record, profile photo files, waitlist entries, support chat history, reactions in groups you have left, comments and likes on reflections you can no longer see, memberships in churches you have left, and data held by Stripe, PostHog, Sentry, Resend, and OpenAI; request those by email. If part of the file cannot be prepared, the file lists what is missing and how to request it. It never includes other members’ private content, invite tokens, or device tokens.
Email hello@mail.kingdomhabits.com to request access, export, correction, deletion, or withdrawal of optional consent. Account deletion requests are confirmed by email before processing.