hæl is made by KI-GEN Studios LLC. This policy describes what the app stores, where it goes, and who else handles any of it.
In short: your fasting, cycle, and weight data stays with you, on your devices, in your own iCloud account, and in Apple Health. Two outside services are involved. TelemetryDeck receives usage signals (what was used, and when; never what was written), under a pseudonymous install identifier; from hæl 5.0.1, nothing about fasting, weight, or Apple Health is sent at all, and RevenueCat verifies purchases and passes a record of each purchase to TelemetryDeck under the same identifier. Neither receives your fasting, cycle, or weight records: no durations, weights, period dates, phases, or anything from Apple Health.
what hæl stores
- Fasting history (start and end times, target and actual duration, completion)
- Body weight entries (one a day), and every weight reading behind them: each number you type, and each sample read from Apple Health
- Menstrual cycle information (last period start date, cycle length, and a history of up to 24 period start dates)
- Profile details you choose to give: birthday, height, and gender, all optional
- Rest days you mark
- Streaks, preferences, and settings, including whether to keep weight numbers out of sight
- Whether the full experience has been purchased
where it is stored
On your device. All of the above is stored in UserDefaults and in App Group shared storage (group.app.hael.fasting), which lets the widget read the same data.
In your iCloud account. If iCloud is enabled, hæl syncs your fasting history between your own devices using iCloud Key-Value Storage. Weight entries, last period start date, and cycle length sync the same way unless you connect Apple Health for them. Once you do, hæl stops copying them to iCloud, removes what it stored there, and Apple Health keeps them in sync instead. Every weight reading and the history of period start dates stay on your device only and are never copied to iCloud. This data lives in your iCloud account under Apple's terms. KI-GEN Studios LLC cannot access it. hæl does not use CloudKit or any server of its own.
Between your iPhone and Apple Watch. The current fast, streak, total fasts, suggested duration, cycle day and phase, and whether the full experience has been purchased are sent directly from your iPhone to your paired Apple Watch using Apple's WatchConnectivity framework.
apple health (healthkit)
hæl uses HealthKit only with your permission, granted through the standard iOS prompt. You can change these permissions at any time in Settings > Health > Data Access & Devices.
hæl reads:
- Menstrual flow, to determine your cycle phase
- Body mass, to show weight trends in the body ledger
- Resting heart rate, for context in the weekly letter
hæl writes:
- Menstrual flow, when you record a period start in hæl
- Body mass, when you log a weight in hæl
When you connect Apple Health, hæl also writes the period starts and weights you already recorded in hæl, but only where Apple Health does not already hold one, so nothing is duplicated.
hæl also writes these, when "record fasts" is on:
- Workouts, recording a completed fast as a mind and body session
- Dietary energy, a zero-calorie entry marking a completed fasting window
From hæl 4.2, fasts are recorded in Apple Health only if you turn on "record fasts" in Settings > Apple Health. It is off by default. Earlier versions record every completed fast once Apple Health access is granted.
When you edit or delete a weight or a past fast in hæl, or correct a period date, hæl replaces or removes the entry it wrote to Apple Health instead of leaving the old one. Entries written by other apps are never changed.
HealthKit data is never sent to KI-GEN Studios LLC, TelemetryDeck, RevenueCat, or anyone else, and it is never used for advertising or marketing.
analytics (telemetrydeck)
hæl uses TelemetryDeck to understand how the app is used, so it can be made easier to use and worth keeping. It sends events, each with the time it happened. An event says that something happened, never its contents: not how long a fast was, what a weight was, which phase of the cycle, or anything from Apple Health.
Events about using the app (a session started, a page or letter was opened, a purchase page was shown, something was shared) are sent under the install's pseudonymous identifier, so they can be counted per install. From hæl 5.0.1, events about fasting, weight, or Apple Health (that a fast began, was completed, ended early, was abandoned, edited, or set for later; that a rest day or a weight was recorded; that Apple Health was connected; that the cycle's prediction was opened) are not sent at all: the app counts them on the phone, for its own pages, and they stay there. Before 5.0.1 they were sent as events, with their time and no contents, under the install's identifier. Some events carry a few details:
- days since the app was last opened
- consecutive-day open streak
- whether the full experience has been purchased
- for a share, which app it was shared to (for example, Messages)
- when the free fourteen days begin, which page they were taken from: the last page of onboarding, or the page shown once after an update (from hæl 4.5); from hæl 4.5.1, also the purchase page, or the same page shown again a week later
- when that page is shown, whether it is the first showing or the second (from hæl 4.5.1)
- which pages of the first-run introduction were reached, by name, once each (from hæl 4.5.1)
- when the free fourteen days don't begin, which page they were tried from, and whether Apple's purchase sheet was closed or the purchase failed; for a failure, Apple's or RevenueCat's error number, never the error's message (from hæl 4.5.1)
- when hæl asks whether it may send notes, that the question was shown, and whether notes were allowed, refused, or put off for later (from hæl 4.5.3)
- from the fifth edition of hæl (5.0): that the letters were opened; which kind of Monday letter was opened (the full letter, the first letter given whole, or the shorter letter); and, for the card that shares the hour of a fast, that it was opened or shared, and whether it was offered after a screenshot or when the fast came full circle. hæl learns that a screenshot was taken only from iOS's notice, never reads the screenshot, and sends no hours or names with these events
- from the fifth edition of hæl (5.0), the purchase page can also be the one shown after the first fast of twelve hours or more, or the morning before the fourteen days close
- from hæl 5.0.1: each time a purchase page is shown, which page it was (the last page of onboarding, the purchase page, the letter at the end of the fourteen days, the morning before they close, the page in settings that offers the one-time purchase, or the page after the first fast of twelve hours or more), so we can see which pages lead to the full experience
TelemetryDeck also receives purchase events for hæl from RevenueCat (see below): for example, that the full experience was bought, restored, transferred, or refunded, and from the fifth edition of hæl (5.0) that a subscription or its free trial started, renewed, was cancelled, or ended. Each event carries the product, its price and currency, the App Store country, Apple's transaction ID, RevenueCat's random app user ID, and whether the device has been asked for tracking permission (hæl never asks). These arrive under the same hashed identifier as the usage signals, so we can see how many people who use the app go on to buy it. They are sent by RevenueCat's servers, not by the app.
TelemetryDeck identifies an install only by a pseudonymous identifier: a one-way hash of the identifier iOS gives this app on this device. It is the same across sessions, so events from one install can be counted together, but it is not your name, email, or Apple Account, and it is not shared with advertisers. TelemetryDeck processes these signals on our behalf, as a service provider, only to measure how hæl is used; it does not receive the durations of fasts, weights, cycle information, or any Apple Health data. See telemetrydeck.com/privacy.
purchases (apple and revenuecat)
From the fifth edition of hæl (5.0) the full experience is a yearly or monthly subscription, or a one-time purchase offered in settings; earlier versions sold it as a one-time purchase only. Either way it is bought through Apple. hæl never sees or stores your payment information.
hæl uses RevenueCat to verify purchases and restore them across devices. RevenueCat receives:
- a random app user ID that RevenueCat generates, not linked to your name, email, or Apple ID
- your purchase and transaction history for hæl
- Apple's identifier for vendor, a device ID that is specific to apps from KI-GEN Studios LLC and cannot be used to track you across other companies' apps
- technical details: device model, operating system version, app version, App Store country, and preferred language
- TelemetryDeck's hashed identifier for this install and hæl's TelemetryDeck app ID, so RevenueCat can pass purchase events to TelemetryDeck (see Analytics above)
- when hæl's purchase page is shown: the time, a session ID, and which offer was on it, under the same random app user ID, so we can see how often the page is seen against how often the full experience is bought (from hæl 4.4.1); from hæl 4.5, also which page it was (onboarding's last page, the page shown once after an update, the purchase page, or the letter at the end of the fourteen days); from hæl 4.5.1, also that page shown again a week later; from the fifth edition of hæl (5.0), also the page shown after the first fast of twelve hours or more, the morning before the fourteen days close, and the page in settings that offers the one-time purchase
- if you take the free fourteen days: that free purchase, and which page you took it from (onboarding or the page shown once after an update), as a label on the same random app user ID (from hæl 4.5); from hæl 4.5.1 the page can also be the purchase page or the page shown again a week later, and a second label holds the day the fourteen days began. From the fifth edition of hæl (5.0) the fourteen days are the yearly subscription's free trial, and the same labels hold the page it began from (which can also be the page after the first fast of twelve hours or more) and the day it began
hæl also checks your purchase on the device itself, by asking Apple's StoreKit whether this Apple ID owns the full experience. That check makes no network request. Once after updating to hæl 4.3, and again if the device holds a purchase RevenueCat has no record of (for example one made before hæl used RevenueCat), hæl asks Apple to send the device's App Store transactions for hæl to RevenueCat, so a purchase can be verified and restored. Settings shows RevenueCat's random app user ID as a support ID, so you can include it if you write to us about a purchase. It is not sent anywhere by showing it.
hæl never gives RevenueCat your name, email, or any other personal detail. RevenueCat uses this data only to verify purchases for hæl and to pass purchase events to TelemetryDeck as described above. It does not receive your fasting, cycle, or weight records, or any Apple Health data. See revenuecat.com/privacy.
support links
Settings links to eating disorder support. To choose the right one, hæl reads the region set on your device, on the device: in the United States and its territories, the link calls the National Alliance for Eating Disorders helpline; elsewhere, it opens findahelpline.com in Safari to find a helpline in your country. hæl sends nothing to either. What happens after you call or open the site is governed by that organization's own privacy policy.
notifications
If you turn on notifications, hæl schedules them on the device. No notification tokens are sent to any server.
siri and shortcuts
hæl offers Siri Shortcuts to begin a fast and check its progress. Siri and Shortcuts requests are handled by Apple under Apple's privacy policy. hæl does not receive that data.
what hæl does not do
- No accounts or logins
- No advertising and no advertising identifiers
- No tracking across other apps or websites
- No selling or sharing of personal data
exporting your data
You can export your fasting history as a CSV file, or a backup of your records as a JSON file, from Settings. The file is created on your device and goes only where you choose to send it.
deleting your data
In the app: Settings > delete all data. This erases your fasting history, cycle data and period history, weight entries and readings, profile details, and preferences from the device and from iCloud Key-Value Storage. It also deletes the weight, workout, and dietary energy entries hæl wrote to Apple Health. Period starts recorded in Apple Health are kept, because they may be part of your wider cycle history. You can remove them in the Health app. Health data written by other apps is never affected.
By deleting the app: this removes on-device data. Data synced to iCloud Key-Value Storage may remain in your iCloud account, so use "delete all data" first if you want it removed everywhere.
Purchase records: Apple and RevenueCat keep purchase records so you can restore your purchase. To request deletion of your RevenueCat record, email hello@hael.app with the Apple order ID from your purchase receipt.
consumer health data
Residents of Washington, Nevada, Connecticut, and other states with consumer health data laws can read the Consumer Health Data Privacy Policy at hael.app/consumer-health-data.
children
hæl is not directed at children under 13 and does not knowingly collect data from children.
changes to this policy
If this policy changes, the updated version will be published at this URL with a revised date.
contact
Questions about this policy or requests about your data: hello@hael.app