Acceptable Use Policy

Applies to buyer requests, uploads, messages, generated files, service catalog entries, support, operator/admin workflows, and API use.

Draft rules for allowed and prohibited requests, uploads, AI-generated outputs, abuse, security misuse, and regulated work limitations.

Allowed requests include websites, software prototypes, automations, DevOps plans, documentation, QA artifacts, infrastructure notes, AI integrations, and other lawful work that can be reviewed before use.

Buyers should provide only data they have rights to use and should remove unnecessary secrets or personal information.

Do not request malware, credential theft, deceptive impersonation, unlawful surveillance, harassment, exploit deployment, spam, evasion, privacy violations, or instructions intended to cause harm.

Do not upload secrets, private keys, regulated records, or confidential third-party content without authorization and approved production controls.

Unsafe uploads should be rejected or quarantined when scanning is required.

Operators should pause requests that involve illegal activity, credential theft, malware, harassment, privacy invasion, or regulated decisions without proper review.

Production upload and scanning controls remain a public production blocker.

Full production malware scanning is not operational.

Moderation tooling is basic and requires escalation workflow hardening.