Privacy Policy

I'm Miri (the "Company") establishes and discloses this Privacy Policy in accordance with Article 30 of the Personal Information Protection Act (PIPA) to protect the personal information of data subjects and to promptly and smoothly handle any related grievances.

1. Purpose of Collecting and Using Personal Information

The Company processes personal information for the purposes below. The personal information processed is not used for any purpose other than those stated below, and if the purpose of use changes, the Company will take necessary measures such as obtaining separate consent in accordance with Article 18 of PIPA.

1-1. Member Registration and Management

• Verifying intent to register
• Identity verification and authentication for member services
• Maintaining and managing membership
• Preventing fraudulent use of the service
• Various notices and communications

1-2. Fortune (Saju) Analysis Service

• Calculating and analyzing Saju (Four Pillars)
• Providing personalized fortune information
• AI-based conversational consultation service
• Providing AI-based real-time voice consultation and managing consultation quality (ages 18 and over)
• Providing lucky elements (colors, numbers, directions, times)
• Providing compatibility analysis and relationship advice involving acquaintances registered by the user
• Providing user-to-user invitation and connection features and relationship content (compatibility summaries, daily relationship content)
• Verifying eligibility for and granting friend-invitation rewards (free credits), and preventing abuse (detecting self-referral, multiple accounts, and cap overruns)
• Conversation safety: if a message you send contains expressions related to risks such as suicide, self-harm, or violence, we automatically analyze that message and, if it shows a risk to the life or physical safety of you or someone you mention, adjust the AI's reply to be safe, show you verified crisis and emergency contacts, and pause fortune notifications for 72 hours (from October 5, 2026).
• Providing the pre-sign-in conversation trial (a first reading and an answer to one question), linking a trial account when you sign in, and preventing misuse of the trial (from October 1, 2026)
• Providing mood records in check-ins and the 21-day journey, and, if you separately consent, personalized consultations that take those records into account

1-3. Service Improvement and Development

• Developing new services and providing customized services
• Service usage statistics and analysis
• Improving service quality
• Analyzing service usage statistics (Google Analytics for Firebase) and measuring ad performance (Google Ads — checking whether an app install, sign-up, or purchase came from an ad)
• Checking the quality of AI replies and support replies, investigating incidents and errors, and comparing AI models (Section 3-3-9)

2. Personal Information Collected

The Company collects the following personal information to provide its services.

2-1. Required Information

• At registration: social login identifier (Apple ID or Google account), email address, name — when using Apple Sign-in / Google Sign-in
• For Saju analysis: date of birth (solar/lunar), time of birth, place of birth
• During service use: AI conversation history, Saju analysis results, service usage records
• When using voice consultation (ages 18 and over): real-time voice data, input/output transcription text of the user and the AI, information the user provides directly during the conversation, call date/time and session identifiers, AI responses and quality-evaluation results
  ※ The original voice audio is not permanently stored in the Company's databases; it is processed in real time to generate AI responses and then destroyed. Only the text transcripts of the conversation are retained for a limited period for consultation quality management and then automatically deleted. Depending on feature settings and processor policies, conversation state/cache may be temporarily retained (up to 24 hours).
• When using acquaintance compatibility (optional): information about an acquaintance entered directly by the user — name or nickname, date of birth, time of birth (optional), place of birth (optional), gender (optional), relationship, blood type (optional)
  ※ Acquaintance information is used solely for compatibility analysis within the user's own account and is not disclosed to the acquaintance or to other users. When entering another person's personal information, the user is responsible for complying with applicable laws, including obtaining that data subject's consent; if the data subject requests deletion, the Company will delete the information without delay (via the in-app deletion feature or an email inquiry). Acquaintance information is destroyed when the user withdraws membership.
• When using friend invitation and connection (optional): information you agree to share mutually when an invitation is accepted — nickname (or name) and compatibility summary results (a non-detailed summary such as score, grade, and description)
  ※ Original birth information such as date and time of birth, and detailed readings, are not disclosed to the other party (only summary results are shared mutually). Mutual sharing stops immediately upon disconnection or blocking. This feature is available only to users aged 14 or older (verified by birth year when accepting a connection request).
• When using friend referral (optional): your invite code, another member's invite code that you enter, the referrer–referee relationship (by account identifier), whether the reward conditions have been met (question count reached, time elapsed since sign-up), and reward grant records
  ※ An invite code is a random 8-character string and contains no personally identifying information such as a name or email. The referrer is not told the referee's name, email, or account; only the fact that “a friend you invited has met the conditions” and the credits granted are notified.
  ※ To prevent abuse, the Company separately stores a one-way hash (SHA-256) of your social login identifier or email address (the original is not stored and cannot be recovered). This hash is used only to enforce one account per person and to calculate reward caps, and is kept separately for one year after membership withdrawal, then destroyed.
• When you contact support: your email address, the subject and body of your inquiry, attachments, and send/receive timestamps
  ※ This covers both the in-app support chat and inquiries sent directly to the Company's support email address (cristina@miri.im). An inquiry may contain information you provide yourself, such as a payment order or receipt number. The Company uses it solely to handle and answer your inquiry, diagnose faults, and improve the service. Non-members may also contact us by email; in that case the Company processes the above only as needed to reply and deletes it once the period in Section 3-3-4 has passed.
• During the pre-sign-in conversation trial: a temporary account identifier (a random string), the information the character asks for (whichever of name, gender, date of birth, time of birth, and place of birth applies), AI conversation history, and the number of trial uses
• When using check-ins and the 21-day journey (optional, separate consent): your mood for the day (on a 5-point scale) and the options you choose in a check-in (whether you did the suggested practice, and the kind of commitment you chose). Because mood records may be considered health-related information, we ask for separate consent the first time you record one; you can use the rest of the service without consenting.
• Marketing communications (optional): whether you have consented to receive marketing communications

2-2. Automatically Collected Information

• Device information (OS version, device model)
• Service usage records
• Access logs
• App error logs (Firebase Crashlytics) — from September 28, 2026 at 00:00 Korea Standard Time (UTC+9), linked to your account identifier (a random string, not your name or email) so that we can diagnose errors and respond to outages (announced September 20, 2026).
• Cookies and access IP information
• Install attribution information (store install referrer, UTM parameters, type of inbound link)
• Records of the issuance, viewing, entry, and acceptance of invite links, invite codes, and referral codes, and their results
• Hashed access IP for abuse prevention (original not stored) — only when deciding whether to grant an invite reward
• App usage statistics (Google Analytics for Firebase): in-app events (screen use, purchases, conversation usage metrics, and similar) and usage attributes (birth year, platform, subscription status, favorite character, and similar), processed linked to your member account identifier (a random string, not your name or email address).
• Ad performance measurement information (Google Ads): ad click identifier (gclid), the ad click and install start times in the store install referrer, sign-up and purchase times, and purchase amount and order number. We do not send this to Google Ads for installs that came from the European Economic Area, the United Kingdom, or Switzerland.
• Device token for notifications (Firebase Cloud Messaging): used to send service notifications such as support replies and billing notices and, if you have agreed to receive marketing communications, proactive messages. It is deleted when delivery keeps failing or when you delete your account.

2-3. Collection Methods

• Collected during registration and service use through the mobile app
• Collected via Apple Sign-in / Google Sign-in
• Automatically generated and collected during service use
• Collected when you send an inquiry through the in-app support chat or to the Company's support email address

2-4. Reading an Invitation Before Creating an Account

Announced September 15, 2026; effective September 23, 2026 at 00:00 Korea Standard Time (UTC+9). These provisions apply when the new invitation and relationship reading feature is made available.

A recipient may enter their own date of birth and consent to its use for a relationship reading without creating an account. When the birth time is unknown, the result uses the information that is available. This feature is available to people aged 14 or older.

An acquaintance invitation checks the entered birthday against the birthday previously entered by the sender. A direct invitation does not require that match. After the recipient requests a connection with an account, the sender must confirm the recipient's display name. Viewing a preview alone does not connect the accounts or notify the sender that it was viewed.

2-5. Pre-Sign-In Conversation Trial

Effective on posting, October 1, 2026. Offered to some new users in certain countries.

Some new users in certain countries can try a short conversation with a character (a first reading and an answer to one question of their own) before signing up with Apple or Google. For this we create a temporary account identifier, a random string rather than a name or email address, and process the information needed for the conversation (whichever of name, gender, date of birth, time of birth, and place of birth the character asks for) and the conversation itself in the same way as members' AI consultations.

When you sign in, the temporary account is linked to that Apple or Google account, so the trial conversation and the information you entered carry over as they are, and the sign-up benefit is granted at that point. If you sign in with an Apple or Google account that is already a member, you are signed in to the existing account and the trial conversation does not carry over.

During the trial you cannot make payments, receive referral rewards, or use the in-app support chat, and we do not send you marketing messages. To prevent misuse, the trial is offered only in genuinely installed copies of the app and has a daily limit.

3. Processing and Retention Period

The Company processes and retains personal information within the retention/use period required by law or the retention/use period consented to by the data subject at the time of collection.

3-1. Member Information

• Retention period: Until membership withdrawal
• Withdrawal processing: After a withdrawal request, personal information is destroyed following a 24-hour grace period. During the grace period, account access is blocked; after 24 hours, deletion proceeds automatically and completes within 48 hours of the request at the latest.
• Statutory retention exception: Records subject to statutory retention under Section 3-3 below (payment/contract records, customer inquiry records, etc.) are not deleted but de-identified (user identifiers replaced with an encrypted hash; contact and payment details in inquiry text masked) and kept only for the statutory period. De-identified records are not used beyond the statutory purpose, except that pseudonymized customer inquiry records may be used solely for internal analysis for statistics and service improvement under Article 28-2 of the Personal Information Protection Act, and we take no steps to re-identify any individual.
• Exception: Where an investigation or inquiry due to a violation of applicable laws is underway, until such investigation or inquiry concludes.

3-2. Service Usage Records

• Retention period: Automatically deleted after the 24-hour grace period following membership withdrawal (completed within 48 hours of the request at the latest)
• Exception: Where retention is required by law, retained for the period specified by that law

3-3-3. User-to-User Connection (Social) Data

The table below describes the existing invitation and connection process. Section 3-3-5 applies to temporary storage and security/usage records for the new invitation and relationship reading feature from its stated effective date.

User-to-user invitation and connection data is destroyed or made inaccessible at the following points:

Event	Connection	Invitation	Compatibility summary (mutually shared)	Notifications / unread
Invitation expiry (default 7 days)	—	Made inaccessible, then deleted (the “expired” indicator on the sender's screen remains until the sender re-sends the invitation or deletes the acquaintance)	—	—
Invitation declined	Not created	Deleted	—	—
Disconnection	Deleted	—	Deleted	Deleted
Block	Hidden + re-invitation blocked	Invalidated	Deleted	Deleted
Membership withdrawal	Disconnected and hidden immediately upon the withdrawal request (fully destroyed when the account is deleted)	Invalidated	Deleted	Deleted
Daily relationship content	Refreshed daily while the connection is maintained (only the current day's content is kept; the previous day's is overwritten)	—	—	—

Friend referral data

• Referrer–referee relationship records: retained for one year after the reward is confirmed (or voided), then destroyed. Upon membership withdrawal, the withdrawing member's side of the record is voided immediately and destroyed when the withdrawal process completes (only a “void” status remains on the other member's side).
• Abuse-prevention identifier hash: stored separately solely for abuse prevention, and kept for one year after membership withdrawal to prevent duplicate rewards through re-registration, then destroyed. The value cannot be reversed to the original and is not used for any other purpose.
• Reward grant records (credit ledger): treated as transaction records under Article 19 of the Terms of Service and the E-Commerce Act (Korea), and follow the statutory retention periods in Section 3-3 (de-identified upon withdrawal).

Notice of discontinuation of the conversation share link feature

The Company is discontinuing the “conversation share link” feature (discontinuation announced on September 5, 2026). Existing links remain viewable until December 4, 2026; after that date, access ends and shared copies are deleted. During the grace period, you may request immediate deletion of your own share links through the app or by contacting support. Upon membership withdrawal, shared copies are deleted as part of the withdrawal process.

3-3-2. Voice Consultation Records

• Voice consultation text transcripts: Retained for 7 days from creation, then deleted without delay (users may also request access or deletion before then)
• Voice consultation quality-evaluation results: Retained as aggregate statistics that cannot identify individuals
• Voice consultation consent records (including consent-wording version, per-item consent results, and time of withdrawal): Until membership withdrawal

3-3-4. Customer Inquiry Records

• Retention period: destroyed without delay once 3 years have passed from the date the inquiry was resolved (records on consumer complaints or dispute resolution under the Act on Consumer Protection in Electronic Commerce — see 3-3 below).
• Inquiries from members: upon account deletion, inquiry records are pseudonymized as described in 3-1 (member identifier replaced with an encrypted hash; contact and payment details in the text masked), retained for 3 years from the date the inquiry was resolved, and then destroyed; internal staff notes are destroyed immediately upon deletion. (Inquiry records of members who deleted their accounts before September 19, 2026 were destroyed together with the account under the previous policy.)
• Email inquiries from non-members: destroyed once the statutory period above has passed, and destroyed without delay upon the data subject's deletion request before then (except where a statutory retention obligation applies).

3-3-5. Temporary Storage and Security and Usage Records for Invitations and Relationship Readings

Announced September 15, 2026; effective September 23, 2026 at 00:00 Korea Standard Time (UTC+9). These provisions apply when the new invitation and relationship reading feature is made available.

The submitted birthday and reading are used to process the preview. Birth details are not placed in the invitation URL, analytics events, or the shared connection document. To avoid asking for the same input again during sign-in, the current browser tab may keep the input and result in session storage for up to 24 hours or until the invitation expires, whichever is earlier. The data is cleared on completion or when the recipient declines. A signed proof contains no original birth input and expires after 30 minutes. Access is rechecked when the page is reloaded or restored.

To limit verification abuse, a keyed hash of a network address is used in a rate-limit record. It is marked for deletion 24 hours after the last permitted calculation request; another permitted request updates the counter and scheduled deletion time. The original address is not stored in that record. Mismatch counters and lock state protect invitation verification.

A result-display receipt contains the invitation identifier, a hash of the signed proof, and the display time, and is marked for deletion after 24 hours. Invitation and connection events, result views, return visits, and account creation time are used to measure activation and usefulness. These measurement records exclude original birthdays, charts, and names. Resolved invitation records follow the existing 30-day retention period. Account-linked experiment assignments and first-conversion summaries are removed when account deletion is scheduled. Actual TTL deletion timing depends on the database's deletion cycle.

3-3-6. Conversation Safety Processing

Announced September 27, 2026; effective October 5, 2026 at 00:00 Korea Standard Time (UTC+9).

• Analysis results are kept only as daily aggregate statistics that cannot identify you (for example, how many crisis notices were shown — for legally required reporting and safety management). We do not store analysis results linked to your account.
• Contact cards shown to you are kept with that conversation and follow the retention and deletion rules for conversation records.
• The notification pause marker is deleted automatically 72 hours after it is set, and the reason for the pause is not stored.
• No person reads your conversations in real time as part of this processing, and we do not provide the analysis results to third parties except where required by law.
• From September 27 to October 4, 2026 (before the effective date), the same analysis runs as a trial. During the trial, the results are not applied to AI replies, support contact guidance, or notifications, and are kept only in daily aggregate statistics that cannot identify individuals. The analysis is processed in the same way as the conversation safety items in Sections 4-1, 5, and 5-2 (OpenAI, L.L.C., with Google (Gemini API) as a backup when OpenAI is unavailable).

3-3-7. Pre-Sign-In Trial Accounts

Effective on posting, October 1, 2026.

• Trial accounts that never sign in: 7 days after creation, the trial conversation, the information entered, and the trial-use count are deleted automatically in the same way as a membership withdrawal. Because this runs once a day, deletion may happen up to one day later.
• If you sign in (link the account): the retention rules for member information (Section 3-1) apply.
• Even during the trial or without signing in, you can ask us to delete your trial information by emailing customer support (cristina@miri.im).

3-3-8. Check-in and Journey Mood Records

Effective upon posting on October 4, 2026 (adds processing already in operation).

• Mood records (check-ins and the 21-day journey) are deleted automatically 12 months after the day they were recorded. If you reset your records or delete your account before then, they are deleted at that time.

3-3-9. Operational Quality Checks and AI Analysis Tools

Effective upon posting on October 4, 2026 (adds processing already in operation).

• To manage service quality and safety, the Company analyzes part of its conversation and customer support records with AI analysis tools: (1) AI reply quality checks — each day we analyze the content of a random sample of conversations and the information remembered from them; (2) support reply quality reviews — we review sent replies together with the inquiries they answer; (3) incident and error investigations — when an error is reported or an anomaly is detected, we check account and usage records to the extent needed to find the cause; (4) AI model comparisons — before adopting a new AI model, we compare replies using part of real conversations, replacing names, place names, contact details, and similar information with pseudonyms where possible.
• We do not send email addresses to these tools. We do not send member account identifiers for (1), (2), or (4), and for (2) we mask names, contact details, and similar information in inquiries and replies before sending them. Drafting support replies (the Google LLC (Vertex AI) item in Section 5) and (3) incident and error investigations may include account information to the extent needed. Investigating and replying to support inquiries (the Anthropic, PBC item in Section 5) does not include member account identifiers or email addresses; it may include inquiry content with names and contact details masked, and account and usage records to the extent needed to find the cause.
• The providers of these tools are OpenAI, L.L.C., Anthropic, PBC, and Google LLC (Vertex AI and Gemini API); retention on the provider side follows each company's data retention policy. The daily automated analyses in (1) and (2) are processed through the API of OpenAI, L.L.C. (business terms), and content sent to analysis tools is not used to train models. The Company keeps the analysis results (scores and classifications) and the copies of conversations used for analysis in a work environment with restricted access, and deletes them one year after the analysis.

3-3-10. Information Remembered from Conversations

Announced October 10, 2026. Deleting memory items together with a deleted conversation applies from October 18, 2026 at 00:00 Korea Standard Time (UTC+9).

• Information that an oracle remembers from conversations is kept for each oracle in your member account and is destroyed together with it upon membership withdrawal (Section 3-1).
• You can erase what the oracles remember with Settings → Manage Memory → Clear, and Settings → Reset Usage Data deletes all conversations together with the remembered information.
• When you delete a conversation, memory items based on that conversation are deleted too.

3-3. Statutory Retention

• Records on contracts or withdrawal of subscription: 5 years (E-Commerce Act (Korea))
• Records on payment and the supply of goods, etc.: 5 years (E-Commerce Act (Korea))
• Records on consumer complaints or dispute handling: 3 years (E-Commerce Act (Korea))
• Records on labeling/advertising: 6 months (E-Commerce Act (Korea))
• Website visit records: 3 months (Protection of Communications Secrets Act)

4. Provision of Personal Information to Third Parties

In principle, the Company processes users' personal information only within the scope specified in Article 1 (Purpose of Collecting and Using Personal Information) and does not process it beyond the original scope or provide it to third parties without the user's prior consent.

However, the following are exceptions.

4-1. Essential Provision for Service Delivery

The Company provides personal information to third parties as follows:

Recipient	Purpose	Information Provided	Retention and Use Period
Google (Gemini API)	AI conversation generation, real-time voice conversation generation and transcription, consultation quality evaluation, backup processing for conversation safety assessment (when OpenAI is unavailable, from October 5, 2026)	Conversation history, Saju analysis results, and—for voice consultation—the user's voice (real-time streaming) and conversation transcripts (stated explicitly from October 5, 2026: the name, gender, date, time and place of birth you entered, conversation summaries and information remembered from conversations, and—when you use those features—psychological survey results and your registered acquaintances' names, relationships and birth information) / Backup processing for conversation safety assessment (when OpenAI is unavailable, from October 5, 2026): the latest message you entered and part of the preceding conversation	Deleted without delay after processing (temporary session state/cache up to 24 hours)
OpenAI, L.L.C.	(1) Writing the first greeting of a conversation (from October 4, 2026) (2) Drafting automatic replies to in-app customer inquiries (3) Generating AI consultation replies in certain countries and plans designated by the Company (from when that feature is offered) (4) Proactive message generation — generated by OpenAI for characters and languages designated by the Company (from September 27, 2026); otherwise backup processing only when the primary provider (Google) fails or is misconfigured (5) Conversation safety assessment (detecting risk signals such as suicide, self-harm, or violence) — only for messages containing risk-related expressions (from October 5, 2026) (6) Organizing what to remember from conversations — organizing ongoing matters, people in your life, conversation preferences, moments you shared and similar points from your conversations with an oracle for use in your next conversations with that oracle (from October 18, 2026)	(1) Character information, current time of day, whether you have visited before, one trait calculated from your birth information (e.g., Day Master, Sun sign, Life Path number), earlier greeting text, one ongoing matter remembered from your conversations with the same oracle (e.g., an upcoming interview or exam — excluding birth information and sensitive information; from October 18, 2026) — excluding your name, date of birth, and any conversation content other than that one remembered matter (2) Inquiry conversation, subscription and payment history (plan, amount paid, payment date, card issuer name, transaction number, status), credit balance and remaining free usage, sign-up date, sign-in method, partially masked email, device type and app version, payment and error diagnostics, summaries of recent inquiries — excluding birth information and consultation conversations (3) Conversation history, Saju analysis results, the name, gender, date, time and place of birth you entered, conversation summaries and information remembered from conversations, and—when you use those features—psychological survey results and your registered acquaintances' names, relationships and birth information (4) Account identifier, analysis results calculated from birth information, conversation summaries and recent messages, information remembered from conversations (excluding birth information), and, where those features are used, psychology survey results and an acquaintance's name and relationship (5) The latest message you entered and part of the preceding conversation (up to three of your messages, the end of the previous AI reply, and the app language setting) — excluding account identifier, name, date of birth, and Saju information (6) Your conversation history with that oracle (your messages and the oracle's replies) and the information that oracle has already remembered — birth information and sensitive information such as health, sex life, political views, religion, trade union membership or criminal records are not stored as memories	Processed with the no-response-storage option applied; under OpenAI API policy, retained for up to 30 days for abuse monitoring and then deleted (encrypted computation cache for response speed up to 24 hours); files used for (4) are deleted once processing is complete (from October 4, 2026) (not used to train AI models)
Google (Firebase)	Data storage and management	Member information, Saju information, conversation history, voice transcripts	Until membership withdrawal (voice transcripts: 7 days from creation)
Google	Google Sign-in authentication	Google account identifier, email, name	Deleted immediately after authentication
Apple	Apple Sign-in authentication	Apple ID, email, name	Deleted immediately after authentication
Apple	Supporting App Store refund request review	Purchase transaction information, service usage/consumption information (usage period, usage volume, etc.)	Per Apple's refund review policy

If you have consented to check-in and journey mood records, your recent mood records are also sent to the AI consultation reply items in the table above (Google (Gemini API) and OpenAI, L.L.C.) when generating AI consultation replies.

4-1-2. Provision to Other Users (User-to-User Connection Feature)

The invitation and connection provisions below apply to the existing process. Section 4-1-3 applies to the new invitation and relationship reading feature from its stated effective date. Existing connections keep the information-use scope below until both people give the new consent. The invite-reward provisions remain unchanged.

Only when a user directly sends an invitation and the other party accepts it does the Company provide the following information to the other user:

Recipient	Purpose	Information Provided	Retention and Use Period
The other user whom you invited and who accepted	Mutual compatibility confirmation and relationship content	Nickname (or name), compatibility summary results, summary chart indicators (summary markers such as day-master element and zodiac sign, not detailed readings), mutually confirmed relationship label (only where both parties have each selected one), daily relationship content (a phrase, temperature, and highlight marker summarizing the day's relationship flow — generated from each user's own perspective and not including the other party's original birth information)	While the connection is maintained (ends upon disconnection, blocking, or membership withdrawal)
The counterpart member of an invite reward (referrer or referee)	Notifying that an invite reward has been granted	The fact that “a friend you invited (or the friend who invited you) has met the conditions” and the number of credits granted (no name, email, or account identifier)	One time, at the point of notification

• Invitation (link): The preview (OG) and crawler-facing screens of an invite link contain no personally identifying information whatsoever. The pre-authentication landing screen may display only the display name (nickname) that the sender chose to disclose when sending the invitation, and contains no information about the recipient or any third party. Personalized content (such as compatibility) is displayed only after the recipient completes identity verification (date-of-birth match).
• Registration notice: If the other party has registered you as an acquaintance and viewed compatibility, you are informed of this during the connection acceptance process, and you may choose to delete your information or decline the connection.
• Daily relationship content: Only the stored computed values (trigger, temperature, highlight marker) are kept on the server; the sentences are generated in each user's app. Even if the other party edits their own birth information, the information confirmed at the time of connection is used, and neither the fact of the edit nor the edited values are provided to the other party.

4-1-3. Connecting and Sharing Relationship Readings

Announced September 15, 2026; effective September 23, 2026 at 00:00 Korea Standard Time (UTC+9). These provisions apply when the new invitation and relationship reading feature is made available.

Each person explicitly agrees before display names and the relationship reading are shared. The reading may include strengths, possible differences, practical suggestions, example phrases, and a daily relationship practice. Original birth dates, times, places, detailed individual charts, and personal conversations are not shown to the other person.

After both people give the new consent, readings use the latest birth information each person confirms in their own account. A change to that information may change subsequent readings. Missing information or unavailable calculations produce an input or retry message. Existing connections keep their previous information-use scope until both people give the new consent.

Disconnecting, blocking, or scheduling account deletion stops access to shared results. An acquaintance invitation recipient may verify their identity and request removal of the acquaintance information entered by the sender. A direct invitation does not create an acquaintance record containing the recipient's birthday. Previewing and connecting are optional.

4-2. Provision Required by Law

• Where there are special provisions in law or it is unavoidable in order to comply with legal obligations
• Where it is unavoidable for a public institution to perform its statutory duties

5. Consignment of Personal Information Processing

For the smooth handling of personal information, the Company consigns personal information processing tasks as follows:

Consignee	Consigned Task	Consignment Period
Google LLC (Firebase)	Cloud server operation and data storage	Until membership withdrawal or termination of the consignment contract
Google (Gemini API)	AI conversation generation service, real-time voice conversation processing and transcription, consultation quality evaluation, backup processing for conversation safety assessment (when OpenAI is unavailable, from October 5, 2026)	Each time the service is used
OpenAI, L.L.C.	Writing the first greeting of a conversation (from October 4, 2026), drafting automatic replies to in-app customer inquiries, generating AI consultation replies in certain countries and plans (from when that feature is offered), proactive message generation (for characters and languages designated by the Company, from September 27, 2026) and backup processing for other proactive messages (when the primary provider fails or is misconfigured), conversation safety assessment (detecting risk signals such as suicide, self-harm, or violence) — only for messages containing risk-related expressions (from October 5, 2026), organizing what to remember from conversations (organizing ongoing matters and similar points from conversations with the same oracle, from October 18, 2026)	Each time the service is used
Google LLC (Google Analytics for Firebase · Google Ads)	Service usage statistics analysis and ad performance (conversion) measurement	Until the entrustment contract ends
Google LLC (Vertex AI — Anthropic Claude models)	Drafting customer support replies (drafting replies and preparing to send replies that pass the Company's review criteria) and drafting replies to store reviews	Each time processing is performed
Anthropic, PBC	Investigating and replying to support inquiries (investigating the cause of inquiries the in-app support AI could not resolve, drafting replies, and preparing to send replies that pass the Company's review criteria)	Each time processing is performed
Plus Five Five, Inc. (Resend)	Sending the emails the app sends (support replies, acknowledgements of email inquiries, and billing, cancellation, and refund notices)	Each time an email is sent
OpenAI, L.L.C. · Anthropic, PBC · Google LLC (Vertex AI · Gemini API)	Operational quality checks (AI reply and support reply quality checks, incident and error investigations, and AI model comparisons — Section 3-3-9)	Each time processing is performed

When entering into consignment contracts, in accordance with Article 26 of PIPA, the Company specifies in the contract or other documents such matters as the prohibition of processing personal information beyond the purpose of the consigned work, technical and managerial safeguards, restrictions on re-consignment, supervision of the consignee, and liability including damages, and supervises whether the consignee processes personal information safely.

5-2. International Transfer of Personal Information

To the extent necessary to perform the AI conversation/voice consultation/customer inquiry service contract concluded with the user, and pursuant to Article 28-8(1)(iii) of PIPA, the Company consigns the processing of and stores personal information overseas as follows.

Recipient (Contact)	Country	Date/Time and Method of Transfer	Items Transferred	Purpose of Use	Retention/Use Period
Google LLC (Privacy inquiries: googlekrsupport@google.com · Google Korea LLC, 152 Teheran-ro, Gangnam-gu, Seoul (Gangnam Finance Center), ☎ +82-2-531-9000 · HQ: 1600 Amphitheatre Pkwy, Mountain View, CA 94043, USA)	USA	Real-time encrypted transmission over the network during consultation	Real-time voice, input/output transcripts, conversation content, Saju analysis results (stated explicitly from October 5, 2026: name, gender, date/time/place of birth, conversation summaries and remembered information, and—when you use those features—psychological survey results and acquaintance information) / Backup processing for conversation safety assessment (when OpenAI is unavailable, from October 5, 2026): the latest message you entered and part of the preceding conversation	Real-time AI conversation/voice conversation generation and transcription, backup processing for conversation safety assessment (when OpenAI is unavailable, from October 5, 2026)	Deleted without delay after processing (temporary session state/cache up to 24 hours)
Google LLC (Firebase, same as above)	USA	Stored continuously during service use	Member information, Saju information, conversation/transcript records, app error logs (linked to the account identifier from September 28, 2026)	Cloud data storage and management	Until membership withdrawal or the end of the retention period (voice transcripts: 7 days)
Google LLC (Gemini API, same as above)	USA	Transmitted at quality evaluation after the consultation ends	Voice conversation transcripts	Consultation quality management	Deleted after processing is complete
OpenAI, L.L.C. (Privacy inquiries: https://privacy.openai.com)	USA	Real-time encrypted transmission over the network when a first greeting, customer inquiry reply, or AI consultation reply is generated; for proactive message generation, encrypted file transfer (daily for characters and languages designated by the Company, from September 27, 2026; otherwise when the primary provider fails or is misconfigured); real-time encrypted transmission over the network for conversation safety assessment (from October 5, 2026); encrypted transmission over the network when organizing what to remember from conversations (from October 18, 2026)	First greeting: one trait calculated from birth information, time of day, whether you have visited before, earlier greeting text, one ongoing matter remembered from conversations with the same oracle (excluding birth information and sensitive information, from October 18, 2026) / Customer inquiries: inquiry conversation, subscription, payment, credit, account, device, and diagnostic information / AI consultation replies: conversation content, Saju analysis results, name, gender, date/time/place of birth, conversation summaries and remembered information, and—when you use those features—psychological survey results and acquaintance information / Proactive messages: account identifier, analysis results, conversation summaries and recent messages, remembered information / Conversation safety assessment: the latest message you entered and part of the preceding conversation (up to three of your messages, the end of the previous AI reply, and the app language setting) — excluding account identifier, name, date of birth, and Saju information / Organizing what to remember from conversations: conversation history with that oracle (your messages and the oracle's replies), information already remembered — birth information and sensitive information are not stored as memories (from October 18, 2026)	First greeting generation (from October 4, 2026), automatic replies to customer inquiries, AI consultation reply generation in certain countries and plans (from when that feature is offered), proactive message generation (for characters and languages designated by the Company, from September 27, 2026) and backup processing, conversation safety assessment (detecting risk signals such as suicide, self-harm, or violence) — only for messages containing risk-related expressions (from October 5, 2026), organizing what to remember from conversations (from October 18, 2026)	No-response-storage option applied; under OpenAI API policy, retained for up to 30 days for abuse monitoring and then deleted (encrypted computation cache up to 24 hours); files used for proactive message processing are deleted once processing is complete (from October 4, 2026)
Google LLC (Google Analytics for Firebase · Google Ads, same as above)	United States	Encrypted transmission over the network during app use and conversion measurement	In-app events and usage attributes (linked to your member account identifier); ad click identifier (gclid), ad click and install start times, sign-up and purchase times, purchase amount, and order number	Service usage statistics analysis and ad performance measurement	In accordance with Google's retention policy and the Company's retention settings
Google LLC (Vertex AI, same as above)	United States and other Google Cloud processing regions	Encrypted transmission over the network when drafting support replies and store review replies	Support inquiries: inquiry subject and body, name, account identifier, subscription and payment status, sign-up date and platform, past inquiry and refund history, and, if you have agreed to it being viewed, part of your recent conversation history / Store reviews: review content and the reviewer's display name	Drafting customer support replies and store review replies	In accordance with Google Cloud's data processing terms (not used for model training)
Anthropic, PBC (privacy@anthropic.com)	United States	Encrypted transmission over the network when investigating and replying to support inquiries	Inquiry subject and body (names and contact details masked), subscription and payment status and payment records (including transaction numbers), sign-up date and platform, past inquiry and refund history, service usage and error records needed to find the cause, and, if you have agreed to it being viewed, part of your recent conversation history — excluding member account identifiers and email addresses	Investigating the cause of support inquiries and drafting replies	In accordance with Anthropic's data retention policy (not used for model training)
Plus Five Five, Inc. (Resend; privacy inquiries: support@resend.com)	United States	Encrypted transmission over the network when sending email	Recipient email address, name, and email body (support replies and billing, cancellation, and refund notices, including amounts)	Sending email	In accordance with Resend's sending log retention policy
OpenAI, L.L.C. (https://privacy.openai.com) · Anthropic, PBC (privacy@anthropic.com) · Google LLC (googlekrsupport@google.com)	United States	Encrypted transmission over the network during analysis	Items analyzed under Section 3-3-9: part of conversation content and remembered information, support inquiries and sent replies (names and contact details masked), account and usage records needed for incident and error investigations, and conversations used for model comparisons (pseudonymized where possible)	Operational quality checks	In accordance with each company's data retention policy

Method, procedure, and effect of refusing the transfer: The international transfers above are essential to providing the AI conversation/voice consultation features. For voice consultation, you can review and refuse the transfer during the separate consent process presented at first use; if you do not consent, you cannot use AI voice consultation, but there is no restriction on using other services. If you do not consent to the transfer related to text-based AI conversation, you cannot use the AI conversation feature. Transfers for automatic replies to in-app customer inquiries are necessary to provide that feature.

If the notice above changes, the Company will inform you in advance (Article 28-8(3)), and when transferring personal information overseas, the Company implements the protective measures set out in Articles 17 through 19 and Chapter V of PIPA and its Enforcement Decree (paragraph 4).

6. Rights of Data Subjects and How to Exercise Them

Data subjects may exercise the following personal information protection rights against the Company at any time:

6-1. Rights

1. Right to request access to personal information
2. Right to request correction of errors
3. Right to request deletion
4. Right to request suspension of processing

6-2. How to Exercise Rights

6-3. Limitations on Exercising Rights

The exercise of data subjects' rights may be restricted in the following cases:

• Where there are special provisions in law or it is unavoidable in order to comply with legal obligations
• Where there is a risk of harming another person's life or body, or of unfairly infringing another person's property or other interests

For users in the EU/EEA, the United Kingdom and Switzerland, you also have the right to data portability, the right to object to processing and the right to lodge a complaint with a data protection supervisory authority. The legal bases for our processing and further details are in our Supplementary Privacy Notice for these users (miri.im/privacy-eu · in French: miri.im/privacy-fr).

7. Destruction of Personal Information

When personal information becomes unnecessary due to the expiration of the retention period, achievement of the processing purpose, etc., the Company destroys it without delay.

7-1. Destruction Procedure

• Information entered by the user is, after the purpose is achieved, moved to a separate database (or separate documents in the case of paper) and stored for a certain period in accordance with internal policies and other applicable laws, or destroyed immediately.
• Such personal information is not used for any other purpose except as required by law.

7-2. Destruction Method

• Electronic files: Completely deleted using technical methods that prevent the records from being reproduced
• Paper documents: Shredded or incinerated

8. Measures to Ensure the Security of Personal Information

In accordance with Article 29 of PIPA, the Company takes the following technical, managerial, and physical measures necessary to ensure security:

8-1. Managerial Measures

• Establishing and implementing an internal management plan
• Regular employee training
• Minimizing and training staff who handle personal information

8-2. Technical Measures

• Encryption of personal information
• Technical countermeasures against hacking and similar threats
• Installation of access control systems
• Retention of access logs and prevention of forgery or tampering

8-3. Physical Measures

• Access control for computer rooms, data storage rooms, and similar facilities

9. Installation, Operation, and Refusal of Automatic Collection Devices

The Company may automatically collect the following information to improve services and provide customized services:

9-1. Information Collected

• App usage patterns
• Device information (OS version, device model)
• Service usage statistics
• App usage statistics (Google Analytics for Firebase, linked to your member account identifier) and ad performance measurement information (Google Ads)

9-2. How to Refuse

Users can refuse the collection of information through their device settings:

• iOS: Settings → Privacy → Tracking → turn off "Allow Apps to Request to Track"

10. Personal Information Protection Officer

The Company designates a Personal Information Protection Officer, as set out below, to take overall responsibility for personal information processing and to handle data subjects' complaints and provide remedies for damages related to personal information processing:

Data subjects may direct any inquiries, complaints, or requests for damage relief related to personal information protection arising from their use of the Company's services to the Personal Information Protection Officer. The Company will respond to and handle data subjects' inquiries without delay.

11. Requesting Access to Personal Information

Under Article 35 of PIPA, data subjects may request access to their personal information from the department below. The Company will endeavor to process such access requests promptly:

12. Remedies for Rights Infringement

Data subjects may contact the following organizations for damage relief, consultation, and similar matters regarding personal information infringement:

12-1. Personal Information Infringement Report Center (operated by KISA)

• Responsibilities: Reporting personal information infringement, requesting consultation
• Website: privacy.kisa.or.kr
• Phone: 118 (no area code)
• Address: (58324) 3F, 9 Jinheung-gil, Naju-si, Jeollanam-do, Republic of Korea

12-2. Personal Information Dispute Mediation Committee

• Responsibilities: Applications for personal information dispute mediation and collective dispute mediation (civil resolution)
• Website: www.kopico.go.kr
• Phone: 1833-6972 (no area code)
• Address: (03171) 4F, Government Complex Seoul, 209 Sejong-daero, Jongno-gu, Seoul

12-3. Supreme Prosecutors' Office Cybercrime Investigation Division

• Phone: 02-3480-3573
• Website: www.spo.go.kr

12-4. National Police Agency Cyber Bureau

• Phone: 182 (no area code)
• Website: cyberbureau.police.go.kr

12-5. For users outside Korea

Please contact your local data protection authority or email us at cristina@miri.im.

13. Changes to This Privacy Policy

This Privacy Policy is effective from September 12, 2026. If there are additions, deletions, or corrections due to changes in law or policy, the Company will provide notice by posting an announcement on this Privacy Policy page at least 7 days before the changes take effect.