Privacy Policy — version history

A review with photos becomes public together with its photos one hour after it is left or edited. You can choose to add a bio to My and your public profile. We add Expo (USA) as the service the app uses to check for a new version — apps that include the update check send an installation identifier, operating system, app version, IP address and similar details to Expo each time they open, so this adds one processor and one transfer outside Korea.

Where	Previous	Revised
Key points · section 1	No bio item. No app update check	Adds an optional bio and includes it in the advice against entering sensitive information. Adds app update check and error records to the information created automatically, and states up front that apps with the update check send them to Expo each time they open
Section 2	No retention period for the bio or app update records	The bio is kept until you remove it or delete your account. App update records are kept as long as Expo needs them to provide updates and run security; states that Expo has not published a specific period
Section 3	No bio deletion explanation	The bio is deleted when you delete your account
Section 5	Ratings appear after one hour; reviews appear without a name in the meantime. Publication of nickname, photo and other information	Text-only reviews appear without a name; reviews with photos appear together after one hour, and the writer can see them right away. A bio is shown on the Foodie card, Foodie profile and public page only when Public profile is on
Section 6	Expo is not a processor	Adds Expo (650 Industries, Inc.): entrusted work, country, items, timing and retention. To refuse, use the website; it cannot be turned off in the app. States that there is no separate processing agreement with Expo and adds a sub-processor link
Section 7	The installation identifier kept on the device is for app error records	Adds the installation identifier used to check for app updates
Section 9	Nickname and photo correction/deletion; nickname and review filtering	Adds bio correction/deletion and filtering. Bios are not used to calculate Meal Scores
Section 12	Advice for nicknames, reviews and photos. Safeguards to be confirmed: Apple, and in the UK Sentry and Google	Extends the advice to bios. Adds Expo, including in the notice for users in Japan about information sent to outside parties
Addendum	Effective October 22, 2026	Posted and effective October 24, 2026. Takes effect on the day it is posted, without the 7 days (30 days if important) of advance notice the previous policy provided for — as with the October 20, 2026 version

Ratings that members with “Public profile” on newly leave or edit now become visible to others one hour later, so we have revised the explanation in section 5, and “Near me” now sends your location set to units of about 100 m, so we have revised section 8 (the same day as the Location-Based Services Terms effective October 22, 2026). The differences from the version effective October 20, 2026 are as follows.

Where	Before	After
Section 5, what is made public	Ratings you newly leave or edit appear at the top right away, so others may be able to guess where you are now; please leave your rating after you have moved on from that place	Ratings you newly leave or edit become visible to others one hour later, and in the meantime your review is shown without your name. Others may still be able to guess where you have been
Section 8, location	The coordinates are rounded to units of about 1 km (“Near me”) or about 100 m (the map) before they are sent	The coordinates are rounded to units of about 100 m before they are sent; “Near me” is also set to about 100 m
Addendum	Takes effect on the day it is posted	Takes effect the day after it is posted. Keeping sign-in records for 3 months still starts on November 4, 2026, as in the previous policy

Members can now attach up to 5 photos to the review on a rating, so we have added review photos to the items we process. Because our members are still only operator accounts, this version takes effect on the day it is posted. The differences from the version effective October 19, 2026 are as follows.

Where	Before	After
Section 1, reviews	Text of up to 300 characters, when it was left and edited, whether an operator hid it	Added up to 5 photos (contract). They are uploaded at a reduced size with extra information such as where they were taken removed, and they are not used in the Meal Score calculation
Sections 2 and 3, retention and account deletion	Reviews are deleted along with the text or the rating, or when you delete your account	Photos are deleted together — taken off screens right away, with their files deleted by the next day. They are not moved to a new number when you delete your account
Key points and section 5, what is made public	Anyone can read reviews, and if “Public profile” is not on, they are shown without a name	Anyone can see the photos attached to reviews, just like the text, and they may remain in search engines’ copies. Asked you to keep faces and personal information out of photos
Section 6, processors and transfers	Supabase stores data and profile photos. Vercel’s request logs arise when you open the website, sign in or send the report form	Supabase also stores review photos (Seoul), and Vercel delivers review photos. Vercel’s request logs also arise when the app loads photos
Section 7, app permissions	Photos — choosing one profile photo	Up to 5 photos can be chosen for a review. The app still does not read your whole photo library
Sections 9 and 12	Reviews are in your information file. For members aged 16–17 — do not write your name or school in reviews	Photos are in your information file too. Asked members aged 16–17 not to post photos showing their face
Addendum	Takes effect the day after it is posted. Keeping sign-in records for 3 months starts on November 4, 2026	Takes effect on the day it is posted. Keeping sign-in records for 3 months still starts on November 4, 2026, as in the previous policy

This version rewrites the policy more briefly, at a level similar to other services, and reflects the current Service — reviews, “Foodies” and following, “Hide this review” and “Delete my score” on the place page, which were launched before this version was posted, and the new screen names. It also includes the keeping of sign-in records from the version effective November 4, 2026, which was withdrawn before it took effect, and it takes effect the day after it is posted. Compared with the version effective October 11, 2026, the main differences are as follows.

Where	Before	After
Whole document	17 sections, with detailed explanations in each section and sections for each country	Shortened to 13 sections, with the items processed, retention periods, and entrustment and transfers outside Korea set out in three tables. Entrustment and transfers outside Korea are in section 6, personal location information in section 8, rights in section 9, and officers and remedies in section 11
Sections 1, 2 and 5, reviews	—	We collect the text of up to 300 characters, when it was left and edited, and whether an operator hid it (contract). Regardless of “Public profile”, anyone can read it, and if “Public profile” is not on, it is shown without a name. It is deleted along with the rating, or when you delete your account
Section 5, “Public profile”	Turning it on lists you in two places — your public page and place pages. Link previews remain for a while after you turn it off	With the “Foodies” tab (including “Latest”) added, you appear in three places and your follower count is shown — this was already the case, and members who had already turned it on were listed too. Added that new ratings appear right away, so others may be able to guess where you are now, and that search engines’ copies may remain. When you turn it off, the Company’s servers take down the preview right away
Sections 1, 2 and 9, following, “Hide this review” and deleting ratings	Ratings are deleted only if you check “Also delete my ratings” when deleting your account, or ask by email	The foodies you follow and the reviews you hid are kept with your account (contract). You can delete ratings one at a time, right away, with “Delete my score” on the place page
Sections 1 and 2, sign-in records	The time of sign-in and the IP address remain in the server provider’s request logs for 7 days	Sign-in records (time, account, sign-in method, IP address, etc.) are kept in the Service’s database (Seoul) (existing practice — until now, for 7 days). From November 4, 2026 they are kept for 3 months (Protection of Communications Secrets Act)
Sections 1, 6 and 7, report form and cookies	We do not use cookies	Set out the one cookie strictly needed for web social sign-in, and the value that prevents misuse of the report form (the IP address transformed so that it cannot be turned back — kept for a day) (existing practice). The report form goes in through the Company’s web server (Vercel)
Sections 1 and 6, maps	Records of linking places to Kakao Map places, and the searches the device sent to Kakao when doing so	Removed — that feature no longer exists
Sections 7 and 8, location and app permissions	Taking a profile photo with the camera	The app may first use a location the device found recently. The camera is used only in the first released version of the app, and we added the permission to put images into your photo library
Section 12, outside Korea	Sections for each country, such as the EEA, Switzerland, the UK, Japan and Singapore	Combined the EEA, the UK and Switzerland into one section; for other countries, we state that rights are exercised in the ways described in section 9, add one line for the United States, and keep Japan’s external transmission notice
Screen names (throughout)	Screen names in the previous app	Now uses the current app’s names, such as “Map”, “Ranking”, “Foodies”, “My”, “Public profile” and “Notices”

A review on October 3, 2026 found things to fix. We moved the Meal Score calculation from GitHub (USA) to Vercel (Seoul, Republic of Korea); app notifications are now sent by the Company’s server (Vercel, Seoul) directly to Google and Apple instead of through Expo (USA); and the app no longer checks for updates with Expo. As a result, we no longer entrust users’ personal information to GitHub or Expo. We also changed the Service so that you can delete your ratings together with your account and no sign-up time is kept in the placeholder for a deleted account. The version effective October 10, 2026, posted on October 3, 2026, is withdrawn before it takes effect and replaced by this version (Addendum, paragraph 2) — because the withdrawn version never took effect, the comparison below is with the version effective October 5, 2026, which is currently in effect. Rows marked “Existing practice” describe processing we already did and are now describing for the first time. The items collected and the purposes do not increase and nothing new is transferred outside Korea — two recipients outside Korea (GitHub and Expo) are removed — so we are giving notice 7 days before it takes effect (section 17). What differs from the version effective October 5, 2026 is as follows.

Where	Before	After
Key points · sections 2, 3, 12 and 16-3, deleting ratings	Not possible in the app or on the web; only by email before deleting the account	If you check “Also delete my ratings” in the first confirmation when deleting your account, all your ratings and “Haven't been” marks are deleted before the account is deleted. To delete only certain places’ ratings, or without deleting the account, ask by email
Key points · section 3, ratings after account deletion	Detached from nickname and sign-in information, moved to a new number, and kept for calculating Meal Scores and statistics	The results calculated from those ratings move to the new number too. We now state that these ratings are pseudonymized information used, under PIPA Article 28-2, only for compiling statistics (calculating Meal Scores); the items and period; that no record links the two numbers; and that the rights to access, delete and so on do not apply (Article 28-7)
At a glance · sections 1 and 7, server request logs · app error records	Time of each request, IP address, requested URL, device and browser information. For error records, the IP address when the device connects directly	Added that Supabase’s request logs also record the approximate area estimated from the IP address (country, region, city, postal code, time zone and a representative coordinate), the network operator, TLS connection details and, for signed-in requests, the member’s account number and sign-in session ID, and that Sentry does not store the IP address but keeps the estimated country, region and city. The Company does not use that estimated area (Existing practice)
Sections 1 and 16-1, notifications	The push token of each device on which you allowed notifications and that device’s app language. In section 16-1, the purpose “Sending notifications, app updates”	We now state the device’s operating system (iOS or Android — Existing practice) and, for an iPhone, whether the token belongs to a development build or a released build of the app (the APNs environment). The APNs environment is a value attached to the token that determines which Apple server a notification is sent to. App updates are removed from the purposes in section 16-1
Sections 2 and 3, placeholder for a deleted account	A random number and the sign-up and deletion times	A random number and the deletion time — the sign-up time is not kept (so that it does not link to the ratings moved to the new number)
Sections 2 and 3, rating deletion records	—	Records made when ratings are deleted (the member’s number, reason, date received and how identity was checked, numbers deleted and time — not which places or scores) are kept for 3 years from the deletion (records kept before; the period is set now)
Sections 2, 6 and 7, operational logs	—	Records of handled requests and of provision under law are kept in the Company’s drive (Google Workspace), with their items and periods (Existing practice)
Section 6, processors — Supabase and Vercel	Supabase sends notifications. Vercel provides the website and report form and handles social sign-in	Vercel also takes on calculating Meal Scores once a day and sending app notifications (asking Google and Apple to deliver them) — both only in Seoul. We now state what Vercel receives to send a notification (push token, notification title and text and the screen that opens when tapped, and the APNs environment for an iPhone) and that it does not keep them once passed to Google or Apple. Supabase manages the queue of notifications to be sent
Sections 6, 7, 8 and 16, Expo	650 Industries, Inc. (Expo) — relaying app notification delivery, providing app updates (USA). The app stores update information and a random identifier created for each installation on the device	Removed. Notifications are sent by the Company’s server (Vercel, Seoul) directly to Google and Apple, and the app does not check for updates with Expo (new versions of the app are released through the app stores). Also removed from the sub-processor lists in section 6, from section 7, from the table in section 8, and from the safeguard tables and the Japanese external transmission notice in section 16
Sections 6, 7 and 16, GitHub	GitHub, Inc. (GitHub Actions) — running the job that calculates Meal Scores once a day (USA)	Removed. Meal Scores are calculated by Vercel (Seoul), and no member information goes to GitHub. Microsoft Azure (USA) is removed from the sub-processors in section 6, and GitHub from section 7 and the safeguard tables in section 16
Section 6, terms of entrustment · sub-processors	Follow each company’s terms of service or data processing agreement	We now state which agreement each company follows — those that agreed in data processing agreements to use information only for the entrusted work and protect it at a level the same as or higher than this policy (Supabase, Vercel, Google and Sentry), and Apple. We added the main sub-processors (Amazon Web Services, Cloudflare, Google Cloud) and the lists (Existing practice)
Section 7, notifications — Google and Apple	Notifications to Android devices and iPhones are sent via Expo	The Company’s server (Vercel, Seoul, Republic of Korea) sends them directly to Google and Apple. Devices get their notification tokens directly from Google or Apple
Section 7, how to refuse	Notifications (Expo, Google and Apple); update checks (Expo) and app error records (Sentry); Meal Score calculation (GitHub)	Notifications (Google and Apple); app error records (Sentry); Meal Score calculation (Vercel). Added that operational logs cannot be refused
Section 10, age	Existing members under 16 — paragraph 4 of this policy’s Addendum	Points to paragraph 6 of the Addendum of the Terms of Service effective October 5, 2026, which sets that procedure
Section 12, automated decision-making	The information used for this calculation is the same as in the “Meal Score calculation” item in section 7	As the Meal Score calculation is no longer in section 7, the information used for it (random account number, sign-up time, places rated and entered scores, and a flag to exclude or down-weight a rating) is now stated in this section
Section 13, security measures	Encryption in transit, access rules, limiting access, and so on	Added the internal management plan and yearly check, confidentiality pledges and training for people who handle personal information, where data is kept, and how files operators download are handled
Section 13, if a data breach occurs	Items leaked, when and how, what you can do, our measures and the relief procedure, where to contact us	Loss, theft, forgery, alteration and damage are covered too, and we will also tell you your legal rights and how to exercise them, such as claiming damages or applying for mediation. If a leak is possible under the law even if not confirmed, we will tell you within 72 hours and again once it is confirmed (PIPA Article 34, as amended effective September 11, 2026)
Section 15, remedies	Supreme Prosecutors' Office Cyber Investigation Division — 1301 · www.spo.go.kr	Removed. The Prosecutors’ Office was abolished on October 2, 2026, and the Public Prosecution Service that took over its work does not investigate
Section 16-1, EEA	—	Added rating deletion records and operational logs to the purposes and legal bases table, and “Also delete my ratings” to the ways to object to ratings remaining after account deletion
Addendum · Key points	Taking effect 4 days after posting; replacing the withdrawn version and the policy effective September 12, 2026, and the processing newly described; the terms review screen for existing members; which app and website versions the location consent applies to; sending the text of the withdrawn version and the previous policy by email (Addendum, paragraphs 2–6)	Removed, as these applied only to the first version. We now state that the version effective October 10, 2026, posted on October 3, 2026, is withdrawn before it takes effect and replaced by this policy (Addendum, paragraph 2). The text of withdrawn versions is sent as described in section 17, and the text of the policy effective September 12, 2026 is sent on request by email (Addendum, paragraph 3)

First version.

This is the first version as a version file; before it, the Privacy Policy effective September 12, 2026 (the previous policy) was published on the web. This version replaces the previous policy. The version effective October 7, 2026, posted on September 30, 2026, was withdrawn before it took effect (Addendum, paragraph 2). Processing that was done before but not described in the previous policy is also described now — these are the entries marked “Existing practice” in the table below. What differs from the previous policy is as follows.

Where	Before	After
At a glance · section 9, location	Location used only on the device when viewing the map, and not stored on the server	You must agree to the Location-Based Services Terms as an optional item to use location features. We now state that rounded coordinates (about 1 km for “Near me”, about 100 m for the map) are sent to the server without sign-in information to find nearby places (Existing practice), and that the server does not store coordinates. We added section 9, “Personal Location Information Policy”
Sections 1, 2 and 9, location use records	—	Records of location feature use (member, feature, channel, time) and the server’s location request count log are kept for 6 months. If you withdraw consent, turn off that feature or delete your account, that member’s records are deleted immediately
Section 1, what we collect	Sign-in identifier, nickname, profile photo, ratings and comments, access times, app version and error records, push tokens	We now state the purpose and basis for each item. We added sign-up time, highlights chosen and edit history, “Haven't been” and saved places, reports, place fixes and blocks, records of notifications sent, IP address and device and browser information, email inquiries (Existing practice), and records of agreement, records of actions and notices, appeals and the report form. We also state that what we receive at sign-up is an indication that you have read this policy, and that it is not the basis for processing
Section 2, retention	While the account is in use. Access records kept for 3 months under the Protection of Communications Secrets Act	Now stated for each item — reports, actions and appeals 1 year after handling; notices about them 1 year after creation; email 1 year; taken-down profile photos until the appeal period ends; push delivery records 7 days and notification records 30 days; access information for signed-in sessions while you stay signed in; server request logs 7 days at Supabase and up to 1 day at Vercel; app error records 90 days; location records 6 months; notices of action at a public page’s address 1 year after they are taken down
Section 3, ratings after account deletion	Kept in a form in which no one can tell who left them, and even the Company cannot restore the link	Detached from nickname and sign-in information and moved to a new random number, with the sign-up time moved too. Without matching against other records, it is not possible to tell who left them, and the Company does not match them. A placeholder for the deleted account (random number, sign-up and deletion times) remains. If you ask before deleting your account, we delete your ratings
Section 5, provision to third parties	Not provided. Only to the extent of demands under law	We now set out the specific cases of provision — legal procedures such as warrants, imminent danger to life or body, reporting illegally filmed material and the like, reporting crimes that threaten life or safety, orders from authorities of other countries, and outcomes sent to people who made reports
Section 5, “Make my Meal Scores public”	Visible only on the page opened by a link, not on place pages	Also appears in “Public Meal Scores” on place pages (Existing practice). We now state that turning it on is consent to making them public
Section 6, processors	Two: Supabase and Vercel. Set and managed by contract	Now eight, adding Expo, Google (FCM), Apple (APNs), Sentry, GitHub (Meal Score calculation) and Google Workspace (email) (Existing practice). We now state that the terms of entrustment follow each company’s terms of service or data processing agreement
Section 7, transfers outside Korea	Only Sentry (USA). Supabase and Vercel in Seoul	Added Supabase and Vercel server request logs (USA and Singapore), Expo, Google and Apple (notifications and updates), GitHub (Meal Score calculation) and Google Workspace (email) (Existing practice). We also state the basis for the transfers (including people not signed in), the information of people not signed in, and how to refuse
Section 7, app error records	Included an account identifier; sent when errors occurred in the app and on the web	No information that could identify the account is included, and records are sent only when an error occurs in the app. Usage records from opening and closing the app are not sent
Section 8, what we store on your device	The web did not keep sign-in state	The web also keeps sign-in information in browser storage (Existing practice). Everything stored on the device is now listed in a table, including that on iPhone what is kept in secure storage may remain after the app is deleted (Existing practice)
Section 10, age	People under 14 could not sign up	In every country, people under 16 cannot sign up. If there are circumstances suggesting a member is under 16, we first restrict their use and tell them why, then check within 14 days and delete the account and the ratings and “Haven't been” marks it left. Members under 16 who signed up earlier cannot agree to the new terms and can delete their account at any time
Section 11, app permissions	—	We now describe the location, notification, camera and photo permissions and what happens if you do not allow them
Section 12, rights	Access, correction, deletion, suspension of processing	Added receiving a file (data portability), objection, deleting ratings, appealing actions and requesting an explanation of automated decisions, and stated that email requests are handled within 10 days
Section 13, security measures	Encryption in transit, minimizing access permissions	Added how we notify you if a data breach occurs
Section 14, officers	Privacy Officer and email	The same person also serves as Location Information Officer and Youth Protection Officer; phone, address and business information added
Section 15, remedies	You could file an administrative appeal	Removed the sentence on administrative appeals, and added challenging decisions under section 12, lawsuits in court and dispute mediation for location information
Section 16, people using the Service from outside Korea	—	Added provisions that also apply in each country, such as the EEA, Switzerland, the UK and Japan. An English version is provided alongside, and for people who live in the EEA, the UK or Switzerland, the English version is equally authoritative
Section 17 · Addendum, changes to this policy	Notice 7 days before taking effect (30 days if unfavorable)	We will post the content before and after together, and keep versions that took effect in the version history. This version is posted at launch and takes effect 3 days later, so this time we cannot keep the 7-day and 30-day advance notice promised by the previous policy (Addendum, paragraph 3). Existing members review this policy on the terms review screen that appears the next time they open the app or website (Addendum, paragraph 4)