HabitHub Privacy Policy

Effective date: August 7, 2026

HabitHub has no accounts. You never sign in, and nothing in the app can identify you by name, email, or anything else you'd use to log in somewhere. This page says exactly what the app stores and what leaves your phone.

What stays on your phone

Everything you record. Your habits' check-in history, the amounts you log, streaks, Freezes, and statistics live in a database on your device and are never sent anywhere. Backups are files you create yourself with Export data in Settings; they go wherever you choose to save or share them, and HabitHub's developer never receives them.

What leaves your phone

HabitHub sends a small number of anonymous usage events to help improve the app. There is no switch that turns this off. This is the whole list:

• When you create, edit, or delete a habit, the event includes that habit as you set it up: its name, its emoji and colour, its optional Description and Why, its scheduled weekdays, and its reminder time. Note that a habit's name, Description, and Why are text you typed — if you write something personal there, that text is part of the event.
• When you create a habit, that same event also records three things about the shape you chose: whether the habit is a simple tick or one measured in amounts, whether it runs daily, weekly, or monthly, and a plain yes or no for whether you typed your own unit instead of picking one from the list. If you typed your own unit, the words you typed are not sent — only the fact that you typed one. The goal you set is not sent either.
• When you archive a habit or restore one from the archive, the event includes that habit in the same way, as it stood at that moment.
• When you open the app, an event records the open, and whether the app was launched fresh or returned to from the background. It records nothing about what you did next.
• When the HabitHub Pro screen is involved, events record that the screen appeared and which part of the app you reached it from, that you left it and whether you had bought by then, that you started a purchase and which plan, how that purchase ended (bought, cancelled, or failed), and how a Restore ended. No payment details are in any of these events; see Purchases below for how a purchase is actually validated.
• When you tap Support, an event records that the row was tapped. It carries nothing else — the conversation happens in Instagram, and none of it comes back to the app.
• When you first set up the app, events record the steps of the welcome flow you completed and your answer to “where did you hear about HabitHub?”

Four facts ride along with the events above: whether HabitHub Pro is unlocked on this device, which plan unlocked it if one did, whether that purchase was a sandbox or TestFlight one rather than a real sale, and the answer you gave to “where did you hear about HabitHub?”. The first three attach once the app has worked out what you own, and the fourth once you have answered that question during setup — so the earliest events of a fresh install carry fewer of them.

Day-to-day use never leaves the device: checking in, logging an amount towards a goal, spending or earning a Freeze, browsing to another week, and everything your streaks are made of are never part of any event.

These events are anonymous. There is no account, no user profile, and no name or contact information anywhere in them. They are tied to a random identifier scoped to your device's install of the app, not to you. Like most internet traffic, the requests also carry your IP address, which may be used to derive an approximate region. The analytics library attaches basic device and app context alongside it: your device's model and operating system version, the version of HabitHub you are running, and your device's language and time zone.

Who processes it

Events are processed by PostHog Inc. on HabitHub's behalf and stored on PostHog's US Cloud (servers in the United States). The data is not sold, not used for advertising, and not shared with anyone else. Events already sent are not retrievable or deletable on request, because nothing in them identifies you to find them by.

Purchases (HabitHub Pro)

HabitHub Pro purchases are processed by Apple. HabitHub never sees your payment details — no card number, no billing address, nothing.

To validate a purchase and work out whether Pro is unlocked on your device, the purchase receipt and transaction identifiers Apple issues are sent to RevenueCat, who process them on HabitHub's behalf (see the RevenueCat privacy policy). This happens whenever you buy or restore a purchase. It is how the app knows what you own; it is not usage data, and it carries none of the events described above.

As with everything else in HabitHub, there is still no account. RevenueCat receives an anonymous identifier the app generates on your device, never your name or email.

Notifications

Habit reminders are local notifications, scheduled and delivered entirely on your device. HabitHub has no server and sends no push notifications.

Children

HabitHub has no accounts, asks for no personal information, and is not directed at children. The anonymous usage events described above are the whole of what it collects — including the habit name, Description, and Why that you type yourself, which is why this page names them plainly above.

Changes

If what the app sends ever changes, this page changes first, with a new effective date.

Contact

Questions? Email yashpatel26@gmail.com.