Eat IT Privacy Policy
Effective date: October 14, 2026
Service: Eat IT
Controller: Eat IT Operator
Contact: [email protected]
The Eat IT Operator ("Operator") establishes this Privacy Policy to protect users' personal information and handle privacy-related inquiries.
1. Purposes, Items, and Retention
The Operator processes personal information necessary to provide the Service.
| Category | Purpose | Items | Retention |
|---|---|---|---|
| Sign-up and login | User identification, account management, session maintenance, fraud prevention | User identifier, email address, name or nickname, profile image URL if provided, login provider, sign-up time, recent login time | Until account deletion |
| Ingredient management | Ingredient registration, editing, deletion, expiration-date management, ingredient matching | Ingredient name, category, quantity, unit, expiration date, ownership status, creation and update time. In a shared fridge, its ingredients, shopping list and your fridge nickname are visible to the members, and the invitation and membership are stored | Until account deletion or user deletion. Items you put in a shared fridge that still has other members stay with that fridge, without your account information, after account deletion |
| Recommendations and recipes | Ingredient-based recommendations, request reflection, recipe adjustment, quality improvement | Ingredient information, liked/disliked foods, allergies, meal style, household type and size, meal goals, cooking time preference, user requests, generated results | Until account deletion or user deletion |
| Gender and age | Ordering recommended video recipes, showing suggested Price Map searches, and showing which supplements peers take, based on aggregates of users of the same gender and ten-year age band | Gender (male or female), age. Required during initial setup | Until account deletion |
| Daily calorie target | Calculating the daily calorie target in the food log (together with gender and age) and showing weekly weight change | Height, weight, usual activity level, goal (lose, keep, or gain), a daily calorie target set by hand, and weights the user logs by date. Optional; without it the standard for the user's gender and age is used | Until account deletion. The target settings such as height, activity level, and goal can be cleared by the user with "Back to the standard", and each weight entered by date can be deleted from the weight list |
| Cooking records and eating patterns | Cooking completion and meal records, ingredient deduction, recent pattern display | Recipe name, ingredient list, cooking steps, cooking time, servings, used/deducted/skipped ingredients, completion time, meal date and slot, dish name, eating-out or skipped-meal status, estimated nutrition. When a meal is logged from a photo, that meal photo (a downscaled copy with location and other capture metadata removed). The photo is served only through expiring links issued to the user, and is deleted when the record is deleted or the account is deleted | Until account deletion or user deletion |
| Shared dining and preference groups | Reflecting preferences of people who eat together | Group name, member name, liked foods, disliked foods, group type | Until account deletion or user deletion |
| External purchase links | Connecting missing ingredient links, confirming purchases after returning to the app, reflecting purchased quantity | Clicked ingredient name, link URL, purchase confirmation, quantity and unit entered by the user | For the period necessary to provide the feature and handle errors |
| Receipt analysis and price records | Receipt-based ingredient registration and neighborhood mart price analysis and display | Store name, address, store phone number, purchase date, total amount, purchased product names (food and non-food), quantity, unit, and price extracted from receipt photos, and the recognized receipt text with payment identifiers masked. Non-food products are used only as price data and are not added as ingredients. Original receipt photos are not stored. Prices are shown to other users on the Price Map without identifying who submitted them | Until account deletion (the app has no per-receipt delete; send a deletion request through the contact address). On account deletion the recognized receipt text is deleted, and the store, purchase date, total, items and prices are kept with identifying details removed |
| Push notifications | Sending service notifications (ingredients, community, chat), and counting which notifications were opened to adjust their timing and number | Push notification token, app installation identifier (a random value created by the app), device platform, language, time zone, record of notifications sent (type and time sent) and the time a notification was opened | Until account deletion |
| Location | Neighborhood verification; searching the Price Map, nearby stores and dining suggestions around your current position | For neighborhood verification: the device's latitude and longitude, location accuracy, the verified province and district, and the verification time (valid for 30 days). For the Price Map and dining suggestions: latitude and longitude at the time of the request, used for that search only and not saved to your account. Your verified neighborhood name and an approximate distance are shown to other users in the community. When you publish a sharing post, the verified position is saved with the post to calculate distance (the coordinates are not given to other users), and the hand-off place you pick on the map is public on the post | Verification data is replaced when you verify again and kept until account deletion. A position saved with a post is kept until the post or the account is deleted. Positions used for searches are not stored |
| Community and chat | Posts, comments, sharing posts, reviews and chat; handling reports; usage restrictions | Nickname, handle, content and photos of posts, comments and reviews; likes, saves, follows, friends, blocks and reports; chat messages and photos. Posts, comments and nicknames are visible to other users. Chat messages are stored on the server and may be reviewed by the Operator to handle reports. Community and chat photos are served from hard-to-guess addresses that anyone who has the address can open without signing in | Until account deletion or user deletion. A post or comment you delete stops being shown to other users at once, and its record stays on the server. Public posts, comments, reviews and recipes may remain after account deletion with the author's details removed |
| Search and activity | Aggregating suggested Price Map search terms, improving dining suggestions, aggregating supplement use among peers | Price Map search terms (per account and day), dining suggestion usage records (search terms, the restaurant you chose, your rating and note), taps on supplement purchase links | Until account deletion |
| Ad display records | Preventing invalid traffic and fraudulent clicks; confirming rewarded-ad points | Member identifier, ad placement and format, impression, click and reward events with time | For as long as needed to prevent invalid traffic and fraud. After account deletion they are kept only with a de-identified account number |
| Supplements | Registering supplements, intake records, ingredient analysis and caution notices | Supplement product name, ingredients, dose, schedule, intake records, favorited products | Until account deletion or user deletion |
| Shopping list | Managing items to buy and comparing prices | Item name, quantity, how the item was added (recipe, search and similar), product details (brand, package size, last seen price) | Until account deletion or user deletion |
| Support and inquiries | Responding to inquiries, checking errors, handling disputes | Email address, inquiry content, attachments, processing records | Up to 3 years after handling, or as required by law |
| Service usage and security | Stability, error analysis, fraud prevention, statistics | IP address, access records, device and usage environment information, app version, error records, sign-in persistence information, app error and performance diagnostics (including member identifier, OS version, app and update version) | Until account deletion or as required by law |
Recommendation, text analysis, receipt and meal photo analysis, and recipe adjustment features may be provided through external processing services. In that case, the Service sends only the minimum ingredient information, preferences, allergy information, requests, cooking records, receipt or meal image, or recipe context needed to provide the feature. The Service does not intentionally send account-identifying information such as name, email address, or profile image URL to the external processing service. Supplement information and ingredient photos are processed in the same way, and the names and tastes you enter for people you eat with are sent when dining suggestions are generated. Ingredient photos are used only for analysis and are not stored, and the server removes location and other capture metadata from photos you upload before they are stored or analyzed. Receipt analysis results do not store payment identifiers such as card numbers, approval numbers, or membership numbers. However, if users directly enter or photograph personal or sensitive information, that content may be processed together, so users should avoid entering or photographing unnecessary personal information.
Gender and age are used only for aggregates inside the Service, and only aggregates covering at least a minimum number of users are reflected in recommendations, so that no individual user's records are revealed. Gender and age are not sent to external recommendation-generation services or the app analytics service, and are not provided to third parties.
Daily calorie target information such as height and weight is used only to calculate the daily calorie target and to show weight change. It is not sent to external recommendation-generation services or the app analytics service, and is not provided to third parties.
2. Legal Retention
Records on contracts or withdrawal, payments, and supply of goods may be retained for 5 years; consumer complaints or dispute records for 3 years; and access logs for 3 months where required by applicable law.
3. Children Under 14
The Service is not intended for children under 14. If use by a child under 14 is confirmed, the Operator may restrict or delete the account.
4. Third-Party Provision
The Operator does not provide personal information to third parties beyond the purposes stated in this Policy without prior consent, except where the user has consented, law requires it, a lawful request is made by an authority, processing is necessary to provide the Service, or the user moves directly to an external shopping or affiliate site.
Community posts, comments, nicknames and your verified neighborhood name are visible to other users, and prices extracted from receipts are published on the Price Map without identifying who submitted them. When you open a link to an external shop, that shop's privacy policy applies.
5. Processing Delegation
| Processing Type | Work Performed |
|---|---|
| Supabase (login authentication) | User authentication, session management, Google / Apple / Kakao sign-in |
| Google LLC (Google Cloud: servers, storage, Vertex AI) | Service operation and data storage, photo storage, processing of recommendations, text analysis, receipt and meal photo analysis, and video recipe conversion |
| Google LLC (Google AdMob and its consent tool) | Banner, native and rewarded ads, frequency capping, fraud prevention, ad performance measurement, rewarded-ad verification |
| NAVER Cloud (maps and geocoding) | Converting verification coordinates to an administrative district, address and coordinate conversion, map display, nearby store search |
| Google LLC (Google Maps Platform) | Address and coordinate conversion and place search for use outside Korea, map display on Android |
| Apple Inc. | Sign in with Apple, map display on iOS |
| Kakao Corp. | Kakao login |
| Expo (650 Industries, Inc.) | Push notification delivery, app update delivery |
| Cloudflare, Inc. | Traffic relay and security |
| Email delivery provider | Delivering inquiry emails |
| Coupang Partners, 11st, NAVER Shopping search | Product and price lookup by ingredient keyword (no member identifiers are sent) |
| YouTube (Google LLC) | Video information lookup and video playback |
| App analytics service provider (Google LLC, Google Analytics for Firebase) | Android and iOS app usage statistics, measuring return visits that carry over a device change or a reinstall, and measuring app-install and sign-up conversions of ad campaigns |
6. Overseas Transfer
The Operator is located in the Republic of Korea and the Service's main servers are in the Republic of Korea, so information of users who use the Service from outside Korea is transferred to and processed in the Republic of Korea.
The Service may use domestic or overseas infrastructure, authentication, recommendation-generation, and app analytics services. Personal information or service usage information may be transferred overseas or processed overseas in that process.
| Transfer Type | Country or Region | Items | Purpose | Retention |
|---|---|---|---|---|
| Login authentication (Supabase) | Overseas service regions | Account identifier, email, login provider, authentication-related information | User authentication and account management | Until account deletion or end of processing contract |
| Infrastructure service | Overseas service regions | Usage records, ingredient and recipe-related data | Service operation and data storage | Until account deletion or end of processing contract |
| Recommendation and analysis processing (Google LLC, Vertex AI) | United States and other countries where Google operates processing facilities | Ingredient information, preference information, allergy information, requests, cooking records, or recipe-adjustment input needed for recommendation generation; supplement information; receipt, meal and ingredient photos; names and tastes of people you eat with; the address of a video you ask to convert | Recipe and dining suggestions, text and photo analysis, video recipe conversion | Until the purpose is fulfilled or the processing contract ends |
| App analytics service (Google LLC, Google Analytics for Firebase) | United States | App instance identifier, a pseudonymous identifier derived from the user identifier when signed in, advertising identifier where permitted by the device, device and app information such as device model, operating system, app version, and language, country or region estimated from IP address, usage events such as first open, session start, screen view, sign-up completion, and login, and the login method | App usage statistics, measuring return visits, and measuring app-install and sign-up conversions of ad campaigns | Google Analytics data retention setting (up to 14 months) |
| Advertising (Google LLC, Google AdMob) | United States and other countries where Google operates processing facilities | Android advertising ID, IP address and the approximate location derived from it, device information, ad interactions, and the internal member number when a rewarded ad is verified | Ad delivery, fraud prevention, ad performance measurement | As set by Google's policies |
| Push notifications and app updates (Expo, 650 Industries, Inc.) | United States | Push notification token, notification title and text, update-check identifier and app version | Notification delivery, app update delivery | After delivery, as set by Expo's policies |
| Traffic relay (Cloudflare, Inc.) | United States and countries where the Cloudflare location nearest to you is situated | IP address, request information | Traffic security and service stability | As set by Cloudflare's policies |
| Maps and places (Google LLC, Google Maps Platform) | United States and other countries where Google operates processing facilities | Coordinates and address or place search terms when the Service is used outside Korea | Address and coordinate conversion, place search | As set by Google's policies |
This information is sent over an encrypted connection (HTTPS) at the time you use the relevant feature.
App analytics information is transferred to Google LLC (United States) over the network from time to time while the Android or iOS app is in use. The Operator does not send email addresses, names, gender, age, or the user identifier itself to app analytics; when you are signed in, only a pseudonymous identifier derived from the user identifier is sent. On Android you can limit use of the advertising ID by deleting or resetting it in device settings, and doing so does not limit use of the Service. The iOS app does not use the advertising identifier. Users who do not want any app analytics transfer can stop it by ceasing to use (deleting) the app.
Users who do not want overseas transfer may stop using the Service and request account deletion. Some overseas processing may be essential to provide the Service, so refusal may limit use of all or part of the Service.
7. Deletion
The Operator deletes personal information without delay when the retention period expires or the processing purpose is fulfilled. Electronic files are deleted in a manner that makes restoration impracticable.
You can delete your account yourself in the app. When you do, your email, name, nickname, handle and login information are deleted without delay and only a number that no longer identifies you remains on the account. Ingredients, meal plans and meal records, meal photos, supplements, intake records and supplement favorites, tastes and people you eat with, your shopping list, notifications and push notification tokens, chat messages and chat photos, neighborhood verification location, search history, likes and your private recipes are also deleted immediately. A private recipe attached to a public post you leave behind stays with that post, and what you put in a shared fridge that still has other members stays with that fridge: ingredients without your account information, shopping items with the account number that no longer identifies you. Public community posts and comments, sharing reviews you wrote, and recipes that are public (including recipes generated by recommendations that are also offered to other users) remain visible without identifying the author (shown as a withdrawn user) unless you delete them before deleting your account; the verified position saved with a post is erased. Receipt records (store, purchase date, total, items and prices) are kept to provide the Price Map, and ad display records are kept to prevent fraud, both attached only to the de-identified account number; the recognized receipt text is deleted. Records that the law requires to be kept are retained for the legal period.
8. User Rights
You may ask the Operator to access, correct, delete or restrict the processing of your personal information, or withdraw consent. You can delete your account yourself in the app from Delete Account on the Settings screen; send other requests to [email protected] or through the in-app inquiry form, and the Operator will act without delay. You can turn off notification, location, camera and photo permissions at any time in device settings. You may exercise these rights through a legal representative or an authorized agent. You may also lodge a complaint with the data protection authority where you live.
9. Automatic Collection
The Service may use cookies, local storage, authentication tokens, and device identifiers (the app installation identifier and push notification token) for login maintenance, security, error checking, and usage statistics. Users may disable some automatic collection through device or browser settings, but some features may be limited.
The Service shows banner, native and rewarded ads through Google AdMob. On Android, the advertising ID (AAID) may be used for ad delivery and app analytics; you can delete or reset it in device settings. The iOS app does not ask for tracking permission and does not use the advertising identifier (IDFA). Ads may be personalized or non-personalized depending on Google's policies and your choices. Where Google requires consent or a choice (for example the European Economic Area, the United Kingdom and Switzerland), Google's consent screen is shown before ads are requested, and in those regions you can change your choice at any time from Ad privacy settings on the Settings screen. If the consent result does not allow ad requests, the app does not load ads. When you watch a rewarded ad to the end to earn points, your internal member number and the ad placement and session value are passed through Google AdMob to the Operator's server to confirm the reward. The Operator keeps a per-account record of ad impressions and clicks to prevent invalid traffic.
The Android and iOS apps use Google Analytics for Firebase (Google LLC). To produce app usage statistics and measure app-install and sign-up conversions of ad campaigns, an app instance identifier, the advertising identifier (AAID on Android) where permitted by the device, device and app information, and usage events such as first open, session start, screen view, sign-up completion, and login are collected automatically and sent to Google. When you are signed in, a value derived from your user identifier that does not reveal it (a pseudonymous identifier) is sent as well, so that return visits by the same user are counted once even after a device change or a reinstall. This value alone does not identify you, but the Operator can match it against account information, so it is protected as personal information. No contact information such as your name or email address is sent, and the pseudonymous identifier is no longer sent after you sign out. On Android you can limit use of the advertising ID by deleting or resetting it in device settings. The iOS app does not use the advertising identifier. This does not apply to the web service.
10. Security Measures
The Operator takes measures such as minimizing access rights, securely storing important information, managing access logs, monitoring abnormal access, applying security updates, and checking vulnerabilities.
11. Contact
Privacy officer: Eat IT Operator
Email: [email protected]
12. Changes
The Operator may update this Privacy Policy due to changes in law, service policy, or external service usage. Important changes will be announced through the app, settings screen, website, email, or another reasonable method.