Androidacy, LLC
Last Updated: February 27, 2026
1. Scope and Incorporation
This Module Repository Policy (“Policy”) establishes the terms governing the submission, discovery, distribution, retention, and management of software modules within the Androidacy Module Repository (“Repository”). This Policy is supplemental to and incorporated by reference into the Androidacy Terms of Service (“ToS”), available at androidacy.com/terms/. Capitalized terms not defined herein have the meanings ascribed to them in the ToS.
This Policy governs matters specific to the Repository: module submission, automated discovery, licensing, intellectual property as it pertains to modules, content retention and removal, developer obligations, deprecation, advertising, exclusivity, and security disclosure. All matters not expressly addressed herein, including without limitation account registration, dispute resolution, governing law, limitation of liability, indemnification, privacy, warranties, disclaimers, and amendment procedures, are governed exclusively by the ToS. Where any provision of this Policy conflicts with the ToS, the ToS shall control unless this Policy expressly and specifically provides otherwise with respect to a defined subject matter.
By submitting a module to the Repository, accessing or using the Repository as an end user, or maintaining a module in the Repository after the effective date of this Policy, you acknowledge that you have read, understood, and agree to be bound by this Policy and the ToS.
2. Definitions
“Discovered Module” means a module identified and added to the Repository by Androidacy through its automated or semi-automated discovery processes, without a direct submission by the module’s developer.
“Developer” means any person or entity that authored, maintains, or holds intellectual property rights in a module hosted in the Repository, regardless of whether the module was directly submitted or discovered.
“Developer-Submitted Module” means a module submitted to the Repository by or on behalf of its developer through the process set forth in Section 3.
“Excluded License” means any software license that, as a condition of use, modification, distribution, or linking, requires the disclosure, publication, or licensing of Androidacy’s proprietary source code, or any license specifically designated as excluded by Androidacy. As of the effective date of this Policy, Excluded Licenses include, without limitation, AGPL-3.0-only, AGPL-3.0-or-later, SSPL-1.0, and any license imposing substantially similar source-disclosure obligations. Androidacy may amend this designation at any time in accordance with the amendment procedures set forth in the ToS.
“License of Record” means the license, whether express or implied, under which a specific version of a module was submitted to or discovered for inclusion in the Repository, as recorded by Androidacy at the time of submission or discovery. For modules discovered pursuant to Section 4.1(b), the License of Record shall reflect the implied license basis.
“Module” means any software package distributed through the Repository, including without limitation Magisk modules, KernelSU modules, APatch modules, and modules for other Android modification frameworks.
3. Module Submission
3.1 Submission Process
Developers may submit modules through the form at androidacy.com/module-repository-applications/. Each submission shall include a valid URL from which Androidacy can retrieve the module package or compilable source code, including without limitation GitHub, GitLab, or Codeberg repository URLs and direct download links. Submissions may include optional reviewer notes, source type designation, and branch specification.
3.2 License Requirements for Submitted Modules
Developer-Submitted Modules may be distributed under any license that is not an Excluded License, including open source and proprietary licenses. A developer who submits a module under a proprietary license thereby grants Androidacy the distribution license set forth in Section 7.1. That grant constitutes the sole legal basis upon which Androidacy distributes the proprietary module. Developers submitting proprietary modules are advised to review the retention provisions of Section 8 prior to submission.
3.3 Developer Representations and Warranties
By submitting a module to the Repository, the developer represents and warrants, as of the date of submission and on a continuing basis for so long as the module remains in the Repository, that:
(a) The developer is the author of the module or has obtained all rights, licenses, and authorizations necessary to submit the module and to grant Androidacy the license set forth in Section 7.1.
(b) The module does not infringe, misappropriate, or otherwise violate any intellectual property right, proprietary right, or other right of any third party.
(c) The module complies with the requirements of Section 5 and all applicable laws and regulations.
(d) All information provided in connection with the submission, including authorship, licensing, and module description, is accurate, complete, and not misleading.
A material breach of any representation or warranty constitutes grounds for immediate removal of the module and suspension or termination of the developer’s account, without prejudice to any other remedy available to Androidacy under this Policy or the ToS.
3.4 Review and Approval
All submissions are subject to Androidacy’s review. Androidacy is under no obligation to approve any submission and may reject any submission in its sole discretion, including without limitation for failure to satisfy the requirements of Section 5, incompatibility with Repository infrastructure, substantial duplication of an existing listing, or insufficient quality. Androidacy does not guarantee any review timeline or provide detailed rationale for rejections.
3.5 Resubmission
A previously rejected submission may be resubmitted after the developer has remedied the deficiencies identified during review. Resubmission creates no obligation on Androidacy to approve the module. Repeated submission of modules that fail to satisfy Repository requirements may result in temporary or permanent revocation of submission privileges.
3.6 Developer Account
Each developer who submits a module shall establish and maintain an account containing accurate and current contact information. Androidacy reserves the right to suspend distribution of any developer’s modules and to revoke submission privileges upon failure to maintain current contact information or upon Androidacy’s inability to reach the developer after reasonable attempts.
4. Discovered Modules
4.1 Discovery and Inclusion
Androidacy operates automated and semi-automated processes to identify and evaluate publicly available modules for potential inclusion in the Repository. Modules identified through such processes may be added to the Repository without a direct submission from the developer, provided the module satisfies one of the following conditions:
(a) The module is published under an open source license that is not an Excluded License and that affirmatively grants the right to reproduce and redistribute the licensed work; or
(b) The module is published on a public source code hosting platform (including without limitation GitHub, GitLab, and Codeberg) without an explicit license, where the terms of service of the hosting platform or the circumstances of publication give rise to an implied license to reproduce and redistribute the code consistent with the platform’s intended purpose.
Discovered Modules shall not include modules published under proprietary licenses or Excluded Licenses.
4.2 Legal Basis for Distribution
Androidacy’s distribution of modules through the Repository is authorized under one or more of the following legal bases, as applicable:
(a) For Developer-Submitted Modules, the express license grant set forth in Section 7.1, arising from the developer’s voluntary submission of the module to the Repository.
(b) For Discovered Modules published under an open source license, the terms of the open source license under which the developer published the module.
(c) For Discovered Modules published without an explicit license on a public source code hosting platform, the implied license arising from the developer’s voluntary publication of the module on such platform, as described in Section 4.1(b).
In each case, the developer’s affirmative act of submission or public publication constitutes the grant, express or implied, upon which Androidacy relies. No additional consent, agreement, or authorization from the developer is required beyond the applicable basis identified above.
4.3 Processing
Androidacy may process, repackage, reformat, and adapt Discovered Modules through the same infrastructure and procedures applied to Developer-Submitted Modules. Such processing includes, without limitation, metadata generation, format standardization and conversion, description indexing, security analysis, and repackaging for Repository compatibility. Where such processing produces material that constitutes a derivative work under 17 U.S.C. § 101, Androidacy shall distribute such material in compliance with the terms of the applicable license or, for modules distributed pursuant to an implied license under Section 4.1(b), in a manner consistent with the scope of that implied license.
4.4 Claiming
A developer of a Discovered Module may contact Androidacy at [email protected] to establish verified ownership, correct metadata, or discuss the listing. Verified ownership permits the developer to manage module metadata and receive communications regarding the module but does not convert the Discovered Module to a Developer-Submitted Module for purposes of the license grant in Section 7.1.
5. Module Requirements
5.1 Technical and Content Standards
All modules hosted in the Repository, whether submitted or discovered, shall satisfy the following requirements:
(a) Compatibility. Modules shall be compatible with supported Android versions and shall conform to the technical specifications of their respective frameworks.
(b) Safety. Modules shall not contain malicious code, malware, spyware, cryptocurrency miners, or any component designed to harm, monitor, exploit, or degrade the performance of end-user devices. Advertising or monetization components that comply with Section 10.2 are not prohibited under this provision; advertising or monetization that fails to satisfy the requirements of Section 10.2 is prohibited.
(c) Licensing. Modules shall be distributed under a license that is not an Excluded License. Discovered Modules shall additionally satisfy the requirements of Section 4.1. Developer-Submitted Modules and Discovered Modules included pursuant to Section 4.1(a) should include a license file or machine-readable license declaration in their source repository or distribution package; the absence of an explicit license file does not preclude listing but may limit Androidacy’s ability to verify and enforce the developer’s licensing intent. Discovered Modules included pursuant to Section 4.1(b) are exempt from this requirement; Androidacy shall record the implied license basis in the License of Record.
(d) Structure and Documentation. Modules shall conform to the structural and packaging requirements of their respective frameworks and shall include documentation sufficient for an end user of ordinary skill to understand the module’s purpose, behavior, and any material risks.
(e) Attribution. Modules shall preserve original authorship credits and, where applicable, commit history. No submission shall misrepresent authorship or remove attribution from forked or derivative works.
(f) Functionality. Each module shall provide substantive functionality. Modules whose sole purpose is the installation of an application, without additional modification or utility, are prohibited.
(g) Disclosure of Material Effects. Modules shall not cause end-user devices to function in ways that a reasonable user would not anticipate. Any material change to device functionality, behavior, or security posture shall be clearly and conspicuously disclosed in the module description prior to installation.
(h) Data Practices. Any module that collects, transmits, or processes personal data from end users shall disclose the nature, scope, purpose, and recipients of such collection in the module description. All such data practices shall comply with applicable law, including without limitation the GDPR, CCPA, and COPPA where applicable. Developers shall not collect, scrape, or harvest personal data from Androidacy, the Repository, or Repository users without Androidacy’s express prior written consent.
5.2 Prohibited Content
The following are prohibited in the Repository:
(a) Modules that infringe upon any third-party intellectual property right.
(b) Modules that violate any applicable law, regulation, or order.
(c) Modules that are substantially duplicative of an existing Repository listing without meaningful technical or functional differentiation.
(d) Modules submitted or manipulated through automated means designed to circumvent review, inflate metrics, or otherwise abuse Repository systems.
5.3 App Store Compliance
Developers acknowledge that Androidacy may restrict the visibility or availability of certain modules within the Androidacy application when the application has been installed through an app store, to the extent necessary for compliance with applicable app store policies. Such restrictions do not affect the availability of the module through the Androidacy website or other non-app-store distribution channels.
6. License of Record and License Changes
6.1 Recording
Androidacy shall record the license under which each module version is submitted to or discovered for inclusion in the Repository at the time of submission or discovery. The License of Record governs Androidacy’s distribution rights for that version.
6.2 Prospective License Changes
Where a developer relicenses a module under a different license that is not an Excluded License (and, for Discovered Modules, is not proprietary), Androidacy shall update the License of Record for versions submitted or discovered after the effective date of the relicensing. Versions previously submitted or discovered remain governed by their original License of Record.
6.3 License Changes to Excluded or Proprietary Licenses
Where a developer relicenses a module under an Excluded License or, for Discovered Modules, under a proprietary license, or where a developer of a previously unlicensed module adds an Excluded License or proprietary license for the first time:
(a) Androidacy shall not accept or ingest new versions published under the newly adopted license.
(b) The last version distributed under a non-excluded (and, where applicable, non-proprietary) license, or under an implied license pursuant to Section 4.1(b), shall remain in the Repository, governed by its original License of Record. For the avoidance of doubt, a nonexclusive license grant, whether express or implied, is not retroactively revoked by the licensor’s subsequent adoption of more restrictive terms for later versions of the same work.
(c) The module shall be flagged as frozen, indicating that it will not receive further upstream updates through the Repository.
(d) Androidacy may, in its sole discretion, distribute security patches or compatibility updates for frozen modules to the extent permitted by the License of Record.
6.4 Disputes
Any developer who disputes Androidacy’s License of Record for a module shall submit supporting evidence to [email protected], including without limitation repository commit history, license file provenance, and release documentation. Androidacy shall review the submission and amend the License of Record if the evidence so warrants. Unresolved disputes are subject to the dispute resolution provisions of the ToS.
7. Intellectual Property
7.1 License Grant: Developer-Submitted Modules
By submitting a module to the Repository, the developer hereby grants to Androidacy a perpetual, irrevocable, worldwide, royalty-free, fully sublicensable, non-exclusive license to:
(a) Host, store, reproduce, and distribute the module through the Repository and any platform operated by or on behalf of Androidacy.
(b) Process, repackage, reformat, and adapt the module as reasonably necessary for Repository infrastructure compatibility, including without limitation metadata generation, format conversion, description indexing, and automated security analysis.
(c) Display the module’s name, description, icon, screenshots, and associated metadata within the Repository, within the Androidacy application, and in materials promoting the Repository.
(d) Submit the module to third-party services for security, quality, compliance, and compatibility analysis.
This grant does not transfer ownership of the module or its underlying intellectual property. The developer retains all right, title, and interest in the module except as expressly granted herein. For modules distributed under proprietary licenses, this Section 7.1 constitutes the sole and complete grant of distribution rights to Androidacy; no additional rights are implied or conferred.
7.2 Discovered Modules
Androidacy’s rights with respect to Discovered Modules arise solely under the applicable legal basis identified in Section 4.2(b) or 4.2(c), as the case may be, and not from the license grant in Section 7.1. For Discovered Modules published under an express open source license, the scope of Androidacy’s distribution rights is determined by the terms of that license. For Discovered Modules distributed pursuant to an implied license under Section 4.1(b), the scope of Androidacy’s rights is determined by the implied license arising from the developer’s public publication, as described in Section 4.2(c).
7.3 User-Generated Content
Reviews, ratings, comments, and other end-user content associated with Repository modules constitute User-Generated Content as defined in the ToS and are subject to the license grant set forth in ToS Section 8.2. Androidacy may retain User-Generated Content associated with a module following the module’s removal from the Repository, subject to anonymization where appropriate.
7.4 Androidacy-Generated Content
Metadata, descriptions, compatibility assessments, security analyses, AI-generated recommendations, and all other content created by or on behalf of Androidacy in connection with a module are the sole and exclusive property of Androidacy, LLC. Removal of a module from the Repository does not obligate Androidacy to remove any Androidacy-Generated Content associated with that module, though Androidacy may elect to do so in its discretion.
8. Content Retention and Module Removal
8.1 Removal by Androidacy
Androidacy may remove, restrict, suspend, or delist any module from the Repository at any time, with or without notice, for any reason it deems sufficient, including without limitation:
(a) Violation of this Policy or the ToS.
(b) Receipt of a valid takedown notice under the DMCA Policy at androidacy.com/dmca/.
(c) Identification of a security vulnerability posing material risk to end users.
(d) Abandonment under Section 9.
(e) Legal compulsion.
(f) Any other ground Androidacy determines, in its sole judgment, to be sufficient.
8.2 Developer-Requested Removal: Developer-Submitted Modules
A developer may request removal of a Developer-Submitted Module by contacting [email protected] with satisfactory evidence of authorship or ownership. Such requests are subject to the following:
(a) Androidacy holds a perpetual, irrevocable license to all submitted versions of the module pursuant to Section 7.1. Androidacy may, in its sole discretion, continue to distribute any previously submitted version. Androidacy shall honor a removal request only where (i) Androidacy elects to do so in its sole discretion, (ii) removal is compelled by applicable law or valid legal process, or (iii) Androidacy determines in good faith that continued distribution would be unconscionable.
(b) Where Androidacy elects to remove a module, the module package shall be removed from active distribution. Androidacy may retain a non-public archival copy for purposes of legal compliance, dispute resolution, and record-keeping.
(c) Androidacy-Generated Content is governed by Section 7.4. User-Generated Content is governed by Section 7.3.
8.3 Developer-Requested Removal: Discovered Modules
A developer may request removal of a Discovered Module by contacting [email protected] with satisfactory evidence of authorship or ownership. Androidacy shall consider such requests but is under no obligation to comply where Androidacy holds distribution rights under the applicable License of Record. In evaluating a removal request, Androidacy may consider:
(a) Whether the License of Record, whether an express open source license or an implied license arising under Section 4.1(b), permits redistribution.
(b) Whether the developer has relicensed subsequent versions under an Excluded License or proprietary license.
(c) Whether continued distribution serves the interests of Repository users.
(d) Whether security, legal, or policy considerations favor retention or removal.
Androidacy shall notify the developer of its determination. Where Androidacy declines a removal request, the developer’s sole remedy is through the dispute resolution provisions of the ToS. For the avoidance of doubt, a removal request submitted under this Section does not constitute and shall not be construed as a DMCA takedown notice. Claims of copyright infringement shall be submitted exclusively through the procedures set forth in the DMCA Policy at androidacy.com/dmca/.
8.4 Effect of Removal
Removal of a module from active distribution does not affect or extinguish:
(a) Copies previously downloaded by end users.
(b) Androidacy’s rights under the License of Record or Section 7.1, including archival and compliance rights.
(c) Androidacy-Generated Content and User-Generated Content, as set forth in Sections 7.3 and 7.4.
(d) Any provision of this Policy or the ToS that by its nature survives removal, including without limitation indemnification and limitation of liability.
9. Module Deprecation and Abandonment
9.1 Deprecation
Androidacy may designate a module as deprecated where: (a) the module has not received a developer update in twelve (12) months or more; or (b) the module is no longer compatible with current Android releases or supported framework versions. Deprecated modules remain available in the Repository but may be displayed with a deprecation notice visible to end users.
9.2 Abandonment
Androidacy may classify a module as abandoned where any of the following conditions is satisfied:
(a) The developer has failed to respond to communications from Androidacy for a period of ninety (90) consecutive days.
(b) The module has not received any update for a period of twenty-four (24) consecutive months.
(c) The developer has made a public statement indicating that the module is no longer maintained.
Upon classification as abandoned, Androidacy may, in its sole discretion, remove the module from active distribution, retain the module with an abandonment notice, or permit a community fork published under a compatible license to replace the original listing.
10. Advertising and Monetization
10.1 Repository Advertising
Androidacy displays third-party advertising on Repository pages, including module listings and detail pages. Premium Members receive an ad-free experience in accordance with their Membership plan as described in the ToS.
10.2 In-Module Advertising and Monetization
Modules distributed through the Repository may include advertising and monetization mechanisms, subject to the following requirements:
(a) Advertising Standards. All in-module advertising shall be non-deceptive, non-disruptive, and shall not interfere with normal device operation. Advertising shall not mimic system notifications, security warnings, or device functionality. Interstitial, audio, and video advertisement formats are permitted where they appear at natural interaction points within the module’s functionality and where a reasonable user would anticipate such formats in context. Such formats are prohibited where they appear without user initiation in contexts unrelated to module functionality or where they cannot be reasonably dismissed.
(b) Malicious Advertising. Advertising shall not serve malicious content, redirect users to harmful sites, or facilitate the installation of unwanted software.
(c) Disclosure. The presence, general nature, and format of advertising or monetization within a module shall be clearly and conspicuously disclosed in the module description prior to installation.
(d) Legal Compliance. All in-module advertising shall comply with applicable law, including without limitation the FTC Act and applicable FTC guidelines concerning endorsements and native advertising.
(e) Alternative Monetization. Developers may include non-advertising monetization mechanisms such as donation links, voluntary contribution prompts, and links to external funding platforms (including without limitation Patreon, Ko-fi, and GitHub Sponsors), provided such mechanisms do not condition access to essential module functionality upon payment unless the module is expressly designated as a paid or premium module in its Repository listing.
(f) Prohibition on Primarily Monetization-Driven Modules. Modules whose primary purpose is to display advertising, generate advertising revenue, or serve as a vehicle for monetization rather than to provide substantive, independent functionality to end users are prohibited. Androidacy shall determine whether a module violates this provision in its sole discretion.
Androidacy reserves the right to remove or restrict any module whose advertising or monetization practices violate these requirements or are, in Androidacy’s sole judgment, detrimental to the end-user experience.
10.3 Revenue Sharing
Androidacy may, in its sole discretion, offer revenue-sharing arrangements to developers of qualifying modules. Eligibility criteria, compensation terms, payment schedules, and program duration shall be established by separate written agreement between Androidacy and the developer. This Policy does not create any entitlement to revenue sharing. Androidacy may modify or discontinue any revenue-sharing program at any time upon reasonable notice to affected participants.
11. Exclusivity Arrangements
11.1 Initiation
Either Androidacy or a developer may propose an exclusivity arrangement for a module. No exclusivity obligation arises under this Policy; any such arrangement requires execution of a separate written agreement by both parties.
11.2 Benefits
An exclusivity agreement may provide for enhanced distribution benefits, which may include without limitation promotional placement, featured designation, algorithmic priority in search results and recommendations, and such additional benefits as Androidacy may make available from time to time. Exclusivity arrangements do not affect baseline listing eligibility or standard distribution; modules not subject to an exclusivity arrangement remain listed and distributed under the standard terms of this Policy.
11.3 Governing Terms
The duration, scope, obligations, termination provisions, and any financial terms of an exclusivity arrangement shall be governed solely by the applicable written agreement between Androidacy and the developer, and not by this Policy.
12. Security and Vulnerability Disclosure
12.1 Developer Obligations
Developers shall respond to reports of security vulnerabilities affecting their modules in a timely manner. Where a critical vulnerability is identified and the developer fails to respond or provide a remediation within a reasonable period, Androidacy may, without limitation:
(a) Suspend or remove the module from active distribution pending remediation.
(b) Apply a temporary patch or mitigation to the extent permitted by the License of Record and note such modification in the module listing.
(c) Display a security advisory to end users accessing the affected module.
12.2 Reporting
Security vulnerabilities in modules hosted in the Repository should be reported to [email protected]. Androidacy shall make reasonable efforts to coordinate disclosure with the affected developer prior to public action, except where immediate suspension or removal is necessary to protect end users from active exploitation or imminent harm.
13. Third-Party Analysis
Developers acknowledge and agree that any module submitted to or hosted in the Repository may be transmitted to third-party services for security scanning, malware detection, license compliance verification, and quality assurance. Androidacy selects such providers in its sole discretion and is not obligated to disclose the identity of any third-party analysis provider.
14. Contact
All communications regarding this Policy, the Repository, removal requests, license disputes, and related matters shall be directed to:
Androidacy, LLC
Email: [email protected]
Copyright and DMCA matters: [email protected]
Privacy matters: [email protected]
Legal matters: [email protected]
This Policy was last updated on the date above. Previous versions are available upon request.