Addon submission rules

This document outlines the rules and guidelines for submitting addons to this platform.

By submitting an addon, you agree to comply with these terms.

We reserve the right to remove any addon that violates these terms. We also reserve the right to update this policy at any time, and it is your responsibility to review it before submitting a new addon.

Prohibited content

You must not submit:

• Abusive, harassing, discriminatory, or threatening content.
• Defamatory, false, or harmful material.
• Malicious code, ads, viruses, or any form of malware.
• Content promoting illegal activities.
• Anything related to politics, religion, gender identities, or any other sensitive topics.

Preconfigured addons

You must not submit addon URLs that contain preconfigured parameters, such as API keys or user-specific configurations.

Examples of prohibited URLs include:

• URLs with encoded configuration data before /manifest.json (e.g., https://example.com/eyJhcGlfa2V5IjoiLi4uIn0=/manifest.json)
• URLs with API keys or authentication tokens embedded in the path

Why this is not allowed

Submitting preconfigured addon URLs poses several risks:

1. Security risk: Accidentally leaking API keys or authentication tokens that could be exploited by others
2. Privacy concerns: Exposing personal or user-specific configuration data
3. Paid addon bypass: Allowing users to bypass paid addon restrictions, which we do not condone
4. User experience: Submitted addons should always be configurable starting from a blank slate, allowing users to set up their own credentials securely

Always submit the base addon URL without any pre-filled configuration parameters. Users should configure the addon with their own credentials after installation.

Disclaimer of liability

We are not responsible for any issues, damages, or legal claims arising from the use of addons submitted to our platform. The responsibility for ensuring compliance with applicable laws and regulations lies solely with the addon submitter.