← Mildio documents

Privacy Policy

Previous version. This policy was in effect from 8 September 2026 to 7 October 2026. See the current policy

About this translation. This is an English reference translation of the Korean privacy policy. The Service is operated from the Republic of Korea and the Korean version is the governing text; if the two differ, the Korean version prevails.

Yujeong Lee (the "Operator") complies with the Personal Information Protection Act of the Republic of Korea ("PIPA") and related laws in order to protect the freedom and rights of users of the mobile application Mildio (Korean name: 삼삼한상; the "Service"). In accordance with Article 30 of PIPA, this policy explains the procedures and standards applied to the handling and protection of personal information, so that any related concerns can be resolved promptly.

In one line

Mildio does not collect users' personal information. There are no accounts, the Operator runs no server, and the information a user enters, along with their location, never leaves the user's device.

1. Purposes of processing personal information

The Operator does not collect or process personal information. The Service handles information for the purposes below, but all such handling takes place inside the user's device and is never transmitted to the Operator.

PurposeInformationWhere it is handled
To show nearby restaurants and placesThe current location determined by the deviceInside the device (Section 6)
To calculate a score against standards that suit the userThe health-related conditions the user selectedInside the device (Section 3)
To show places the user savedThe favorites listInside the device (Section 3)

The Operator runs no server of its own for the Service. There is therefore no path by which a user's information could be received, stored, or read by the Operator.

2. Categories of personal information processed

The Operator processes no personal information. Specifically, none of the following is ever collected.

CategoryCollected?
Legal name, gender❌ Not requested
Nickname, date of birth❌ Not transmitted to the Operator — stored on the device only (Section 3)
Email address, phone number❌ Not collected
Account details (ID, password)❌ There is no sign-up process at all
Payment or card details❌ The Service is free and has no payment feature
Contacts, address book, photo library❌ Not accessed (for profile photos see Sections 3 and 6)
Advertising identifier (IDFA), device identifiers❌ Not collected
Usage records, access logs, behavioral analytics❌ Not collected; no analytics SDK is embedded
The user's location❌ Not transmitted to the Operator (Section 6)
Health-related selections entered by the user❌ Stored on the device only (Section 3)

3. Information stored only on the user's device

This section is not a statutory requirement. It is disclosed voluntarily so that users can know exactly how the Service behaves.

  1. The information below, selected or saved by the user in the Service, is stored only inside the user's device and is transmitted to no one, including the Operator.
ItemExampleWhere it is stored
Nickname, date of birthThe name the app uses to address the user; date of birthDevice storage
Profile photoOne photo chosen by the userA file on the device (the app's private area)
Health-related selectionsConditions of interest such as hypertension or diabetes; dietary conditionsDevice storage
FavoritesRestaurants and places the user savedDevice storage
Screen settingsLast screen viewed, sort order, whether onboarding was completedDevice storage
Request counterA number used to manage the daily volume of API callsDevice storage
  1. If the user uses device or cloud backup, the information above may be included in those backups in line with the relevant backup policy. That is a matter between the user and the device or cloud provider, and the Operator is not involved.

4. Processing and retention periods

Because the Operator collects no personal information, it holds none and no retention period arises.

Information stored on the device under Section 3 remains there until the user deletes it. The Operator sets no separate retention period.

5. Procedures and methods for destroying personal information

  1. Because the Operator holds no personal information, there is no destruction procedure carried out by the Operator.
  2. Information stored on the device under Section 3 is deleted as follows.
    • Deleting the application: everything stored on the device is deleted along with it.
    • Deleting individual items: within the app, favorites can be removed one by one, and on the My profile screen the nickname can be cleared, the date of birth can be turned off, and health-related selections can be changed.

6. Handling of location information

  1. Purpose: used solely to show restaurants and places near the user.
  2. How it is handled: the location determined by the device is used to compose the screen and then discarded. It is not sent to any server of the Operator and is not stored permanently on the device. The Service provides no feature that records travel routes or visit history.
  3. What leaves the device: to look up nearby information, a location must be sent to public open APIs. In doing so the Service uses approximate coordinates rounded to a fixed unit, not exact coordinates. Weather information is requested by a grid number covering a fixed area of the country, not by coordinates.
  4. Consent and withdrawal: location permission is granted or refused by the user through the process provided by the operating system (iOS), and can be withdrawn at any time in device settings.
  5. The permission is optional, not required. The Operator requests only the single device permission below.
PermissionTypeWhy it is neededIf not granted
LocationOptionalTo show nearby restaurants and places ordered by distanceThe user can select an area manually and use every feature as normal

The Operator states the above on the permission request screen. No permission other than this one is requested, and the Service does not access contacts, the microphone, the camera, or the photo library.

About profile photos: when a user sets a profile photo, the Service does not access the photo library. It receives only the single photo the user picks in the system-provided photo picker, and no separate permission is required for this. The photo received is stored on the device only (Section 3).

  1. Usable without granting permission: even if location access is not allowed, the user can select an area manually and use the Service.
  2. Because the Operator neither collects nor retains personal location information, nor provides it to third parties, no separate location-information terms or consent procedure under the Act on the Protection and Use of Location Information is established.

7. Personal information of children under the age of 14

The Operator does not collect personal information from children under the age of 14. There is no sign-up process and no information identifying a user is requested at all, so no procedure for obtaining a legal representative's consent is established.

8. Handling of sensitive information and pseudonymized information

  1. Sensitive information: the health-related conditions a user selects in the app (conditions of interest and the like) may by their nature amount to sensitive information. These values are stored on the device only and are not transmitted to the Operator, and the Service has no feature that discloses them externally. No procedure for choosing whether to disclose them is therefore established.
  2. Pseudonymized information: the Operator does not process pseudonymized information under Article 28-2 of PIPA or related provisions. The rounding of coordinates described in Section 6(3) is a measure that coarsens a value so that an exact location is not revealed, and differs from the processing of pseudonymized information as defined by law.

9. Provision to third parties, outsourcing, and cross-border transfer

  1. Provision to third parties: the Operator does not provide users' personal information to third parties.
  2. Outsourcing: the Operator does not outsource the processing of personal information.
  3. Cross-border transfer: the Operator does not transfer users' personal information abroad.
  4. Additional use or provision: because the Operator collects no personal information, no additional use or provision beyond the original purpose arises.

Each of the above holds because there is no personal information to provide, outsource, or transfer.

10. Connections to external services

The Service connects to the external services below in order to display information. The Operator does not send any information that could identify a user in the course of doing so.

DestinationWhat is sentPurpose
Public Data Portal API servers (apis.data.go.kr) — Korea Tourism Organization, Ministry of Food and Drug Safety, Small Enterprise and Market Service, Korea Meteorological AdministrationRounded approximate coordinates, search terms, the identifier of the item to look upLooking up places, menus, nutrition data, and weather
Korea Tourism Organization image server (api.visitkorea.or.kr)Image addressesDisplaying photos
Apple Maps (maps.apple.com)Destination coordinates, only when the user taps directionsOpening the device's maps app (the app does not communicate with it directly; it opens the maps app)

The only parties the Service actually exchanges data with are the public-agency API servers listed above.

  1. Those servers are operated by the respective agencies and, as with any web service, access records (such as IP addresses) may remain on those agencies' servers. That follows each agency's own policy; the Operator neither collects nor reads such records.
  2. The Service contains no advertising network, no behavioral analytics tool, and no crash-reporting tool.
  3. The external library the Service uses is for drawing screen animations; it performs no network communication and collects no information.
  4. However, if the user has allowed diagnostic sharing in device settings, the operating system may send anonymous diagnostic information to Apple when the app terminates unexpectedly. This is a function of the operating system, not a collection tool added by the Operator. The user can turn this sharing off in device settings.

11. Installation and operation of automatic collection devices, and refusal thereof

  1. The Service does not install or operate devices that automatically collect behavioral information (cookies, advertising identifiers, behavioral analytics scripts, and the like).
  2. The Service does not allow third parties to collect users' behavioral information. It provides no personalized advertising, and carries no advertising at all.

12. Automated decision-making

The Operator makes no automated decisions within the meaning of Article 37-2 of PIPA.

13. Rights and duties of data subjects and their legal representatives, and how to exercise them

  1. Users have the right to request access, correction, deletion, and suspension of processing in relation to their information (Articles 35 to 37 of PIPA).
  2. Because the Service stores information only on the user's device, users can exercise these rights immediately, without going through the Operator, as follows.
RightHow to exercise it
AccessView the stored values directly on the My profile screen in the app
CorrectionChange the nickname or date of birth on the My profile screen, or reselect the health-related conditions
DeletionDelete favorites individually, or delete the application (deletes everything)
Suspension of processingRevoke location permission in device settings, or delete the application
  1. Because the Operator does not hold users' information, there is nothing held by the Operator to request the deletion of. Deleting it directly is the fastest and most certain method.
  2. For questions about exercising these rights, please use the contact in Section 15 and the Operator will respond in good faith.

14. Measures to secure personal information

The Operator takes the following measures.

  1. A structure that does not collect: no server is operated and processing happens only on the device, so no information that could leak is created in the first place.
  2. Coarsening location values: coordinates sent to external APIs are rounded so that an individual's exact location cannot be identified.
  3. Protecting data in transit: all communication with external servers uses HTTPS encryption.
  4. Protecting API keys: public API keys are kept out of the source code and managed in separate configuration.
  5. Reliance on device protection: information stored on the device is protected by the app sandbox and device encryption provided by the operating system. Users are encouraged to set a device lock (passcode or biometrics).

15. Privacy officer and complaint handling

For enquiries, complaints, or remedies concerning the handling of personal information, please use the contact below. The Operator will respond and act promptly.

ItemDetails
Privacy officerYujeong Lee
Emailaspynlee.dev@gmail.com

16. Remedies for infringement of data subjects' rights

To obtain remedies for infringement of personal information rights, users may apply to the following bodies for dispute resolution or consultation.

BodyContact
Personal Information Dispute Mediation Committeewww.kopico.go.kr / 1833-6972
Privacy Infringement Report Centerprivacy.kisa.or.kr / 118 (no area code)
Supreme Prosecutors' Office, Cyber Investigation Divisionwww.spo.go.kr / 1301 (no area code)
National Police Agency, National Office of Investigation (Cyber Bureau)ecrm.police.go.kr / 182 (no area code)

In addition, a person whose rights or interests have been infringed by a disposition or omission of the head of a public institution in respect of a request under Article 35 (access to personal information), Article 36 (correction or deletion of personal information), or Article 37 (suspension of processing of personal information) of PIPA may file an administrative appeal as provided by the Administrative Appeals Act.

17. Changes to this privacy policy

  1. If this policy changes, the Operator will state the changes and their effective date and give notice within the Service and at the public address below seven days before the effective date (or thirty days before for changes that materially affect users' rights).
  2. When changes are made, the versions before and after will be published side by side so that users can easily see what changed. Earlier versions remain available.
  3. Public address: https://yujeongleeeee.github.io/safedish-info/privacy.html (English reference translation: privacy-en.html)

Addendum

This policy takes effect on 8 September 2026.