Uhpenry Licensing Terms

These Licensing Terms (“Terms”) govern the licensing, distribution, and monetization of any project, code, or content (“Project”) sold, shared, or otherwise made available through Uhpenry.
By publishing, purchasing, or accessing a Project on Uhpenry, you acknowledge and agree to be bound by these Terms, the Uhpenry Terms of Service, and all applicable laws.

---

1. License Requirement

1. Mandatory License Inclusion
   All Projects, whether free, paid, private, or restricted-access, must include a valid license clearly stating the scope of rights granted to the user or recipient.
   A license must be:

   • Provided at or before the time of Snapgate availability.
   • Accessible for as long as the Project remains available to the user.

2. Acceptable License Types

   • SPDX-recognized open-source licenses (e.g., MIT, Apache 2.0, GPL).
   • Custom licenses in clear, understandable language.
   • Commercial or proprietary licenses drafted by the booth or their legal counsel.

3. Prohibited Practices

   • Publishing a monetized or gated Project without a license.
   • Concealing licensing terms until after purchase.

---

2. User Rights and Restrictions

1. Rights Granted
   Users receive only those rights explicitly stated in the license. If a right is not mentioned (e.g., redistribution, modification), it is not granted.

2. No Implied Rights
   Uhpenry grants no default rights. All rights must originate from the booth's provided license.

3. Examples of Rights That Must Be Explicit

   • Commercial use
   • Redistribution (with or without modifications)
   • Derivative works and adaptations
   • Attribution requirements
   • Support or maintenance commitments

---

3. Uhpenry's Role in License Enforcement

Uhpenry is not a contracting party to the license between booth and user but enforces platform rules requiring that:

• A valid license is attached to any monetized or gated Project.
• The license is visible to and accepted by the user before access.
• Violations may result in content removal, access revocation, refunds, or account sanctions.

---

4. License Modification and Retraction

1. No Retroactive Changes
   Booths may not alter or revoke a license for any user who has already purchased or been granted access.

2. Permitted Prospective Changes
   License terms may be updated for future transactions, provided that:

   • The new license is posted before further sales or access grants.
   • Existing users remain under the terms in effect at their time of purchase.

---

5. Third-Party Content and Attribution

If a Project incorporates third-party code or assets under separate licenses:

• The booth must disclose such licenses within the primary license file or a clearly named "ATTRIBUTION" file.
• All attribution, redistribution, and usage conditions from third-party licenses must be honored.

---

6. AI-Generated Code Policy

6.1 Mandatory Disclosure

Booths must clearly disclose the use of AI-generated code or content if:

• It constitutes a material or functional portion of the Project.
• It impacts security, licensing, or core features.

Disclosure must be included in a visible license section, README, or equivalent documentation.

6.2 Legal Responsibility

Booths are solely responsible for ensuring that:

• AI-generated content does not infringe third-party intellectual property rights.
• They have full authority to license the AI-generated work.
• Licensing terms of AI tools used (e.g., GitHub Copilot, OpenAI Codex) are fully complied with.

6.3 Prohibited Conduct

• Generating content intended to reproduce or evade licensing restrictions of proprietary works.
• Failing to disclose significant AI involvement.
• Misrepresenting AI-generated content as exclusively human-authored.

Violations will result in takedowns, account suspension, and/or permanent bans. Refer to AI-Generated Code Policy for further information.

---

7. Enforcement and Remedies

Within its platform scope, Uhpenry reserves the right to:

• Temporarily or permanently disable Snapgate for non-compliance.
• Remove non-compliant Projects.
• Enforce user refunds in cases of material license misrepresentation.
• Suspend or terminate accounts for repeated or severe violations.

All enforcement actions are final within the platform but do not preclude external legal remedies.

---

8. Dispute Resolution

Licensing disputes must be reported via the Dispute Resolution Policy.
Uhpenry will:

1. Review the applicable license and evidence.
2. Determine whether terms were violated.
3. Issue enforcement actions within platform scope.

AI-specific disputes will additionally consider:

• AI usage disclosures
• Licensing provenance documentation
• Tool usage logs and timestamps

---

9. Confidentiality

Licenses do not grant Uhpenry the right to resell, redistribute, or otherwise commercially exploit Projects.
All licensing data and user acceptance logs are stored securely for audit and compliance purposes.