Living Album (Meomureum) Privacy Policy
Effective date: September 1, 2026 (v1.0) · v1.1 effective date to be separately announced · v1.2 applies from its publication date (July 8, 2026) · v1.3 applies from its publication date (September 12, 2026) · v1.4 effective September 19, 2026 · v1.5 effective October 3, 2026 · v1.6 effective October 3, 2026 · v1.7 effective October 11, 2026 · v1.8 effective October 15, 2026
Version: v1.8 Company name: VERITAPHOS CO., LTD. · Representative Director: Hyunhwa Lee (Inside Director)
Privacy Officer: Hyunhwa Lee (Representative Director) · support@meomureum.app
Notice on the governing version: This English translation is provided for the convenience of non-Korean users and is for reference only. In the event of any conflict or discrepancy between this English version and the Korean original, the Korean original shall prevail and have legal effect.
Living Album (Meomureum; meomureum.app, hereinafter the "Service") values the personal information of its Users and complies with the Personal Information Protection Act (PIPA) and related laws and regulations. This Policy explains the items, purposes, and retention periods of the personal information the Service collects, as well as the rights of Users.
Article 1 (Items of Personal Information Collected)
1. Collected upon sign-up and authentication
| Item | Method of Collection | Required/Optional |
|---|---|---|
| Email address | Direct entry or social login | Required |
| Password (stored encrypted) | Direct entry | Required (for email sign-up) |
| Nickname (title) | Direct entry | Required (when joining a Household) |
| Date of birth | Direct entry | Optional (when using the birthday reminder feature) |
| Social login identifier | Kakao, Google, or Apple login | Required (for social login) |
- When a User signs in with Apple and chooses "Hide My Email," we receive a relay email address created by Apple instead of the actual email address.
2. Collected during use of the Service
| Item | Point of Collection | Purpose |
|---|---|---|
| Uploaded photos and EXIF metadata | When a photo is uploaded | Storing, managing, and displaying photos |
| Entered information such as event names, tags, and titles | Directly entered by the User | Curation and search features |
| Facial Recognition results (information identifying persons in a photo: person, face location, recognition confidence) | Automatically processed after a photo is uploaded (limited to persons who consented to Facial Recognition) | Identifying and classifying persons for Automatic Curation |
| Reference facial feature vector (biometric information) | When a reference face is registered after consent to Facial Recognition | Identifying and classifying persons for Automatic Curation |
| Facial region in a photo (a single area enclosing the faces — its position and size — and the number of faces; no information about who they are) | Automatically processed after a photo is uploaded (all photos) | Adjusting the photo's placement so faces are not cropped on Digital Frame and album screens (Article 3 (8)) |
| Service usage records (access times, feature usage history) | Automatically generated during use of the Service | Service improvement, troubleshooting |
| IP address | Automatically generated when accessing the Service | Security, detection of anomalous access |
| Push notification delivery information (per-device notification delivery address and encryption key; for the iPhone app, the device notification token; a device label, e.g., "Android Chrome" or "iPhone") | When the User turns on "Receive push notifications" on the notifications screen | Sending notifications such as birthdays and "on this day years ago" |
| Advertising and analytics identifiers (cookie-based), visit and usage records | Automatically generated when visiting the Service | Service usage analysis, advertising performance measurement |
| Sign-up acquisition path information (referral parameters utm_source, utm_medium, utm_campaign, utm_term, utm_content; the domain of the immediately preceding site visited; the path of the first page visited; information on the invitation link used to sign up) | Temporarily stored in a cookie on the first visit (valid for 30 days); upon consent to this Policy after sign-up, retained together with the account and the cookie deleted | Sign-up acquisition path analysis (Article 11 (4)) |
3. Collected at the time of payment
| Item | Processing Party | Remarks |
|---|---|---|
| Card number, CVC, expiration date, simple-payment authentication information | KG Inicis / Kakao Pay (PG; not retained by Living Album) | Processed directly by the PG company |
| Payment identifier (PortOne billingKey/customerKey), card type, last 4 digits of the card | Living Album | Recurring payment and refund processing |
| In-app subscription (Google Play / App Store) payment method and payment information | Google LLC (Google Play) · Apple Inc. (App Store) — not retained by Living Album | The Android app is handled directly by Google Play, and the iPhone app by the App Store |
| In-app subscription records (subscription product, order number, times of subscription start, expiration, renewal, cancellation, and refund, test-purchase status) | Living Album (verified via RevenueCat) | Reflecting the plan (entitlement) · renewal and cancellation processing |
Living Album does not directly collect or store sensitive payment information such as card numbers, CVC, or expiration dates.
4. Collected during identity verification
When a Household creator (Owner) completes identity verification, we receive the following items from the verification authority (KG Inicis Integrated Authentication).
| Item | Method of Collection | Required/Optional |
|---|---|---|
| Name, gender, date of birth, mobile phone number, carrier, Korean/foreign national status, encrypted Connecting Information (CI) | Received from the verification authority (KG Inicis Integrated Authentication) | Required (when creating a Household) |
- Purpose of collection and use: Confirming that the Household creator (Owner) is at least 19 years of age; preventing duplicate sign-ups and fraudulent use (identifying a single individual)
- Retention and processing method:
- The CI is converted to a SHA-256 hash for storage; the original value is not stored.
- For the date of birth, only the year is retained (to determine adult status).
- Name, gender, mobile phone number, carrier, and Korean/foreign national status are destroyed immediately upon verification and are not stored.
- Retention period: until the member withdraws (account deletion)
Article 2 (Purposes of Collecting and Using Personal Information)
| Purpose | Item | Retention Period |
|---|---|---|
| Member sign-up, authentication, and account management | Email, password, nickname | Until member withdrawal |
| Identity verification (confirming the Owner is 19+, preventing duplicate sign-ups and fraudulent use) | CI (SHA-256 hash), year of birth, date and time of verification | Until member withdrawal |
| Service provision (photo storage, sharing, Digital Frame) | Photos, EXIF, event names | 30 days after member withdrawal (protection period) + up to 6 months with the User's consent (at the Company's discretion; recovery not guaranteed) — Terms of Service Article 7 |
| Temporary storage in the Trash | Photos deleted by the User | Permanently deleted when the retention period set by the Household elapses or when the User empties the Trash — Terms of Service Article 6-5 |
| Public Posts | Public copy, published body text | Deleted upon unpublishing or member withdrawal — Terms of Service Article 9-2 (7) |
| Identifying and classifying persons for Automatic Curation (including showing faces on the person buttons in Photos) | Reference facial feature vector, Facial Recognition results | Deleted immediately upon withdrawal of consent, application for member withdrawal, or withdrawal from a Household · Facial Recognition results are deleted together with the photo when that photo is permanently deleted |
| Photo screen fitting (so faces are not cropped) | Facial region in a photo | Deleted together with the photo when that photo is permanently deleted |
| Payment processing and settlement | Payment identifier, card information (last 4 digits) | The period prescribed by the relevant laws (up to 5 years) |
| Verifying in-app subscriptions (Google Play / App Store) and reflecting entitlements | Member identifier, in-app subscription records | The period prescribed by the relevant laws (up to 5 years) |
| Sending push notifications | Push notification delivery information | Deleted when the User turns off notifications, withdraws notification permission on the device, or withdraws membership |
| Responding to customer inquiries | Email, inquiry content | 3 years after processing is completed |
| Service improvement and troubleshooting | Usage records, IP | 1 year |
| Sign-up acquisition path analysis | Sign-up acquisition path information | Cookie before retention: deleted 30 days after the day first stored, or upon consent to this Policy / After sign-up: destroyed together with the account when it is deleted after the 30-day protection period following member withdrawal + up to 6 months with the User's consent — Article 11 (4)(5) |
| Marketing and event announcements (consenting Users only) | Until consent is withdrawn |
Article 3 (Processing of Facial Information)
(1) Automatic Curation — a core feature of the Service that automatically gathers photos by conditions such as person, time, and place and displays them in Digital Frames and albums — only works if persons in photos can be identified. To this end, the Service processes facial information, which constitutes sensitive information (biometric identification information) under Article 23 of the Personal Information Protection Act.
(2) Limitation of processing purpose — Facial information is used solely for identifying and classifying persons for Curation within the relevant Household. Displaying a small image of a person's face on the person buttons in Photos is included in this purpose. It is not used for advertising, provision outside the Household, or analysis for any other purpose.
(3) Separate consent — Consent to the processing of facial information is obtained on a screen separate from other terms and consents. This consent is required to use the Service, and the Service cannot be used without it (refunds in cases where a User declines consent and cancels during a paid period are governed by Article 6 (8) of the Terms of Service).
(4) Processing method
- Only the reference face of a consenting person is registered and retained as a feature vector. A consenting person means: (1) a Household member who has signed up for the Service and consented in person; (2) a child under 14 years of age for whom the Household Owner, as the legal representative, has consented; or (3) a person who is not a Household member and who, after opening a request link (e.g., via KakaoTalk) sent by the Household Owner, has consented in person. In case (3), no Service account or Photos viewing right is created; the consent applies only to that Household's photos and may be withdrawn at any time from the same link (upon withdrawal, the reference facial feature vector and recognition results are deleted immediately). As a consent record, we retain the time of consent, the version of the consent document, and the method of confirmation. No one may consent on behalf of a person 14 years of age or older, and such a person is excluded from Facial Recognition matching until they sign up and consent in person (tags that directly display a name are retained).
- Faces are found in uploaded photos and matched only against registered reference faces.
- Faces that do not match (including the faces of persons who have not consented) are not stored as feature vectors and are discarded immediately after matching.
(5) Deletion — In the following cases, the reference facial feature vector of the relevant person is deleted without delay.
- Consent to Facial Recognition is withdrawn
- An application for member withdrawal is made
- The person withdraws from, or is removed from, a Household (limited to that Household)
- The photo from which the reference face was created is permanently deleted
- The person is deleted or the account link is removed Facial Recognition results (person, face location) are deleted upon withdrawal of consent, and are deleted together with a photo when that photo is permanently deleted.
(6) Processing location — Facial analysis and the storage of reference facial feature vectors take place on Amazon Web Services (Rekognition) in the Seoul region (ap-northeast-2) of the Republic of Korea, and are not transferred abroad. We have applied a setting (AI service opt-out) that prevents AWS from using or storing input images for service improvement. For analysis, photos temporarily pass through server functions (Vercel, executed in the Seoul region) and are not stored.
(7) Users may review and correct recognition results, and corrected results may be used to improve the reference face of the relevant person.
(8) Face location check (not identity determination) — To keep faces from being cropped when a photo is fitted to the screen on Digital Frame and album screens, the Service automatically checks only where faces are located in all photos uploaded (regardless of consent to Facial Recognition). This process does not determine whose face it is, and does not create or store feature vectors. As a result, for each photo we store only a single area enclosing the faces (position and size) and the number of faces, and these are deleted together with the photo when it is permanently deleted. The processing location is the same as in (6).
Article 4 (Provision of Personal Information to Third Parties)
As a rule, the Company does not provide Users' personal information to third parties. It may be provided only in the following exceptional cases.
- When the User has consented in advance
- When a government agency so requests pursuant to the law
- When an investigative agency so requests in accordance with lawful procedures for the investigation of crimes such as child and youth sexual exploitation material
Article 5 (Entrustment of Personal Information Processing)
In order to provide the Service, the Company entrusts the processing of personal information as follows.
| Entrusted Party | Entrusted Work | Items Processed | Processing Location |
|---|---|---|---|
| Supabase Inc. | Authentication and DB management | Email, nickname, usage records, sign-up acquisition path information | Republic of Korea (Seoul region) |
| Cloudflare Inc. (R2) | Photo file storage | Photo originals, EXIF metadata, Public Post copies | Asia Pacific (Japan or Korea) |
| Vercel Inc. | Server function execution | Transient data during request processing | Republic of Korea (fixed to Seoul region) |
| Plus Five Five, Inc. (Resend) | Email delivery | Email address, delivery content (subject and body) | Processed in the Tokyo region (corporate domicile in the United States) · Sub-processor Amazon SES |
| PortOne Co., Ltd. | Payment integration and data processing | Payment identifiers (billing key, order number), order information (product name, amount), purchaser information (name, email, mobile phone number) | Republic of Korea |
| KG Inicis Co., Ltd. | Card payment approval and settlement | Payment method information (card), payment approval information, order and purchaser information | Republic of Korea |
| Kakao Pay Corp. | Simple payment (Kakao Pay) approval and settlement | Payment method information, payment approval information, order and purchaser information | Republic of Korea |
| KG Inicis Co., Ltd. | Identity verification (Integrated Authentication) | Name, gender, date of birth, mobile phone number, carrier, Korean/foreign national status, CI | Republic of Korea |
| Amazon Web Services (Rekognition) | Facial analysis and reference face storage (Automatic Curation) · face location check in photos (Article 3 (8)) | Photo images (temporarily transmitted during analysis), reference facial feature vectors | Republic of Korea (Seoul region, ap-northeast-2) |
| Google LLC | Service usage analysis and advertising performance measurement | Advertising and analytics identifiers, visit records, IP address | United States |
| RevenueCat, Inc. | In-app subscription (Google Play / App Store) payment verification · renewal, cancellation, and refund tracking | Member identifier, in-app subscription records, device and app information (device model, OS and app version, language and country settings), IP address | United States (Amazon Web Services) |
| The push service provider of the User's device (Chrome / Android app = Google LLC Firebase Cloud Messaging · iPhone app = Apple Inc. Apple Push Notification service · other browsers = the respective manufacturer) | Push notification delivery | Notification delivery address (iPhone app = device notification token), notification content — for browsers and the Android app, encrypted (openable only by the Service and the User's device); for the iPhone app, the notification title, body, and the screen address to open when tapped | Each provider's region, such as the United States |
In entering into entrustment contracts, we comply with the relevant laws and regulations so that personal information can be managed safely.
Subscriptions in the Android app are sold and paid for directly by Google LLC (Google Play), and subscriptions in the iPhone app by Apple Inc. (App Store), each in accordance with their own terms and privacy policies. Living Album does not receive payment method information.
The three payment companies (PortOne, KG Inicis, Kakao Pay) are all domestic corporations and are therefore not subject to overseas transfer. Depending on the payment method chosen by the User, processing is handled by either KG Inicis (credit/debit cards) or Kakao Pay (simple payment).
Article 6 (Overseas Transfer of Personal Information)
Because the infrastructure of the entrusted parties below is located abroad, personal information is transferred overseas. Details regarding this are as follows.
(1) Vercel Inc. (hosting)
| Category | Details |
|---|---|
| Transferee | Vercel Inc. (440 N Barranca Ave #4133, Covina, CA 91723, USA) |
| Country of transfer | United States |
| Items transferred | Request information generated when using the Service — IP address, browser and device information, request path, cookies, transient data during request processing |
| Purpose of transfer | Application hosting and server function execution |
| Timing and method of transfer | Transmitted over the network each time a User accesses the Service |
| Retention period | Deleted within a reasonable period upon termination of the contract |
| Contact | privacy@vercel.com |
- Server functions are configured to run in the Seoul region, but static assets are cached and delivered from regions worldwide, and logs and backups may be processed overseas, such as in the United States.
(2) Cloudflare, Inc. (photo storage and delivery)
| Category | Details |
|---|---|
| Transferee | Cloudflare, Inc. (101 Townsend Street, San Francisco, CA 94107, USA) |
| Country of transfer | United States |
| Items transferred | Photo and video files and EXIF metadata, Public Post copies, IP addresses contained in access logs |
| Purpose of transfer | Photo and video storage and delivery, Public Posts |
| Timing and method of transfer | Transmitted from the User's browser and the server when photos and videos are uploaded and viewed |
| Retention period | Customer content: the earlier of the contract's expiration/termination or the time when processing is no longer necessary / Access logs: 12 months |
| Contact | legal@cloudflare.com |
- The bucket where photos are stored is located in the Asia-Pacific region, but Cloudflare operates geographically distributed data centers and backups in other regions.
(3) Plus Five Five, Inc. (Resend, email delivery)
| Category | Details |
|---|---|
| Transferee | Plus Five Five, Inc. (2261 Market Street #5039, San Francisco, CA 94114, USA) |
| Country of transfer | United States |
| Items transferred | Recipient email address, email subject and body (including display names, Household names, and links contained in the body), delivery metadata |
| Purpose of transfer | Sending emails such as sign-up verification, family invitations, and payment and inquiry notices |
| Timing and method of transfer | Transmitted from the server at the time each email is sent |
| Retention period | Deleted within 90 days after account closure |
| Contact | privacy@resend.com |
- Email processing takes place in the Tokyo region (ap-northeast-1), and Amazon SES is used as a sub-processor for delivery. The transferee's corporate domicile is in the United States.
- Email open and link-click tracking features are not used. Accordingly, recipients' IP and device information is not transferred.
(4) Google LLC (analytics and advertising performance measurement)
| Category | Details |
|---|---|
| Transferee | Google LLC (1600 Amphitheatre Parkway, Mountain View, CA 94043, USA) |
| Country of transfer | United States |
| Items transferred | Advertising and analytics identifiers (cookie-based), visit and usage records, IP address, the Household identifier passed during conversion measurement |
| Purpose of transfer | Service usage analysis and advertising performance measurement |
| Timing and method of transfer | Transmitted from the User's browser when a Service visit or conversion occurs (completing sign-up, entering the walkthrough) |
| Retention period | Event data 2 months, user data 14 months |
| Contact | Google's privacy inquiry channel (privacy policy information page) |
(5) RevenueCat, Inc. (in-app subscription payment verification)
| Category | Details |
|---|---|
| Transferee | RevenueCat, Inc. (1032 E Brandon Blvd #3003, Brandon, FL 33511, USA) |
| Country of transfer | United States (stored in the Amazon Web Services US region) |
| Items transferred | Member identifier (email and name are not sent), in-app subscription records (subscription product, order number, times of subscription start, expiration, renewal, cancellation, and refund, test-purchase status), device and app information (device model, OS and app version, language and country settings), IP address |
| Purpose of transfer | Payment verification and renewal, cancellation, and refund tracking for in-app subscriptions (Android = Google Play · iPhone = App Store), and reflecting the plan (entitlement) |
| Timing and method of transfer | Transmitted over the network from the app when the User loads subscription/purchase history in the app, and from Google Play, the App Store, and the Service server when the subscription status changes |
| Retention period | Deletion requested upon member withdrawal · however, payment records may be retained during the statutory retention period under Article 7 |
| Contact | compliance@revenuecat.com |
- The information of Users who do not make in-app subscriptions is not transmitted to RevenueCat.
(6) Push notification delivery (the push service provider of the User's device)
| Category | Details |
|---|---|
| Transferee | The push service provider of the browser or app the User uses — Chrome / Android Living Album app: Google LLC (Firebase Cloud Messaging · 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA) · iPhone Living Album app: Apple Inc. (Apple Push Notification service · One Apple Park Way, Cupertino, CA 95014, USA) · other browsers: the respective browser manufacturer |
| Country of transfer | The server region of each provider, such as the United States |
| Items transferred | Per-device notification delivery address (iPhone app = device notification token), notification content — for browsers and the Android app: encrypted notification content (the notification title and body are encrypted so that only the Service and the User's device can open them, and the provider cannot see the content) / for the iPhone app: the notification title and body and the screen address to open when tapped (processed by Apple to deliver to the device) |
| Purpose of transfer | Delivering to the device the push notifications the User has turned on (birthdays, "on this day years ago," etc.) |
| Timing and method of transfer | Transmitted over the network from the Service server each time a notification is sent |
| Retention period | Subject to the provider's policy after delivery (we request that undelivered notifications be discarded after being retained for up to 12 hours) |
| Contact | Google's privacy inquiry channel · Apple's privacy inquiry channel (apple.com/legal/privacy/contact) · the privacy inquiry channel of each browser manufacturer |
- Push notifications are sent only when the User has turned them on in person, and can be turned off at any time on the notifications screen.
Method of refusal and its effects
Consent to overseas transfer is a required consent item at sign-up. You may refuse to consent, but if you do, member sign-up and use of the Service will be restricted. After sign-up, you may stop the transfer by withdrawing your membership, and transfers to Google may be refused individually by the method in Article 11 (3). Transfers to RevenueCat do not occur unless you make an in-app subscription, and push notification delivery stops when you turn off notifications on the notifications screen.
Article 7 (Retention and Destruction of Personal Information)
(1) After the purposes of collecting and using personal information have been achieved, the Company destroys the relevant information without delay.
(2) Where retention is required by the relevant laws, the information is retained for the periods below.
| Retained Item | Basis for Retention | Retention Period |
|---|---|---|
| Records of contracts and withdrawal of offers | Act on the Consumer Protection in Electronic Commerce, Etc. | 5 years |
| Records of payment settlement | Act on the Consumer Protection in Electronic Commerce, Etc. | 5 years |
| Records of consumer complaints and dispute resolution | Act on the Consumer Protection in Electronic Commerce, Etc. | 3 years |
| Access logs | Protection of Communications Secrets Act | 3 months |
(3) Method of destruction: Electronic files are permanently deleted in an unrecoverable manner, and photo files are physically deleted from R2.
Article 8 (Rights of Users)
Users may exercise the following rights at any time.
| Right | Method |
|---|---|
| Request to access personal information | In-Service settings or email |
| Request to correct or delete personal information | In-Service settings or email |
| Request to suspend processing of personal information | Email (support@meomureum.app) |
| Portability of personal information (export) | Email request (support@meomureum.app) — a copy of the retained data is provided after identity verification |
| Withdrawal of consent (marketing, Facial Recognition, etc.) | In-Service settings |
The Company notifies the requester of the outcome of a request within 10 days.
Article 9 (Principles for the Operator's Access to Photos)
(1) The operator does not routinely view Users' photos.
(2) Where access to photos is necessary to respond to a Service malfunction or to handle a User's inquiry, access is made only after obtaining the User's explicit, temporary consent (valid for 48 hours).
(3) In exceptional cases where there is a lawful request from an investigative agency pursuant to the law, access may be made, and in such cases the relevant details are recorded.
(4) All operator access is recorded in an audit log that includes the reason for, time of, and scope of access.
Article 10 (Measures to Ensure the Security of Personal Information)
The Company takes the following security measures to protect personal information.
- Encrypted storage of passwords (bcrypt)
- Application of database row-level security (RLS)
- Encryption of all communication segments via HTTPS
- Use of Signed URLs when accessing photo files
- Application of the principle of minimizing Service access privileges
Article 11 (Use of Cookies)
(1) The Service uses cookies to maintain authentication sessions and provide Service features, to analyze sign-up acquisition paths, and to analyze Service usage and measure advertising performance.
(2) Users may refuse the storage of cookies through their browser settings. However, if cookies are refused, some Service functions, such as login, may be restricted.
(3) The Service uses Google Analytics and Google Ads for usage analysis and advertising performance measurement. In this process, visit and usage records are collected, and the Company does not combine account-identifying information (email, name, member number) with these records. However, in order to count advertising conversions without duplication, the Household identifier is transmitted together at the time of conversion (see Article 6 (4)). Users may refuse collection by the following methods.
- Install the Google Analytics Opt-out Add-on:
https://tools.google.com/dlpage/gaoptout - Turn off ad personalization in Google Ad Settings:
https://adssettings.google.com - Refuse the storage of cookies in browser settings (see Article 11 (2))
(4) For sign-up acquisition path analysis, the Service temporarily stores the path by which the User first visited the Service in a cookie. The cookie is valid for 30 days from the day it was first stored and is not extended by revisits. If you consent to this Privacy Policy after sign-up, that information is retained together with the account, and at that point the cookie is deleted. If you have not consented or have not signed up, this information remains only in the User's browser cookie and disappears when the validity period elapses; it is not retained by the Service.
- Items collected (sign-up acquisition path information): referral parameters (utm_source, utm_medium, utm_campaign, utm_term, utm_content), the domain of the immediately preceding site visited, the path of the first page visited, information on the invitation link used to sign up
- Information on the invitation link used to sign up is not placed in the above cookie and is not newly collected. The already-retained invitation records used to process family invitations and joining are used together at the time of acquisition path analysis.
- The path of the first page visited is stored excluding the portions after the question mark (?) and hash (#) in the address, and addresses that contain a unique value within the path, such as invitation or sharing links, are stored in a form with the unique value removed (e.g.,
/invite/[token]). - Sign-up acquisition path information is used only for sign-up acquisition path analysis; it is not provided to third parties and is not combined with advertising identifiers such as ad-click identifiers.
(5) Sign-up acquisition path information is destroyed together with the account when it is deleted after the 30-day protection period following member withdrawal, or after up to 6 months where the User has consented. If the User refuses the storage of cookies in their browser settings, sign-up acquisition path information is not collected (see Article 11 (2)).
Article 12 (Privacy Officer)
| Category | Details |
|---|---|
| Name | Hyunhwa Lee |
| Title | Representative Director |
| support@meomureum.app | |
| Contact | 070-8983-8906 |
Users may contact the above for inquiries, complaints, or remedies related to personal information.
Complaints related to personal information may also be filed with the following agencies.
- Personal Information Protection Commission: privacy.go.kr / tel. 182
- Korea Internet & Security Agency (KISA): privacy.kisa.or.kr / tel. 118
Revision History
| Version | Effective Date | Changes |
|---|---|---|
| v1.8 | October 15, 2026 | Notice following the iPhone app launch — added Apple login to social login in Article 1 (with notice on the "Hide My Email" relay address) · device notification token for the iPhone added to push notification delivery information · added direct processing by the App Store (Apple Inc.) to in-app subscription payment, added the App Store to in-app subscription verification in Articles 2 and 5, added Apple Inc. (Apple Push Notification service) to the push service providers in Article 5, added the App Store to the transfer purpose and timing in Article 6 (5) · added (6) iPhone app notification delivery (Apple Inc. · notification title, body, and screen address) |
| v1.7 | October 11, 2026 | Notice following the introduction of Android app subscriptions (Google Play) and push notifications — added rows for push notification delivery information, in-app subscription payment (processed directly by Google Play, not retained by Living Album), and in-app subscription records in Article 1; added in-app subscription verification and the push notification purpose in Article 2; added the entrustment of RevenueCat, Inc. and push service providers and the notice of direct processing by Google Play in Article 5; established overseas transfers in Article 6 for (5) RevenueCat (USA) and (6) push notification delivery (push service providers); supplemented the method of refusal |
| v1.6 | October 3, 2026 | Added (3) a person who is not a Household member and consented in person via a request link to the consenting persons in Article 3 (4)-1 (no sign-up or viewing rights · applies only to that Household's photos · withdrawable from the link · consent record retained) |
| v1.5 | October 3, 2026 | Specified Automatic Curation as a core service and began Facial Recognition — replaced the facial information rows in Article 1 (Facial Recognition results · reference facial feature vector · facial region in a photo), replaced the use-purpose and retention-period rows in Article 2, fully revised Article 3 (purpose limitation · separate consent · matching only against the reference faces of consenting persons · immediate discard of non-matching faces · consent by the legal representative for children under 14 · expanded grounds for deletion · (8) face location check for all photos (not identity determination)), revised the AWS entrusted work in Article 5. Deleted the former Article 3 (6) ("no automatic person classification provided · no analysis performed") |
| v1.4 | September 19, 2026 | Notice of collection of sign-up acquisition paths — added 1 automatic-collection row in Article 1 (sign-up acquisition path information), 1 use-purpose and retention-period row in Article 2, added sign-up acquisition path information to Supabase's processed items in Article 5, added sign-up acquisition path analysis to the cookie purposes in Article 11 (1), and newly established paragraph (4) (cookie validity 30 days · cookie deleted upon sign-up completion · items collected · path storage method · use restrictions) and paragraph (5) (time of destruction · not collected when cookies are refused). Corrected the Resend transfer items in Article 6 to "email address, delivery content (subject and body)" to align with Article 5 and the actual delivery content (MMR-INTL-TRANSFER-1). Newly established Article 3 (5)(6) (facial feature vectors processed in the Seoul region · no overseas transfer / currently no automatic person classification provided, only deletion requests performed) · stated the full corporate names of the three payment entrustees in Article 5 and added Kakao Pay Corp. · specified Resend's processing region (Tokyo), sub-processor (Amazon SES), and non-use of open tracking · specified the AWS region ap-northeast-2 · corrected the retention point in Article 11 (4) to "upon consent to this Policy after sign-up" (matching the corresponding rows in Articles 1 and 2) and specified that invitation link information is not newly collected but uses existing invitation records (MMR-INTL-TRANSFER-2 · MMR-PRIVACY-V14-3). ★ Fully rewrote Article 6 (MMR-INTL-TRANSFER-2) — added statutory required items such as transferee addresses, timing and method of transfer, retention periods, and contacts, deleted the statement "Vercel is excluded from overseas transfer because it is in the Seoul region" (static assets, logs, and backups are processed overseas), reflected the Household identifier passed during conversion in the Google transfer items and corrected the Article 11 (3) wording. ★ Premised on non-storage of ad-click identifiers · non-provision to third parties |
| v1.3 | September 12, 2026 (publication date) | Notice following the introduction of web analytics and advertising performance measurement tools (Google Analytics 4, Google Ads) — newly established 1 automatic-collection row in Article 1, 1 entrustment row in Article 5, 1 overseas-transfer row in Article 6, and the expansion of cookie purposes and the refusal-method notice (paragraph (3)) in Article 11. ★ Premised on non-combination of account information · non-use of remarketing |
| v1.2 | July 8, 2026 (publication date) | Newly established the collection items, purposes of use, and retention method for identity verification (KG Inicis Integrated Authentication) — the CI is stored only as a SHA-256 hash, and 1 identity-verification row was added to the entrustment table |
| v1.1 | To be separately announced after legal review | Corrected retention periods (30 days after withdrawal + 6 months with consent, consistent with Terms of Service v1.1) · newly established rows for the retention periods of the Trash and Public Posts · reflected the single-storage capacity · added entrustment and overseas-transfer items for Public Post copies |
| v1.0 | September 1, 2026 | Initial version |
Notice on the governing version: This English translation is provided for the convenience of non-Korean users and is for reference only. In the event of any conflict or discrepancy between this English version and the Korean original, the Korean original shall prevail and have legal effect.