PyneHub logoPyneHub
All legal documents

PyneHub Terms of Use & Acceptable Use Policy

Last updated: July 18, 2026

These Terms of Use ("Terms") govern access to and use of the PyneHub website, developer panel, on-device client, and app catalog (together, the "Service"). By using the Service or uploading apps, you agree to these Terms and to the Acceptable Use Policy (AUP) in Part B. If you do not agree, do not use the Service.

PyneHub is a maintainer-controlled hub. The public may browse and view app source; only approved developers may publish.

Part A — Terms of Use

1. Accounts and eligibility

  • Developer accounts are granted only to approved developers who complete onboarding (email verification, 2FA, and acceptance of the Developer Agreement / CLA). See legal/DEVELOPER_ONBOARDING.md.
  • You are responsible for activity under your account and for keeping your credentials and 2FA secure. Notify us immediately of any compromise at [email protected].

2. License to platform code and to apps

  • PyneHub platform code is licensed under Apache-2.0 (see /LICENSE).
  • Apps published on PyneHub are licensed by their respective developers. Developers must ensure each app carries a clear, compatible open-source license and that they have the right to publish it.

3. Developer responsibilities

By publishing, you represent and warrant that you own or have the rights to the app, that it does not infringe third-party rights, that it complies with applicable law (including export controls and sanctions), and that it is not malware and contains no intentionally harmful or deceptive functionality. See the Developer Agreement / CLA for the full representations.

4. Logging and monitoring

You acknowledge and consent that the Service logs operational metadata (timestamps, file identifiers, file hashes, IP addresses, device identifiers, and actions) for security, integrity, audit, and abuse-prevention purposes, as described in legal/PRIVACY_POLICY.md.

5. Availability; no warranty

The Service is provided "AS IS" and "AS AVAILABLE" without warranties of any kind, to the maximum extent permitted by law. We do not warrant that the Service or any app will be uninterrupted, secure, or error-free.

6. Limitation of liability

To the maximum extent permitted by law, PyneHub and its maintainers will not be liable for indirect, incidental, special, consequential, or punitive damages, or for loss of data, profits, or goodwill, arising from use of the Service or any app obtained through it.

7. Indemnification

You agree to indemnify and hold harmless PyneHub and its maintainers from claims, damages, and expenses arising out of apps you publish or your breach of these Terms (see the Developer Agreement / CLA for details).

8. Suspension and termination

We may suspend or terminate accounts or remove apps that violate these Terms, the AUP, or applicable law, including on an emergency basis (see Part B).

9. Governing law

The governing law and venue will be specified by PyneHub's operators upon legal review. (Operators: set jurisdiction; see Follow-up actions.)

10. Changes

We may update these Terms; material changes will be dated and, where appropriate, notified to developers by email.

Part B — Acceptable Use Policy (AUP)

You must not use the Service to upload, publish, distribute, or facilitate:

  1. Malware or harmful code — viruses, trojans, ransomware, spyware, cryptominers, backdoors, or code that damages, disables, or gains unauthorized access to devices or data.
  2. Deceptive or fraudulent apps — impersonation, phishing, hidden data exfiltration, or misrepresenting an app's functionality or publisher.
  3. Rights-infringing content — apps that infringe copyright, trademark, patent, trade secret, or privacy/publicity rights.
  4. Illegal content or activity — anything unlawful in the applicable jurisdiction, including content that violates export controls or sanctions.
  5. Privacy violations — collecting or transmitting personal data without a lawful basis and clear disclosure.
  6. Abuse of the platform — attempts to bypass upload gates, scanning, rate limits, RBAC, or audit logging; probing or attacking the Service.

Violations may result in immediate removal, account suspension, and referral to authorities where appropriate.

Part C — Takedown & Emergency Removal Procedure

PyneHub uses a DMCA-style notice-and-takedown workflow for alleged infringement and an expedited path for malware/security incidents.

C.1 Emergency removal (malware / active security incident)

If an app is reasonably suspected to be malware or to pose an active security risk, PyneHub may remove or quarantine it immediately, before or without prior notice, to protect users and devices. We will:

  1. Quarantine the artifact (make it non-downloadable) and flag its version.
  2. Record the file hash(es), timestamps, and reason in the audit log.
  3. Notify affected developers and, where warranted, users (see legal/INCIDENT_RESPONSE.md for templates and timelines).
  4. Preserve evidence per the incident-response retention rules. Restoration requires developer remediation and maintainer re-review.

C.2 Copyright / IP takedown (DMCA-style)

To report allegedly infringing content, send a notice to [email protected] with the subject "Takedown Request" including:

  1. Your contact information (name, email, and, if applicable, organization).
  2. Identification of the copyrighted or protected work claimed to be infringed.
  3. Identification of the app/version/URL on PyneHub you want removed, with enough detail for us to locate it (app id, version, file hash if known).
  4. A statement that you have a good-faith belief the use is not authorized by the rights holder, its agent, or the law.
  5. A statement, under penalty of perjury, that the information is accurate and that you are the rights holder or authorized to act on their behalf.
  6. Your physical or electronic signature.

Our process:

  1. We acknowledge receipt and assign a ticket.
  2. We review; if the notice is valid, we disable access to the app/version and notify the developer with a copy of the notice.
  3. Counter-notice: the developer may respond with a counter-notice containing their contact info, identification of the removed material, a statement under penalty of perjury of good-faith belief the removal was a mistake or misidentification, and consent to jurisdiction/service.
  4. If we receive a valid counter-notice and the complainant does not pursue legal action within the period required by applicable law, we may restore the material.
  5. Repeat infringers: accounts with repeated valid infringement notices will be suspended or terminated.

All takedown actions, notices, and counter-notices are recorded in the audit log and retained per legal/pynehub.config.yaml.

Contact

General/legal/takedown: [email protected] Security/emergency: [email protected]