Steam Generative AI Policy
Effective January 2026 ยท Applies to all games using AI-generated player-facing content
What the policy requires
Valve's policy mandates that any game with AI-generated content must clearly disclose it on the Steamworks store page before launch. The policy draws a hard distinction between two categories:
| Category | Definition | Example |
|---|---|---|
| Pre-Generated | AI was used to create assets during development; the output is fixed in the shipped game | Character portraits generated with Midjourney; background music composed with Suno |
| Live-Generated | AI generates content in real time during gameplay, specific to each session or player | Procedural dialogue via GPT; dynamic NPC faces |
Failure to disclose โ or incorrect categorisation โ results in Valve rejecting your store page submission or delisting your game after launch.
How OriginGuard satisfies Steam requirements
| Obligation | OriginGuard Output | Status |
|---|---|---|
| Disclose AI-generated player-facing content | steam_disclosure.disclosure_statement โ copy-paste ready text |
โ Covered |
| Distinguish Pre-Generated from Live-Generated content | category field enforced at point-of-export via VS Code extension |
โ Covered |
| Ensure disclosed content matches shipped assets | SHA-256 hash verification โ any modification is flagged as tampered | โ Covered |
| Block non-compliant assets from shipping | GitHub Actions build gate โ PR blocked if scan fails | โ Covered |
originguard scan in CI โ copy steam_disclosure.disclosure_statement to your Steamworks page. Done.
EU AI Act โ Article 50
Effective August 2, 2026 ยท Applies to all AI systems targeting EU users
What Article 50 requires
Article 50 of the EU AI Act imposes transparency obligations on deployers of AI systems. For game studios, this translates to four concrete requirements:
- AI-generated content must be labelled as such in a machine-readable format.
- The labels must be technically robust โ not easily removable by downstream processing.
- Deployers must retain documentation about AI systems used and the content generated.
- Documentation must be available for regulatory audit on request.
How OriginGuard satisfies Article 50
| Obligation | OriginGuard Output | Status |
|---|---|---|
| Machine-readable synthetic content labels | eu_ai_inventory.tools[] โ structured JSON per tool per category |
โ Covered |
| Technically robust labelling (tamper-evident) | SHA-256 hash in .origin sidecar; any asset modification invalidates the tag |
โ Covered |
| Retain documentation for audit | Master_Disclosure.json uploaded as a CI artifact with 90-day retention |
โ Covered |
| Identify AI systems used | tool and category fields per asset in the provenance record |
โ Covered |
Master_Disclosure.json CI artifact. Every field maps directly to Article 50 requirements.
Full compliance coverage at a glance
| Regulatory Obligation | Regulation | OriginGuard Field |
|---|---|---|
| Disclose AI-generated player-facing content | Steam AI Policy | steam_disclosure.disclosure_statement |
| Distinguish Pre-Generated vs Live-Generated | Steam AI Policy | .origin.category |
| Hash-verified asset integrity | Both | .origin.sha256 |
| Machine-readable synthetic content mark | EU AI Act Art. 50 | eu_ai_inventory.tools[] |
| Retain documentation for regulatory audit | EU AI Act Art. 50 | Master_Disclosure.json CI artifact |
| Identify AI systems and tools used | EU AI Act Art. 50 | .origin.tool |
| Block non-compliant assets from shipping | Both (best practice) | GitHub Actions build gate |
| Internal audit trail with CRITICAL warnings | Both (best practice) | integrity_report |