Data you create
Your topic definitions, event times, optional notes, daily references, goal settings, and archived-topic state are stored in a protected local database on your iPhone and paired Apple Watch. The Home Screen widget uses the same iPhone App Group store. The database directory is excluded from iCloud Backup.
Private event notes and Journey reflection notes are limited to 500 characters and 4,096 UTF-8 bytes, whichever limit is reached first. Emberless applies this boundary to local edits, incoming paired-Watch records, and oversized notes created by an older version.
If you start a 90-day Journey, its topic, start date, fixed Journey time zone, daily responses, timer starts, completion dates, and optional reflection notes are stored locally on your iPhone. Journey progress is not sent to Apple Watch, a developer server, or iCloud.
Emberless does not use CloudKit or provide iCloud history sync. iPhone and paired Apple Watch exchange topic and event records directly through Apple's WatchConnectivity framework. Normal activation and lifecycle updates exchange only the latest topic, selection, entitlement, and reset state. Event changes use separate durable queued payloads. A full-history repair occurs only when topic-aware capability is first discovered or when you choose Sync history now in Watch Settings.
Apple Health
Apple Health is optional and is used only for the Smoking topic. If you grant access, Emberless queries heart rate, resting heart rate, heart-rate variability, respiratory rate, and oxygen saturation to show nearby context for logged Smoking events.
Emberless does not write to HealthKit and does not persist, upload, sell, or share HealthKit data. Health values remain in memory only while you use the relevant Smoking feature. They are not shown for other topics, placed in notifications, exported to CSV, used for rewards or comparisons, or used to decide whether Emberless Pro is available.
Notifications
Optional Smoking pace messages are calculated on device from your Smoking logs and chosen daily reference. They do not include Apple Health values or data from another topic.
Emberless Pro can schedule a neutral, repeating local reminder time for an individual topic. These reminders are generated by the operating system from the time you choose; they are not remote marketing messages or health predictions.
Journey Path XP, Rhythm, badges, and day availability are calculated on device. Event totals, Apple Health values, purchases, and notification interactions never contribute to Journey rewards.
Emberless Pro purchases
Emberless Pro is an optional one-time, non-consumable in-app purchase handled by Apple. Emberless reads Apple's signed StoreKit transaction status only to determine whether Pro features are available. The developer does not receive your App Store password, payment-card information, or Apple Account credentials.
Purchase and restore actions do not change your tracking data. A derived Pro-access status is sent from iPhone to the paired Watch so the Watch can apply the same topic-writing limit. Price, transaction details, and Apple Account information are not sent to the Watch.
If Pro is revoked or temporarily cannot be verified, your topics, settings, and event history are not deleted. Existing data remains readable. The free writing limit may make active topics after the first three view-only until Pro is restored or you change your active set.
Your controls
You can edit or delete individual events, archive and restore topics, remove a completed Journey day's progress, or restart one topic's Journey without deleting event history.
Deleting an event immediately removes its original time, topic, source, and note from Emberless storage. A redacted synchronization marker keeps only what paired-device conflict resolution needs, so an old offline copy cannot restore the deleted entry.
After confirmation, Delete all Emberless data redacts every event and advances an iPhone-owned reset generation. The paired Watch adopts the newer generation and removes older local events; the iPhone rejects payloads from an older generation. A generation-unaware older Watch app must be updated before event sync can resume after a reset.
Every active use of event data—history and counts, analytics, notification rules, widget, Watch, and CSV—filters to the device's current reset generation. A log started while a reset is crossing process boundaries is saved only if the generation remains current; otherwise Emberless removes the attempted record and asks you to log it again.
Delete all also removes Journey progress and pattern definitions, restores default Smoking settings, clears in-memory Apple Health context, disables supportive notifications, clears notification state, and removes all pending and delivered Emberless notifications. It does not revoke system Health permission or cancel an App Store purchase. You can change Health permission in system Settings and use Restore Purchases on iPhone.
Medical disclaimer
Emberless is for self-tracking and general wellness. It is not a medical device and does not diagnose, prevent, monitor, or treat disease. Apple Health readings may be delayed, incomplete, or measured at a different time. Patterns shown are associations and do not prove that Smoking caused a change. For medical concerns, contact a qualified healthcare professional. For urgent symptoms, contact local emergency services.
Contact
Developer and data controller: ASIM CAN ALKAN
Privacy information and self-service help are available through the official Emberless Support page. This policy will be updated when an additional monitored contact channel is introduced.