Privacy Policy

3.1 Account and profile data (registration/login)

When you register or log in via email/password, Apple, or Google, we process in particular:

• email address (for Apple, possibly a relay address)
• display name (chosen by you; sometimes provided by Apple/Google)
• profile picture (optional)
• user ID, createdAt
• time zone (from device/region settings; used for correct day/week logic)

Authentication is handled via Firebase Authentication.

3.2 App functionality data (groups/habits/streaks)

To provide core app functionality, we process data such as:

• group and membership data (e.g., groupId, joinedAt, role such as admin/member)
• posting/habit rules (interval, weekdays, post mode)
• streak and activity/statistics data (e.g., streak, lastPost, nextPost, postsThisWeek, weeklyPostCount, weekStart)

3.3 Posts / content

CoThrive allows posts as images within groups/journals. We process:

• the image (stored in Cloud Storage)
• metadata in the post record (Firestore), e.g. createdAt, groupId, userId, and possibly username, userProfilePic, streakAtPostTime

Visibility: within a group, group members can typically see your display name, profile picture, streak, the post image, and the post time.

Image metadata (e.g., location/EXIF): Images are converted into an optimized format and metadata (e.g., EXIF) is removed. CoThrive does not store location data as a dedicated post field.

3.4 Push notifications (reminders / optional marketing)

We use Firebase Cloud Messaging (FCM) for push notifications. We process:

• one or more FCM push tokens (e.g., multiple devices or token rotation)
• user-related status/settings data (e.g., whether reminders are enabled)

3.5 In-app notifications

CoThrive may store and display notifications inside the app (e.g., group-related events). This typically includes:

• linkage to your userId, title/body, timestamp, read/unread
• optional context fields (e.g., group reference or a reason/description where needed)

3.6 Moderation, admin actions, reports, removals (“kicks”)

Group creators and assigned admins can remove members (“kick”) or delete posts. For accountability and abuse prevention, we may process:

• who performed which action and when (admin/audit context)
• a reason/description entered by an admin (generally not visible to regular users)

If a reporting feature is used, reports may contain:

• a reason/description
• identifiers and context about the reported content (e.g., post ID, userId, timestamp)
• relevant metadata/references needed for moderation

3.7 Blocking feature

If users block other users, we store a block list (e.g., blocked user IDs, possibly display-related information). Purpose: to hide/prevent interactions.

3.8 Export features (images/ZIP, sharing)

Users can export their own content (e.g., save images locally or bundle them into a ZIP, potentially as a premium feature). This may involve:

• local processing on the device (download, bundling)
• sharing via the operating system’s share sheet to third-party apps/services chosen by the user

Once a user shares content with third parties, further processing is handled under the responsibility of that third party.

3.9 Local storage on the device (cache/offline)

For performance and offline capability, certain data may be stored locally on your device, in particular:

• Firestore offline persistence/cache
• local app settings/flags (e.g., onboarding status, timestamps, configuration/cache values)

Users can usually remove such local data via OS functions (e.g., “clear app data”) or by reinstalling the app.

3.10 App permissions

Depending on how you use CoThrive, the app may request permissions such as:

• camera (to capture a post)
• photos/media (to choose an image)
• notifications (push reminders)
• optionally storage/saving (export to gallery/files, depending on platform)

Permissions can be revoked at any time in your device settings.

3.11 Analytics, crash reports, remote config, security/diagnostic data

We use, among others:

• Firebase Analytics (usage analytics, e.g., for product improvement and feature measurement; events may include login/sign-up methods, group/post actions, and error situations)
• Firebase Crashlytics (crash/error diagnostics for stability)
• Firebase Remote Config (delivery of configuration/feature flags, e.g., maintenance mode or links)
• Firebase App Check (integrity/abuse protection; depending on platform via appropriate integrity mechanisms)

Depending on the service, we may process:

• app interactions/events
• technical identifiers (e.g., app instance IDs), device/system information
• crash diagnostics (e.g., stack traces)
• integrity/security signals for abuse detection (App Check)

4.1 Performance of a contract (Art. 6(1)(b) GDPR)

For:

• account creation, login, account management
• groups/journals, posting, streak/leaderboard calculations
• in-app notifications, blocking feature
• export features (provision)
• enabling premium/subscriptions (technical processing)

4.2 Consent (Art. 6(1)(a) GDPR)

For:

• push notifications (OS permission + in-app toggle)
• optional marketing (separately enabled)

4.3 Legitimate interests (Art. 6(1)(f) GDPR)

For:

• IT security, abuse prevention, infrastructure protection (App Check, rules, logs)
• stability and troubleshooting (Crashlytics)
• enforcing group rules and investigating abuse (moderation/reports)
• analytics for product improvement (Firebase Analytics), where consent is not required or where processing is otherwise lawful in context

5.1 Google Firebase (Google LLC)

Firebase Auth, Firestore, Cloud Storage, Cloud Functions, FCM, Analytics, Crashlytics, Remote Config, App Check.

5.2 RevenueCat

For subscriptions/premium features (e.g., subscription status/entitlements, product/receipt information, linkage to an app user ID, technical diagnostics for processing).

5.3 Apple / Google (in-app purchases)

Payments and subscription management are handled via the respective store:

• Apple App Store / In-App Purchases
• Google Play / Google Play Billing

We typically do not receive payment details (e.g., credit card numbers), but receive purchase/subscription status and/or receipt information. Subscriptions can generally be managed and cancelled in the respective store settings.

5.4 Website hosting (Vercel)

The website is hosted by Vercel. When you access the website, technically necessary data is processed (e.g., IP address, date/time, requested page, user agent) to provide and secure the website.