Privacy Policy
How the HelloMi app and website handle personal information: what, why, where and for how long.
- Document version
privacy.v12- Last updated
- Effective date
If a translation differs from the Korean text, the Korean text prevails.
Contents
At a glance
- You sign in to use the app. Meal photos and records are kept on your device and with your account on our server in Seoul.
- AI photo analysis and the AI coach run only after two separate consents (health-related information and transfer abroad). Only what is needed goes through our server to the AI processor, and nothing is used to train AI.
- Analysis copies on our server (photos and results) are deleted automatically 30 days after the meal's last analysis activity.
- App usage records contain no photos, foods or health information, and error reports carry no value that identifies you.
- We use no advertising SDK, no advertising identifier and no third-party analytics, and we neither sell personal information nor provide it to third parties.
Personal nutrition references
Optional age, calculation sex, height, weight, activity and regional standards are used to calculate nutrition references. You can keep a food diary without providing them or consenting to health-profile processing. Comparisons use logged nutrient values, data availability and your confirmation that the day is fully logged. They are not diagnoses or supplement dosing advice.
App calculations and day-completion confirmations are processed on the device. Profiles and confirmations entered separately on the web stay in that account’s browser storage and are deleted on sign-out. Optional screening for supplement information does not ask for condition or medicine names. When you request coaching, the relative dates and counts of completed meals in the selected records go to the existing coach server; its calculated comparison states and evidence identifiers may go to the existing AI provider. Existing server processing and backup of coach profiles keep their separate consent and retention rules. This feature does not send raw body measurements or screening answers to a new external provider.
Optional analysis-completion notifications
If you enable analysis-completion notifications and allow system notifications, our server processes a push token, random installation identifier, account ID, platform, language, UTC offset, quiet hours, daily send limit, pause setting and update time. To deliver completion or failure notices, tokens, generic text and opaque event/request identifiers are sent over encrypted connections through Expo Push Service (650 Industries, Inc., United States) to Apple APNs or Google FCM. Notifications contain no photos, food names, calories, health information or entered content. Expo holds notification content only in memory and queues needed for delivery; subsequent delivery and retention follow Apple and Google policies. Our device registrations expire after 90 days without an update, and queued delivery/status records are deleted on the next cleanup after 24 hours. Registration is removed when an opt-out or sign-out request reaches the server, AI consent is withdrawn, or the account or server copies are deleted. Server processing may be delayed offline; notifications already handed off cannot be recalled. You can still view analysis results in the app if you decline notifications.
How do the app trial and store free trial differ?
Store free trials use the existing subscription-management processing. The store determines trial eligibility; RevenueCat and our server process entitlement, trial-period type, period, renewal and cancellation transaction details. The store handles payment-card information, which we do not receive. The processors and retention periods are the same as for Plus subscriptions.
1. General provisions and scope
WorkNPLAY Inc. (the controller, the "operator") publishes this policy under Article 30 of the Korean Personal Information Protection Act (PIPA) to protect personal information and handle related complaints. It applies to the HelloMi mobile app (iOS and Android), this website and the web dashboard, wherever you use them. Section 22 says where the service is offered and section 23 adds what users in some US states need to know.
- Contact: contact@hellomi.app · Business details: Terms, Article 20
2. Purposes of processing
We process personal information only for the purposes below. If a purpose changes, we tell you in advance and ask again for any consent it needs.
- Meal diary: storing photos, times, meal types, foods and portions and showing daily, weekly and monthly summaries and a photo calendar.
- AI analysis: estimating the foods and portions of a meal from its photo or from what you say or type, and calculating nutrition. For a food the food database does not have, AI estimates the nutrition values, which are shown as estimates.
- AI coach: suggesting one thing to try at the next meal from the goals you chose and your meal records, a weekly check-in, and answers to questions about your own records.
- Keeping your data with your account: keeping your records, photos, favorites, planned meals, personal profile and remembered choices with your account and showing them on your other devices and the web dashboard.
- Number display on the web dashboard (optional): showing or hiding nutrition numbers on the web dashboard as you chose when you applied your choice to the web from the app.
- Usage limits, the free trial and the paid subscription (Plus), and abuse prevention: counting analyses, checking the trial period and subscription status, keeping the trial from starting again when someone signs up again with the same sign-in method, and stopping abnormal use.
- Consent management and proof: recording which text you agreed to or withdrew, and when.
- Running and improving the service: understanding from app usage records how steps such as sign-up, the first record, the trial and the subscription, and features are used, and taking into account the cancellation reason you give, if any, before managing a subscription.
- Service emails: a welcome email, one reminder if no meal has been recorded after sign-up, and a notice before the trial ends, sent to the email address of the account. They are not advertising.
- Reliability and security: finding the causes of errors and crashes, and controlling access.
- Answering questions and requests to exercise your rights, and meeting legal obligations.
News and offers are emailed only with separate consent, off by default. Refusing does not limit the service. We do not target advertising using health information or sell personal information. Neither we nor the AI processor train AI models on your photos or records.
3. Personal information we process
The items and where they are stored, per feature. No feature asks for your name or phone number, and none collects your location.
| Feature | Items | Required or optional | Where it is stored |
|---|---|---|---|
| Photo meal diary (core) | Meal photos (copies in app storage), meal date, time and type, the capture time read from the photo, foods and portions you enter, edit or say, calculated nutrition values, favorites, planned meals, remembered choices (usual amounts, foods you chose, how many people shared the meal, how much broth you have), display and language settings | Needed for the service | This device and your account (our server); on the device, each account has its own storage |
| Age check | Your birth year (and month in the boundary year). The birth year is stored in your personal profile and used to calculate your reference values; the month is used only for the eligibility check. The result (eligible or not) is stored as a consent record. | Required | This device and our server |
| Guest account from the earlier version | A random anonymous user ID, sign-in tokens (in the device secure storage), when the account was created and last used, the app language, the last UTC offset, a hash of the user ID | Created in app version 1.0 when you first turned on AI analysis or usage statistics or asked for marketing emails. The current version creates none; after updating, signing in moves the device’s records to that account | This device and our server |
| Sign-in | The sign-in method (Apple, Google, Kakao or email), your member identifier there, when it was linked, and what the method sends (it differs by method; see "Email" and "What sign-in providers give us" below). The user ID, sign-in tokens (in the device secure storage), when the account was created and last used, the app language, the last UTC offset, a hash of the user ID. | Required (you sign in to use the app) | This device and our server |
| Account sync | Meal records (date, time, meal type, foods, portions, nutrition values), copies of the meal photos made again on the device (2048 px long edge for viewing and a 512 px thumbnail; location and other photo data are left out when they are made — the original photo never leaves the device), favorites, planned meals, remembered choices, content-free markers of deleted records. How far each device has synced is stored only on that device. | Required (signed-in accounts) | Our server (Seoul (ap-northeast-2)) |
| Web dashboard | Shows the records and photos kept with your account. The browser keeps only the sign-in session and display settings (no cookies). | Optional (Plus and the trial) | Your browser's storage |
| Number display setting for the web dashboard | A single on/off value: whether the web dashboard shows or hides nutrition numbers. We store it when you apply your current choice to the web in the app. If you never have, it stays at the default (hidden), and the web also hides the numbers whenever it cannot read the value. | Optional (signed-in accounts) | Our server (Seoul (ap-northeast-2)) |
| AI analysis (photos, and logging or fixing a meal by speaking or typing) | The meal photo (JPEG) with location, capture time and other metadata removed, its size and hash, the meal type, the app language, meal and photo IDs created by the device. When you log or fix a meal by speaking or typing, what you said or typed and the food names and portions of that meal. Results: estimated foods, portions and nutrition values, the model used, processing region and token counts. AI nutrition estimates for foods the food database does not have are stored with only the food name and the values, without any user information, and reused for foods of the same name | Part of the required consents (two separate consents; can be withdrawn later) | Our server and the AI processor (transfer abroad) |
| Personal profile | Goal, birth year or age or age band, height, weight, the energy formula (the male or the female equation; not your gender identity), usual activity, whether a special situation applies (pregnant or breastfeeding, or under a professional’s meal plan), foods you do not eat (allergies and ingredients to avoid) and food preferences. Every item may be left empty. | Part of the required consents (separate consent for body information) | This device and your account (our server) |
| AI coach | The next-meal actions you chose and your check-in answers, weekly check-in results, questions you asked the AI coach and its answers (conversations), reports of an AI answer (an ID pointing to the answer, the reason, anything you wrote and — only if you turn it on — the reported AI text), content-free usage records | Part of the required consents (two separate consents; can be withdrawn later) | Our server and the AI processor (transfer abroad) |
| Server export | A ZIP file with everything our server keeps for the account: the account (sign-in method names and link times), the account details (app language, last UTC offset, when it was created and last used, the number display setting for the web dashboard), consent records, the records, photos and deletion markers kept with the account, the AI analysis copies (requests, results, run records, photos), the AI coach records (profile, chosen actions, check-in answers, weekly check-ins, questions and answers, reports about AI answers), the analysis-limit usage and the app usage statistics. It serves your rights of access and portability (PIPA Articles 35 and 35-2), so every account gets it, on Free and on Plus. One at a time and up to 3 a day; each download link works for 15 minutes. It also contains favorites, planned meals, remembered choices, speak-to-fix usage, step records, cancellation reasons, the service email log and the re-signup check records of the account’s sign-in methods. | When you ask for it | Our server |
| App usage records | Event name code, time, local date, entry point, small code values (screen code, logging method, photo count, kind of field edited, kind of analysis outcome, calendar view, reaction to a feedback card), OS, app version, device region (country code). Step records (onboarding steps, first analysis, sign-up, permission answers, payment screen shown or closed, trial start and conversion, limit reached, notification settings, visits) and whether a step was kept on the device before sign-up. No foods, photos, health values or text you wrote | Part of the required consents | Our server |
| Consent records | The user ID and its hash, consent item, granted or not, text version, time, app version, platform (iOS or Android) | When the app uses our server | This device and our server |
| Usage-limit and trial records | A hash of the user ID, the period (local date and month), reserved, committed or released state, times, when the free trial started (when the account was created) | When you use AI analysis | Our server |
| Re-signup check record | A value made from the sign-in method that cannot be turned back into it, when the trial first started with that method, when it was last checked, and hashes of the user IDs of the accounts that use it now. When an account is deleted its hash is removed, and only that account’s analysis counts per day for the last 62 days are kept instead. Neither the email address nor the raw member identifier of the sign-in method is stored. | When you sign in | Our server |
| Paid subscription (Plus) | Our server: plan, status (active, grace, expired, revoked), expiry time, and the subscription transaction records (store, product, transaction ID and original transaction ID, event type, purchase, renewal, expiry and event times, price, currency, store country, live or test environment). The subscription processor: user ID, store transaction ID, product, purchase, renewal, cancellation and refund times, price and currency, store country, platform. No other details such as your name or email go to the processor. Card numbers and other payment details are handled by the app store; we never receive them. | When the Plus screen first loads the prices (user ID), and at each purchase, renewal, cancellation and refund | Our server and the subscription processor |
| Cancellation reason | The reason you chose before managing a subscription (one of the given options), your plan at the time (trial, Plus or Free) and the time | Optional (only if you answer) | Our server |
| Error and crash reports | Error type and a masked message (app and web; the server sends only an error code), the stack trace without local variables, app version, environment, OS name and version, device model, browser or runtime name and version, the page or API route pattern (no values), request number, status and error code, time, event ID | Needed for the service | The error-report processor (transfer abroad) |
| Questions and requests | Email address, the content of your message, and when you write from the app, the app version, platform and support reference | When you contact us | Our support mailbox (mail processor) |
| In-app feedback | The text of feedback you send in the app (a problem or a suggestion), one screenshot you attach to a problem (optional), diagnostics attached automatically (app version, OS, device model, language, plan, theme, recent error codes), and what you type when asked why you came back (optional). No meal, photo or health information and no email address is attached. | When you send it | Our server |
| How you found the app | The store country code, the source code of the install, and your answer to one question about how you found the app (optional, one of the given options). Stored with the app usage records. | Part of the required consents (the survey answer is optional) | Our server |
| Service emails | The kind of email sent (welcome, meal reminder or trial-end notice), when it was sent and the result. The address is read from the sign-in records when the email is sent and is not stored separately. | Signed-in accounts with an email address | Our server and the email processor (transfer abroad) |
If you choose email and password authentication, your email address and password are sent over an encrypted connection to Supabase Auth for signup, sign-in and password resets. Supabase stores your email address and a password hash, not the plaintext password. The address is also used for verification, recovery and account-security emails. Authentication records are deleted with the account; stopping marketing emails does not delete your sign-in account.
We store your chosen marketing email address, account ID, consent time, source, text version and language, address verification status and time, and hashes of verification and unsubscribe tokens on our server. These support address verification, news and offers, and consent management. No marketing is sent before address verification; consent older than two years is excluded until reconfirmed.
Information created or sent automatically
- When the app uses our server, each request carries the app version, OS, device region code, UTC offset and app language. The server stores the OS, app version and country code only with usage events, and the app version and platform only with consent records; it uses the offset only to determine the periods of the usage limits (local date and month) and when the free trial ends.
- For people who leave before signing up we keep only a count per day and step. These counts store nothing that identifies a user or device, and no IP address.
- Server logs keep only allow-listed fields: request number, route pattern, status code, duration, error code, event code, model name, input and output token counts, cache token counts, reasoning token count, stop reason code, refusal category code, format check rule codes, a hash of the user ID, subscription event type. They never contain photos, food names, request or response bodies, or the raw user ID.
- As part of internet traffic, IP addresses and browser or app details reach the server and hosting providers and the error-report processor. The server host's access and sign-in logs (IP addresses included) are deleted within 7 days at most. The error-report tools in the app and on the web are set not to attach IP addresses to reports. The error-report processor is also set, in every project, not to store IP addresses.
- The app requests camera permission and, if you enable notifications, notification permission. Meal-reminder times stay on your device. If you choose analysis-completion notifications, our server and Expo, Apple and Google notification services process a push token and notification settings. Notifications contain no photos, food details or health information. The app does not request location, microphone or full photo-library access; it reads only photos selected in the system picker. Keyboard dictation is an operating-system feature.
What sign-in providers give us
- Apple: your member identifier and an email address (if you choose to share it; with Hide My Email, a relay address Apple forwards).
- Google: your member identifier, email address, name and profile picture address.
- Kakao: your member identifier and whatever you agree to share on Kakao’s consent screen (nickname, email address, profile picture). All of them are optional; you can sign in without them.
Sign-in details are stored in Supabase authentication records. The email is used for account-security notices and may be shown for confirmation or editing when you choose marketing emails. Marketing requires separate consent and address verification. We do not use names or pictures for other purposes. Authentication records are deleted with the account. Each company runs its own sign-in. Their policies: Apple, Google, Kakao.
What the AI coach sends and does not send
- Next-meal suggestion: the app language, the goal and situation you chose, meal facts (a number used only inside the request, relative date, meal type, kind of place, food-group tags, certainty, kind of source), the list of candidate suggestions the server picked, the status and check-in results of past actions, limit codes.
- Weekly check-in: the app language, the action sentence, a count of your check-in answers made by code, the number of meals and days logged.
- Asking the AI coach: the app language, the screen the question came from, your question as written, the recent turns of the same conversation (at most 6 exchanges; the app’s ‘See what is sent’ shows how many are actually sent, which can be none), the current action sentence and its check-in result, meal facts (as above). A question that needs a safety answer, such as medical, medication, pregnancy, breastfeeding, eating-disorder or emergency questions, sends nothing; the app shows a fixed answer instead.
- Not sent: the raw values of height, weight and age, the energy formula, numbers calculated from your profile, nutrition values of meals, food names, meal or user IDs, original photos or photo metadata, address or location, exact times, name, email, phone number or sign-in details. Numbers are calculated by our code and added on screen; they are not sent to the AI. However, your question to the AI coach and any earlier conversation sent with it go as written, so anything you type there (for example a food name) is sent with it.
- The meal information of a coach request is held in memory only while the request is handled and is not stored. No long-term memory is built from your conversations.
4. Sensitive information (health-related)
Meal photos and the foods and nutrition estimated from them, meal records and body measurements may count as health information, so under PIPA Article 23 we ask for this consent separately from other consents. When you start, the consent screen sets out these items, and tapping "Agree to all required items" records each of them separately with its text version. Going back or closing the screen is not consent, and without agreeing you cannot start the service. If you withdraw later, only that AI feature turns off; the photo diary and manual entry keep working.
| Feature | Consent items (text version) | Withdrawal |
|---|---|---|
| AI photo analysis | Health-related information, transfer abroad (consent.ai.v2) | My profile > Manage data > Withdraw required consent. The whole required consent is withdrawn, so AI analysis, the coach and app usage records stop together. New uploads stop at once and pending analyses are cancelled; when the withdrawal reaches our server, the photos, analysis requests, results and run records there are deleted. Results already on your device stay there. To turn them on again, tap My profile > Manage data > Turn on again. |
| Personal profile | Server processing of the body information you choose (consent.profile.v2) | Turning it off deletes the profile on our server; you can keep logging and using the coach without numbers. |
| AI coach | Health-related information for personal coaching, transfer abroad (consent.coach.v3) | Turn the coach off. Pending requests stop and their results are discarded, and the coach records on our server (chosen actions, check-in answers, weekly check-ins, questions and answers, caches) are deleted in the same step. |
If a consent text changes, the app asks again, and the feature stays off until you agree again.
5. Retention periods
Turning this off in settings or using an email unsubscribe link stops new marketing sends and immediately deletes the marketing address, consent details and tokens when the request reaches our server. Already dispatched mail cannot be recalled. Unverified addresses expire after 24 hours and are cleaned up. We keep only the account ID and withdrawal time for seven days as a minimal record of processing the request, and keyed hashes and counts for up to 24 hours to prevent verification-email abuse. Account deletion removes account-linked marketing records too. The sign-in email and security notices are separate from marketing withdrawal.
To prevent duplicate sends, we keep account and campaign identifiers and sending-attempt status valid for up to 24 hours, without the email address or message body. Expired verification, withdrawal, delivery and abuse-prevention records are deleted by the next daily cleanup. Marketing consent details follow the withdrawal deletion rule above, not the general service-consent proof retention below. The temporary abuse-prevention counters follow the same expiry after withdrawal or account deletion.
| Information | Retention | Notes |
|---|---|---|
| Records on this device | Until you delete them or the app; deleting the account also removes that account’s records on this device | We cannot access them. |
| Analysis copies on our server (photos, requests, results, run records) | Deleted by a daily cleanup job 30 days after the meal's last analysis activity | Deleted as soon as the request reaches our server when you delete the meal, withdraw AI consent or request deletion of server copies. |
| Meal markers (meal ID, server arrival time, deletion flag, IDs of purged photos) | Until a server-copy deletion request, the account deletion or the guest clean-up | No food or photo content. It keeps a deleted meal from coming back through a late request. |
| Records, photos, favorites and planned meals kept with the account | Until you delete the account | Deleting a record removes its content and photos at once; only a content-free marker that tells your other devices about the deletion stays while the account exists. |
| Remembered choices | Until you delete the account or clear them in the app | You can clear them in the app at any time. |
| Server export files | 7 days after creation | — |
| App usage records | 400 days after our server receives them | Deleted with a server-copy or account deletion request. |
| Cancellation reason | 400 days after you answer | Deleted with the account. |
| In-app feedback | Until you delete the account | What you typed about why you came back: 400 days after we receive it |
| Service email send records | Until you delete the account | — |
| Guest account from the earlier version | Until it is deleted; if it is not used for 365 days it is deleted automatically with all its server data | A guest account has no contact details, so we cannot warn you in advance. Records on your device stay. |
| Signed-in account and its linked sign-in methods | Until you delete the account | Deleting the account unlinks Kakao and revokes the Sign in with Apple authorization. |
| Number display setting for the web dashboard | Until you delete the account | A server-copy deletion request also removes it, and the web then hides the numbers again; applying your choice to the web from the app stores it again. |
| Free trial start record | While the account exists | It keeps the trial from restarting when server copies or device records are deleted, and goes with the account. |
| Re-signup check record | 13 months after it was last checked | Kept apart from the account and not deleted with it. Used only so that signing up again with the same sign-in method does not start a new trial and the month’s usage keeps counting. |
| Subscription status | While the account exists | — |
| Subscription transaction records | 5 years after the transaction | Kept as the Korean E-Commerce Act requires for payment and supply records. When the account is deleted the link to your user ID is cut and the records are kept apart under a hash only, then deleted when the period ends. |
| Consent records | While the consent stands, then 3 years after its withdrawal, the account deletion or the guest clean-up | Kept to prove consent; after a deletion request the link to the user ID is cut and only a hash remains. |
| Usage-limit ledger | 13 months after the end of the month it counts | A content-free usage record. A deletion request cuts the link to the user ID and keeps only a hash. |
| Deletion request receipts | 3 years after completion | Only a hash of the user ID, the scope and the times, so a repeated request is processed once and the deletion can be shown. |
| Coach records | Actions: 90 days from creation (90 days from refusal for a declined action). Check-in answers and weekly reviews: 90 days from initial creation. An action is also kept until the fixed expiry of any check-in answers still retained for it. Conversations with the AI coach: 30 days from the start of the conversation. Content-free usage records: 30 days | Deleted at once when you turn the coach off or delete a conversation or everything. Viewing, resending the same request or editing a check-in answer does not extend retention. |
| Personal profile on our server | 365 days after its last edit | Deleted at once when you turn the body-information consent off or delete the account. |
| Reports of an AI answer | 30 days after handling (at most 90 days after receipt) | Used only to handle the report; it stays until handled even if you turn the coach off. |
| Error and crash reports | Up to 90 days after the processor receives them | — |
| Server access and sign-in logs | 7 days at most | There are no automatic backups of the server database. |
| Website access logs | The host's (Vercel) standard retention (runtime logs up to 1 day) | — |
| Support email | 3 years after the matter is closed | The period the Korean E-Commerce Act sets for complaint and dispute records. |
| AI processor (Anthropic, PBC) | Anthropic, PBC does not use your photos to train AI. It deletes what it receives within 30 days, but if it is flagged as a possible policy violation it may be kept for up to 2 years and its safety classification scores for up to 7 years, with exceptions where the law requires retention. | The processor's retention policy |
If another law requires us to keep some information, we keep it apart from other information and only for that period.
6. How information is destroyed
- We destroy information without delay when its retention period ends or its purpose is achieved.
- Server: database rows are deleted and photos and files are deleted through the storage service. If a deletion fails, it stays on a retry list until it succeeds.
- When you withdraw a consent (AI photo analysis, app usage statistics, the AI coach or the personal profile) or delete your coach records, any server export file that may contain that information is deleted as well. Make a new export if you need one.
- Device: My profile > Manage data > Delete all records on this device erases every record in the database so it cannot be recovered (the file is rewritten), and removes photos, drafts and settings. If the app stops halfway, it finishes on the next launch.
- Deleting the app: the operating system removes the records on the device with the app. On iOS, sign-in data kept in the Keychain (secure storage), an age check result that blocked use, and a server deletion request not sent yet can remain after the app is deleted. A reinstall drops the unsent deletion request, and it does not use the old sign-in data, which is deleted or replaced when the app next connects to our server. The age check result still applies after a reinstall. Analysis copies on our server are deleted automatically 30 days after the meal's last analysis activity. On Android, app data backup is turned off. iOS device backups (iCloud or a computer) are your own backups under your settings and may include app data.
7. Provision to third parties
We do not provide personal information to third parties, except where a law specifically requires it or an investigating authority demands it through a legal procedure. AI analysis and coaching, the server, subscription management, error reports and support mail are processing on our behalf, described in sections 8 and 9. You pay the app store (Apple App Store or Google Play) directly, and the store handles payment under its own responsibility.
8. Processors
| Processor | Task | Agreement |
|---|---|---|
| Anthropic, PBC | AI photo analysis (estimating foods and portions) and AI coach answers | Commercial Terms and Data Processing Addendum |
| Supabase Pte. Ltd. | Server database, account sign-in, photo and file storage, running server functions | Data Processing Addendum |
| Vercel Inc. | Hosting and delivering this website and the web dashboard pages | Data Processing Addendum |
| Functional Software, Inc. (Sentry) | Error and crash reports of the app, the website and the server | Data Processing Addendum |
| RevenueCat, Inc. | Managing the purchase, renewal and cancellation status of the store subscription (Plus) | Data Processing Addendum |
| Plus Five Five, Inc. (Resend) | Sending account authentication and password-reset emails, address-verification emails, service emails, consented news and offers, and account-security notices | Data Processing Addendum |
| Google LLC (Google Workspace) | Receiving and storing support email | Data Processing Addendum |
Each processor uses the sub-processors (such as cloud providers) that its agreement above discloses. The agreements prohibit use for other purposes and cover security measures, limits on sub-processing, supervision and liability, and we supervise that the processors handle personal information safely. If a processor or its task changes, we update this policy without delay.
9. Transfer abroad
Our server runs in the Supabase Seoul (ap-northeast-2) region. In the cases below personal information is transferred outside Korea (processing or storage on our behalf). Every transfer uses an encrypted connection (TLS).
AI photo analysis and AI coach
| Item | Details |
|---|---|
| Recipient and contact | Anthropic, PBC · privacy@anthropic.com · 548 Market St, PMB 90375, San Francisco, CA 94104, USA |
| Country | United States (every request uses the US-only processing setting inference_geo "us") |
| When and how | Each time an analysis or a coach answer is requested, through our server |
| Items | Photo analysis: the meal photo with location, capture time and other metadata removed, the meal type, the app language. Logging or fixing by speaking or typing: what you said or typed and the food names and portions of that meal. Nutrition estimates: food names. AI coach: what section 3 lists as sent. No name, contact details, user ID or meal ID is sent. |
| Purpose | To estimate the foods and portions in the photo and calculate nutrition, and to write coach answers |
| Retention | Anthropic, PBC does not use your photos to train AI. It deletes what it receives within 30 days, but if it is flagged as a possible policy violation it may be kept for up to 2 years and its safety classification scores for up to 7 years, with exceptions where the law requires retention. |
| Legal basis | Your separate consent (PIPA Article 28-8(1)(i)) |
| How to refuse, and what happens | If you do not agree, or withdraw with My profile > Manage data > Withdraw required consent, nothing is sent. Without agreeing when you start, you cannot start the service; if you withdraw later, only that AI feature turns off and the photo diary and manual entry keep working. |
Error and crash reports
| Item | Details |
|---|---|
| Recipient and contact | Functional Software, Inc. (Sentry) · legal@sentry.io |
| Country | United States |
| When and how | Automatically, each time an error occurs in the app, on the website or on the server |
| Items | The error and crash reports of section 3. No name, email or user ID, photos, food or nutrition values, health information, request or response bodies, device name, location, screenshots, or record of taps and screens. Native crash reports are built at the operating-system layer outside the app’s shared filter and carry only the stack, device model and OS, no app data. |
| Purpose | To find and fix errors and crashes |
| Retention | Up to 90 days |
| Legal basis | Processing on our behalf needed to perform our contract with you, disclosed in this policy (PIPA Article 28-8(1)(iii)). |
| How to refuse, and what happens | Error reporting is needed to provide a stable service and cannot be turned off on its own. If you do not want it, you can stop using the service and ask us to delete your account and data. |
Subscription (Plus) management
| Item | Details |
|---|---|
| Recipient and contact | RevenueCat, Inc. · compliance@revenuecat.com |
| Country | United States |
| When and how | For an existing HelloMi server account, the app sends its user ID when checking store-region update availability or loading Plus prices. The app and store send transaction information at purchase, renewal, cancellation and refund. Update checks do not create a new anonymous RevenueCat account. |
| Items | The paid subscription (Plus) items of section 3 |
| Purpose | To provide Plus access according to subscription status and check update availability using the storefront country code returned by the store. This code is not GPS location and is not inferred from the device language. |
| Retention | The processor's whole customer record is scheduled for deletion 5 years after the account is deleted (the retention period of transaction records). If a store subscription you did not cancel renews after that, the date moves to 5 years after the last transaction. |
| Legal basis | Processing on our behalf needed to perform our contract with you, disclosed in this policy (PIPA Article 28-8(1)(iii)). |
| How to refuse, and what happens | A regional update check may use the existing account ID before the Plus screen opens. An unavailable store country remains unknown. Free features remain available without a subscription. |
Server operations support
| Item | Details |
|---|---|
| Recipient and contact | Supabase Pte. Ltd. · privacy@supabase.com |
| Country | Singapore and the other countries where the server provider’s staff work (the data stays stored in the Seoul (ap-northeast-2) region) |
| When and how | By remote access when needed for incident response and operations support |
| Items | The information stored on our server |
| Purpose | Running the server reliably and responding to incidents |
| Retention | The retention of our server in section 5 |
| Legal basis | Processing on our behalf needed to perform our contract with you, disclosed in this policy (PIPA Article 28-8(1)(iii)). |
| How to refuse, and what happens | This processing is needed by features that use our server. You can turn off optional features or request account deletion. |
Website hosting
| Item | Details |
|---|---|
| Recipient and contact | Vercel Inc. · privacy@vercel.com |
| Country | The United States and the other countries of its delivery network |
| When and how | Each time you open the website |
| Items | Access logs (IP address, browser details, requested address, time). The dashboard’s records and photos go from our server straight to your browser, not through the host. |
| Purpose | To deliver and protect the website |
| Retention | The host’s standard retention (runtime logs up to 1 day) |
| Legal basis | Processing on our behalf needed to perform our contract with you, disclosed in this policy (PIPA Article 28-8(1)(iii)). |
| How to refuse, and what happens | Nothing is transferred if you do not open the website. The app works without it. |
Email · Resend
| Item | Details |
|---|---|
| Recipient and contact | Plus Five Five, Inc. (Resend) · support@resend.com |
| Country | United States (storage is independent of the sending region) |
| When and how | By encrypted transmission when an email is sent |
| Items | Recipient email, subject and body (including authentication or password-reset links and verification codes, marketing verification or unsubscribe links, service emails (welcome, meal reminder, trial-end notice), or security-event notices), sending time and delivery result. Passwords, meal data and health information are not sent to Resend. |
| Purpose | Sending account authentication and password-reset emails, address-verification emails, service emails, consented news and offers, and account-security notices |
| Retention | On standard Resend plans, email and delivery logs remain for 30 days and backups for seven days. Unsubscribing or deleting a HelloMi account does not instantly erase these already transmitted records. Contact us to request earlier deletion. |
| Legal basis | Processing on our behalf needed to perform our contract with you, disclosed in this policy (PIPA Article 28-8(1)(iii)). |
| How to refuse, and what happens | You can decline marketing or withdraw through settings or an unsubscribe link without losing service access. Authentication, password-reset, address-verification and account-security emails contain no advertising and are sent separately from marketing consent. |
Support email
| Item | Details |
|---|---|
| Recipient and contact | Google LLC (Google Workspace) · https://support.google.com/policies/contact/general_privacy_form |
| Country | The United States and the other countries of the mail service’s data centers |
| When and how | When you email us |
| Items | Your email address and message |
| Purpose | To answer your questions and requests |
| Retention | 3 years after the matter is closed |
| Legal basis | Processing on our behalf needed to perform our contract with you, disclosed in this policy (PIPA Article 28-8(1)(iii)). |
| How to refuse, and what happens | Nothing is transferred if you do not email us. |
10. Your rights and how to use them
You can ask at any time to access, correct or delete your personal information, to stop its processing, to withdraw consent and to receive your data. Using these rights never puts you at a disadvantage.
| Right | How |
|---|---|
| Access and copy | My profile > Manage data > Export my data: creates a ZIP of the meals, foods, nutrition and photos on your device (photo location data is removed). Everything our server keeps comes as a server export from the web dashboard's settings (Free and Plus alike). |
| Correction | Edit foods, portions, date and meal type in the meal's details. The values on your device are the record of truth; analysis results on our server are not edited but can be deleted. |
| Deletion | Delete a meal, My profile > Manage data > Delete all records on this device, My profile > AI & privacy > Request deletion of analysis copies on our server, My profile > Account > Delete account. See the deletion guide for details. |
| Stop processing, withdraw consent | My profile > Manage data > Withdraw required consent. AI analysis, the coach and app usage records stop together; to turn them on again, My profile > Manage data > Turn on again. To stop other processing, ask by email as below. |
Outside the app you can ask by email. Address: contact@hellomi.app. If you write from My profile > About & notices in the app, the mail includes the support reference we need to find the account. You can also ask through a legal representative or someone you authorize. We answer within 10 days of receiving the request; if we cannot finish in that time, we tell you why and when we will.
11. Children under 14
The service is only for people aged 18 or older. On first launch the app asks for your birth year with a neutral question that does not reveal the age limit, and stores only the result. If you are not eligible the app is blocked and sends nothing to our server from that device. We do not collect personal information of children under 14; if we learn that we have, we destroy it without delay.
12. Security measures
- Administrative: we keep and follow an internal management plan and limit the people who handle personal information to the minimum (the CEO).
- Access control: row-level security is enforced on every server table, so each user can read and write only their own data; anything else runs only under server-side roles limited to what the task needs. Photo storage is private, and the app uploads and reads only through signed addresses issued by the server.
- Photo metadata removal: before upload, the device always strips EXIF, XMP and IPTC metadata such as location (GPS) and camera details, and the server strips again by the same rules when it confirms the upload.
- Encryption: traffic between the app or website and the server, and between the server and the processors, uses encrypted connections (HTTPS/TLS), and data stored on the server is encrypted at rest. Sign-in tokens on the device are kept in the operating system's secure storage (iOS Keychain, Android Keystore).
- Minimal processing: secrets such as the AI keys exist only on the server, AI requests carry no user ID or meal ID, and server logs and error reports keep only allow-listed fields.
13. Automatic collection tools
- App: we do not collect advertising identifiers (IDFA, AAID) and do not track you across other companies' apps or websites. The app contains no advertising or third-party analytics SDK. We use the Sentry SDK for error and crash reports and the RevenueCat SDK for Plus subscription management; the data sent and the transfer timing for each are described in sections 3 and 9.
- Website: no cookies, no analytics, no advertising, no external fonts and no forms. If an error occurs, an error report goes to Sentry. The web dashboard keeps the sign-in session and display settings in the browser's storage (localStorage); they go when you sign out or clear the site data in your browser.
14. Behavioral information
We do not collect or share behavioral information for targeted advertising. App usage records are used only to run and improve the service, never for advertising, and are not given to third parties.
15. Pseudonymized information
We do not process pseudonymized information.
16. Automated decisions
AI estimates of foods, portions and nutrition and the AI coach’s suggestions are information you can check, change or decline; they make no decision about your eligibility, rights or obligations. They are therefore not automated decisions under PIPA Article 37-2.
17. Use of generative AI
AI photo analysis and the AI coach use a generative AI model. We say so beforehand on the consent screen, and the app labels what AI produced as 'AI estimate' or 'AI' everywhere (Korean AI Basic Act, Article 31). AI results can be wrong, so please check and correct them.
18. Not a medical device
19. Chief privacy officer
- Chief privacy officer: CEO (named as the representative in Terms, Article 20)
- Contact: contact@hellomi.app — there is no separate department; the officer handles requests directly.
20. Remedies
For advice or dispute resolution about a privacy infringement you can contact the agencies below (in Korea). You can also contact us first.
| Agency | Phone (in Korea) | Website |
|---|---|---|
| Personal Information Dispute Mediation Committee | 1833-6972 | https://www.kopico.go.kr |
| Personal Information Infringement Report Center (KISA) | 118 | https://privacy.kisa.or.kr |
| Supreme Prosecutors' Office | 1301 | https://www.spo.go.kr |
| Korean National Police Agency | 182 | https://ecrm.police.go.kr |
21. Changes to this policy
We announce a change in the app and on this website at least 7 days before it takes effect (30 days for a change to your disadvantage). If what you agreed to changes, such as a new processor, country or purpose, the app asks for your consent again. Changes are listed in the change log below.
22. Where the service is offered
HelloMi is not offered in the European Economic Area (the 27 EU countries, Iceland, Norway and Liechtenstein), the United Kingdom and mainland China, and the app is not listed in the app stores there. If you are there and need to reach us about this policy or your data, use the contact above.
If you are in Switzerland, the Swiss Federal Act on Data Protection (FADP) applies too. You can use the rights of section 10 (access, a copy, correction, deletion, withdrawing consent) as described there and complain to the Federal Data Protection and Information Commissioner (FDPIC). Transfers abroad are as in section 9.
23. Users in the United States (state privacy laws)
- We do not sell personal information, share it for targeted advertising, or profile you. There is therefore nothing to opt out of under "Do Not Sell or Share".
- Consumer health data (Washington My Health My Data Act, Nevada law and similar laws): the health-related data we handle is meal photos and their estimates and meal records, the personal profile and coach records. You provide it, we use it only for the purposes of section 2, and we share it with no one except the processors of section 8. We collect it and let processors handle it only after the consents of section 4.
- Rights: you can ask to confirm whether we process your data, and to access, delete, correct or receive it, or withdraw consent, as described in section 10 or at contact@hellomi.app. If you disagree with our answer, write again with "Appeal" in the subject; we answer within 45 days.
Change log
-
privacy.v12Sections 3 and 5 add in-app feedback (text, an optional screenshot, automatic diagnostics, the answer about why you came back) and how you found the app (store country code, install source code, an optional survey answer). Processors and transfers abroad are unchanged. This amendment takes effect on the day it is published. -
privacy.v11Signing in is now required to use the app, and no new guest accounts are created. Favorites, planned meals, the personal profile and remembered choices are also kept with the account, and the device stores each account separately. Consent is given once at the start by agreeing to all required items; app usage records moved into the required items and step records were added. For people who leave before signing up we count only a number per day and step. A re-signup check record keeps the trial from starting again when someone signs up again with the same sign-in method. AI nutrition estimates, logging and fixing by speaking or typing, service emails and cancellation reasons are added. Processors and the countries of transfer are unchanged; service emails are added to the email processor’s tasks. This amendment takes effect on the day it is published. -
privacy.v10The meal records and photos of a signed-in account are kept with the account without a separate backup consent and show on other devices and the web dashboard. The account backup consent and turning backup off are removed; records kept with the account stay until the account is deleted. To keep records on this device only, do not sign in. Support mail sent from the app includes the support reference automatically. Processors and transfers abroad are unchanged. This amendment takes effect on 16 November 2026. -
privacy.v9Added optional personal nutrition references, day-completion confirmations, nutrient-data availability and device/browser storage scope. -
privacy.v8Restores processing of account creation times and trial-start records to start the 14-day app trial and prevent restarts. Separate store trials are verified through existing subscription transactions and entitlements; other purposes, processors and retention conditions remain unchanged. -
privacy.v7Clarifies that new accounts receive no app-trial start record; separates earlier account and trial records used to preserve granted access and prevent restarts from store subscription transactions. -
privacy.v6Adds existing subscription processing for store trials and optional analysis-completion push data, Expo and Apple/Google delivery, retention and withdrawal; distinguishes local meal reminders. -
privacy.v5Added optional marketing email collection, purposes, withdrawal and deletion; account-security notices; and Resend processing, US transfers and delivery-record retention. This amendment takes effect on 22 October 2026. -
privacy.v4Section 3: notification permission added. If you turn on reminders, the app requests notification permission; reminder settings and times stay on your device and are not sent to our server, and notifications show no meal details or health information. The personal information we process, our processors, transfers abroad and retention periods are unchanged. This change took effect on the day it was published because the app had not been released and no one had an account; once there are users, changes are announced in advance as section 21 describes. -
privacy.v3Final text: sign-in, account backup, the web dashboard, the paid subscription, error reports (Sentry) and the support-mail processor added; transfers abroad set out per recipient; retention periods settled (consent records 3 years, guest accounts deleted after 365 days unused, and others); the AI processor's contact and retention completed; where the service is offered (not the EEA or the UK) and notices for users in Switzerland and the US added; the operator details gathered in the Terms (Article 20) and the officer shown by title and email. -
privacy.v2-draftOperator details (name, representative, business registration number), chief privacy officer and support email added (draft). -
privacy.v1-draftFirst draft. Server copies 30 days, usage statistics 400 days, deletion completed within 30 days.