Effective date: September 28, 2026
Christian75 is provided by Slade Holdings LLC. This policy explains the information used by the app, the optional Together feature, purchases, analytics, and advertising attribution.
You do not need to create an account to use Christian75. We do not ask for your payment-card number, phone contacts, or location inside the app. If you choose Together, you provide a display name and the app creates an identifier for your participation. If you email support, we receive the address and message you send.
Your challenge history, settings, reminders, onboarding choices, and written study notes, prayer notes, reflections, and gratitude entries are stored in the app's local database. The app uses onboarding choices to personalize your plan. Raw onboarding answers and personal journal text are not included in the app's production analytics events or Together payloads.
Local data remains on your device until it is removed. Deleting the app may delete that data. Device backups and restores are controlled separately by Apple and your device settings.
Christian75 offers a weekly subscription and a lifetime unlock through Apple's in-app purchase system. Apple processes payments. RevenueCat retrieves product options, validates purchase status, restores purchases, and determines access to paid features.
Purchase records can include an app-user identifier, product, transaction, subscription status, and technical information associated with the purchase. The app associates its installation analytics identifier with RevenueCat so purchase events can be measured in PostHog. Christian75 does not receive or store your payment-card number. You can manage subscriptions through your Apple account.
We use PostHog to understand app usage and identify problems with onboarding, purchases, and daily practice flows. The app generates an installation identifier and sends selected events, such as opening the app, completing onboarding, viewing the purchase screen, restoring access, and completing a challenge day. Events may include the plan identifier, day number, number of scheduled practices, purchase product, and technical app/device information.
The app disables PostHog session replay, automatic screen capture, and automatic element-interaction capture. These analytics do not contain your personal journal text or raw onboarding answers.
If you create or join a Together challenge, shared challenge information is sent to Supabase so participants can stay in sync. This includes the challenge title, dates and rules, practice definitions, display names, participant identifiers, completion states, and timestamps. Shared progress can include fitness-practice checkmarks when those practices are part of the plan. Custom practice names and details in a shared plan are also visible to the group.
Keep invite codes private. People who possess a code can access the shared challenge. Together does not require an authenticated account, and participant names and identifiers are not verified identities. Share only information you are comfortable making available to people who have the code.
Disconnecting as a participant removes your participation and shared completions from the active group. If the owner disconnects, the active shared group is deleted for everyone. These actions do not erase local challenge history or copies another participant has already saved. Deleting the app alone does not send a server-side disconnect request.
Christian75 uses the TikTok App Events SDK to measure advertising performance. The app initializes that SDK and sends its configured attribution events only after you grant Apple's App Tracking Transparency permission. Events can include app activity and purchase-screen or checkout activity, along with advertising and technical identifiers available to the SDK. Raw onboarding answers and personal journal text are not sent to TikTok.
Declining tracking permission does not prevent you from using Christian75. You can change the permission in iOS Settings. This permission controls advertising tracking; it does not disable the separate PostHog product analytics or services used to validate and restore purchases.