Module Repository Requirements Policy

Effective Date: September 10, 2024

1. Preamble

This Module Repository Requirements Policy (“Policy”) establishes the legally binding terms and conditions governing the submission, management, and distribution of digital content—specifically software modules, including but not limited to Magisk, KernelSU, and other modules—within the Androidacy Module Repository (“Repository”). By submitting a module (“Module”), participating in, or using the Repository, you (“Developer” or “User”) agree to comply with and be bound by the terms and conditions of this Policy as of the date of your engagement.

2. Submission and Compliance

2.1 Module Standards and Requirements

1. Compatibility and Technical Standards: All Modules submitted to the Repository must be inherently compatible with modern Android operating systems and must conform to the technical standards and requirements prescribed by Androidacy.
2. Legal Compliance: Modules must not contain malicious code, knowingly or unknowingly distribute malware, infringe upon any intellectual property rights, or violate any applicable laws or regulations.
3. Developer Account: Developers are required to establish and maintain an account with accurate and up-to-date contact information. Androidacy reserves the right to terminate any Developer’s account and remove associated Modules if unable to establish contact with the Developer.
4. Structural and Content Requirements: Modules must adhere to specified structural and content guidelines, including the inclusion of a comprehensive README.md file at the root of the Module’s repository and compliance with the appropriate format for the framework utilized.
5. Authorship and Originality: Modules must preserve original authorship credits and commit history. Submissions must not replicate or closely resemble any existing Module in the Repository.
6. Prohibition of Automated Submissions and Fraud: Users and Developers are prohibited from using automated means to submit Modules or to engage in any activity intended to defraud Androidacy or manipulate the Repository.
7. Third-Party Submission and Analysis: Modules may be submitted to and analyzed by third parties for compliance, security, and quality assurance purposes.
8. User Expectations: Modules must not cause end-user devices to function in ways that users would not reasonably expect. Any significant changes to device functionality must be clearly disclosed to the user prior to installation.
9. Data Privacy and Consent: Developers are prohibited from scraping or collecting personal data from Androidacy or its users without prior informed consent. Any collection of personal data must comply with applicable privacy laws and regulations.
10. Functionality Assurance: Developers must make reasonable efforts to ensure that their Modules function correctly and as intended. Modules should be thoroughly tested prior to submission to the Repository.
11. Prohibition on Sole-Purpose App Installation: Modules may not be used for the sole purpose of installing an application. Modules should provide meaningful functionality beyond merely installing an app.
12. App Store Compliance: Developers acknowledge that certain types of Modules may be hidden or restricted if Androidacy’s application is detected to be installed from an App Store, in order to maintain compliance with App Store policies.

3. Distribution, Monetization, and Revenue Sharing

3.1 Rights and Obligations

1. Advertising Rights: Androidacy reserves the irrevocable right to display advertising on all pages related to hosted Modules. This serves to cover hosting and operational costs while maintaining free access for end-users. Users may opt to remove advertising by paying a predetermined fee. Developers wishing to remove advertising from their Module pages may contact Androidacy to negotiate a custom agreement.
2. Approval of Third-Party Paywalls and Advertising: Developers may implement paywalls or include advertising for third-party services within their Modules, provided they obtain prior approval from Androidacy. All such advertising must be clearly identified as such.
3. Revenue Sharing: Androidacy retains sole discretion to engage in revenue-sharing arrangements with Developers of eligible Modules, subject to traffic metrics and quality criteria. Participation in revenue-sharing programs is contingent upon meeting criteria set by Androidacy, which are subject to change without notice.
4. Right to Exclusivity: Androidacy reserves the right to require exclusivity or a period of exclusivity for certain Modules at its discretion. Developers will be notified if such a requirement applies to their Modules.

4. Automated Submissions and Module Removal

4.1 Provisions for Module Removal

1. Automated Inclusion: Androidacy utilizes automated processes for the discovery and inclusion of Modules, provided such Modules meet established licensing and compliance requirements.
2. Developer Removal Requests: Developers may request the removal of their Modules, subject to providing satisfactory evidence of authorship. Androidacy reserves the right to refuse such removal requests at its sole discretion unless legally obligated to comply or if deemed necessary for user safety.
3. Androidacy’s Right to Remove Modules: Androidacy reserves the right to remove any Module that violates this Policy or for any other reason at its sole discretion.

5. Legal Provisions and Disclaimers

5.1 Intellectual Property and Licensing

1. License Grant: By submitting a Module, Developers grant Androidacy a perpetual, irrevocable, worldwide, royalty-free, and unrestricted license to use, reproduce, modify, distribute, display, perform, and create derivative works of the Module in any media formats and through any media channels, as necessary for the provision of services.
2. Retention of Rights: Developers retain all their rights, title, and interest, including all intellectual property rights, in and to their Modules, except as expressly granted to Androidacy under this Policy. This grant does not revoke the Developer’s rights unless legally necessary.
3. Third-Party Analysis: Developers acknowledge and agree that their Modules may be submitted to and analyzed by third parties for purposes including but not limited to compliance, security assessments, and quality assurance.

5.2 Data Privacy and Security

1. Prohibition on Data Scraping: Developers are prohibited from scraping or collecting personal data from Androidacy or its users without obtaining prior informed consent.
2. Compliance with Privacy Laws: Any collection, use, or distribution of personal data must comply with all applicable privacy laws and regulations, including but not limited to GDPR, CCPA, and other relevant statutes.

5.3 Disclaimer of Liability

1. Limitation of Liability: Androidacy disclaims any liability for damages arising from the use or misuse of Modules.
2. No Warranties: Modules are provided “as is” without any warranties, express or implied, including but not limited to warranties of merchantability or fitness for a particular purpose.
3. User Responsibility: While Androidacy endeavors to ensure the security and benefit of Modules, it makes no guarantees, express or implied. Users are solely responsible for their use of the Repository and any Modules obtained therefrom.

6. Amendments and Jurisdiction

6.1 Policy Amendments

1. Right to Amend: Androidacy reserves the right to amend this Policy at any time. Such amendments shall become effective upon posting to the Repository. Continued use of the Repository constitutes acceptance of the revised terms.
2. Severability: If any provision of this Policy is found to be unenforceable or invalid, the remaining provisions shall remain in full force and effect.

6.2 Governing Law

1. Jurisdiction: This Policy shall be governed by and construed in accordance with the laws of the United States, without regard to its conflict of laws principles.

7. Additional Terms

1. Supplementary Agreements: This Policy is supplementary to, and does not replace, Androidacy’s General Terms, Privacy Policy, and Community Contribution Agreement. In the event of any conflict between this Policy and other agreements, the more specific terms shall govern.
2. Entire Agreement: This Policy constitutes the entire agreement between the parties concerning its subject matter and supersedes all prior agreements and understandings.

Effective as of September 10, 2024.