1. Who this policy covers
Habit Protector is a mindful app-blocking application for Android, Android TV, iPhone, iPad, and Mac, provided by the operator identified on your app-store listing (Vitality Trails on Google Play). This Privacy Policy applies to the Habit Protector app, its optional account-sync features, and this website.
Habit Protector is designed for adults and is not directed to anyone under 18. We do not knowingly collect personal information from children.
2. Information processed on your device
You can use Habit Protector without creating an account. The app keeps the information needed for your local protection plan on your device, including:
- the apps you select for protection;
- rule schedules, limits, challenges, and challenge settings;
- local progress and protected-app usage summaries; and
- the identifier of the foreground app needed to enforce a rule.
Installed-app names and native package or application identifiers stay on the device. Optional account sync can send opaque selection references, rule settings, and aggregate usage and progress as described below; it does not upload your installed-app catalog.
Free-plan allowances may be updated through Firebase Remote Config. Validated values are cached for offline use and applied at the next app session. A first-use date stored locally can determine which free-history policy applies to this installation; it is not sent as an analytics event or used to create a cloud account. History limits do not delete stored history.
Android Accessibility Service
Habit Protector uses Android's Accessibility Service only to identify when a protected app is in the foreground and to present the relevant protection challenge. It reads application identifiers from window events or window metadata for local rule matching, not messages, passwords, typed text, or page text. It does not record the screen or perform touch gestures on your behalf. On Android TV, the optional whole-screen protection mode can show a branded gate over apps, Home, and Settings, handle remote-control keys, return to Home, and send media-control commands to enforce the session you configured.
Usage Access measures protected-app time for your limits. Foreground services and ongoing notifications keep user-started protection, movement tracking, and habit timers running; optional audio guidance can continue while a habit is active. Exact alarms apply your scheduled protection boundaries. These accesses support the features you choose. Accessibility can be disabled in Android settings at any time. Optional Android TV guest credentials and guest-session state stay on that TV, and guest viewing is excluded from the owner's progress.
Apple Screen Time and Mac protection
On iPhone and iPad, Screen Time authorization lets the app apply your protection rules. Apple's private app-selection tokens remain in the local App Group shared with the protection extensions. Account sync uses selection references and counts, not a catalog of app names. On Mac, the app observes the foreground application to apply local rules while Habit Protector is running; it does not read window text.
Movement, Health Connect, and Apple Health
Movement habits use device motion or step activity to verify progress. When you choose the optional workout habit, the app requests read-only access to completed exercise sessions in Health Connect on Android or completed workouts in Apple Health on iPhone. On Android, it requests only the exercise-read permission, not heart rate, routes, workout write access, background health reads, or extended health history.
Exercise session identifiers, start and end times, and active duration are processed locally to check workouts within your current protection window and avoid double-counting. The Android check excludes manually entered sessions and pause or rest segments. Raw workout records are processed transiently on your device and are not uploaded to our cloud. Verified duration and habit completion are kept as habit progress. If you enable optional account sync, aggregated workout and movement progress can be sent to Firebase and associated with your account to coordinate the habits and protection you request across your devices.
On iPhone and iPad, releases with the privacy controls described here mark the app-state directories containing health-derived progress, local sync caches, and shared native state as excluded from device backups. Local records remain on the device. Other settings and history stored in those same directories are also excluded and should not be relied on for recovery through an iCloud device backup. This does not remove copies from backups made by older app versions or change the optional Firebase account sync described above.
Health and movement data are not used for advertising, sold, or shared with data brokers. You can decline workout access and use another habit, revoke exercise access in Health Connect on Android, or revoke Health and Motion & Fitness access in Apple settings. Revoking access stops future reads; it does not automatically delete previously synced progress. Use the account-deletion options below to request removal of account data. These features support general wellbeing and do not provide medical diagnosis or treatment.
3. Information collected when online features are used
Technical information and purchase-service identifiers may be processed even when you use the app without an account. Account sync is optional. Depending on the features you use, we may process:
- Technical information: app version, operating-system information, device or installation identifiers, network metadata, country or region, language and time zone used by remote configuration, security attestation results, and limited diagnostic information. The app does not request GPS or precise-location access.
- Crash reports: in releases with the Share crash reports control in Settings, sharing with Firebase Crashlytics is optional and off by default. The choice applies to this device, including guest use, and is independent of an account or subscription. If you opt in, reports include technical error types, stack traces, app version, operating system, device information and installation/session identifiers and technical foreground/background session timing generated by the SDK. Reports may include active Remote Config rollout metadata. We use these reports to find and fix failures. We do not attach your account ID, email, selected apps, rule names or habit answers. If you also enable usage statistics, reports may include recent analytics events as troubleshooting breadcrumbs. Dart error messages and context are filtered before reporting; native crash reports can contain exception details collected by the SDK. You can turn Share crash reports off in Settings at any time. The app stops submitting new reports and asks the SDK to discard pending reports. Reports already sent or in transit cannot be recalled by that switch. With sharing off, the SDK may still store crash information locally. After turning sharing on, reopen the app: startup removes old crash reports before sharing becomes active. If cleanup cannot be completed, sharing remains pending. Earlier releases without this control, including iOS build 128, enabled technical crash reporting automatically.
- Purchase information: product, entitlement, and subscription status supplied by Google Play, the Apple App Store, and RevenueCat. We do not receive your full payment-card number.
- Optional account information: your email address, a profile name if supplied by your sign-in provider, Firebase user identifier, synced rules, device records, progress, messaging token, and supported usage summaries when you create an account and enable sync.
- Support communications: information you choose to send when contacting the support channel shown on your app-store listing.
- Website data: ordinary request data such as IP address, browser type, requested page, and security logs processed by Cloudflare to deliver and protect this website.
Paywall, purchase and Android campaign measurement
In releases with this measurement, RevenueCat receives a view event when a plan is displayed, including the offering shown and available placement and experiment context. RevenueCat also processes purchase information and technical SDK data. We use these records to compare plan presentations and understand purchase conversion. They are linked to a RevenueCat customer identifier, which can be linked to your app account when you sign in.
This measurement is separate from optional Firebase usage statistics and continues when that sharing choice is off. It is not anonymous and is not used for personalized advertising or cross-company tracking. We do not include selected apps, habit answers, health records or Screen Time activity in paywall impressions. An offline SDK may send a view later; turning optional usage sharing off does not delete RevenueCat records. Contact support for access or deletion requests; store transaction records may be subject to separate retention obligations.
Android releases with campaign measurement read available campaign, source, medium, ad and keyword labels from Google Play Install Referrer. We send validated labels to RevenueCat to compare acquisition sources with purchases, including website and advertising campaigns. These labels are linked to the original RevenueCat customer for this installation, independently of optional Firebase usage sharing. We do not send click IDs, advertising identifiers or the raw referrer to RevenueCat. We store the customer binding and pending validated labels locally to prevent repeated collection or assignment to another customer. SDK acceptance completes this local record; RevenueCat may synchronize it later. The access and deletion options described here also apply to these records.
Optional usage statistics
If you select Share and continue during setup or enable optional usage statistics in Settings, Google Firebase Analytics processes a small set of product events: setup steps, opening the rule editor, creating or editing rules with their rule and schedule categories, viewing the paywall, and purchase outcomes. It also processes technical app and device details, a random app-instance identifier, approximate region derived from network information, and automatic session, engagement and purchase events. We use this information to understand which features work well and improve the app.
We do not attach selected apps, installed-app lists, rule names, exact schedules, habit answers, health or workout records, Screen Time activity, account IDs, email addresses or advertising identifiers to these events. We do not use usage statistics for advertising or cross-company tracking. The choice applies to this device and is independent of crash reporting, account sync and subscriptions. The app works fully if you decline. Account, purchase, security and sync processing remains separate. RevenueCat paywall and Android campaign measurement also remain on when you decline these optional Firebase statistics.
You can change your choice in Settings at any time. No pre-consent events are queued for later sharing. Turning sharing off stops new collection and clears pending analytics on this device. It does not recall requests already in transit or delete data already received. Analytics identifiers are reset when the SDK is attached on a new app process and when you change the sharing state; they are not tied to your account by the app.
We retain usage records only while needed to assess and improve the features described above, subject to our analytics property retention settings. Aggregated statistics may be retained longer. Deleting an app account does not automatically identify these separate analytics records. Contact support with questions or data requests; we may need information to locate records and will explain when we cannot identify them.
Website download campaign links — October 19, 2026
Links to this website may contain campaign labels describing a source, channel, campaign or creative. We carry these labels to Google Play or the App Store when you use a store link or the automatic download redirect, so we can compare campaign performance in aggregate store reports. Untagged website visits are labeled as website traffic.
With JavaScript and browser storage available, the latest campaign labels are kept in this tab’s session storage and used for up to 30 minutes from capture. They are removed when the tab session ends. This feature does not create a user identifier, set an advertising cookie, collect a browser fingerprint or send analytics events. We do not forward ad click IDs or arbitrary query parameters. Campaign labels should never contain personal information. This is separate from optional in-app usage statistics.
Apple and Google process store visits and downloads under their own privacy policies and apply their reporting thresholds. These reports do not let us identify an individual visitor from a website campaign label. Normal store links remain usable when JavaScript or browser storage is unavailable.
Launch waitlist — notice added October 8, 2026
If you request a launch notification, we store your email address, language, consent version and timestamps in Cloudflare D1. We use Cloudflare Turnstile and keyed hashes of your address and request IP to limit abuse. Cloudflare processes ordinary security request data. No confirmation email is sent at signup. Addresses are stored as unverified; format validation does not prove ownership. A sending provider will be selected before the launch announcement, and this notice will identify that provider before addresses are shared with it.
By submitting the form, you request one launch email with the available platform links. To leave before launch, contact support. We remove your raw email and retain a keyed suppression record to prevent someone else from adding it again. The launch email will include an unsubscribe option. This list is separate from app accounts and is not used for unrelated marketing.
We review the list every 90 days and remove addresses that are no longer needed for the planned launch. After the launch campaign is sent or abandoned, we close the list and remove remaining raw addresses within 30 days. Suppression records remain while the list is active. Provider delivery and security logs follow their retention settings. Contact support to request access or deletion.
4. Why we process information
We use information only as reasonably necessary to:
- provide protection rules, challenges, insights, and optional sync;
- authenticate accounts and keep them secure;
- validate purchases and manage Pro access;
- understand plan conversion and acquisition sources through RevenueCat purchase and Android campaign reporting;
- understand and improve app features when you opt in to usage statistics, and technical performance in earlier test versions;
- send service-related notifications you have enabled;
- detect fraud, abuse, or technical failures;
- respond to support and legal requests; and
- operate and protect the public website.
Depending on where you live, these activities rely on performing our agreement with you, your consent, our legitimate interests in providing and securing the service, or compliance with legal obligations.
5. Service providers
Any third party with whom we share user data is required to provide the same or equal protection of that data as stated in this privacy policy and required by the App Store Review Guidelines. We limit sharing to the purposes described here and require appropriate confidentiality, security, use limitations, and deletion safeguards through the applicable service and data-processing terms.
We use service providers that process information for the purposes described above:
- Google Firebase: Authentication, Cloud Firestore, Cloud Functions, Cloud Messaging, App Check, Installations, and Remote Config, Crashlytics for technical crash reporting, and Analytics for optional usage statistics in releases with that control and in the earlier test versions described above.
- Google Play: app distribution, purchases, subscriptions, install campaign labels, and store support.
- RevenueCat: purchase validation and subscription entitlement management, plan conversion and Android campaign reporting using a guest or account-linked app user identifier.
- Apple: App Store distribution and payments, Sign in with Apple, push notifications, and device/app attestation.
- Cloudflare: hosting, delivery, and security for this website.
These providers may process information in countries other than your own under their own privacy terms and appropriate transfer safeguards. We do not sell or rent personal information.
6. Retention
Local information remains on your device until you remove it, clear app data, or uninstall Habit Protector. Synced information is kept while your account is active and for only as long afterward as necessary for backup, security, dispute, or legal purposes.
When you delete an account in the app, our authenticated deletion flow removes the Firebase account and associated synced Habit Protector data. A technical deletion receipt may remain for up to eight days so the operation can finish reliably and be audited. Apple, Google Play, and RevenueCat may retain transaction records as required for billing, fraud prevention, accounting, and law.
7. Your choices and rights
- Use the app without an account.
- Turn optional usage-statistics sharing on or off in Settings on each device in releases that provide this control. Declining does not limit free or paid features.
- Turn optional crash-report sharing on or off in Settings on each device in releases that provide this control.
- Choose which apps and schedules are included in each local rule.
- Disable Accessibility access or notifications in Android settings.
- Revoke exercise access in Health Connect on Android.
- Revoke Screen Time, Health, motion, or notification permissions in Apple settings.
- Quit the Mac app or disable its optional Start at Login setting.
- Turn off optional account sync and sign out.
- Delete your account from Settings → Account sync → Delete account.
Depending on your location, you may also have rights to access, correct, delete, restrict, or receive a copy of personal information, and to object to or withdraw consent for certain processing. To make a request without access to the app, email [email protected] or follow the account-deletion instructions. We may need to verify that you control the account before acting on a request.
8. Security
We use reasonable technical and organizational safeguards, including authenticated access controls and encrypted network transport. No system can be guaranteed completely secure, so protect your device, Apple or Google account, and sign-in credentials.
9. Changes to this policy
We may update this policy as Habit Protector or applicable requirements change. We will publish the updated version here and revise the effective date. If a change is material, we may provide an additional in-app or store notice when appropriate.
10. Contact
For privacy questions or requests, contact Habit Protector support at [email protected].