These are disclosure requirements for External App connections. Each connection screen identifies its operator, data and retention and obtains legally required separate consent. This document alone authorizes neither a particular connection nor disclosure.
Planned notice: November 9, 2026. Comments and objections close November 23, 2026, 23:59. Planned commencement: November 24, 2026, 00:00, all KST (UTC+9). Delayed notice requires adjustment preserving the current notice and objection periods.
Apps using Musecat services, data or APIs for crawling, advertising, commercial activities or arcade-discovery functions that substitute for or compete with Musecat and create a concrete or objectively foreseeable conflict of interest may not be developed, tested, distributed or operated. See Terms Article 12.
Unauthorized crawling and data access are prohibited even for public material. Member consent, registration or credential issuance does not authorize prohibited purposes or collection outside approval. Normal use and expressly approved API requests are distinguished.
Macros and scripts directly calling APIs must first be registered as Bots and use dedicated credentials. Editing without registration using personal Bearer tokens is grounds for suspension. All Bot work uses the owner account’s permissions, and owners must manage commands and credentials. Terms Article 12-2 governs responsibility and exemptions.
Where an external operator receives personal information for its own service, show the following before connection. Distinguish the app’s display name from the recipient’s actual legal identity.
Suggested consent item: “I consent to disclosure of the information described above to this app’s operator.” It does not cover other apps or all future fields. Distinguish necessary and optional permissions; refusing optional permissions must not block unrelated functions.
Explain reading separately from posting, editing and other actions within Musecat. “Account connection” or “profile access” must not conceal writing permissions.
Show action types, targets and scope before approval and obtain renewed approval for expansion. Distinguish consent to disclosure from authorization to act on the account.
In a separate flow, disclose source/operator, purposes, external account ID, selected profile/game records, retention and refusal effects. Where collection relies on consent, present:
“I consent to Musecat collecting and using the selected information from the external service described above.”
This does not permit the external app to read private Musecat information or edit Musecat data. Bilateral connections require checking each direction’s fields and permissions; one successful direction must not be presented as full completion.
Assess the transfer basis where information is sent to an overseas app or accessed from abroad. For consent-based transfers, separately disclose:
Suggested item: “I consent to the overseas transfer described above.” Disclosure consent and transfer consent must each satisfy their applicable requirements. Entrustment or storage relying on another legal basis requires the corresponding disclosures and safeguards.
Provide a cancellation option before approval and a disconnection route afterward. Revocation shall stop new requests under the permission; Musecat’s tokens and stored material follow finalized destruction rules. Independent external accounts or delivered data may require separate requests to their operators.
Keep only necessary evidence identifying member/app, notice version, actual data and permissions, purposes, retention, approval/refusal time and withdrawal. The evidence itself requires a lawful basis and retention rule; do not unnecessarily duplicate raw tokens as proof.
See the Terms amendment and Privacy Policy amendment.
English and Japanese are convenience translations. The Korean version governs interpretation of discrepancies, subject to mandatory applicable law and statutory rights.