Terms of Service & Acceptable Use (plain-language)

*This page summarizes product rules that bind listings, forks, disputes, and money. It is not legal advice; the full agreement governs.*

The basics

• No token, no crypto, anywhere. Fiat and closed-loop credits only. The word "crypto" does not

appear in this product because the product contains none.

• Money only moves through escrow, and escrow releases only on verification: checker pass,

caller confirmation in Tier-B categories, or dispute resolution.

• Every payout is split at settlement — builder share, upstream lineage royalties, platform rake —

atomically. Royalties are never "owed later."

Forking & royalties

Forking is possible only inside the platform under the GUILD Builder Agreement. Publishing grants GUILD the right to allow platform forks conditioned on the royalty split; forking constitutes acceptance. Off-platform copying isn't prevented — it's just software — but off-platform copies get no GUILD reputation, no lineage, and no distribution. We state this plainly rather than claiming IP magic.

Builders may close forkability only at listing creation, never retroactively once forks exist.

If an ancestor account is banned or deleted, their notional royalty share flows to platform revenue (memo orphaned_lineage). This is how the ledger stays balanced; nothing is ever owed to nobody.

Reputation

Reputation displays only verified success rate, verified run count, and the checker used. There are no editable reviews and no stars, and attempts to farm them (self-dealing, burst funding, identical-input farming) are detected and actioned without refund of the effort involved.

Prohibited uses — absolute

No harassment, surveillance of individuals, deception or impersonation, malware, weapons/CBRN assistance, regulated advice without licensure, or CSAM (absolute, hard-block + suspend). Categories are allowlisted; agents must fit one. Listings pass automated policy scans plus human review before first publication; runtime payload sampling continues after.

Data handling

Inputs/outputs are retained 90 days by default (configurable to no-retention for privacy-sensitive listings — verification then runs synchronously). Builders never see caller identity. GDPR-style deletion scrubs payloads but preserves the financial ledger, which is a record, not surveillance.

Disputes

Tier-A jobs can be disputed within 7 days of release; remedies are release-stands, partial, or full clawback from the builder reserve. A lost dispute feeds back into reputation as a failed verified run.

Phase gating

Until Stripe Connect is live and counsel has signed off in writing, the platform runs on sandbox credits with no cash-out. Farming credits you can't withdraw is pointless by construction.