Privacy Policy

1. How HabitStride works

HabitStride lets you create habits, track completions, use timers, schedule local reminders, join challenges, view progress, export and restore local backups, and use optional health integrations where supported.

Habit titles, descriptions, notes, and reminder messages are user-generated content. Avoid entering information you do not want stored on your device or included in a local export file.

2. Data stored on your device

If you use HabitStride, the app may store on your device:

• habit titles, descriptions, notes, categories, icons, schedules, reminder settings, and reminder messages;
• completion history, skipped days, streaks, timers, counts, and goals;
• challenge progress, badges, points, and app preferences;
• local diagnostic journal entries and local telemetry-like events used inside the app.

This data is stored locally on your device. Separately, the usage and purchase information described below is transmitted to Google Analytics for Firebase, RevenueCat, and the relevant store. Operating system backup settings may also affect copies of app data; those backups are separate from HabitStride cloud features.

3. Optional health data

With your permission, HabitStride may read from Apple Health on iOS and Health Connect on Android, where supported:

• step counts;
• sleep data;
• workout data, including related distance and calories on Android where available;

Health data is used to update relevant habits. Health permissions are optional. If you do not grant permission, health sync features will not work, but manual tracking remains available where supported.

Health-derived habit results may be stored locally and may be included in local backup files you export. Health measurements and locally derived results are not included in app events sent to Firebase Analytics or purchase data sent to RevenueCat. Analytics may report the Health feature category and events about permission requests and sync attempts, as described in section 6. We do not use Health measurements for advertising, marketing, or sale to third parties.

You can manage or revoke access in Apple Health or Health Connect settings. Revoking access does not delete results already saved in HabitStride or exported files.

4. Purchases and subscriptions

HabitStride uses RevenueCat to validate purchases and manage subscriptions and Premium entitlements. RevenueCat receives an SDK-generated app user identifier, receipts or purchase tokens, and product, transaction, and subscription status information. This is used for purchase validation, restoration, enabling Premium, and subscription reporting.

Apple App Store on iOS and Google Play on Android process payments and billing details through your store account. HabitStride receives purchase and entitlement information without processing your payment card details. Restoration uses the store and account used for the purchase; it does not restore habits or local history.

Details about purchase data processing are available in RevenueCat's Apple App Privacy and Google Play Data Safety documentation.

5. Notifications

HabitStride uses local notifications. It does not use push notifications and does not collect push notification tokens. Local notification content may include habit-related text on your device.

Google Play developer notifications communicate purchase and subscription events between Google's servers and subscription management services such as RevenueCat. They are separate from local user reminders and are not push notifications sent by HabitStride to your device.

6. Analytics and diagnostics

HabitStride uses Google Analytics for Firebase on iOS and Android to understand app usage and improve the app. The app sends events about onboarding, screens viewed, habit creation and completion, calendar, insights, and paywall use. Parameters include general habit and tracking categories, schedule type, whether a reminder is enabled, and the number of active habits. Purchase events may include the plan, store, transaction identifier, value, and currency.

Health feature events include the feature type (steps, sleep, or workout), permission-request context and result, and sync attempts. On iOS, completing a permission request does not prove that read access was granted. App events do not include habit titles, descriptions, notes, reminder messages, habit identifiers, raw Health measurements, or Health sample timestamps.

Separately from these events, the SDK automatically collects an app-instance identifier, events such as first opening, sessions and engagement, device and operating system information, app version and language, and purchase events where supported. Google derives coarse location from masked IP addresses. On iOS, the SDK may collect the device's identifier for vendor (IDFV); on Android, it may collect the advertising identifier when available. Advertising identifier collection depends on the platform, permissions, and SDK configuration. Using SDK identifiers does not make these data anonymous.

SDK collection details are available in Google's documentation for iOS and Android. HabitStride separately keeps local diagnostic journals and events used inside the app.

7. Local backups and sharing

HabitStride includes a local JSON export feature. Exports can include habit state, gamification state, event logs, install date, health-derived habit results, and other backup data. If you share an export file, the chosen share destination is outside HabitStride's control.

8. Why we use data

We use data to:

• provide habit tracking, reminders, progress, local backup/restore, and Premium features;
• restore purchases and manage entitlement status;
• understand app usage and improve app features;
• respond to support and privacy requests;
• maintain app reliability, security, and legal compliance.

9. Service providers

Depending on the features you use, data may be processed by:

• RevenueCat for subscription and entitlement processing;
• Google Analytics for Firebase for app analytics;
• Apple App Store and Google Play for billing and subscriptions;
• Apple Health on iOS and Health Connect on Android, when you grant permissions;
• your chosen share target if you export or share a backup file.

We do not sell personal data.

10. Reset, deletion, and retention

You can reset local HabitStride data in the app where the feature is available. Resetting does not necessarily delete every copy: automatic local backups, exported files, and operating system backup copies may remain. Deleting the app may remove local data depending on the operating system. Revoking permissions or deleting HabitStride does not delete source data in Apple Health or Health Connect.

Resetting or deleting the app does not automatically delete information already sent to Firebase, RevenueCat, or the stores, and does not cancel Apple App Store or Google Play subscriptions. Cancel separately in the Apple or Google Play account used for the purchase. Exported files and shared copies must be managed separately.

Local data, provider records, and support correspondence are managed separately. For requests about deletion or retention of data processed outside your device, contact contact@coreorbit.eu.

11. Your rights

Depending on your location, you may have rights to access, correct, delete, restrict, or export your personal data, object to certain processing, withdraw consent, and lodge a complaint with a data protection authority.

To exercise rights, contact contact@coreorbit.eu. We may need information to verify your identity before acting on a request.

12. Children

HabitStride is intended for users who are at least 16 years old. If you believe a child under 16 has provided personal data, contact us.

13. Changes

We may update this Privacy Policy when the app, legal requirements, or providers change. The date above will be updated when the policy changes.