Privacy Policy
Last updated: July 16, 2026
Summary
D's fresh Habit Tracker ("Habit Tracker") is designed as a local-first app. It does not require an account and does not contain advertising, analytics, tracking, third-party crash reporting, or other third-party SDKs. Habit Tracker does not send your app data to a server operated by the developer.
Information Handled By The App
Depending on how you use it, Habit Tracker can handle habit and routine templates; categories; metric definitions and goals; schedules, reminders, and milestones; dated entries and exact values; notes; progress; settings; and Health sync status.
If you use accountability features, local records can also include a partner name, contact hint, sharing preference, and message template. If you attach a Photos item, the app stores its Apple Photos asset identifier. If you write a value to Apple Health, the app stores the resulting HealthKit object identifier so it can associate that sample with the app entry.
These records are stored in the app's private container on your device. Habit Tracker does not use CloudKit, and its app data stores are excluded from device backup.
Data Collection And Tracking
- Habit Tracker has no developer-operated account or server.
- Habit Tracker has no ads, analytics, tracking, or third-party crash-reporting service.
- Habit Tracker does not share app data with advertising or analytics partners.
- Under Apple's App Privacy definition, the developer does not collect data because app data is not transmitted off the device to the developer or another third party.
Apple system features and any app or service you select when sharing are governed by their own terms and privacy practices.
Apple Health
Apple Health integration is optional and write-only. Habit Tracker can request permission to write exactly three kinds of data: body mass, dietary water, and dietary caffeine. It does not request permission to read Health data.
A supported value is eligible for writing only when you confirm that it is exact and choose to allow the Health write. Habit Tracker stores the object identifier returned by HealthKit so it can associate, update, or delete the sample when you edit or delete the corresponding app entry. Apple Health data is stored and managed by Apple Health, not in the Habit Tracker database.
Photos
When you choose a food photo, Habit Tracker stores a reference to the selected item in your Apple Photos library rather than copying the image into its database. The app uses Apple's Photos framework to request a thumbnail when it needs to show that reference. If the selected item is stored in iCloud Photos and is not currently available on the device, Apple Photos may retrieve it from iCloud. Habit Tracker does not upload the photo to a developer-operated server.
Removing a photo reference or deleting Habit Tracker data does not delete the original item from your Photos library.
Local Notifications
If you enable reminders, Habit Tracker schedules local notifications with iOS. No developer server is used to send them. Notification text may be visible on your lock screen or other connected Apple devices according to your system notification settings.
App Lock
If you enable App Lock, Habit Tracker asks iOS to verify the device owner using Face ID, Touch ID, or the device passcode as available. The app receives only the authentication result; it does not receive or store biometric data or your device passcode.
App Lock is an access gate inside the app. It is not separate encryption for the Habit Tracker database or exported files. Keep your device passcode secure.
JSON Export And Sharing
When you choose to export, Habit Tracker creates a readable JSON file. The export can include templates, metric definitions, schedules and reminder rules, milestones, accountability details, entries, dates, values, notes, Apple Photos asset identifiers, Health sync status and object identifiers, reminder history, and settings represented in those records. If you have training records from an earlier beta, they can also be preserved in the export for upgrade safety.
The export is prepared in temporary, backup-excluded storage. It leaves the app only when you select a destination through the iOS share sheet. The selected app, service, person, or storage location then controls the shared copy. Keep exported files private because they may contain sensitive health-adjacent records, notes, names, and contact hints.
Deleting Data
The in-app Delete app data from this device action clears Habit Tracker's local records, settings, generated exports, photo references, and scheduled app notifications.
This action does not delete samples already written to Apple Health, originals in your Photos library, or export copies and messages that you previously shared outside the app. You can manage Health samples in Apple Health and must delete external copies at their destination.
Training Pack In Version 1.0
Habit Tracker 1.0 does not offer, sell, restore, or process purchases for the Training Pack. Existing training records from an earlier beta are retained locally and included in JSON exports so an upgrade does not discard them.
Security
Habit Tracker relies on the iOS app sandbox and Apple system protections. No storage method is risk-free, so keep your device and operating system protected and up to date. Treat shared JSON exports as sensitive readable files.
Changes
This policy will be updated when Habit Tracker's data handling changes. The date above identifies the current version.
Contact
For privacy questions or help, use the Habit Tracker support page. Do not include health logs, photos, JSON exports, accountability details, or other private information in a public support request.