# Component Publishing Agreement

Welcome to publishing components on this platform. To ensure platform ecosystem compliance, security, and user rights, you must strictly comply with the following terms. **Submitting for publication constitutes acceptance of this agreement**.

---

## I. Legality and Compliance Requirements

- **Do not publish any component content that violates national laws, regulations, industry regulatory standards, and public order and good customs**.
- **Prohibited content includes politically sensitive, violent or bloody, pornographic or vulgar, hate speech, discriminatory, feudal superstitious, or other违规 information**.
- **Do not publish components involving gambling, fraud, pyramid schemes, illegal finance, or other illegal purposes**.
- Component functionality and content must align with the platform's positioning and **must not exceed the scope of services allowed by the platform**.

---

## II. Intellectual Property and Authorization Standards

- **You must ensure that you have complete and legal intellectual property rights to the published components (including code, interface design, assets, etc.), with no third-party ownership disputes**.
- If the component uses open-source code, third-party libraries, or assets (such as images, icons, fonts), **you must strictly comply with the corresponding open-source licenses (such as MIT, GPL, Apache, etc.) or authorization terms**, and **clearly indicate the source and copyright information**.
- **Plagiarism or copying of others' published component content is prohibited**, as is the unauthorized use of others' intellectual property achievements.
- If the component involves others' portrait rights, name rights, trademark rights, or other rights, **you must obtain written authorization from the relevant parties in advance** and **disclose the authorization information** in the component description.

---

## III. Content Authenticity and Quality Commitment

- **Components must have basic usability, with no known vulnerabilities that could cause system crashes, data loss, or other serious issues**.
- If the component relies on third-party services (such as API interfaces, cloud storage, etc.), **you must clearly indicate dependencies, applicable environments, and risk warnings for third-party services in the description**.
- **Publishing blank, test-only, advertising redirect (no actual functionality, used only for promotion), or invalid components unrelated to the platform is prohibited**.

---

## IV. Security and Privacy Protection Obligations

- **Components must not contain malicious code (such as viruses, Trojans, worms), backdoor programs, or functions that may steal user data**.
- If the component needs to collect user data (such as account information, device information, usage records, etc.), **the following requirements must be met**:
  - **Clearly inform users of the scope, purpose, and usage of data collection**;
  - **Obtain active user authorization (such as pop-up consent)**, and provide ways to delete data and withdraw authorization;
  - **Do not collect data beyond the scope**, and **do not use user data for purposes outside the agreement or disclose it to third parties** (except as required by laws and regulations);
- **Components must have basic data security protection capabilities** to avoid user data leakage or tampering due to their own vulnerabilities.

---

## V. Maintenance and Update Responsibilities

- **You are advised to maintain components regularly**, promptly fix functional vulnerabilities, adapt to platform version updates, and be compatible with mainstream operating environments.
- If the component has major security issues (such as data leakage risks, malicious code injection, etc.), **you must submit a fix within 24 hours** and cooperate with the platform for emergency handling.
- If you plan to stop maintaining or delist the component, **you must announce the notice on the component details page 7 days in advance** to reserve migration time for users who have already used the component.
- When updating components, **clearly label the update content** (such as new features, bug fixes, compatibility adjustments), and **do not add new permissions or违规 features that are not described in the update**.

---

## VI. Platform Review and Violation Handling

- **The platform has the right to review components you submit**. The review standards are based on this agreement and platform rules. The review results (**approved / rejected / rectification required**) will be notified through system notifications.
- If the component violates this agreement, **the platform has the right to take the following measures**:
  - **Require rectification within a time limit, and suspend component display during the rectification period**;
  - **Directly reject the publication application, and no refund of review costs incurred (if any)**;
  - **Delist published违规 components and clear related display data**;
  - **If you violate this agreement multiple times (3 times or more cumulatively)**, the platform has the right to **permanently ban your publishing account** and reserves the right to pursue legal liability.

---

## VII. Disclaimer

- **You must bear the legal responsibilities arising from component violations, infringement, or quality issues** (including but not limited to third-party claims, administrative penalties). The platform does not assume related joint liability.
- The platform **does not assume compensation liability** for user losses caused by improper component use, environment adaptation issues, or third-party service failures.
- **The platform has the right to adjust the terms of this agreement** based on laws and regulations updates, industry changes, and platform development needs. Updates will be notified through platform announcements. **Your continued publication of components constitutes acceptance of the updated agreement**.
