MOYO Studio (the "Operator") complies with the Personal Information Protection Act of the Republic of Korea and other applicable laws, and treats the protection of users' personal information as its highest priority. This Policy explains how users' personal information is collected, used, stored, and destroyed, and how users may exercise their rights.

IMAGO (the "Service") lets users take and edit photos on the web or in a mobile application, lets event hosts set up a place where participants can shoot and upload photos without installing anything, and organizes the resulting photos into a shared album.

1. Purposes of Processing

The Operator processes personal information for the purposes below. Information is not used for any other purpose, and if a purpose changes the Operator takes the steps the law requires.

• Providing the Service: taking, composing and storing photos, building frames, creating and managing events, participant photo and video uploads, the live photo wall, organizing albums and delivering links, running spaces
• Account management: identifying members, keeping sessions signed in, syncing content across devices, managing event passes and member benefits
• Payment: processing payments for paid plans, renewing subscriptions and giving advance notice, keeping payment records, sending receipts and transaction notices, handling refunds
• Support and notices: answering enquiries, sending announcements, notifying policy changes, warning before an album is deleted, handling reports
• Notifications: where the user has allowed them, push notifications such as new photos in a space, memory notifications and event notices
• Stability and quality: analysing the causes of errors and crashes, and visit and usage statistics that do not identify individuals
• Preventing misuse: detecting and responding to abnormal use, automated screening of inappropriate photos

2. Categories of Personal Information Processed

• Members (web and app)
  • Information provided at Google or Apple sign-in: email address, name, profile picture, account identifier (UID). If a user chooses "Hide My Email" at Apple sign-in, the Operator receives the relay address Apple creates.
  • Account copies of the frames a member has made and the photos a member has taken, stored so they follow the member to a new device. Only that member can view them.
  • Subscription status, payment history, event passes held, and records of member benefits granted
• Hosts (creating events, paying)
  • The member information above
  • Payment-related information handled through the payment gateway (PG)
  • Event information, such as the event name the host enters, and records of photographer links issued
  • Contact details such as an email address provided with an enquiry
• Participants (shooting, sharing, uploading)
  • The photos and videos a participant takes or uploads through the Service
  • An anonymous identifier (the anonymous sign-in ID of the app or browser) used when uploading, and a name the participant may optionally enter so that their photos can be grouped in the album
  • Participants use the Service without signing up. The Operator does not collect a participant's contact details or other identifying information.
• People who upload through a photographer link
  • The photos uploaded. The access key for the link is issued and kept on the Operator's server.
• When using the mobile application
  • Camera permission: used only to take photos.
  • Photo library permission: used to save photos taken, and, if the user has turned on "Shooting together today", to find photos taken that day (their time taken and the images, limited to those the user chooses to upload) and upload them to a space. If permission is not granted, everything other than that feature still works, and the Operator does not view the photos taken.
  • A push notification token, if the user has opted in to notifications
  • For in-app purchases, the store purchase identifier and subscription status (via RevenueCat)
  • App usage statistics (Google Analytics for Firebase): which screens were used, device type, OS version, app version, and an app instance identifier that does not identify a person
  • App crash reports (Firebase Crashlytics): the error and when it occurred, device model, OS version, app version, and an installation identifier that does not identify a person
• When using the web
  • Visit statistics (Vercel Web Analytics): the pages visited, the referrer, country, and device and browser type. No cookies are used, IP addresses are not stored, and the data is viewed only in aggregate form that cannot identify a person. Key actions such as creating an event or paying are recorded with the product type and currency only.
  • Error reports (Sentry): the error, the page it occurred on, browser and OS type, and the time. IP addresses are configured not to be stored.
  • Access country: the connecting IP address is used to determine the displayed currency, payment method and sharing method. The IP address itself is not stored.
  • Cookies that remember the language and currency setting. They are not used for advertising or behavioural analytics, and can be refused in the browser settings.
  • Abuse prevention (Google reCAPTCHA and App Check): for requests that need protection, such as sign-in and saving, browser and device information is sent to Google to judge whether the use is by a person. Google's privacy policy and terms of service apply to this.
• Information that may be generated automatically
  • Access logs and device or browser information, to the extent needed to operate the Service

Location data embedded in photo files (EXIF GPS) is removed on the user's device before upload, and the Operator does not collect it. On Android, the Operator does not request the photo location permission (ACCESS_MEDIA_LOCATION).