Habits Shape Life

Privacy policy

Version 1.8 · Effective date set on publication (draft pending business details)

This policy describes the current development version. We update it when data practices change.

1. Operator and contact

Habits Shape Life is operated by 성공하는 습관. Its representative is the privacy officer. Send requests to access, correct, delete, restrict or copy your information, consent withdrawals and privacy complaints to syc1117@gmail.com. We may ask for the minimum information needed to verify ownership, and we reply without undue delay—within 10 days, or within any period set by the law that applies to you, such as one month under the GDPR.

2. Information we process

Google, Kakao or Apple account identifiers and profile/email information returned by the selected sign-in provider, for authentication and account identification through Supabase Auth. We do not collect your provider password. Kakao requests a stable account identifier without additional email, nickname or photo scopes.
Routine titles, goals, notes and completion; foods, quantities, units, calories and nutrients; workout sessions, sets and drafts; saved items, dates and edit timestamps. Records are stored on your device and synchronized with the account server (Supabase).
Language, theme, health connection preferences and sign-in sessions. Preferences are local. Sessions use iOS Keychain or Android secure storage.
Apple refresh tokens are encrypted on the server for authorization revocation on unlinking or account deletion. The encryption key is separate from the database. Kakao linkage identifiers and revocation receipts support account management and are removed with the account.
Support emails and necessary security/request metadata, such as IP addresses and request times, processed by service providers to operate and protect the service.
Country of residence, self-entered age, and records of your terms, privacy and health-processing decisions (document version and time): to confirm sign-up at 16 or older and keep consent records. Date of birth is not collected. Withdrawals and changes are recorded too.
Subscription information—store, product, transaction and subscription identifiers, status, expiry and renewal times, account link identifiers (Apple appAccountToken, Google obfuscated account ID) and Google purchase tokens: to verify subscriptions, manage access and apply cancellations and refunds. Google purchase tokens are stored encrypted. Card details are not collected.
Invitation code and when it was added: to check eligibility for the first-subscription discount, count sign-ups and subscriptions per promotion partner and settle revenue shares. Partners see only aggregates that do not identify you.
Operator-issued free access for the developer and promotion partners (period, reason, issuer): to provide agreed free use and keep an issuance record.

Optional app usage analytics

After sign-in, feature-use times, success and failure outcomes, statistics and comment visibility, search result availability, platform, app version and language may be collected to improve usability and reliability. The analysis identifier is linked to an account; these events are not anonymous. Food names, search terms, weight and nutrient values, workout details, routine text and the contents of guidance are not copied into analytics events.

Collection is enabled only after the applicable legal basis and device requirements are reviewed. Where notice and an objection option are sufficient, collection starts after the notice is displayed; where prior consent is needed, it starts after you opt in. Unreviewed regions remain off. You can stop or resume participation and delete previously collected analytics in Settings → App usage analytics. Resuming does not recreate events from the period you did not participate. Deleting analytics does not change your participation setting.

These choices do not affect record storage, subscriptions or AI connections. Necessary security and service-operation logs and payment records are managed separately. Usage events are retained for up to 13 months. Minimal deletion receipts are retained for 15 months to prevent deleted analytics from reappearing in restored backups or earlier operator downloads. Operator downloads must follow the same deletion and retention rules.

Sharing records with your chosen AI service

You can connect your own ChatGPT or Claude account to our read-only MCP service. Before granting access, we identify the receiving service, list every record type that will be shared (diet, workout and routine records, body weight, permitted health-app summaries, desired changes and related routines, previously entered goals and notes) and ask for a single consent. Shared records can include past and future records. After connecting, you can narrow sharing item by item or disconnect under “Connected AI”. Existing connections do not automatically receive newly added categories.

The purpose is to let that AI service answer your questions using your records. We do not provide an in-app AI chat, charge an AI fee or store the conversations. Your AI provider’s account terms, processing practices, features and fees apply. Review that provider’s privacy information before connecting: OpenAI or Anthropic. The recipient may process information outside your country under its terms. Applicable transfer requirements must be met before a recipient and data source are enabled.

In Settings → Connected AI, you can reduce the shared scope or disconnect each service. To expand access, reconnect from that service and approve the new scope. Disconnecting blocks future queries; it cannot erase information already delivered to an external conversation. Manage those conversations with the recipient. A valid AI sharing grant can still read retained records when your Habits Shape Life subscription ends. Analytics choices neither grant nor revoke AI access.

We share only supported personal wellness records and permitted health summaries needed for your request. We do not add clinical or medical-provider records. Consent does not override source or recipient restrictions. Limited access audit metadata records which connected client requested which tool and whether the request succeeded; it does not store AI conversation text or returned health values.

3. Sign-in and on-device records from earlier versions

The current version is used with a signed-in account, and only people aged 16 or older can sign up. Records saved on a device without signing in under earlier versions are not moved into another account automatically. In-app account deletion also clears that account’s pre-sign-in originals on the current device.

4. Optional health connection and Watch measurement

With permission, the phone reads active energy from Apple HealthKit or Android Health Connect to display daily activity calories and synchronize daily totals, dates, sources, time zones and update times to your account. Health information supports record storage, cross-device synchronization and reviewing changes over time.

After an explicit start on Watch or choosing “Use Watch” on the phone and granting health permissions, Habits Shape Life displays heart rate and active energy and saves workout type, start/end times, duration and active energy to Apple Health. One measurement spans sets and rests until “End entire workout”. Workout routes are not collected or saved.

Cardio results from a Watch linked to your signed-in app send workout type, times, duration, final workout active calories and source identifiers to the diary and account sync. “Import health workouts” requires separate consent and is off by default. When enabled, it imports cardio workouts from the last 30 days, then changes: type, times, duration, source, available distance and active calories linked to that exact workout. Workout active calories are retained only with a verified source association. Manually edited values are preserved during re-import. Workout calories are not added again to daily activity totals. Source distance for indoor workouts may be retained but is not used in the interface or statistics.

Turning import off stops new reads and retains existing records. Deleting a diary record removes it from Habits Shape Life synchronization but does not delete the original in Apple Health or Health Connect. Manage health permissions and original records in operating-system health settings. We do not use health data for advertising, sale or AI training. Health access is optional; manual phone entry remains available.

5. Service providers and international transfers

The following companies process information to provide the service. Processors act under contract and only as needed; sign-in and app store providers follow their own policies. Retention follows section 6 and each provider's policy.

Supabase Inc. (United States), Supabase Pte. Ltd. (Singapore) and subprocessors: authentication, record storage and synchronization, server functions. The database region is Seoul, South Korea (ap-northeast-2). Account identifiers, records and technical logs are sent over the network for sign-in and sync requests and for support or security work.
Cloudflare, Inc. (United States): the website and records web, and storage of encrypted backup files (R2). Technical request data on each visit; encrypted backup files at each scheduled backup.
GitHub, Inc. (United States): the scheduled backup environment (a private Actions runner) that reads, encrypts and uploads accounts and records during each backup.
Apple Inc. and Google LLC (United States): sign-in, app store payments and subscription status notices. Sign-in identifiers and subscription transaction information are exchanged at sign-in, purchase and subscription changes.
Kakao Corp. (South Korea): Kakao sign-in; the Kakao account identifier is received at sign-in.

The current version requires a signed-in account, so the service cannot be used without these transfers. Deleting your account stops further processing. Sharing with ChatGPT or Claude that you connect yourself follows the AI sharing section above.

Supabase privacy · Subprocessors · Data processing agreement · Google privacy · Kakao privacy · Apple privacy · Cloudflare · GitHub

6. Retention and deletion

Account records are retained while providing the service. Deleting your account removes the server account and its associated records and clears the account’s records on the device performing deletion. Apple/Kakao authorization is revoked as part of the applicable account operation. Provider failures can require retrying before deletion completes. Your Google, Kakao or Apple account itself is not deleted.

When a current app on another device receives authoritative server confirmation of account deletion, it clears that account’s local records. Offline devices, expired sessions and older app versions may delay or prevent this check. Uninstall the app on those devices to remove local copies. System health records are not deleted. Files exported using earlier app versions must be deleted separately.

We retain only an internal deleted account ID and deletion timestamp to prevent old backups from restoring deleted accounts. This contains no email, name, record content or tokens. Separate deletion-ledger retention and exclusion during restoration remain pre-release verification items.

Subscription transaction records (store, product, transaction identifiers, status and period) are kept separately from the account after deletion and removed once no longer needed for duplicate purchase checks, refunds, disputes and legal retention duties. Invitation code entries are deleted with the account; settled partner payouts are kept only as non-identifying aggregates for the tax retention period.

Information whose retention period has ended or whose purpose has been met is destroyed without delay. Electronic files are deleted so they cannot be recovered, and encrypted backups are deleted automatically when their retention window (currently 35 days) ends. We keep no personal information on paper. Information that law requires us to keep is stored apart from other data and destroyed when that period ends: under Korea's Act on Consumer Protection in Electronic Commerce, contract, withdrawal and payment records for 5 years and complaint and dispute records for 3 years.

The current Supabase Free plan exposes API/database logs for one day and authentication audit logs for one hour. These visibility windows do not guarantee deletion of all provider-internal security copies. Support information is kept as needed to resolve requests and follow-up, then deleted, except where applicable law or dispute handling requires retention.

7. Backup and security

Account synchronization is not a separate historical backup. Separately from Supabase Free managed backups, a private GitHub Actions runner is configured to encrypt account and record backups and store them in Cloudflare R2. Production backups are currently removed after 35 days; retention changes will be announced. Isolated restoration checks are performed; recoverable data depends on successful backups and their retention window. The app and web offer no record file export or import; to receive a copy of your records, contact us. Reading records from your own connected ChatGPT or Claude account follows the AI sharing section above. We use HTTPS and account-scoped access controls. This is not end-to-end encryption with keys exclusively controlled by you.

8. Your rights

Edit or delete records and delete your account in the app. You can also follow our account deletion instructions without reinstalling the app. Contact us to access, correct, delete or restrict your information or withdraw consent; on request we send a copy of your records in a machine-readable format (JSON). Health connection, app usage analytics and AI sharing can each be turned off in Settings at any time. We do not make automated decisions that produce legal or similarly significant effects for you. Available rights and how they are handled depend on the law that applies to you.

9. Linked sign-in methods

Authenticate an additional Google, Kakao or Apple identity while signed in to associate it with the same app account. This does not merge records belonging to another app account. Unlinking removes that sign-in method without deleting your records. Keep at least one usable sign-in method. Apple may require reauthentication to revoke access; unlinking Kakao also ends the service’s Kakao connection.

10. Changes and this website

We update the effective date when practices change and provide notice or consent where required. Public information pages have no advertising or visitor-analysis scripts. Signed-in app usage analytics follow the separate controls above. Hosting and email providers may process technical request metadata or messages needed to provide their services.

The signed-in records web uses browser storage only for: the sign-in session (authentication token); display settings such as language, theme, weight unit and the last statistics view; a per-account copy of records, changes waiting to upload and unsaved drafts; and, if you take part in app usage analytics, events waiting to be sent. We use no advertising or tracking cookies. Clearing this site's data in your browser settings removes them; you then need to sign in again.

11. Subscriptions and promotion partners

The yearly subscription uses the relevant app store. We process verified subscription transactions and entitlement information, not card details. Cancellation, expiry, refund and account deletion are separate operations. Expiry alone does not delete retained records. Prices and availability are shown by the store.

Information needed to pay and report taxes for promotion partners (name, contact, payout account, tax details) is collected under a separate agreement and kept apart from app user data. A partner's statistics show only sign-up, subscription and refund counts and amounts attributed to their own invitation code.

12. Children under 16

People under 16 cannot sign up, and we do not knowingly collect their personal information. If we learn that someone under 16 has signed up, we delete that account and its records. A parent or guardian can ask us to delete it at the contact address above.

13. Users in the EU, UK and similar regions

Where the GDPR or a similar law applies, we rely on these legal bases:

Contract: your account, record storage and synchronization, subscription verification and support.
Explicit consent: health data connection and account storage, sharing records with an AI service you connect, and app usage analytics where prior consent is required.
Legal obligation: keeping payment and tax records.
Legitimate interests: security and abuse prevention, incident response and backups, and settling promotion partner payouts based on invitation codes. You can object to this processing.

You can withdraw consent at any time without affecting processing before withdrawal. You can request access, correction, deletion, restriction, objection and portability (receiving a copy in a machine-readable format), and you can lodge a complaint with the data protection authority where you live. South Korea is covered by an EU Commission adequacy decision. Transfers to processors in other countries, such as the United States and Singapore, use the safeguards those providers offer, such as the standard contractual clauses in the Supabase data processing agreement.

14. Remedies in Korea

You can also seek advice or report privacy violations to the Personal Information Dispute Mediation Committee (1833-6972, kopico.go.kr) or the Personal Information Infringement Report Center (118, privacy.kisa.or.kr).