Terms and Conditions: Read, Relax, Enjoy!
Please read them carefully to understand your rights and responsibilities.
1. Welcome to Themes.run
1.1 The sources of templates aggregated by this platform include: Open source template library: follow the license agreement indicated in each template (such as MIT License, CC BY-SA 4.0, etc.) User-generated templates: original/secondary creations uploaded by registered users (must comply with the provisions of Chapter 3)
1.2 The functions you obtain through this platform include: Introduction to open source templates and guidance to the open source platform to use the template Copyright registration and notarization service for user templates (optional value-added function)
2. Rules for using open source templates
2.1 You must strictly abide by the original agreement requirements marked on each template, including but not limited to: Attribution requirements: Keep the author information page in the template file (the account will be frozen if deletion is detected) Infectious agreement: When using GPL/AGPL agreement templates, derivative works must be open source Business restrictions: CC BY-NC agreement templates are prohibited from being used for direct revenue projects (such as paid template website themes)
2.2 The platform provides automated agreement detection tools, but you still need to verify by yourself: The compatibility of the template authorization scope with your usage scenario Legal risks when using multiple agreement templates in combination
3. User uploaded content
3.1 By uploading, you declare and guarantee: You own all intellectual property rights of the template or have obtained redistribution authorization from the original author Do not contain any patented technology (such as exclusive algorithms for certain UI animations) Clearly mark the open source projects and modified parts on which the derivative works are based (in accordance with GPL requirements)
3.2 You can choose the authorization method for the template: Open source model: Bind SPDX standard protocol (such as Apache 2.0, CC0, etc.) Commercial authorization: Set a minimum selling price (≥$1) and authorize the platform to handle copyright disputes
3.3 The platform has the right to remove the following content: Templates that fail to pass the protocol test within 48 hours Works that receive more than 3 infringement complaints and fail to provide evidence within 72 hours
4. Revenue and sharing
4.1 Distribution of download revenue of user templates: Basic share: 70% goes to the uploader, 30% is the platform service fee Agreement reward: Templates using CC0 agreement will receive an additional 15% traffic subsidy
4.2 Settlement rules: Withdrawal is available for purchases over $50 (PayPal/Stripe) Dispute period: The payer can appeal copyright issues and freeze the share within 14 days after downloading
5. Infringement handling
5.1 Follow the DMCA counter-notification process: The complaining party needs to provide: ① URL of the infringing content ② Proof of ownership ③ Contact information The platform will remove the disputed template within 5 working days and notify the uploader
5.2 Responsibility for malicious complaints: The party making a false complaint must bear a $300 liability deposit each time
6. Disclaimer
6.1 The platform does not guarantee: The code security of the templates uploaded by users (it is recommended to run in a sandbox environment) The real-time validity of the open source agreement (may change due to project updates)
6.2 You are solely responsible for the losses caused by the following actions: Mixed use of incompatible open source agreements (such as GPL and BSD) Failure to update the template copy with changed licensing terms in a timely manner
7. Other Terms
7.1 Governing Law: Intellectual property disputes are subject to the laws of California, USA User profit-sharing disputes are subject to arbitration by the Singapore International Commercial Court
7.2 Update notification method: Agreement changes will be written into the template metadata (via verification tool prompts) Major term updates will be announced via GitHub issue