Last updated: 2 May 2026 · Private beta. Use it well or lose access.
Don't do
Use fuggit to host malware, phishing kits, exploit dev for unauthorised targets, illegal content, or content violating others' IP.
Try to bypass authentication, scope checks, rate limits, or main-protection rules.
Probe for vulnerabilities without coordinating with the operator first. Use the security disclosure path in the privacy policy.
Use fuggit to attack other systems (denial-of-service staging, credential brute-forcing, etc.).
Resell access, mirror the service, or operate fuggit as a platform for unrelated third parties without prior agreement.
Push so much data that you visibly degrade service for other private-beta users (single repos > 5 GB, sustained CI volume > 100 jobs/hr, etc.). If you have a legitimate large workload, talk to us first.
Tell us when something breaks. Tell us when something is missing.
Build marketplace apps. Use the scoped-token API.
Enforcement
Violations may result in account suspension, content removal, or termination, with reasonable notice except for security incidents or court orders. Appeals to matt@jupitersoft.net.