November 5, 2026Amendment
Musecat Amendment Comparison

This comparison accompanies the amendment announcement. The current Terms and Privacy Policy remain applicable until commencement.

Planned notice: November 9, 2026. Comments and objections close November 23, 2026, 23:59. Planned commencement: November 24, 2026, 00:00. All dates and times are KST (UTC+9). Delayed notice requires adjustment preserving current notice and objection periods.

This is a convenience translation of the comparison of the Korean reference texts. Consult the current Terms, proposed Terms, current Privacy Policy and proposed Policy for full wording.

Main Changes

  • Address web use and future mobile applications together.
  • Clarify plazas, field checks, poster/QR outputs and responsibility.
  • Specify the existing unauthorized-crawling prohibition and new external-developer and Bot conditions.
  • Detail interruptions, damages, reporting and account restrictions.
  • Expand privacy descriptions to actual functions and visibility. Disclose retention end events, provider roles and overseas processing scope.

General Terms Comparison

Current provisionProposed provisionTypeAffected users
Article 1: general service relationshipArticle 1: identify Techclip, web/app/API scope and contactClarificationAll users
Article 2: community, members, feeds and arcade documentsArticles 2–3: accounts, apps, policies, separate terms and Korean-reference interpretationSupplementAll users
Article 3: registration by acceptanceArticle 4: application/acceptance, refusal/deferral and reasons, children and representativesDetail and additionApplicants and relevant members
No specific account-management/assignment ruleArticles 5 and 17: credential security, theft reporting, transfer restrictions and lawful delegationAdditionMembers
Article 4: feeds, arcade documents, profiles, history and other servicesArticle 6: discovery, visits, favorites, rankings, campaigns, messages, integrations, Bots and creation toolsExpanded scopeRelevant function users
No mobile-specific provisionArticle 6-2: environments, updates, permissions, push, uninstall versus account deletion and separate paid conditionsAdditionApp users
No created-output provisionArticle 6-3: storing, printing and distributing allowed poster/QR outputs; component and posting rightsAdditionCreation-tool users
Article 5: maintenance, failures and communications interruptions; advance notice if possibleArticle 7: grounds, prior/emergency notice and normally 30-day notice for important discontinuationDetailAll users
No distinct free-function compensation ruleArticle 7(4)–(5): lawful free changes alone versus fault-based damages and paid refundsAdditionRelevant users
Article 8: moderation, temporary hiding and deletion requests on withdrawalArticle 8: public Content, private messaging and shared plazas; leaving versus deletionDetailContent and conversation users
No field-check disclaimerArticle 8(8): completion is a user record, not an Operator investigation or certification of accuracyAdditionField-check users
Article 9: author copyright and operational useArticle 9: ownership, necessary license, visibility, deletion and additional rights for promotion/AIDetailContributors and users
Articles 3/8: warnings, restrictions, suspension and termination, political/religious disputesArticle 10: violations, duration, notice, response and appeal; distinguish opinions from specific harmDetail and changeMembers and violators
Article 8: temporary hiding during legal disputesArticle 11: evidence, response, notice, temporary measures versus copyright suspension/restorationDetailClaimants and authors
Article 7: minimum data and Policy referenceArticle 13: Policy and separate procedures for disclosure, transfers and locationSupplementAffected individuals
Article 3: withdrawal through feedback and possible retention of restricted accountsArticle 14: requests, verification, data, surviving rights and display changes versus destructionDetailWithdrawing members
No specific damages/exemption structureArticles 15–16: fault, causation, special loss, force majeure, external failures and warranty scope; non-excludable liabilities reservedAdditionAll users
Article 6: social-media/feed noticesArticle 18(1): general service announcements versus individual noticesChangeAll users
Article 11: at least seven days’ notice, rejection within 14 days and deemed acceptanceArticle 18(2)–(3): normally seven days; 30-day notice and individual notification for unfavorable/material changes; distinguish silence from express consentChangeExisting members
No specific governing-law, jurisdiction or severability provisionArticle 19: Korean law, lawful jurisdiction, dispute resolution and partial invalidityAdditionAll users

Additional External App and Bot Conditions

These apply when the relevant function or access method is used. Normal interface use does not require Bot registration.

Current provisionProposed provisionTypeAffected users
Article 10: unauthorized crawling prohibitedArticles 10 and 12(5): specify scraping and unauthorized access, including public data and noncommercial collectionDetail and expanded access scopeData collectors/API users
Article 10: prior consent for AI trainingArticles 9(4) and 12(9): operational licenses/API permissions are not AI rights; obtain necessary additional rights and privacy permissionsDetailAI-data users
No specific external-purpose restrictionsArticle 12(7)–(10): crawling, advertising, commercial and concretely conflicting apps; purpose/monetization disclosures, change approval and revocationAdditionExternal developers/operators
Only general reference to partnered servicesArticle 12: app-specific notices, reading/writing/bilateral permissions, withdrawal, testers, publication and developer dutiesAdditionConnected members/developers
No Bot registration/authentication ruleArticle 12-2(1)–(3): register direct API automation, use dedicated credentials; prohibit unregistered personal-Bearer editingAdditionAPI automation users
No Bot attribution/management ruleArticle 12-2(4)–(6): all work attributable to owner; command/credential management; no direct-contribution XP; collection prohibitions remainAdditionBot Owners
No Bot sanctions/exemptionsArticle 12-2(7)–(9): owner suspension/revocation, no-fault error exemptions and statutory carve-outsAdditionOwners and violators

Privacy Policy Comparison

This supplements processing disclosures; where new collection or disclosure requires consent, this notice does not replace it. Mention of an unreleased function does not assert current availability.

Current contentProposed contentScope
Sections 1–2 focus on membership, Content and feedbackSections 1–2 distinguish purposes, items and legal bases by functionIndividuals using relevant functions
Account, IP, posts and report activitySections 2–3 add messages/photos, plaza, location/visits, outputs, Bots, developer functions and pushRelevant users
Public/private distinctions not specificSection 3 specifies visibility, inquiry recipients, plazas and distributed outputsContent/conversation users
Section 3 retains account, connection and activity information until withdrawalSection 4 separates end points and statutory exceptions; specific periods/end events and expiry versus actual destruction are explainedMembers/non-members
Section 4 promises immediate deletion on withdrawal requestSections 4–5 distinguish actual destruction, renamed accounts, collaborative records and backupsWithdrawal/deletion applicants
No specific disclosure, entrustment or transfer sectionsSections 6–8 specify app-specific disclosures, processors, transfer information and consent; actual entities/details still to finalizeAffected individuals
Location/external accounts not detailedSections 9–10 separate location, imports, bilateral consent and withdrawal/data treatmentLocation/connection users
Section 5 explains cookies and blockingSections 11/11-2 add local drafts, cache, permissions, push, SDKs and uninstall/account-deletion distinctionWeb/app users
Officer and remedy bodies primarily listedSections 12–15 add rights, representatives/children, security and contact procedures; signed-out contact remains to finalizeIndividuals/representatives
Effective date onlySection 16 distinguishes notice and publication from separately required consentAffected individuals
General IP/read-history description without specific guest read protection or external verificationSections 2, 4, 7, 8, 11, 12 and 16: deployed account/IP/session and read state, calculation versus deletion, cookies, raw-IP transmission to Turnstile, provider roles, rights and notice correction; published provider countries/retention criteria and actual log/backup rotation are distinguishedMembers and guests making protected reads
No specific distinction between entrustment disclosure and transfer consentTerms Article 13(4)–(6) and Policy Sections 7–8 distinguish disclosure and the underlying basis, statutory disclosure/notification for necessary overseas entrustment/storage, and cases requiring separate consent; no blanket renewed consent requirementRelevant individuals

Timing and Feedback

The current documents took effect on July 1, 2024. Planned notice is November 9, 2026; objections close November 23, 2026, 23:59; planned commencement is November 24, 2026, 00:00, all KST (UTC+9). This preserves both the current minimum seven-day notice and 14-day objection period: exclude the notice date, allow 14 full days, then commence the next day. Late actual notice requires rescheduling while preserving the current notice and objection periods. Publication of this comparison alone neither commences the amendment nor authorizes new processing.

Send comments through Musecat Support.

English and Japanese translations are for convenience. In case of differing meanings or interpretations, the Korean version is the reference, without excluding mandatory applicable law or statutory rights.

Musecat
All About Arcades