Privacy
This policy describes what Helio stores, where it goes, and what it does not do. It is written from the app's actual behaviour rather than from a template, and it is meant to be read in full — it is short on purpose.
The short version.
Helio is developed and operated by an individual developer, Oleksandr Slobodianiuk. For any question about this policy, or to exercise any of the rights described below, write to alexslkmain@gmail.com.
Helio uses Firebase Authentication (Google).
Everything below lives under users/{your uid} in Google Cloud Firestore, readable and writable only by that account:
habits — the habits you create: title, optional description, whether it is an Inspire or an Exhaust, its energy value, icon and colour, schedule, and reminder settings.dailyLogs — one document per calendar day, holding what you logged that day and the day's score.notes — the free text you write on a habit for a given day.habitVotes — your "useful" / "not for me" votes on the suggested-habit catalogue.meta — your app settings (appearance, language, day structure, energy limits, display toggles) and your bookmarked suggestions.aiChatMessages, aiInsights, aiUsage — reserved for the AI assistant described in section 10. That feature is switched off in this version, so nothing is written to them. They can only ever be written by our server, never by the app on your device.When you vote on a suggested habit, the app also increments a shared, app-wide counter of likes, dislikes and additions for that suggestion. That counter is a number only — it carries no user identifier and nothing about you can be read back out of it.
Deleting the app removes all of this from the device.
The iPhone app includes Firebase Analytics. The companions — widgets, Apple Watch, Mac — contain no analytics at all.
The app itself sends exactly five events, all of them about the first-launch intro, and none of them containing anything you typed:
onboarding_page_viewed — page number and page nameonboarding_skipped — page numberonboarding_completed — how it ended (finished, skipped, or via sign-in)onboarding_sign_in_tapped — page numberonboarding_sign_in_succeededEach also carries whether the intro was the real first launch or a replay from Settings. Every parameter is a whole number or a short fixed keyword. No habit names, no notes, no free text, no personal data ever leaves the app through analytics.
Separately from those events, the Firebase Analytics SDK collects a standard set of automatic events and device properties defined by Google — for example installs, session starts, app version, device model and coarse region. That set is Google's, not ours; we neither extend nor configure it. See Firebase's own privacy documentation for what it contains.
Helio does not use the advertising identifier (IDFA), shows no App Tracking Transparency prompt, and declares no tracking in its App Store privacy manifest.
The app links Firebase Crashlytics, and crash collection is enabled at launch. When the app crashes or hits a handled error, Crashlytics records the technical detail: the stack trace, the app version, the device model and OS version, and a small set of keys we attach so a report can be located — the screen or operation involved, your user identifier, and, where relevant, the internal identifier of a habit or a date key such as 2026-08-02. Habit titles and note text are never attached.
Because Helio is run by one person, non-fatal errors are also mirrored to a private Telegram channel that only the developer reads, so problems are noticed the day they happen. What is sent there:
Habit titles, note text and daily logs are never sent to this channel.
The home screen widgets and the Apple Watch app never talk to a server. They read the shared on-device container described in section 3, and any tap you make there is handed back to the iPhone app, which records it. The Watch receives its copy from your iPhone directly, over Apple's device-to-device connection.
The Mac companion is a full client and reads and writes the same Firestore data as the iPhone, under the account you signed in with.
Habit reminders are local notifications scheduled on your device by iOS. There is no push service, no device token, and nothing about your reminders is sent anywhere.
Settings offers two rows that hand a summary of your habit data to Claude or to ChatGPT so you can talk it through with an assistant you already use. This is entirely opt-in, and it works like this:
claude.ai or chatgpt.com in your browser with the text prefilled. Nothing is submitted for you — you review it and press send.Helio sends nothing to Anthropic or OpenAI itself. The conversation happens in your own account with that service, and what happens to the text afterwards is governed by your agreement with them.
The app binary contains an AI assistant feature: a tab with insight cards about your own history and a chat that can answer questions about it. It is disabled by a server-side switch, and both of its halves default to off. While the switch is off the tab is not merely locked — it is absent, there is no way to reach it, and the server refuses every request regardless of what the app asks. In this version, no habit data is sent to Anthropic or to any AI provider by the app.
It is described here because the code paths are present and we would rather state plainly what they would do. If the feature is ever switched on, it would work like this: your request and the relevant slice of your own data — habits, logged days, and notes on the days in question — would be sent from our Cloud Function to Anthropic's API to produce an answer. It would be read-only: the assistant can look at your data but has no ability to log, change or delete anything. This policy and the App Store privacy disclosure will be updated before that switch is turned on, not after.
To tell you when a newer version is available, the app occasionally asks Apple's public App Store lookup service about its own bundle identifier. Nothing about you is included in that request.
These providers operate globally, so your data may be stored and processed outside your country, including in the United States. Traffic between the app and these services is encrypted in transit.
In the app: Settings → Account → Delete Account. If you are signed in, iOS asks you to authenticate once more to confirm it is you.
This deletes your habits, daily logs, notes, votes, bookmarks and settings, the AI documents in section 3 if any exist, and then the sign-in account itself. It is permanent and there is no backup to restore from. The app then starts again as a new anonymous user.
Two things it does not reach, because they are stored separately by Google and not filed under your habit data: analytics records and crash reports. If you want those removed as well, email us and we will delete what those tools allow. Uninstalling the app removes every local copy from that device.
Data you have not deleted is kept for as long as the account exists, because it is the app's content — a habit log from two years ago is the point of the app. Error and feedback messages in the developer channel are kept only as long as they are useful for fixing the problem.
Depending on where you live — in the European Economic Area, the United Kingdom, Switzerland, Ukraine, California and elsewhere — you have the right to ask what personal data is held about you, to obtain a copy, to have it corrected, to have it deleted, to object to or restrict its processing, and to withdraw consent you previously gave. Deletion is available immediately in the app; for anything else, write to alexslkmain@gmail.com and it will be handled. You also have the right to complain to your local data protection authority.
The legal basis for processing is the performance of the service you asked for (storing and syncing your habits), your consent where the app asks for it explicitly (notifications, "Discuss with AI"), and a legitimate interest in keeping the app working (crash and error diagnostics).
Helio is not directed at children. It does not knowingly collect personal data from children under 13, or under the higher age of consent that applies in some countries. If you believe a child has provided personal data through the app, write to us and it will be deleted.
If this policy changes, the effective date at the top of the page changes with it, and the change will be made before the behaviour it describes ships — not after.