Hankkirang

Effective September 30, 2026 · Version 2026-09-30.2

Hankkirang Privacy Notice

This is a beta draft for a planned South Korea, EU and US launch. It must not be used as a public-launch notice until operator contact details, possible EU representative obligations, processors and cross-border transfer details are finalised.

1. Contact

Hankkirang individual developer. Privacy request contact: wshji31800@gmail.com.

2. Device-local use

Your calorie goal and logs, foods, meals, recipes, supplements, medication, real name, display nickname, status message and preferences are stored on your device by default. Signing in does not upload these records. Clearing browser/app data may erase them. You can download a backup and delete local records in Settings. Only if you connect a folder or NAS and turn on automatic backup in Settings is a password-locked backup file kept there; it is never uploaded to Hankkirang’s servers, and the password is not stored.

3. Account data

If you choose Google sign-in, Supabase Auth processes your Google account ID, email, display name, profile photo and authentication session to operate your account and friend connections. We also record the versions and time of your Terms/privacy acceptance, language and minimum-age confirmation. These records are retained until account deletion, unless a specific legal retention duty applies and is disclosed. You appear under one name everywhere—friends, groups and the public space: your nickname if you set one, otherwise your sign-in account’s name; public mode needs a nickname. The real name in your profile stays on this device and is never sent. In cloud mode your nickname, one-line bio, profile photo and visibility settings (activity numbers, followers, who may send friend requests) belong to your account, so every device signed in to it shows the same; in local mode they stay on this device. They are kept until account deletion, and a photo or bio is deleted as soon as you remove it. Your profile photo is cleaned of location and other photo details before upload and served, with a permission check on every request, only to friends, members of a group you share, and people with public mode on when you are too (unless either blocked the other). Your space shows each viewer only the posts they may already see, and, if you allow it, numbers counted over those posts (posts, recipe cards, likes received, saves) and your followers. Declining account processing does not prevent device-local use. Google's own processing is described in the Google Privacy Policy.

4. Sharing with friends

Only when you enable sharing for a named friend do selected meal names, daily calorie/macronutrient totals, or supplement names and taken status go to Supabase and become visible to that friend. We ask separately for each recipient and category, and record the choice, policy version and time until either account is deleted. Active published data is deleted, or that friend's access ends, when you revoke sharing or disconnect. An offline revocation takes effect after it reaches the server. Medication, notes and individual food details are not published.

5. Community groups

The community is available only after sign-in and acceptance of the community notice (version 2026-09-30.2), which you accept together with the terms when you sign up; the two acceptances are recorded separately. In private, invitation-only groups, only what you write or choose is stored on Supabase, and only members of that group can see it.

DataPurposeRetention
Group name and description, role (owner or member), time joined (groups show your profile name and photo)Running groups and showing membersUntil you leave or are removed, or the group or account is deleted
Post text, a meal you pick (dish name, meal slot, calories if you add them) or recipe (name, cooking time, ingredients, steps, calories per serving and each ingredient’s weight and nutrition), photos, comments, likes and bookmarksSharing meals and recipes with group membersDeleted immediately when you delete it, leave or are removed, or the group or account is deleted
Report reasons and times, block list, invitation code hashes, expiry and use counts, rate-limit countersSafety and preventing spam and abuseUntil the reported item or the account is deleted, the invitation expires, or the limit window ends

The community server does not accept medication, dose, side-effect or body-measurement records, and rejects meal or recipe fields outside the allowed list. Location (EXIF) and other photo details are removed on your device before upload, and the server rejects photos that still contain them. Other members never see your e-mail or sign-in account details. A post or comment with three reports is hidden from everyone except its author. Only authors delete their posts; the group owner can remove a member, which deletes that member’s posts and comments in the group. “Save recipe” copies a post, with its recipe photo, calories and ingredient nutrition, to this device only. “Eat together!” sends an in-app notification with your group display name to the other members of that post’s group.

5-1. Public mode · public mode notice version 2026-10-03.2

Public mode is off by default and cannot be turned on without signing in. Only when you set a nickname and read the public mode notice in Settings or the Popular tab can you and others with public mode on see each other’s public posts and follow each other. Without it you post only in groups you were invited to, as before. Group posts and group names are never made public. The public space shows your nickname, profile photo and one-line bio.

DataPurposeRetention
Public mode status, the notice version you accepted and whenRunning the public space and recording consentUntil account deletion (hidden while off, restored when turned on again)
Title, text and photo of public posts, a meal, recipe or exercise (type, name, minutes, calories burned), comments, likes and bookmarksSharing between people with public mode onDeleted immediately when you delete it or your account
FollowsBuilding the Following tabUntil you unfollow, block, or delete your account

Turning public mode off hides your public posts, comments, public name and follows from others at once (nothing is deleted) and closes the public space to you. If you are offline, it is hidden on this device right away and shown as “turning off” until the server is told. Public posts and comments cannot contain links, and text matching a list of abusive or advertising terms is refused. Blocking someone hides both people’s public posts and comments from each other and ends follows. A public post or comment with three reports (spam or advertising, abuse or harassment, exposed personal information, false health information, other) is hidden from everyone except its author and reviewed by the operator; contact details are in section 1. Medication, dose, side-effect and body-measurement records, including weight, are never accepted in public posts, and eating together and its notifications stay inside groups.

6. Providers and transfers

Google OAuth, Sign in with Apple and Supabase Auth support sign-in; there is no e-mail or phone sign-up. Account data, opted-in friend data and community data are held in the configured Supabase project. The primary database region shown in project settings is Seoul, Republic of Korea (ap-northeast-2). Google and Supabase may use additional locations or subprocessors for service operations and support. Processor and cross-border transfer details must be verified and added before public launch. No Google or Apple account connection occurs when you use the app without signing in.

6-1. Mobile advertising · addendum September 27, 2026

The iOS and Android apps use Google AdMob. Google may process IP addresses, device and app identifiers, ad impressions, clicks, video interactions, and diagnostic and performance information for advertising, fraud prevention and measurement. Development builds also connect to Google’s advertising service.

Hankkirang does not provide personal meal or health records, real names, searches, photos, backups or authentication sessions for ad targeting or analytics. The Android app does not request advertising ID permission, and the iOS app does not request tracking authorization. These settings do not mean that all device-data processing or tracking is absent. Where required, advertising privacy choices are presented, with a settings button to revisit available choices.

See Google’s advertising privacy information and its iOS and Android data disclosures. Cross-border processing, retention and rights-request details must be verified and included before public launch.

6-2. Optional encrypted cloud synchronization · Updated September 28, 2026

Devices synchronize personal record changes and deletions only after you turn on cloud data linking and consent for that account and device. Food and calorie records, meal plans, recipes, supplements, medications, weight, preferences and profiles are encrypted on your device before upload. The server stores account and device IDs, consent status, synchronization and key versions, times, the ciphertext and its encryption parameters. Photos attached to records are stored once as separate encrypted files; the server learns only their size and an identifier derived from your account key. Devices first check whether anything changed and download only changed content.

In standard security, a randomly generated account key is stored encrypted in Supabase Vault and provided after your sign-in and device linking consent are verified. No separate synchronization password is needed, but the operator can technically decrypt your records.

Enhanced security keeps the decryption key only in secure storage on your mobile devices; since September 29, 2026 it cannot be newly turned on, and accounts that already use it can keep it or switch to standard security. A new device signs in with the same account and connects with a one-time link key created on an already linked device. A link key expires one hour after it is created and becomes invalid once used or regenerated. The server stores only a verification hash, the encrypted key being transferred, and its expiry and use status; the secret and the plaintext key are never sent. If you lose every linked device, signing in alone cannot recover your cloud records. Enhanced security does not retroactively protect earlier server copies or data that was already exposed.

Account deletion removes the latest encrypted copy, the encrypted photos and the server-managed key. Turning linking off stops further transfers. Choosing Delete cloud copy in My data deletes the server copy, encrypted photos, server-managed key and link keys at once without deleting your account, and turns off cloud linking on every device. Records on your devices are not deleted; if the request fails, it is retried when you are back online. Photos you delete from your records are also deleted from the server when that change is synchronized (photos uploaded less than 10 minutes earlier, at the next synchronization). Changing the security mode re-encrypts records and photos with the new key before the previous copies and key are discarded. Earlier manual backups remain until you delete them or the account. A copy protected by an earlier synchronization password is converted after you enter that password once. Initial linking and conflicting changes require your choice after reviewing categories and counts. Signing in or purchasing does not turn on synchronization. Local records remain available offline.

6-3. Health app connection · Added September 28, 2026

Only when you connect it yourself from Settings or the Diet tab, the app reads weight, body fat percentage, BMI (Apple Health), workout duration and active calories from Apple Health on iPhone or Health Connect on Android (including values written by Samsung Health and InBody). The values are saved as diet records on this device only after the app shows you what it will import and you choose to import.

Values from the health app are not sent to Hankkirang servers, are not used for advertising or analytics, and Hankkirang does not write to the health app. Imported records are included only in the folder sync or cloud data linking you have turned on, like other personal records. After you disconnect, records already imported stay until you delete them, and you can revoke read access in Apple Health or Health Connect settings.

6-4. Community push notifications · Added September 29, 2026

Only when you turn on ‘Community notifications’ in Settings for a signed-in account in cloud mode, the app stores your phone’s push notification token, a random app installation identifier and the platform (Android or iOS) with that account. They are used only to notify your phone when someone in your groups shares a recipe or invites you to, or joins, a meal. Without an account or in local mode, no token is created or sent.

Notifications pass through Google Firebase Cloud Messaging (Android) and Apple Push Notification service (iOS) and carry only the kind of notification, the sender’s group nickname, the post identifier and a short hash that tells accounts apart. Health records such as meals, calories, supplements, doses and body measurements, and post contents, are never sent; the text is written on your phone. Notifications from people you blocked or about hidden posts are not sent.

The server deletes the token when you turn notifications off, another account turns notifications on on the same phone, the push service reports the token as no longer valid, or you delete your account. Switching to local mode does not contact Hankkirang servers: your phone stops showing notifications at once and deletes its push token, so the server's next attempt fails and its registration is deleted too. If deletion on the server fails, your phone stops showing notifications at once and deletion is retried in cloud mode. You can turn off Hankkirang notifications in your phone settings at any time.

6-5. Supplement and dose reminders · Added September 29, 2026

Only when you turn them on in Settings, your phone itself schedules reminders for the next seven days at the times set for your supplements and the scheduled times of your doses. Their contents and times are stored on this device only and are not sent to Hankkirang servers or any push service. By default they show no names, for example ‘Time for your supplements’ or ‘You have a dose due today’; supplement and medicine names appear only if you turn on ‘Show names in reminders’. Turning reminders off removes every scheduled reminder.

6-6. Sign in with Apple · Added September 29, 2026

If you sign in with Apple in the iPhone app, Supabase Auth receives your Apple account identifier, your email (the relay address Apple creates if you choose ‘Hide My Email’) and sign-in session information, and processes them for the same purposes as Google sign-in (sign-in, account identification and friend connections); they are deleted when you delete your account. Your name is not requested. Google and Apple accounts are never merged automatically, even when the email is the same; a second sign-in method joins an account only when you link it yourself, confirming with that provider while signed in.

When you delete your account, the app asks you to confirm with Apple once more, revokes the Sign in with Apple connection (token revocation) and then deletes the account. The one-time authorization code and Apple’s tokens are used only for the revocation and are not stored. Apple’s own processing is described in the Apple Privacy Policy.

7. Your rights and security

Settings offers account deletion, local record deletion and backup, and a server account-data export; you can revoke friend sharing, delete community posts and comments at any time, and download the community data you created together with your account data. Without accepting changed terms you can still stop sharing with friends or disconnect, delete your posts, comments and groups, leave groups, turn off public mode, and turn off cloud sync and delete the server copy; only posting and sharing anew wait for your acceptance. Contact us to exercise applicable access, correction, erasure, restriction and objection rights. Server access controls restrict friend data to the recipients you select. Material policy changes will be announced before they take effect. Account features are available only to users aged 18 or older.