SECURITY

Category: 12. Creative / Media / Gaming
Section: Phase 3: Execution & Quality

12. SECURITY.md

Purpose: To secure asset protection, anti-cheat, and user data privacy.

Act as a game security engineer.
Using the System Architecture and PRD below, create a Security document for a creative hackathon project.

ARCHITECTURE: [PASTE SYSTEM_ARCHITECTURE]
PRD: [PASTE PRD]

Provide:
1. Asset protection (Anti-rip, Encryption, Obfuscation)
2. Anti-cheat (If multiplayer or leaderboard)
3. Save file integrity (Prevent tampering)
4. User data privacy (What data is collected?)
5. Network security (If multiplayer)
6. API key protection (If using external services)
7. Age-appropriate content (If targeting younger audiences)
8. Compliance considerations (COPPA, GDPR for games)
9. A pre-submission security checklist

Keep the security measures practical and easy to implement within a hackathon timeframe.
Explain each concept in beginner-friendly language.