Mirua Privacy Policy — English Reference

Revision: 1.8.0
Effective date: 2026-10-20
Last revised: 2026-09-20

Reference document: English Terms

This is a reference translation. The Korean policy is authoritative for Korean users, and the Japanese policy applies to Japanese users. In case of any discrepancy, the applicable Korean or Japanese version prevails.

1. Controller

Mirua, represented by OH YUJUN, Korean business registration number 339-29-01761. Address: Unit 901-346, 9F, 33 Dongtanjungsimsangga 1-gil, Dongtan-gu, Hwaseong-si, Gyeonggi-do 18455, Republic of Korea. Privacy contact: [email protected], +82-70-8058-8479.

2. Data and purposes

Mirua processes:

• account and social-login identifiers, an internal lookup address derived from the provider identifier, an email hint supplied on the first Google or Apple login to suggest a contact email (distinct from the ownership-verified contact email), display name, image, OAuth credentials, verification state, date of birth, and gender (optional) for registration, login, account security, user identification, confirming that you are 14 or older, recommendations and service analytics by age group and gender, and notices about birthday perks;

• a contact email address (raw and a normalized value for duplicate checks), its registration and ownership-verification times, and a permanent-bounce flag, to secure the contact channel required to complete registration, verify ownership, and deliver essential account and security notices;

• Legal and promotion consent evidence, including the consent type and decision, document version and SHA-256, locale, source, request ID and time; for an official promotion license, the title and full text shown at acceptance, the territory, term, editing and withdrawal scope, and the server-snapshotted creation title and creator display name;

• AI chat input, output, character and session identifiers, long-term memory representations, and safety results for conversation and continuity;

• session tokens, IP, User-Agent, an app-generated device identifier, device links, timezone, and push token for authentication, fraud prevention, and notifications;

• free reward ledgers, items, attendance, ad-reward session results, and participation-token records for service integrity;

• after paid diamonds are enabled, store, environment, product ID, transaction and order identifiers, encrypted purchase proof, verification, grant and refund state, paid and bonus quantities, and a pseudonymous transaction key for purchase fulfillment and legally required records;

• private creations, image URLs, creator website, Discord and X links and their visibility settings, favorites, progress, support requests, reports, evidence, operational logs, hourly connection-time aggregates, and daily AI-usage aggregates (token and response counts) for requested features, safety, support, and service-usage statistics; and

• a reported AI response, character and message references, hashed device or session references, and review status when the user uses an in-app output-report action. That path does not collect the user's prompt, conversation history, or free-text explanation.

• monthly membership (after activation): store, product and transaction identifiers, purchase proof, subscription status, service period and auto-renewal status, verification and refund history, and daily benefit claims, from store results, server verification and claim requests, for subscription verification, benefits, duplicate-claim prevention, cancellation, refunds and support;

• general chat reports: after consent to send the conversation, conversation messages retrieved when reporting are automatically attached to the report.

Mirua does not collect payment-card, bank-account, or Korean resident-registration numbers. After paid diamonds are enabled, Apple or Google handles the payment method and Mirua receives only transaction information needed for verification.

3. AI processing

Before member AI chat and the creation-consultation feature that reviews or rewrites free-text drafts, Mirua obtains separate consent to process sensitive data the user directly enters, including health, political views, religion or belief, sex life, and criminal history, to generate AI responses and provide the conversation. Such content may remain in chat messages for up to 90 days after last activity, or, if sooner, until the user deletes the chat or account. Refusal or withdrawal disables AI chat and creation consultation, while donations, rewards, coupons, saving creations, purchases, legal documents, support, account deletion, and logout remain available. When withdrawing, the user may choose to also delete all stored conversations, including chat memory, at the same time; after withdrawal, existing conversations are not used for new AI processing.

AI responses and memory processing use Mirua's own AI models. Chat text is not sent to external commercial generative-AI services operated by other companies. By default this processing runs on private servers in the Republic of Korea controlled by Mirua; when additional processing capacity is needed, Mirua temporarily runs the same models on GPU servers rented by the hour from external GPU providers (Runpod Inc., Nebius B.V., and DataCrunch Oy (Verda) — see Section 6). A conversation assigned to an external server may continue to be processed there after domestic capacity recovers, to keep the connection and finish the processing. Mirua starts and stops those servers; only while one is running is conversation content used in that server's memory to generate responses and to extract memories after a conversation; while domestic servers cannot serve memory-search vector computation because of an outage or their state cannot be confirmed, that computation runs there too on the same conditions; when a domestic server is confirmed healthy, it stays domestic. Memory is not wiped the moment a response completes: a temporary cache computed from the conversation may remain in the inference process's memory for reuse and is released when it is replaced or the process ends. Ordinary request-body logging is disabled and the servers are configured not to write conversation content to the provider's storage; Mirua verifies this by measurement. Mirua uses an external GPU provider only after the applicable data processing agreement has been concluded and the processing scope (including sensitive information entered by users and information of minor users) has been confirmed, and sends no user personal data to a provider for which that confirmation is not complete. User conversations, memories, and creations are not used to train AI models, including pretraining, fine-tuning, or building training datasets. Sensitive topics are not blocked based on keywords alone, and sensitive facts are excluded before storage in long-term memory. Secret identifiers and credentials are masked before transmission.

4. Retention

• date of birth and gender: until final account purge;
• authentication sessions: up to 90 days after the latest extension, with an absolute maximum of 180 days from creation, or earlier logout/deletion;
• inactive AI sessions and messages: 90 days after last activity;
• memory-retrieval logs: 30 days;
• server operational logs: 180 days;
• administrator access and activity logs: 731 days, covering two years including a leap day;
• AI usage statistics (daily per-user, per-character aggregates of input, output, and cache token counts and response counts and lengths): 90 days with the user link; thereafter user identifiers are removed and custom-character references are reduced, and the data is kept only as aggregate statistics that no longer identify a user; the user link is severed immediately upon account deletion;
• hourly connection-time aggregates (hourly totals only): 365 days, deleted immediately upon account deletion;
• long-term memory: while the account remains active, subject to per-user and per-character limits, and deleted at account purge;
• push tokens: until notification withdrawal, invalidation, or account deletion;
• legal and promotion consent evidence: until final account purge; each work-specific promotion license lasts one year from acceptance without automatic renewal, and records of its acceptance, expiry, and withdrawal times are retained separately until account purge to evidence the agreed scope and the exercise of rights;
• creations: until user deletion or account purge;
• general inquiries and conversation reports: automatically deleted three years (1095 days) after closure, or after last activity for an unclosed inquiry; earlier account purge also deletes them;
• suspension-appeal conversations: automatically deleted 180 days after completion; incomplete appeals are excluded from this scheduled deletion, and earlier account purge also deletes them;
• consumer complaint and dispute records related to paid transactions: three years after completion of handling, separated from general support content and limited to items required for the statutory purpose;
• AI output reports: the retention standard is 180 days after receipt; the response is encrypted and raw device or session references are replaced with hashes. Service access and review end 178 days after receipt, and failed scheduled deletion raises an operational alert and is retried without undue delay;
• reward and participation integrity records and their internal linkage key: one year by default and no more than five years after account purge, and deleted earlier when the purpose ends or a shorter operational period applies; separated from authentication and public identifiers and access-restricted as pseudonymized personal data without claiming a special statutory status;
• after paid diamonds are enabled, minimum purchase, grant, and refund records: five years, separated from authentication by a pseudonymous transaction key after account deletion and without storing chat content or payment-card data.

The periods for inactive AI chats, memory-retrieval logs, server operational logs and connection-time aggregates are defaults. A setting of 0 disables their scheduled cleanup; it does not mean a shorter retention period. A shorter positive setting applies as configured. Account purge is separate, and statutory retention records are handled separately.

5. Deletion

An account-deletion request immediately disables active sessions and the push token. A seven-day recovery period follows. After it expires, chats, memories, private creations, device links, support data, notifications, interactions, current reward balances, inventory, progress, and attendance state are deleted; authentication credentials are purged; and public identifiers and profile or activity metadata are replaced with non-identifying substitute values. A user-created item adopted into the official catalog is immediately deactivated and its internal creator linkage is removed. A narrowly scoped internal linkage key may remain in access-restricted reward and participation integrity records for one year by default and no more than five years. Upon account deletion, Mirua also attempts to revoke Google or Apple authorization on the provider side (and Kakao or LINE once those logins are offered); if this cannot be completed immediately, the required credential is kept encrypted for a limited time while revocation is retried, and is removed once revocation succeeds. Database recovery files on access-restricted company-managed storage use owner-only file permissions and are ordinarily retained for no more than 30 days. Encrypted copies replicated daily to offsite storage operated by Backblaze, Inc. in the United States are also retained for no more than 30 days; the internal file and its external replica are copies of the same data, not independent originals. Separate image-storage backups are kept on a rotation of no more than 14 days. A restored backup must be checked against deletion records and re-purged before production use.

Accounts whose registration remains incomplete more than 30 days after creation automatically enter the seven-day deletion grace period. Accounts already registered when processed are excluded.

An internal copy tied to a schema-change recovery point takes priority over ordinary rotation and may remain beyond 30 days until that binding is updated.

6. Providers and international processing

Mirua uses the following providers and international-processing paths:

• Expo and Apple/Google push infrastructure deliver optional notifications. Google or Apple provides login when selected by a user; Kakao and LINE will apply once those logins are offered. Kakao authentication, once offered, is processed in the Republic of Korea.
• Cloudflare provides network security, public-image delivery, and support-email forwarding. Public requests also pass through a Vultr Holdings Corporation reverse proxy in Tokyo, Japan, which may process IP addresses, timestamps, URLs, headers, and related request metadata.
• Backblaze, Inc. stores encrypted disaster-recovery copies in the United States (US West region). Server backups, including personal-data database backups, are encrypted on company devices before daily replication, so Backblaze holds only encrypted data. There is no individual opt-out from disaster-recovery backups needed for the service; users may request account deletion to stop future processing, subject to the retention and deletion procedures above.
• When Mirua's own servers need additional processing capacity, Runpod Inc. (United States; data center in Iceland, Romania, the Netherlands, or the United States as selected by Mirua), Nebius B.V. (Netherlands; processed in Finland), and DataCrunch Oy, operating as Verda (Finland; processed in Finland), provide temporarily rented GPU servers on which Mirua runs its own AI models — only providers for which the data processing agreement has been concluded and the processing scope confirmed. Overseas processing of this kind is performed only to the extent necessary to perform the service contract a user has requested, after the statutory disclosures have been provided in this Policy under PIPA Article 28-8(1)(3)(a); processing that does not meet that requirement is not performed until a separate lawful basis such as consent is secured. The content sent includes system instructions, character and story settings, the user persona, conversation history and long-term memory items together with user input and AI responses, creation-consultation drafts, conversations used for reply suggestions, and support inquiry content when an administrator uses the AI draft or translation feature. Mirua does not add user account IDs, email addresses, or user IP addresses as separate metadata fields; personal information included in conversations, settings, or support content may nevertheless be transmitted as part of the content. It is sent from Mirua's server over an encrypted connection (TLS through a dedicated Cloudflare tunnel) and processed in memory while such a server is running, for response generation, post-conversation memory extraction, and — only while domestic servers cannot serve it because of an outage or their state cannot be confirmed — memory-search vector computation (when a domestic server is confirmed healthy, that computation stays domestic); a conversation assigned to an external server may continue there after domestic capacity recovers. Safeguards: transport encryption, access control that admits only Mirua's server (a per-server tunnel and Cloudflare Access service token), encrypted storage of access credentials, request-body logging disabled, and no transmission before the agreement and scope are confirmed. Memory is not wiped the moment a response completes: a temporary cache may remain in the inference process's memory for reuse and is released when replaced or when the process ends; the servers are configured not to write conversation content to the provider's storage, and Mirua verifies this by measurement. Provider-side network and account logs follow each provider's data processing agreement and policy. Because this capacity is needed for the service as a whole, there is no per-item opt-out. Even without using AI chat, overseas processing may occur through creation consultation, memory processing of conversations already requested, and AI drafting or translation of support inquiries; users may ask in-app support to stop overseas processing, in which case features that require it may become unavailable, and may also request that future processing stop by deleting the account (processing already started may be completed).
• Google (Play Integrity) and Apple (App Attest/DeviceCheck) receive an app identifier and device-integrity attestation automatically to block forged apps and tampered requests. This security transmission cannot be disabled individually. These providers may process limited token, network, authentication, backup, or image data in their service regions. Once paid diamonds are enabled, Apple Inc. or Google LLC also processes store payment verification, grants, and refunds in their respective payment-processing regions.
• Cloudflare forwards support email in transit without storing it to a company mailbox operated by Google LLC (Gmail). Gmail stores the sender's email address and inquiry content in the United States and other processing regions only as long as needed for handling and dispute response; users may instead contact support inside the app.
• Resend(Plus Five Five, Inc.) sends contact-email verification messages, registration-completion welcome messages and administrator security emails. It processes recipient email addresses, message subjects and bodies (including verification codes), and delivery and bounce status in the United States under a data processing agreement for as long as needed for sending and bounce handling. Mirua keeps its own delivery records until their security-audit purpose is fulfilled. Because a contact email address is required to complete registration, there is no per-item opt-out; users may stop registration or delete the account.

When you access Mirua web pages (the account-deletion page or legal-document pages), Cloudflare may set security cookies for security and bot protection. The app does not use cookies.

Your acknowledgment that you have read the Privacy Policy records delivery of this notice; it does not constitute blanket consent to all processing. Service-essential processing is limited to what is necessary under contract performance or another applicable lawful basis, and any processing that requires separate consent remains separate. Rewarded advertising remains unavailable until separate consent is obtained and the actual mediation partners, countries, data categories, and retention periods are confirmed. If activated, AppLovin and each actual advertising partner will be disclosed immediately before the request. Refusal affects only the optional ad feature.

Firebase Analytics-based usage analytics is not currently collected. Any future activation requires prior disclosure in this Policy, completion of the notice procedure, and the user's separate opt-in in the app; no events are sent before consent. Ad storage and ad-personalization signals are always disabled. Rewarded advertising is currently unavailable, and the AppLovin SDK is not initialized or used to request ads. Any future activation requires the disclosure, separate-consent, and withdrawal conditions to be completed first.

7. Rights and safeguards

Users may request access, correction, deletion, suspension of processing, data portability, consent withdrawal, and account deletion. Requests are received primarily through app settings and the in-app support channel, and requests that need identity documents are also handled safely inside the app.

If you need to report or consult about a personal-data violation in Korea, you may contact the Personal Information Infringement Report Center (118, privacy.kisa.or.kr), the Personal Information Dispute Mediation Committee (1833-6972, kopico.go.kr), the Supreme Prosecutors' Office Cyber Investigation Division (1301, spo.go.kr), or the Korean National Police Agency National Office of Investigation Cyber Bureau (182, ecrm.police.go.kr).

If you cannot access the app, you may apply through the public account-deletion page (https://aimirua.com/account/delete) or [email protected]. Please do not attach sensitive documents such as ID cards to email — Mirua will separately guide you through any required verification. Mirua verifies the requester and responds within the applicable legal period, explaining any lawful restriction.

Mirua applies least-privilege access, administrator authentication, encrypted transport, encryption for sensitive chat fields, environment-separated secrets, integrity records, rate limits, controlled backups, regular vulnerability checks, and incident response. Required regulator and user notices are provided after a qualifying incident.

8. Children, optional choices, and updates

Users under 14 may not register. Your date of birth is required at sign-up so that Mirua can verify that you are 14 or older; it checks the date of birth you enter and does not proceed with registration if you are under 14. Gender is optional, and leaving it blank changes nothing about registration or use. Consent to marketing notifications and consent to night-time (9 p.m. to 8 a.m.) notifications are each optional and can be withdrawn at any time in Settings. For users aged 14 or older who are minors, legal-representative consent may still be required depending on the information or contract involved. Push notifications, marketing, personalized advertising, and rewarded ads are optional and separate from required service consent.

Changes that do not affect users' rights or obligations, such as corrections of typographical errors or contact details, are announced in the app or by similar means at least 3 days before they take effect, and changes to rights or obligations that are not adverse to users at least 7 days before. Changes that are adverse to users or that change the scope of consent are announced in the app or by similar means at least 30 days before they take effect and notified individually through in-app notices and an individual notice screen on your next access, and, where consent is required, renewed consent is requested only for the items that changed. Changes that materially expand purposes or third-party disclosure receive any separate consent required by law.

Requests are accepted at any time. Staffed support hours are Korean business days, 10:00–17:00 KST, excluding weekends and Korean public holidays. Mirua aims to provide an initial response within three business days.

9. Revision history