Kkirok Privacy Policy
Effective date: October 21, 2026
1. Personal Information Processed and Purposes of Use
| Category | Items Processed | Purpose of Use |
|---|---|---|
| Sign-up and Login | Email address, Apple/Google user identifier, login provider, authentication/session tokens or their encrypted values/hashes | Identity verification, maintaining login, account protection |
| Meal Records | Food name, meal type, record date, intake amount, calories and nutrition information, calorie goal | Saving, viewing, and editing meal records and providing statistics |
| AI Analysis | Food photos or search terms selected by the user, analysis results, image hashes, model, processing time, and token usage | Food recognition, nutrition information estimation, quality improvement, and error handling |
| Dose and Weight Records (Optional) | Medication name, actual single dose (mg), dose date, optional time, time zone, whether it is the first dose, optional memo; measurement date, weight (kg), optional time, time zone; version and time of separate consent | Managing dose and weight history for members who have given separate consent, and date-based viewing linked with existing food records. This information is not transmitted to external AI or external analytics SDKs. |
| Subscription | Product ID, Apple transaction identifier, hash of the Google Play purchase token, order ID, base plan, offer, subscription start, purchase, and expiration times and status | Verifying Apple and Google Play subscriptions, providing paid features, preventing duplicate and fraudulent use |
| App Usage Step Records | Server-side hash of a random usage-flow identifier created on the device, platform and app version, screen step and success/failure, server receipt time | Error handling and usability improvement for the startup, authentication, and first-record process. In apps that support this feature, it is sent to Kkirok's own servers while the service is in use and is not provided to advertisers or external analytics SDKs. It does not include food names, search terms, photos, calories, medication or weight values, advertising identifiers, or account identifiers. |
| iOS Install and Ad Performance Statistics (Optional) | App instance identifier, device, operating system, and app information, basic app events such as first launch, sessions, and app updates, approximate region derived from temporary processing of the connecting IP address | Measuring install sources and ad performance through Google Analytics and Google Ads. Collected only in supported live iOS apps when the user turns on “Share Install Statistics.” Health and meal records, photos, search terms, email, Kkirok account ID, and advertising ID are not sent, and the data is not used for ad personalization or remarketing. |
| Service Operation | Request time, error code and processing status, temporary processing of IP address, usage records | Security, incident response, usage limits, and prevention of fraudulent use |
The camera and photo library are accessed only when the user takes or selects a photo. Kkirok does not keep original photos in its own storage; they are processed in memory and then used for the AI analysis request.
2. Collection Methods
App usage step records are generated automatically during the start screen, authentication, search, analysis, and record-saving processes. No separate participation consent screen is displayed. A random flow identifier that is not linked to the account is used; on logout, the current flow is reset and server deletion is requested. Information not deleted due to communication failure is also cleaned up no later than 30 days after receipt begins. Figures may differ from actual user or install counts due to app reinstallation, multiple devices, or offline use.
iOS Install Statistics Sharing is a separate optional feature. It is off by default, and the relevant Google Analytics SDK is not started until it is turned on in Profile settings. Turning it off stops further collection and also withdraws consent for ad measurement. You can use the app's other features even if you do not opt in. These statistics are separate from the “App Usage Step Records” on Kkirok's own servers described above, and automatic screen name collection and collection of the advertising ID and identifier for vendors (IDFV) are not used. Google signals, collection of granular location and device information, and ad personalization are also not used.
Dose and weight records are an optional feature. You can use existing food records, search, and subscriptions without separately consenting to the collection and use of health information. You can withdraw consent in the feature's consent management; upon withdrawal, dose and weight history is deleted, but existing food records are retained.
Apple Health weight sync and Android Health Connect weight sync are separate optional features. If the user consents to health information processing for their Kkirok account and to the import period, and allows weight reading in the health app, the weight, measurement date and time, source, and identifying information for duplicate and deletion handling are stored on the server for that account. Kkirok does not write or delete records in the health app and does not provide imported health information to external AI or ad analytics.
Health Connect requests only reading weight for the period selected by the user, and does not request other health data types or write permission to the health app. Records older than 30 days are imported only if the device supports the additional historical-data read permission and the user allows it. Even if permission is revoked or the read result is empty, weights that have already been imported are not automatically deleted.
In new app versions that support disconnecting and deleting imported weights, imported weights (including imported records that were edited or selected as the representative value) are deleted after the number of entries and the period to be deleted are confirmed. Only weights imported from the disconnected provider are deleted; manually entered weights, weights imported from other providers, and the originals in Apple Health and Health Connect are retained. Merely stopping the connection in older versions does not delete records. The minimum source identifying information needed to prevent re-import of deleted originals and request-retry verification information are kept while the relevant health information consent remains in effect, and are deleted together upon consent withdrawal or account deletion. Measurement values are not kept in this deletion verification information.
- When members enter information directly in the app or select photos
- Information transmitted during Apple and Google login and Apple in-app purchase and Google Play billing
- Minimum usage and error records automatically generated on the server during service use
3. Retention and Use Period
App usage step records: Up to 30 days from the start of receipt. Deletion of the relevant flow is requested on logout, and disaster recovery backups are kept for up to 30 days.
Optional iOS install statistics: The Google Analytics user and event data retention period is set to 2 months, and period extension based on new activity is not used. This period may not apply to aggregated standard reports, and conversion data exported to Google Ads is subject to that service's retention policy. Withdrawing consent stops further collection and does not mean that information already transmitted is deleted immediately. Requests for deletion or suspension of processing can be submitted to the contact below.
- Account, meal, and user-linked analysis records: Retained while the member uses the service, and deleted immediately from the production DB upon account deletion.
- Optional dose and weight health information: Retained while the member uses the consented feature, and deleted from the service DB upon individual deletion, consent withdrawal, or account deletion. Hiding from the screen is not consent withdrawal or deletion. Disaster recovery backups are kept for up to 30 days, and deletions and withdrawals are applied upon restoration.
- Email verification codes: Valid for 10 minutes after issuance and processed only as a hash for verification.
- Identifiable operational logs and DB backups: Kept for up to 30 days. Backups are used only for disaster recovery, and upon restoration, the information of users who have already deleted their accounts is deleted again.
- Transaction records required to be retained by law: Records of contracts, order withdrawals, and payment and supply may be kept separately from other information for 5 years; records of consumer complaints and disputes for 3 years; and records of labeling and advertising for 6 months.
4. Provision of Personal Information to Third Parties
The Operator does not sell personal information and, in principle, does not provide it to third parties. However, it is provided only to the extent necessary where the user has separately consented or there is a legal basis.
5. Outsourcing of Processing and Overseas Transfer
| Processor / Destination Country | Items / Purpose | Timing / Method | Retention Period |
|---|---|---|---|
| Anthropic, PBC United States | Food photos or search terms consented to by the user, and analysis prompts AI food and nutrition analysis | Transmitted via HTTPS when the user requests an AI feature | Under the standard Anthropic API policy, inputs and outputs are deleted within 30 days of receipt or generation. Exceptions may apply for usage policy enforcement or legal compliance |
| Resend, Inc. United States | Email address, verification code, and verification email content Sending identity verification emails for sign-up | Transmitted via HTTPS upon email sign-up or resend requests | Email data 30 days. Upon contract termination, deletion procedures under the processor's policy apply |
| Apple Inc. United States | Apple user identifier and App Store transaction information Apple login, subscription payment, and verification | Processed via HTTPS upon Apple login, purchase, or subscription status change | Period in accordance with the Apple account, payments, and relevant laws |
| Google LLC (Google Analytics·Google Ads) Google's global processing facilities, including in the United States | App instance identifier, device/app information, basic app events, and approximate region for optional iOS install statistics Measuring install sources and ad performance. Excludes health and meal records, photos, search terms, email, Kkirok account ID, and advertising ID | Transmitted by the SDK via HTTPS after “Share Install Statistics” is turned on in Profile, and processed for measurement purposes in Google Ads linked to Analytics | Analytics user and event data 2 months (no extension based on activity). Aggregated reports and Ads conversion data are subject to the respective service's policies |
| Google LLC United States | Google user identifier and Google Play product, purchase token, order, and subscription status Google login, subscription payment, and verification | Processed via HTTPS upon Google login, purchase, or subscription status change | Period in accordance with the Google account, Google Play billing, and relevant laws |
Overseas transfer of install statistics can be stopped by turning off “Share Install Statistics” in Profile. Refusing does not restrict basic app features. Google's processing facilities and storage practices are described in the Firebase Privacy Information, Google Analytics Data Protection Information and Google Privacy Policy.
You may decline transmission to Anthropic or withdraw consent in the app settings. In this case, photo analysis and AI additional search cannot be used, but other features such as manual entry and general search remain available.
6. Destruction Procedures and Methods
When account deletion is completed, the account, meal records, user-linked AI analysis, usage, correction, and search requests, sessions, and OAuth information are permanently deleted in a single DB transaction, so that they are no longer accessed or used in the production service. Shared nutrition and search caches that are not linked to users and de-identified aggregate information may be retained.
7. User Rights and How to Exercise Them
- You can view, edit, and delete your meal records in the app.
- You can delete your account and linked information using the account deletion feature in Profile.
- You can withdraw consent to external AI data transmission in Profile.
- You can turn install statistics sharing on or off in Profile in supported iOS apps.
- Requests for access, correction, deletion, or suspension of processing can be submitted to the contact below.
Auto-renewing subscriptions must be canceled, separately from account deletion, in the subscription management screen of your Apple ID or Google Play; deleting the app or deleting your Kkirok account alone does not automatically cancel the store subscription.
8. Security Measures
The Operator applies reasonable safeguards such as encryption in transit (HTTPS), encrypted or hashed token storage, access permission restrictions, administrator authentication, DB backups, and review of error logs.
9. Children Under 14
Kkirok is not provided for children under the age of 14, and if it becomes known that information belongs to such a user, it will be deleted after the necessary verification.
10. Changes to This Policy
If this Policy is amended due to changes in laws or the service, notice will be given through the app or service screens before it takes effect. For material changes, separate consent will be obtained where necessary.
11. Privacy Inquiries
Operator: JHSoft
Email: kkirok.app@gmail.com