Acceptable Use Policy

Scope

These rules supplement the Terms of Service and govern accounts, Git pushes, uploads, APIs, automated jobs, webhooks, forum messages and downloads. They are intended to protect users and infrastructure while preserving lawful open-source work.

Prohibited uses

Do not use ArchForge to compromise systems without authorization; distribute credentials stolen from others; operate phishing, botnets, ransomware delivery, exploit-as-a-service or illicit marketplaces; threaten others; publish unlawful intimate images; distribute illegal material; or evade legal takedowns. Do not deliberately overwhelm the server, bypass quotas, scan internal services through webhooks or circumvent rate limits and permission checks. Do not upload content infringing third-party rights without a defense or license.

Legitimate code and research

Source code that could be dual-use is not automatically prohibited. Lawful proof-of-concept research, vulnerability writeups and educational security tools may be allowed, subject to context, applicable law and safe disclosure. Operators should distinguish discussion and defensive research from operational abuse. If unsure, request guidance through published contact channels before posting.

Resource usage and automation

Respect Git storage quotas, payload limits, API rate limits, repository permission settings and the acceptable workload of the Pterodactyl host. Webhook destinations must be public HTTPS endpoints and must not be configured to target loopback, private networks or cloud metadata services. Do not use shared infrastructure for cryptocurrency mining or denial-of-service traffic. Additional limits may change with advance notice where appropriate.

Enforcement and review

Potential violations may be investigated using appropriately restricted records. Restrictions should be necessary, documented and proportionate; false positives can be challenged using the published complaint pathway where applicable. Illegal content complaints are handled through the Legal Notice and report form, while security vulnerabilities follow the Security Policy.

Changes and version history

This policy applies from its stated effective date once published. Material changes are dated and versioned. Earlier versions remain available to administrators for audit, and any notice or renewed agreement required by applicable law is handled separately. Questions and legally valid notices may be sent using the contact details in the Legal Notice.