Acceptable Use Policy

• Secrets of any kind: credentials, API keys, tokens, private keys or connection strings.
• Personal data about any individual.
• Malware, backdoors, or code designed to exfiltrate data, damage systems or evade security controls.
• Third-party proprietary code you are not licensed to publish, including an employer’s code.
• Code whose attached licence is inaccurate or incompatible with its dependencies.
• Content that infringes intellectual-property, privacy or other rights, or that is otherwise unlawful.

• Retrieve your own snippets, or use additional/coordinated accounts to inflate usage, ranking or earnings (wash-trading and sybil farming).
• Fund credits with stolen or fraudulent payment methods, or use the payout system to launder funds.
• Bulk-scrape or export the catalogue to rebuild or resell a competing catalogue.
• Circumvent metering, or attempt to reconstruct locked bytes without paying for retrieval.
• Reverse-engineer, probe or overload the service, or run automated abuse against it.

We may reject or delist deposits, revoke snippets, reverse retrievals, forfeit affected credits and withdrawable balances, suspend or terminate accounts, and — where appropriate — report activity to payment networks or law-enforcement. Screening is partly automated (multi-model safety and commodity checks) and partly manual; neither is a guarantee, and enforcement does not create liability on our part.

If you find a snippet that violates this policy — unsafe code, a licence problem, or leaked secrets — report it from the console (corpus.report_issue) or contact us. Confirmed security issues can trigger revocation and notification of everyone who retrieved the affected card.