Privacy
Updated 13 November 2026. This notice covers Habby’s current iPhone app, account service and website, operated by Anh Minh Le / AMSOFT.
Your habits
Habits, progress, reading notes and running timers are saved in a local database so the app works offline. When you sign in, Habby syncs your account’s habits with its database in Singapore so you can continue across devices. The first account used on a device automatically adopts meaningful device habits; later accounts keep separate local workspaces. Device backups are governed by your Apple settings.
Reminders and timers
With notification permission, Habby schedules reminders on your device using your habits and recent activity. When signed in, private action-timing summaries also sync with your account to help plan reminders across devices. Planning uses a fourteen-day learning window; older summaries are pruned when the app next exchanges data. This feature data is separate from optional analytics. Habit names and progress may appear in notifications and reminder or timer Live Activities, subject to your iOS privacy settings; reading reflections never appear there. You can change notification and Live Activity permissions in iOS Settings.
Optional AI Log
If you choose Log, Habby sends your request and your account’s habit names, settings, recorded current-day progress and timer state, and saved routine memories through Vercel AI Gateway to providers running a DeepSeek model to interpret the habit changes you requested. Log requires a signed-in account. Existing saved reading reflections are not included in this habit context, although anything you say in a request is message content. Voice input sends a short recording through Vercel AI Gateway to OpenAI for online transcription. The app asks for iOS microphone access before recording; granting access does not start a recording. A live waveform uses temporary on-device audio levels that are not saved or sent to analytics. A separate AI pass uses the recognized words and your habit names to correct likely speech recognition errors. Stopping a recording automatically submits that corrected text as a habit command; unclear speech asks you to record again, and removing habits still requires confirmation. Temporary recordings are removed from the app after transcription or cancellation and are not stored in Habby’s chat database. AI processing may occur outside Singapore. Habby requests that providers do not use these requests for training. Gateway and model providers may retain submitted data under their own policies. You can stop future AI processing by not using Log; this does not delete requests already sent.
Log requests, AI responses, proposed actions and their outcomes are linked to your account and stored in Supabase until your account is deleted. The full transcript is separate from the shortened context used to process later requests. Shortening that context or restarting a server function does not delete your messages. Each account has one continuing conversation without an inactivity expiry. Habby can save useful preferences, goals and routine details as exact quotes from your messages, linked to their source message. Saved memories are kept with your account separately from shortened conversation context, so they survive compaction and work across devices. You can review and remove saved memories through What Habby remembers. Removing one clears the working context, while the original conversation messages remain readable. Deleting the account removes its server Log records. Local command receipts stay with the account’s local workspace. Log content and audio are never sent to PostHog or application logs. Ordinary habits continue to work without Log or a network connection.
Your account
Signing in is optional. When you create an account or use Apple or Google sign-in, Supabase Auth processes your email address, provider identity, authentication information and basic profile details supplied by your provider, such as your name. Habby stores your account ID and a profile record. We use this information to authenticate you, protect account access and provide account support.
Apple and Google sign-in request basic identity and email information. Habby does not request access to your Google mail, contacts, calendar or files. Google user data is used for sign-in and account identification; it is not sold, used for advertising or used to train AI models.
Service providers
Supabase hosts Habby’s account service and database in Singapore. Vercel hosts this website and the API, with API compute configured in Singapore. Resend delivers account verification, sign-in and password recovery emails and processes the recipient address and message. These providers may process operational information, such as request and email delivery logs, under their own policies. Provider login screens are governed by Apple’s or Google’s policies.
Storage and retention
Habby uses your verified account ID to check your subscription with Polar automatically, so the same account can restore purchases on another device. Purchases provisioned through Habby’s authenticated checkout are linked to that account ID. The app caches the last verified subscription status separately for each account in its local database; habit content is not sent to Polar. Older device license credentials are left untouched and are no longer used by the app. All current app features remain available without a subscription.
During account deletion, Habby retains a limited active-subscription and benefit snapshot for your private export and pending cleanup. This snapshot excludes payment methods and license credentials. It is removed from the cleanup job after deletion and from the export when its seven-day link expires.
The app stores sign-in sessions in iOS Keychain. Account and synced habit records remain until they are deleted. Signing out removes the app’s local sign-in session, returns to your separate device habits and preserves the account’s local saved data and pending changes for a future sign-in. Sync receipts and history are retained to support devices returning after an offline period. Operational logs and backups may remain subject to service-provider retention schedules.
Account deletion and your data export
In app versions supporting account deletion, choose Delete account in Account. Deletion is scheduled after a 24-hour grace period. You can cancel until permanent deletion starts; successful cancellation revokes any issued export link. At the deadline, account changes stop and Habby snapshots committed server data, including your profile, synced habits, history, timers, private reminder summaries, full Log transcript, saved routine memories and relevant subscription state. Keep devices online before the deadline. Unsynced changes, local Health configuration and readings, opaque Screen Time selections and other device-only data are not included.
Habby emails a private download link to your verified address using Resend. The link works without signing in for seven days from issuance, including after your account is gone, unless you cancel deletion. Anyone with the complete link can download the file, so keep it private. Preparation or email-acceptance failures delay deletion; acceptance by the email service does not confirm inbox delivery. The download page and deletion requests do not send analytics. After seven days, the active export payload and capability are removed. Previously downloaded files and provider-managed backups are outside this link’s control.
Permanent deletion removes your Auth account and account-owned database records. Apple-linked accounts authorize with Apple again so Habby can revoke access at deletion; the revocation credential is encrypted and removed after revocation or cancellation. Polar subscriptions and benefits are canceled without an automatic refund, and customer details are anonymized where supported. Polar retains required historic financial records. Email, AI and infrastructure providers may retain operational or previously submitted data under their own policies; deleting Habby records does not claim to retract data already processed by those providers.
When a device confirms completed deletion, Habby removes that account’s local habit data and recognized migration backups. Signed-in devices privately enroll a cleanup proof before a deletion request exists, so an enrolled device can reconnect and confirm cleanup after staying offline for the whole deletion window. Account-bound enrollment is removed with the account. A device that never enrolled needs separate verified recovery; failed sign-in alone does not erase its data. Separate device habits and other accounts remain. Minimal on-device retirement markers retain account/workspace identifiers to reject stale callbacks and prevent importing device habits again; they contain no habit content. Server completion records keep opaque request/proof identifiers, status and timestamps for later cleanup confirmation, with no email, account ID or export content after deletion. Canceled-request ownership records are cleared after 30 days or when the account is deleted. Your Apple device backups remain governed by your settings.
Optional app analytics
Share app analytics is on by default when no preference has been saved, and can be turned off in Settings. A saved choice is preserved. If enabled, Habby sends an anonymous device identifier, fixed screen/control labels and coarse success/failure outcomes for habit actions, account flows, settings, reminders and timer Live Activities to PostHog’s US cloud. Foreground engagement is grouped into duration ranges. Events never contain habit names, kinds, identifiers, amounts, goals, saved activity times, schedules or reflections, account IDs or emails, credentials, callback URLs or raw errors. A generic Restore purchases interaction does not include subscription or customer state. Private reminder-learning summaries are not sent to PostHog. Automatic interaction capture and session replay remain disabled. The API also sends coarse request events, using a fresh random identifier for each request and fixed endpoint/method/status/timing fields. These events are used to understand product use and service reliability.
Optional website analytics
Website analytics is off until you enable Share website analytics in the footer. Its saved browser preference is separate from the iPhone app. If enabled, fixed page and link labels, observed section/scroll-depth ranges and coarse duration ranges for time with the page visible are sent through Habby’s API to PostHog’s US cloud. Each browser tab uses a random anonymous identifier that is never joined to an account. No page URLs, query strings, fragments, referrers, email addresses, form text or profile data are included. Event timestamps are delivery metadata; no saved habit or account data is read.
A bounded browser queue retains up to 100 coarse events for at most 24 hours to retry failed sends. Retries keep the same event identity. Turning the preference off clears the queue and tab identifier and stops new capture; an already-sent request may still arrive. Activity while disabled is not backfilled. Blocking browser storage leaves only an in-memory preference and queue. These analytics do not use session replay, advertising cookies or automatic content capture.
Contact and account requests
Subscription checks, checkout provisioning and legacy license-verification requests bypass API analytics.
For account access, correction, deletion or privacy questions, email minh@amsoft.vn from your account address. We may verify account ownership before making changes. To remove local habit data, use your device’s app and backup settings.