Privacy
Privacy Policy
Helio (Energy tracker) for iPhone, Apple Watch and Mac · Effective 28 October 2026
This policy describes what Helio stores, where it goes, who processes it, and how to delete it. It is written from the app's actual behaviour rather than from a template.
The short version.
- Helio needs no account. On first launch it creates an anonymous account so your data has somewhere to live. Signing in with Apple or Google is optional.
- Your habits, daily logs, notes and AI conversations are stored under that account on Google's Firebase, and cached on your device.
- If you use the AI assistant, what you ask and the relevant part of your habit data are sent to Anthropic (Claude) to produce an answer. Voice input is sent to OpenAI to be turned into text and speech. Photos you attach are sent to Anthropic. Helio does not keep your audio or your photos.
- Subscriptions are sold and billed by Apple. Helio never sees your payment details.
- If you report a bug, the report and any screenshots you choose to attach are stored under your account and reviewed by the developer with the help of Anthropic's Claude. Screenshots are deleted 90 days after the report is reviewed.
- Helio uses Firebase Analytics and Crashlytics. There are no ads, no advertising identifier, no tracking across other companies' apps, and nothing is sold. Usage analytics can be switched off in Settings.
- You can delete your account and its data from inside the app.
1. Who is responsible
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.
2. Your account and identity
Helio uses Firebase Authentication (Google).
- By default you are anonymous. On first launch the app signs you in anonymously. That produces a random user identifier (a UID) which exists so that your data can be filed somewhere. It is not linked to your name, your email, your phone number or your Apple ID.
- Sign-in is optional and lets the same data appear on more than one device. If you choose Sign in with Apple or Sign in with Google, the provider passes an account identifier and, depending on what you allow, an email address and a name to Firebase Authentication. If you use Apple's "Hide My Email", the app only ever sees the relay address Apple generates. Helio never sees or stores your password.
- The Mac companion requires sign-in, because it talks to the server directly and an anonymous session there would create a second, empty account.
3. What Helio stores
Everything below lives under users/{your uid} in Google Cloud Firestore. The app on your device can read only its own account's data.
habits — the habits you create: title, optional description, type, 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 and your bookmarked suggestions.
aiChats, aiChatMessages — your conversations with the AI assistant (section 4). They are written only by our server.
aiInsights — the most recent set of AI insight cards generated for you.
aiUsage — monthly counters used to enforce your plan's AI limits: number of requests, tokens used, voice seconds and "Discuss with AI" uses. Counts only, no content.
entitlement — your current plan: its tier, the App Store product and transaction identifier behind it, its expiry, and whether it comes from a purchase, a promotional code, a complimentary grant or a thank-you for a confirmed bug report.
bugReports — the bug reports you send, their screenshots and their review status (section 10).
- On the account document itself, when usage analytics is on: the Apple Search Ads attribution token described in section 7, and the date it was recorded.
When you vote on a suggested habit, the app also increments a shared, app-wide counter for that suggestion. That counter is a number only and carries nothing about you.
Copies kept on your device
- An offline cache of the data above, so the app works without a connection.
- A small local copy of a few settings so the app can start correctly before it reaches the network, including your answers to the AI consent screens and the analytics switch.
- A shared container that the home screen widgets, the Apple Watch app and the Mac app read: today's ring, your habit list, and taps that have not yet reached the phone.
Deleting the app removes all of this from the device.
4. The AI assistant
The AI tab offers insight cards about your own history and a chat you can type into, dictate into, attach a photo to, or talk to by voice. How much of it you can use depends on your plan (section 6). Before anything is sent, the tab shows a consent screen explaining that your habit data will be sent to Anthropic; nothing is sent until you agree.
What is sent to Anthropic
The assistant is Anthropic's Claude, called from our Cloud Functions — your device never talks to Anthropic directly. To answer, our server sends Anthropic:
- your message, and the recent messages of the same conversation so it has context;
- the part of your data needed for the question: habit names and settings, what you logged and when, scores, and — when a question concerns particular days — the notes you wrote on those days;
- a photo, if you attached one (see below).
Insight cards are generated the same way from a summary of your habits and logs. The assistant is read-only: it can look at your data but cannot log, change or delete anything.
Photos
You can attach a photo from your library (through Apple's photo picker, which gives the app only the photo you choose) or take one with the camera, which asks for camera permission. The photo is resized on your device and sent to our server, which passes it to Anthropic with your message and then discards it. Helio does not store the photo: the saved conversation records only that a photo was attached. A small preview is kept in memory while the app is open and is gone when it closes.
Dictation and voice chat
Both require microphone permission and only run when you start them.
- Dictation records a short clip on your device and sends it to our server, which passes it to OpenAI's speech-to-text service and returns the text to the message field. You review the text before sending it. The audio is not stored or logged by Helio.
- Voice chat is a live call with a voice model from OpenAI. Our server sets the call up; the audio then streams directly between your device and OpenAI. OpenAI's model does not have access to your data. When you ask about your habits, the question is answered by Claude through our server as above, and the answer is passed back to OpenAI to be spoken — so OpenAI receives the text of those answers as well as your voice. Helio does not record the call audio. The on-screen captions of the call are saved into the conversation.
Your conversation history
Conversations are saved to your account so you can come back to them, and you can delete any of them in the app at any time. An account keeps at most 20 conversations: when a new one would exceed that, the oldest conversation that is not pinned is deleted automatically. The number of voice calls whose captions are kept is also limited by plan, and older call captions are removed after each new call.
Reporting an answer
If you report an AI message as objectionable, a copy of that message's text, the reason you chose and your user identifier are stored in a separate moderation record, and a notice with an excerpt is sent to the developer channel (section 9). That record is kept after the conversation or the account is deleted, because its purpose is moderation.
How the AI providers handle it
Anthropic and OpenAI process these requests as our service providers under their commercial API terms, which state that data sent through their APIs is not used to train their models. Each provider may keep request data for a limited period for safety and abuse monitoring, as set out in their own policies: Anthropic, OpenAI. Helio has no separate zero-retention arrangement with either.
5. "Discuss with AI" in Settings
Settings also offers two rows that hand a summary of your habit data to Claude or ChatGPT so you can talk it through in an assistant you already use.
- The first time you use each service, a dialog explains what is about to be shared and asks you to confirm. The confirmation is remembered on that device.
- The summary is built on your device: how many habits and logged days you have, average scores and recent trend, the last few days with the names of what you completed, per-habit completion rates and streaks, and totals by time of day and weekday. Your notes are not included.
- The summary is copied to your clipboard and
claude.ai or chatgpt.com opens in your browser with the text prefilled. Nothing is submitted for you.
- Our server counts how many times a month you use each service, to apply your plan's limit. It receives no part of the summary.
That conversation happens in your own account with that service, and what happens to the text afterwards is governed by your agreement with them.
6. Subscriptions and purchases
Habit tracking, widgets, Apple Watch and Mac are free. Paid plans raise the limits on the AI assistant. Subscriptions are sold through the App Store: Apple handles payment, billing, renewal, cancellation and refunds, and Helio never receives your card or payment details. You manage or cancel a subscription in your Apple ID settings.
- When you buy or restore, the app sends Apple's signed transaction to our server, which verifies Apple's signature and records the product, the original transaction identifier, the expiry and the account it belongs to.
- With each purchase the app gives Apple an identifier derived one-way from your user identifier, so a purchase can be matched back to your account. It cannot be turned back into your user identifier.
- Apple sends our server notifications when a subscription renews, lapses or is refunded, so your plan stays correct.
The app contains the RevenueCat purchases SDK, but it is not switched on in this version and sends nothing. This policy will be updated before it is.
7. Analytics
The iPhone app includes Firebase Analytics (Google). The companions — widgets, Apple Watch, Mac — contain no analytics.
- Events the app sends describe how the app is used. Each event is a timestamped record with a few parameters, which are counts or short fixed keywords, never text you typed:
- moving through the first-launch intro, the tutorials, announcements and the screens you open (screen names);
- habit interactions without any title or text: creating, editing or deleting a habit, logging or un-logging one, which surface it happened on (app, widget or Apple Watch), how many days back the day was, a time-of-day bucket (night, morning, afternoon or evening), and the catalogue identifier of a habit you added from the built-in suggestions;
- a daily content-free summary of each completed day: counts and scores only (how many habits were logged, how many were gains and drains, the day's total score);
- your settings choices (for example a theme, a language, a day-structure hour or a switch) and reminder changes (enabled or disabled, weekdays and offset);
- notification permission outcomes and taps on a notification (whether it was a habit reminder or another kind);
- sign-in, sign-out and account-deletion outcomes, with the sign-in provider name only (Apple or Google), and the outcome of the share sheet;
- opening, completing or dismissing the paywall, redeeming a code (the outcome only) and the review prompt;
- AI feature usage metadata: that a message was sent (and whether it had a photo), outcomes, latency, durations and counts, a request being refused (for example by a limit), viewing an insight, voice and dictation session lengths — never the content of any of it;
- opening or sending a bug report or an idea and seeing its verdict (the area and the number of images only);
- the identifiers of the error messages the app shows (a fixed message key and a kind, never the text), and your suggestion votes by catalogue identifier.
- User properties: your plan tier, app language, a rough bucket of how many habits you have, whether you are signed in and with which provider, how the app was installed (App Store, TestFlight or Xcode), and your device setup — whether a Helio widget is installed, whether an Apple Watch is paired or has the app, and your notification permission state (allowed, denied, not yet asked or provisional).
- Automatic data collected by the Firebase SDK itself: an app-instance identifier generated by Firebase (not the advertising identifier), app version, device model and OS version, sessions, and an approximate region that Google derives from your IP address.
What analytics never receives: habit titles and descriptions; the text of notes and day notes; AI messages, answers, transcripts and dictation text; the text and screenshots of bug reports and ideas (only the area and a count of images); your email address; your name; your user identifier or any account identifier (it is not set as the analytics user ID, so events cannot be tied to your account); your photos (only a count); redeem or promo code text (only the outcome); and the advertising identifier (IDFA), which the app neither reads nor asks permission for.
Analytics events are copied daily into our own Google BigQuery dataset in the EU, where we keep them so that we can study how the app is used. We also read Apple's aggregate App Store Connect reports (downloads, sessions) into a private storage bucket in the EU; those reports contain no per-user data.
Apple Search Ads attribution. On first launch the app asks Apple's AdServices framework for an attribution token — a short-lived token Apple issues so that an install can be credited to an Apple Search Ads campaign — and stores it with your account. It is not the advertising identifier and involves no tracking prompt.
You can switch this off in Settings → Share anonymous usage analytics. While it is off, Firebase Analytics collection stops and the attribution token is not collected. The switch is on by default.
Helio does not use the advertising identifier (IDFA), shows no App Tracking Transparency prompt, and does not track you across other companies' apps or websites.
8. Crash reports and error diagnostics
The app uses Firebase Crashlytics, and it is not affected by the analytics switch. When the app crashes or hits a handled error, Crashlytics records the technical detail — stack trace, app version, device model, OS version — together with your user identifier and a few keys that locate the problem, such as the operation involved, a habit's internal identifier or a date such as 2026-09-29. Habit titles, note text and AI conversations are never attached. Crashlytics data is also copied into our own Google BigQuery dataset in the EU, where it stays linked to your user identifier.
9. The developer channel
Because Helio is run by one person, some events are sent to a private Telegram channel that only the developer reads:
- Errors — the error description, the operation it came from, and the same identifiers as in section 8, with the app version, iOS version and device model.
- Crash notices — a line on the next launch saying the previous session crashed, with app version, iOS version and device model.
- Account events — that a sign-in, sign-out, new anonymous session or account deletion happened, with the user identifier.
- Ideas you send through Settings → Help improve Helio → Suggest an idea — your message, with your user identifier, app version, iOS version and device model. This is how your message reaches a human.
- Bug report notices — one line per bug report (section 10) with its reference number, app version, app language, the area you picked and the number of screenshots. The text of the report, the screenshots and your user identifier are not sent.
- AI message reports — as described in section 4.
- Server alerts and a weekly summary — operational alerts from our Cloud Functions and a weekly report of aggregate numbers (for example how many accounts were active). These contain no user content and no per-user identifiers.
Habit titles, notes, daily logs and AI conversations are never sent to this channel, except the text of an AI message you choose to report.
10. Bug reports
You can report a bug in Settings → Help improve Helio → Report a bug. Nothing is sent until you press send.
- What a report contains: the area of the app you pick, what you write about the problem and, if you add it, what you were doing just before. The app adds the app version and build, the iOS version, the device model, the app language and your plan.
- Screenshots: you can attach up to three. You choose them yourself in Apple's photo picker, which gives the app only the images you pick and needs no access to your photo library. Nothing is captured or attached automatically. A screenshot can show personal information, so crop it before sending if needed.
- Where it is stored: the report and its screenshots are stored under your account in Cloud Firestore, and the app shows you its status. A separate review record, readable only by the developer, holds your user identifier, the device key described below, and the review notes and verdict.
- AI-assisted review: the developer reviews reports with the help of Anthropic's Claude. During that review, the text of the report, the details listed above and the screenshots may be processed by Anthropic. See Anthropic's privacy information.
- Device key, for fraud prevention: so that one device cannot collect thank-you rewards again and again, the app sends a one-way SHA-256 hash of the identifier Apple gives Helio on your device (
identifierForVendor), and our server hashes it again with a secret key (HMAC). Only that result is stored. It cannot be turned back into the device identifier, it is not the advertising identifier, and it is not shared with anyone. It is stored in the review record and in a per-device record that counts reports and holds the dates of the most recent report and of rewards from the past year.
- Thank-you reward: if a report is confirmed as a real bug, our server adds 30 days of the next plan up to the same account (the
entitlement record in section 3). No code is issued and no payment is involved.
How long it is kept. Screenshots are deleted 90 days after the report gets its verdict. The report text and its details are kept until you delete your account, and deleting the account removes all your reports, their screenshots and their review records. The per-device record names no account and is kept after the account is deleted, so that deleting and re-creating an account does not reset the reward limit (section 17).
11. Widgets, Apple Watch and Mac
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. It contains no analytics.
12. Notifications
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.
13. App integrity and update check
Requests to our Cloud Functions are checked with Firebase App Check, which uses Apple's App Attest to confirm they come from a genuine copy of the app. 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.
14. What Helio does not do
- No advertising, no ad networks, no sponsored content.
- No sale of personal data, and no sharing of it for anyone else's marketing.
- No tracking across other companies' apps and websites, and no data brokers.
- No location access (only the approximate region Google derives for analytics), no HealthKit or health data, no contacts. The only permissions the app asks for are notifications (for reminders), the camera and the microphone (for the AI assistant).
- No marketing email. Your address, if the app receives one, is used for sign-in and for replying to you.
15. Who processes your data
- Google — Firebase Authentication, Cloud Firestore, Cloud Functions, Analytics, Crashlytics and App Check host and process the data described above; Google Sign-In if you use it. See the Firebase privacy documentation and the Google Privacy Policy.
- Anthropic — generates AI chat answers and insights, processes photos you attach (section 4), and assists the developer in reviewing bug reports (section 10). See Anthropic's privacy information.
- OpenAI — transcribes dictation and runs voice chat (section 4). See the OpenAI Privacy Policy.
- Apple — App Store purchases and subscription billing, Sign in with Apple, App Attest and Search Ads attribution. See the Apple Privacy Policy.
- Telegram — carries the developer channel described in section 9. See the Telegram Privacy Policy.
These providers operate globally, so your data may be stored and processed outside your country, including in the United States. Traffic between the app, our server and these services is encrypted in transit.
16. How long data is kept
- Your habits, logs, notes and settings are kept for as long as the account exists — a log from two years ago is the point of the app — until you delete them or the account.
- AI conversations are kept until you delete them, subject to the 20-conversation limit and the voice-caption limit in section 4. Insight cards are replaced when new ones are generated.
- Audio and photos are not stored by Helio; they exist only for the duration of the request. Anthropic and OpenAI may retain request data for a limited period under their own policies (section 4).
- Bug reports: screenshots are deleted 90 days after the report gets its verdict; the report text and details are kept until the account is deleted. The per-device record used against reward abuse is kept after that (section 10).
- Analytics events are anonymous (they are not linked to an identity) and are kept in our BigQuery dataset in the EU with no expiry. In the Google Analytics console, per-user data used for explorations is kept for 14 months.
- Crash reports and server logs that are linked to a user identifier (the BigQuery copy of Crashlytics data, and operational logs of our server functions copied to BigQuery) are deleted automatically after 2 years. The server logs are limited to fixed fields such as event names, counts and codes.
- Apple's aggregate App Store Connect reports are not linked to any user and are kept with no expiry.
- Messages in the developer channel are kept only as long as they are useful for fixing the problem or answering you.
17. Deleting your data
In the app: Settings → Account → Delete Account. If you are signed in, you are asked to authenticate once more to confirm it is you.
This deletes your habits, daily logs, notes, votes, bookmarks and settings, your AI conversations and insights, your AI usage counters and plan record, your bug reports with their screenshots and review records, 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. Deleting the account does not cancel an App Store subscription — cancel it in your Apple ID settings.
What deletion does not reach:
- The record of an App Store subscription is detached from your account but kept — the product, Apple's transaction identifier and its expiry — so that the subscription can be restored to a new account and cannot be misused across accounts.
- Moderation records of AI messages you reported (section 4).
- The per-device record used to limit bug-report rewards (section 10). It holds the device key, a count of reports and the dates of the most recent report and of rewards from the past year, and no user identifier.
- Anonymous analytics rows, which are not linked to your identity and so cannot be found or removed for you individually, and messages already in the developer channel.
- Crash reports that Google stores in Firebase Crashlytics itself. On your request we also delete the rows in our own BigQuery dataset that are linked to your user identifier (the Crashlytics copy and the server logs); email us and we will delete what those tools allow.
- Data already processed by Anthropic or OpenAI, which is subject to their retention policies.
Uninstalling the app removes every local copy from that device. If you would rather not delete in the app, email us and we will do it for you.
18. Your rights
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. You also have the right to complain to your local data protection authority.
The legal basis for processing is: performance of the service you asked for (storing and syncing your habits, running the AI features you use, managing your subscription, reviewing the bug reports you send); your consent where the app asks for it (the AI assistant, "Discuss with AI", notifications, camera and microphone); and a legitimate interest in keeping the app working and understanding how it is used (crash and error diagnostics, preventing abuse of bug-report rewards, and analytics, which you can switch off).
19. Children
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.
20. Changes to this policy
If this policy changes, the effective date at the top of the page changes with it, and the change is made before the behaviour it describes ships — not after.
21. Contact
alexslkmain@gmail.com