Privacy
How Dominion handles your information.
Last updated September 13, 2026. This page explains the data used to run the app and the choices available to you.
Information we use
Dominion stores account and profile details, challenge participation, daily check-ins, points, badges, rewards, private-group membership, subscription status, and the settings needed to operate your account.
Your private journal entries are available only to your account. Group information is visible only to members of that group. If you deliberately create a public progress share, the link shows the limited progress summary described before you share it; it does not include your journal, email, exact activity dates, or group details.
If you add a profile picture, Dominion stores the prepared thumbnail, not the original image selected on your device. Payment card details are handled by Stripe and are not stored in Dominion's database.
If you request early access, we store your name, email, request time, and request status so the Dominion team can review it and contact you about access. A signed-in request may also be connected to your verified account ID. Submitting a request does not create an account or subscription, send an invitation, or enroll you in marketing. Requests are not public, and submitting again does not create another pending request.
Why we use it
We use this information to authenticate you, provide the challenge and membership, save progress, calculate points and streaks, support private groups, process billing, prevent abuse, resolve support requests, and protect the service.
Service providers
Dominion uses Supabase for authentication, database, storage, and server functions; Stripe for checkout and subscription management; and Cloudflare for web hosting and delivery. Those providers process only the information needed for their role under their own terms and privacy commitments.
Slack and Discord group delivery is off for launch. If it is enabled later, nothing is sent until a group administrator connects a destination and each member saves explicit sharing choices. Data sent to an external service is then also covered by that service's policies.
Retention and your choices
We keep information while your account is active and as needed for billing, security, legal obligations, dispute resolution, and backup recovery. Some records may be retained in limited or de-identified form when required to protect the service or document a completed request.
Signed-in members can request a copy of their account data or request account deletion from Profile. The request page shows its current status. Canceling a subscription does not by itself delete an account.
For an early-access request, contact Support to ask about correction or deletion, including if you do not yet have an account. We retain requests for review, follow-up, and duplicate prevention; account deletion does not automatically remove a separately submitted request. The browser-local development preview stores only a hashed-email receipt and request time, not the submitted name or email, and sends no real request.
For privacy questions or to report a concern, visit Support. Also review the Terms and Cancellation and Refund Policy.