November 5, 2026Amendment
Musecat Amended Terms of Service

Amended Terms of Service. The current Terms apply before commencement.

Planned notice: November 9, 2026. Deadline for comments and objections: November 23, 2026, 23:59. Planned commencement: November 24, 2026, 00:00. All dates and times are Korea Standard Time (KST, UTC+9). If notice is delayed, commencement will be adjusted to preserve the notice and objection periods under the current Terms.

See the amendment comparison for changes and affected users.

Article 1 Purpose

① These Terms govern the rights, obligations and liabilities of Techclip (the “Operator”) and users in relation to Musecat, the formation and termination of the service agreement, and related matters.

② These Terms apply to the Operator’s websites, applications and APIs. Independently operated external services are subject to their operators’ terms. The Operator’s responsibility in relation to those services is determined by these Terms and applicable law.

③ Inquiries and requests to exercise rights may be submitted through Musecat Support.

Article 2 Definitions

  1. “Service” means the functions provided by the Operator, including arcade and game information, collaborative editing, location-based discovery, activity records, community features, messaging and external integrations.
  2. “User” means a member or non-member using the Service.
  3. “Member” means a person who has accepted these Terms, entered into the service agreement and received an account.
  4. “Account” means the identifying unit assigned to a member for authentication and management of service activity.
  5. “Content” means posts, comments, photographs, profiles, arcade information, collaborative documents, revision history and other material posted or transmitted through the Service.
  6. “External App” means a website, application or program independently operated by another operator or developer and integrated with the Service.
  7. “Developer” means a person registering an External App or integrating the Service through an API.
  8. “Operating Policy” means published rules specifying usage standards and procedures within the scope of these Terms.
  9. “Bot” means a program that directly requests an API to read or modify information using its owner account’s permissions, including macros, scripts and automation tools regardless of name or implementation.
  10. “Bot Owner” means the member registering a Bot to their account and managing its credentials and execution permissions.

Article 3 Application and Interpretation

① The Operator shall make these Terms readily accessible within or through the Service. Material provisions affecting users’ rights or obligations shall be clearly presented and explained as required by law.

② Separate terms or individual agreements applicable to a particular function take priority within their scope, except where contrary to mandatory law.

③ Operating Policies specify implementation standards. Their adoption or amendment alone shall not restrict essential user rights or impose material obligations absent from these Terms.

④ Acceptance of these Terms does not replace separate disclosures or consent required for personal information collection and use, third-party disclosure, overseas transfer or use of personal location information.

⑤ Matters not addressed here are governed by applicable law and valid individual agreements. Ambiguous provisions shall be interpreted in users’ favor as required by law.

⑥ English and Japanese translations are provided for convenience to assist understanding. If their meaning or interpretation differs from the Korean version, the Korean version is the reference for interpretation. This does not exclude mandatory applicable law or statutory user rights.

Article 4 Formation of the Agreement

① The agreement is formed when an applicant accepts these Terms, completes the prescribed application and receives the Operator’s acceptance.

② The Operator may refuse or defer acceptance until the cause is resolved where:

  1. Another person’s identity or credentials, or false information, are used.
  2. The application seeks to evade a lawful restriction under law or these Terms.
  3. Capacity, technical failures or security risks prevent normal service provision.
  4. Comparable circumstances would make formation unlawful or substantially impair safe operation.

③ Unless legally restricted or justified by a specific security reason, the applicant shall be informed of the reason for refusal or deferral.

④ Before accepting children under 14, the Operator must establish legally required parental consent and verification procedures. Such registrations shall not be accepted while those procedures are unavailable. Transactions requiring a minor’s legal representative’s consent, including paid contracts, are governed by applicable law.

Article 5 Account Management and User Obligations

① Members shall protect account information and credentials and promptly notify the Operator upon discovering theft or unauthorized use.

② Members shall not arbitrarily assign, lend or pledge an account or contractual status, except through legally permitted or Operator-approved delegation or integration procedures.

③ Members shall update changed registration information through the available means. The Operator is not responsible, to the extent it is not at fault, for losses caused by inaccurate information, negligent credential management or delayed notification attributable to the user.

④ Official arcade or business account users shall possess legitimate authority for their activities. Registration or a role label does not mean that the Operator represents the arcade or external business or guarantees its performance.

⑤ Users shall comply with applicable law, these Terms and lawfully published Operating Policies.

Article 6 Services and Usage Conditions

① Subject to availability of each function, the Operator provides:

  1. Arcade and game information and collaborative editing.
  2. Nearby discovery, visit verification, visit records and favorites.
  3. Profiles, activity history, levels, rankings and campaigns.
  4. Community posts, comments and member messaging.
  5. Support, inquiries and reporting.
  6. External App login, account connections, imported records and developer APIs.
  7. Registered Bot automation for user convenience.
  8. Creation and download of posters, guidance material and QR material.

② Reasonable restrictions based on age, authorization, activity level or request volume may be established according to law or the function’s nature. Criteria and restrictions shall be disclosed before use.

③ Users bear their device, internet and telecommunications costs under their provider contracts. Charges imposed directly by the Operator require separate disclosure.

④ Levels, activity points and rankings indicate participation. Unless expressly stated otherwise, they do not constitute cash, redeemable property or an entitlement to economic benefits. Paid entitlements and statutory rights are unaffected.

⑤ Before a paid service contract is formed, the Operator shall separately disclose price, billing frequency, duration, withdrawal, cancellation and refund conditions. Acceptance of these Terms alone does not authorize payment or automatic renewal.

⑥ Mentioning a function does not guarantee its launch, continuous availability or launch date. Trial functions shall be identified with their conditions and limitations in advance.

Article 6-2 Mobile Applications

① These Terms apply to the Operator’s mobile apps. Distribution-platform rules and separately applicable software licenses also apply within their scope without unfairly restricting statutory rights. Platform rules do not transfer the Operator’s service or privacy responsibilities to the distributor.

② Supported environments and material changes may be announced. Necessary security or compatibility updates may be required, and obsolete versions restricted on reasonable grounds. Articles 7 and 18 apply to changes affecting legitimate user rights.

③ Access to cameras, photographs, files, location and other device resources requires purpose and permission disclosures when the function is requested, and compliance with law and operating-system procedures. Refusing an optional permission shall not unfairly restrict unrelated functions.

④ Service and push notifications follow the applicable settings and permissions. Operating-system permission does not constitute consent to marketing messages. Advertising messages require their own legal basis. Liability for delayed or missing notifications due to network or device conditions is governed by Articles 15 and 16.

⑤ Uninstalling the app, changing devices or logging out on one device does not itself terminate the account, erase server data or cancel a separate subscription. Deletion and subscription cancellation procedures and their effects shall be explained separately. Apps allowing account creation shall provide an in-app deletion request route and any external web route required by the distribution platform.

⑥ Paid apps, digital purchases and subscriptions require advance disclosure of the actual price, billing entity, renewal, cancellation and refund conditions under applicable law and valid platform payment rules. App use or acceptance of these Terms alone is not subscription consent.

Article 6-3 Created Material

① Users may create and download posters, guidance and QR material. Templates and elements provided for that purpose may be used non-exclusively, within their disclosed purpose, to create, save, print, display and distribute outputs. Separately stated element licenses also apply.

② This permission covers authorized outputs, not separate sale or unrestricted sublicensing of source templates, fonts, photographs, trademarks or other components. Users’ own text and images remain subject to Articles 8 and 9.

③ Users shall obtain necessary posting or arcade authorization and check displayed information and QR destinations. The tool does not guarantee arcade approval, trademark-owner affiliation or the lawfulness of printed material. Accuracy and liability are governed by Articles 15 and 16.

④ Normal creation and distribution of authorized outputs is distinct from Article 12’s restrictions on External Apps and data use. This permission does not authorize automated collection, advertising use by External Apps or data resale.

Article 7 Changes, Suspension and Discontinuation

① The Operator may change or temporarily suspend all or part of the Service where:

  1. Maintenance, replacement, updates or security measures are necessary.
  2. Equipment failure, communications disruption or abnormal traffic prevents normal operation.
  3. Legislation, court orders or lawful regulatory measures require restriction.
  4. Natural disasters, war, major emergencies or comparable force majeure occur.
  5. External services cease or technical changes prevent an integrated function.
  6. Comparable reasonable technical or operational circumstances exist.

② Reasons, timing and effects of planned changes or suspension shall be announced beforehand. If emergency security action or an unforeseen failure makes prior notice impossible, notice shall follow without undue delay.

③ Discontinuation of the entire Service or an important function shall in principle be announced at least 30 days beforehand, with reasons, timing, data treatment and available export options. If advance notice is objectively impossible due to force majeure or similar circumstances, notice and necessary user protections shall follow as soon as possible.

④ Lawful change or discontinuation of a free function does not, by that fact alone, create an obligation to pay separate monetary compensation. This does not exclude damages attributable to the Operator or statutory obligations.

⑤ Refunds for unperformed paid services, accrued contractual rights and statutory protections shall be addressed separately. Articles 15 and 16 govern damages and exemptions relating to suspension or discontinuation.

Article 8 Content Management and Visibility

① Users shall hold necessary rights or lawful permission for submitted Content, including copyright, image rights and personal information.

② Public Content and profiles may be displayed or searchable according to selected or disclosed visibility. Appropriate information and choice shall precede new disclosure of private material.

③ Private messages and inquiries are provided to recipients or authorized staff. Operator access for reports, troubleshooting or legal obligations is limited to what is necessary and subject to access controls.

④ Users may use editing, deletion and visibility controls or contact Support. Treatment of collaborative material, conversations and records connected to others’ contributions is explained by the function and Privacy Policy.

⑤ Users may separately retain originals where lawful and consistent with others’ rights. This does not shift the Operator’s legal or contractual retention, security, destruction or liability obligations to users.

⑥ Shared member plazas are distinct from private one-to-one messages. Text, photos and author information are visible to other eligible members. Where no separate joining is required, posting is not directed solely to selected recipients. Leaving or clearing local display history does not delete server posts; deletion and retention follow the function and Privacy Policy.

⑦ The Operator shall take necessary measures against harmful use and infringement, including reporting, restricting objectionable Content and blocking abusive users, under Articles 10 and 11. Disclaimers do not remove statutory user-protection obligations.

⑧ Arcade check requests, findings and completion labels reflect user submissions and the function’s verification criteria. They do not certify an Operator investigation or an error-free arcade status. Location processing is subject to Article 13.

Article 9 Intellectual Property and Content License

① Rights in the Service’s software, design, trademarks and Operator-created material belong to the Operator or lawful right holders. User and third-party rights are reserved.

② Service use grants only the permission allowed by these Terms and law, not ownership of intellectual property. Open-source software and packages retain their respective licenses.

③ Users grant the Operator a non-exclusive license necessary to store, reproduce, transmit, display, search and preview their Content in the Service. Format conversion, resizing and accessibility processing are limited to those purposes.

④ The license is limited by visibility and purpose. External redistribution of originals, separate advertising or promotion and AI-model training requiring additional rights require those rights to be obtained separately, together with necessary privacy procedures.

⑤ The license normally ends when Content is deleted. Previously lawfully transmitted copies, recovery backups and collaborative material incorporating others’ contributions may be processed only for necessary purposes and periods under law and the Privacy Policy.

⑥ Lack of copyright in facts does not authorize access, collection or reuse without permission. Articles 10 and 12 apply subject to mandatory legal rights. Display of game names, trademarks or external services does not itself establish affiliation, endorsement or agency.

Article 10 Prohibited Conduct and Restrictions

① Users shall not engage in:

  1. Impersonation, credential theft or unauthorized account use.
  2. Threats, persistent harassment, hate speech, sexual exploitation, unlawful intimate imagery or other infringement.
  3. Repeated false arcade data or fabricated visits, or manipulation of points, rankings, reactions or campaigns.
  4. Unsolicited advertising messages, spam or repeated flooding.
  5. Malware, access-control circumvention or excessive requests disrupting operation.
  6. Exceeding External App permissions, unauthorized onward disclosure or re-identification.
  7. Crawling, scraping, automated collection or data access without prior express Operator permission, or breach of Article 12’s development and usage restrictions.
  8. Direct automated API use or editing through personal Bearer tokens without Bot registration required by Article 12-2.
  9. Other unlawful conduct or infringement of legitimate rights.

② The Operator may warn, hide Content, restrict a function, suspend for a stated period or terminate the agreement, considering seriousness, repetition, harm and urgency. Permanent restriction requires serious or repeated violations or comparable justification.

③ Normally, reasons, scope, duration and appeal methods shall be notified beforehand with an opportunity to respond. Urgent harm or security risks may require action first and prompt subsequent notice. Disclosure may be limited for lawful reasons or victim protection.

④ Users may appeal through Support. The Operator shall review evidence, explain its decision and revoke or adjust a restriction if the appeal is justified.

⑤ Political or religious views, legitimate criticism or error reports alone are not grounds for restriction. Specific harm, relevance and repeated operational interference shall be considered.

⑥ Re-registration to evade restrictions may be restricted. Withdrawal alone shall not convert a temporary sanction into a permanent one. Identifiers used to prevent re-registration require their own lawful basis and retention period.

Article 11 Infringement Reports and Takedowns

① A claimant may identify Content, explain the infringement and provide supporting evidence to request deletion, suspension or other lawful relief.

② The Operator shall take legally required action and notify the claimant and author. Qualifying temporary measures under the Korean information-network legislation may block access for up to the statutory 30 days.

③ Copyright suspension and restoration follow the separate Copyright Act procedure. The preceding temporary-measure period does not apply indiscriminately to all claims.

④ Authors may submit evidence of lawful rights or a response. The Operator shall determine continuation, modification or restoration under law and the evidence and notify the outcome. Reports and private messages shall not be disclosed beyond necessary handling.

Article 12 External Apps and Developer APIs

① Connection disclosures and consent shall be app-specific. The Operator shall disclose the external operator, purpose, data, retention and effects of refusal beforehand and obtain separate consent where legally required. See the connection notice draft.

② Reading Musecat data, writing on a member’s behalf and importing external records are separate permissions. Expansion requires appropriate disclosure and approval. Each direction of a bilateral connection must have its completion status identified separately.

③ Members may disconnect or withdraw consent through available controls or Support. New requests under the revoked permission shall stop. Deletion of previously delivered data or separate external accounts may also require contacting that operator. Musecat’s own deletion and disclosure-stopping obligations remain unaffected.

④ Developers shall accurately disclose operator identity, contact information, privacy policy and purpose; comply with approved purpose, permissions, visibility and limits; secure credentials; and destroy unnecessary information after disconnection or purpose completion unless lawfully retained.

⑤ Users and Developers shall not crawl, scrape, automatically query, collect, extract, copy, store or access data through pages, screens, APIs, file stores, databases or other Service paths without the Operator’s prior express permission. This applies regardless of visibility, login, commercial purpose, volume or load. A public address, technical accessibility, absence of a robots.txt block or a member’s consent does not constitute that permission.

⑥ Normal use of provided interfaces and approved app requests within expressly allowed APIs, purposes, data, permissions and limits are distinguished from unauthorized access. Bot registration and authentication under Article 12-2 also apply to automation. Registration or credential issuance does not authorize other purposes, bulk collection, hidden interfaces, circumvention, credential sharing, unauthorized redisclosure or re-identification.

⑦ Developers shall not use Musecat services, data or APIs to develop, test, distribute or operate apps, sites or programs that:

  1. Aim to crawl, scrape, collect data in bulk or build a separate database.
  2. Use Musecat material for advertising placement, targeting, measurement, promotion or advertising revenue.
  3. Aim at direct or indirect commercial activity, including paid sales, subscriptions, commissions or data sales.
  4. Primarily provide arcade search, discovery, comparison, recommendations, maps or listings that substitute for or compete with Musecat’s discovery functions while diverting its data, Content or user traffic, creating a concrete conflict of interest or objectively foreseeable risk of one.

⑧ Developers shall accurately disclose purpose, core functionality, monetization and data usage and obtain approval before changing them. Initial approval or member connection consent does not authorize prohibited purposes. Development registration, tester designation or technical conformance does not constitute public-release approval. Development audiences must be observed and unnecessary real personal information excluded from nonpublic test material.

⑨ API permission does not transfer copyright, privacy rights or unrestricted reuse rights. Paragraphs 5–8 regulate use of Musecat services, data and APIs, not independent development without them. Separate public-package licenses and mandatory legal rights remain respected.

⑩ The Operator may reasonably request evidence of purpose, monetization, approved data use and deletion. Depending on severity, repetition and harm, it may refuse or revoke approval, revoke tokens, block APIs or terminate the agreement, subject to Article 10 notice and appeal. It may seek cessation, deletion of unauthorized data and damages as permitted by law.

⑪ Developers shall promptly report security incidents and fulfill applicable notice, reporting and mitigation duties. Nonurgent compatibility changes or API retirement require advance notice of the change, transition method and schedule with a reasonable transition period.

⑫ App registration, review or approval does not guarantee the external operator’s conduct, availability or contractual performance. Liability follows each party’s fault and applicable law.

Article 12-2 Bot Registration and Owner Responsibility

① Bots are convenience tools, not independent members or holders of additional privileges. They may act only within their owner account’s permissions and authorized functions.

② Macros, scripts, scheduled programs and other automation directly requesting APIs must first be registered as Bots and use their dedicated issued credentials, regardless of frequency, schedule or commercial purpose. The Bot and its actual owner must remain identifiable. Technical success is not authorization.

③ Unregistered automation shall not call APIs using personal login Bearer tokens, session information or other ordinary account credentials. Creating, editing or deleting Service information, including arcade data, in this manner is grounds for account suspension. Registered Bots that bypass identification by using ordinary credentials are treated alike. Requests generated by normal use of the Operator’s ordinary app or website are not unregistered automation under this paragraph.

④ All Bot creations, edits, deletions, submissions and other actions are performed under and attributed to the owner account; the owner bears management and usage responsibility for their content and results. Lack of personal review, automated execution, scheduling or third-party code does not itself release the owner. Liability for stolen credentials or Operator fault is determined under law.

⑤ Owners shall review commands, targets, edits and permissions and prevent malfunction or duplicate execution. Credentials must be confidential. Upon discovering leakage, theft or abnormal work, owners shall promptly stop execution, revoke credentials or block access and notify the Operator. Liability for harm caused or aggravated by negligent management follows law.

⑥ Registration does not waive Article 12’s collection, crawling, advertising, commercial-purpose or conflicting-app prohibitions. Owners must respect authorized APIs, targets, purposes and limits and shall not evade restrictions or exceed permissions. Bot work earns no experience points awarded for direct member contributions; Bot attribution and history may be distinguished according to visibility rules. Owners shall not disguise Bot activity as direct contributions.

⑦ Violations, including unregistered requests or automated editing using ordinary credentials, may lead to owner-account suspension, Bot restrictions, credential revocation, API blocking or termination according to severity, repetition and harm. Article 10 governs notice and appeal; serious data or security risks may be blocked first with prompt subsequent notice.

⑧ Registration does not guarantee the legality, accuracy, completeness or recoverability of selected code, commands, input or results. The Operator is not responsible for Bot configuration or command errors, malfunction, duplicates, misuse or negligent credential management where it is not at fault and no statutory liability applies.

⑨ The Operator is not automatically obliged to pre-review every Bot action or reverse properly processed work merely on request. Obligations arising from its fault, defects, security failures or applicable law, including correction, deletion, recovery and damages, remain unaffected. Non-excludable liabilities under Articles 15 and 16 cannot be shifted to owners.

Article 13 Privacy and Location Information

① Processing purposes, data, legal bases, visibility, retention, destruction and rights are addressed in the Privacy Policy amendment. The current Policy and applicable law remain applicable before commencement.

② Terms acceptance or Policy acknowledgment is not blanket consent for optional collection, third-party disclosure, overseas transfer or marketing.

③ Personal location services require legally mandated separate terms, disclosures and consent. Device permission does not replace legal consent. Refusal shall not unfairly restrict functions not requiring location.

④ When entrusting personal information processing, the Operator shall disclose processors and tasks through the Privacy Policy or other lawful means and comply with contractual and supervisory duties. Entrustment alone does not require separate user consent; a lawful basis for the underlying processing remains necessary.

⑤ Overseas transfers require a basis under Article 28-8 of the Personal Information Protection Act. Separate transfer consent may be unnecessary where processing entrustment or storage is necessary for entering into or performing the user contract and the statutory details are disclosed in the Privacy Policy or notified by a legally prescribed method, or another lawful non-consent basis and its conditions apply. Where separate consent is required, obtain it before transfer. An independent recipient’s own-purpose processing shall not automatically be treated as entrustment.

⑥ Publication, changes and applicable dates of the Privacy Policy shall be readily ascertainable. General announcements, Terms acceptance or continued use do not replace legally required individual notification or separate consent.

Article 14 Termination and Data Treatment

① Members may request termination through withdrawal controls or Support. Only necessary identity verification shall be required. Legally restricted requests shall receive the basis, reason and available resolution.

② Information, connections and Content shall be handled under law and the Privacy Policy. Changing an email or display name alone does not establish anonymization or destruction.

③ Residual collaborative records, messages and public Content shall be explained before withdrawal. Statutory access and deletion requests remain available afterward. Limits on recalling external copies do not remove statutory obligations.

④ Termination does not affect accrued damages claims, unsettled debts or statutory rights and duties. Obligations inherently surviving termination continue only for their lawful purpose and scope.

Article 15 Damages

① A party whose intentional or negligent breach of these Terms or law causes harm to the other is liable as provided by law.

② Applicable law governs scope. Where Civil Act Article 393 applies, ordinary loss is the principle and loss arising from special circumstances is compensable only where the liable party knew or could have known those circumstances. Business loss, lost expected profit or data loss is neither automatically excluded nor automatically compensable merely by its label.

③ Contributing user fault shall be considered under law. These Terms do not unfairly shift the burden of proof to users.

④ A user whose unlawful conduct or breach causes a third-party claim shall reasonably cooperate in fact-finding and resolution and compensate attributable harm and legally recoverable reasonable response costs. Operator fault and unrelated losses shall not be shifted to the user.

⑤ Unfairly short claim deadlines, excessive evidence requirements or waivers of statutory rights shall not be imposed. Limitation periods follow law.

Article 16 Exemptions and Limitations of Liability

① Where force majeure, including natural disasters, war or major emergencies, prevents provision, the Operator is not liable for resulting interruption or unavailability to the extent it is not at fault, except where law imposes liability.

② Change, maintenance, interruption or discontinuation alone does not establish liability. Where the Operator is not at fault, it is not liable unless otherwise provided by law. Prior notice does not excuse an attributable failure or breach.

③ In the absence of Operator fault or statutory liability, it is not responsible for harm arising from:

  1. User-attributable credential mismanagement, inaccurate input, devices or network conditions.
  2. Failures, policy changes or closure of external networks, login providers or apps beyond reasonable control.
  3. Third-party information errors or independent communications, transactions or disputes.
  4. Unlawful third-party access, malware, transmission interference or data damage.

④ External failure or attack does not itself establish an exemption. The Operator remains responsible for breached contractor-management, security, prevention and response duties imposed by law or contract.

⑤ Real-time accuracy or fitness for a particular purpose of arcade opening, hours, equipment, prices, faults, queues and user material is not individually guaranteed. Users should verify necessary details with the arcade or source. Express warranties, knowingly false information and harm attributable to the Operator are not excluded.

⑥ Unless expressly agreed, uninterrupted availability, uptime, speed, permanent external API compatibility or particular commercial results are not guaranteed. Express service levels, paid performance and legal responsibilities remain unaffected.

⑦ Independent contracts with arcades, External Apps or other parties are their parties’ responsibility. Unless the Operator expressly acts as party, agent or guarantor, or law provides otherwise, it does not guarantee performance. If it later supplies or intermediates transactions, it bears responsibility for its actual role.

⑧ These limitations do not apply to intentional misconduct or gross negligence of the Operator, its performance assistants or employees, statutory privacy or location responsibilities, or any other non-excludable liability. Free provision does not remove such liability.

Article 17 Assignment and Individual Arrangements

① Users shall not arbitrarily transfer contractual status except as permitted by law or approved procedures.

② Transfers by the Operator, including personal information accompanying a business transfer, require lawful notice, consent and protection of data-subject rights. These Terms do not constitute blanket consent to all transfers.

③ Failure to enforce a right immediately does not itself waive it, subject to good faith, limitation periods and users’ legitimate reliance.

Article 18 Notices and Amendments

① Material individual actions shall be notified through reasonable means such as service alerts or registered contact details. General notices may be published within the Service. Publication does not replace legally or contractually required individual notice.

② Amendments shall normally be announced at least seven days before commencement with reasons, changes and date. Unfavorable or material amendments shall be announced and individually notified at least 30 days beforehand.

③ Users declining amendments may request termination. Silence or continued use alone shall not constitute consent to unfavorable amendments or separately consent-based personal information processing. Express consent shall be obtained where law requires it or important contractual content is changed.

Article 19 Governing Law, Disputes and Severability

① Korean law governs, without excluding mandatory applicable consumer protections.

② Users may seek resolution through Support. The Operator shall review and respond. Statutory dispute-resolution and judicial procedures remain available.

③ Jurisdiction follows applicable procedural law. Users are not compelled to sue exclusively at the Operator’s location or waive statutory access to courts.

④ Invalid or unincorporated provisions normally do not invalidate the remainder, except where the remaining agreement cannot achieve its purpose or would be unfairly unfavorable, as determined by law.

Supplementary Provisions

① This amendment was prepared on November 5, 2026. Publication of this draft alone does not replace the current Terms.

② The current Terms took effect on July 1, 2024. Notice is planned for November 9, 2026; comments and objections will be accepted until November 23, 2026, 23:59; commencement is planned for November 24, 2026, 00:00. All dates and times are KST (UTC+9).

③ Delayed notice requires adjustment preserving the existing notice and objection periods. Legally required consent or prior measures must be completed separately; the schedule does not establish their completion.

Musecat
All About Arcades