Developers are responsible for ensuring that their games, content, and data practices comply with applicable laws and the Game License & Upload Agreement.
Before submitting a game to the Kongregate platform, developers should review the following checklist to help ensure that their game and related materials comply with the Game License & Upload Agreement, the Data Processing Addendum (DPA), and the Developer Content Standards.
This checklist is intended to help developers prepare their game for distribution and reduce the risk of legal or compliance issues after publication.
Technical Submission checklist
Please review these technical notes for guidance on:
- if you plan to use Kongregate's virtual goods API (Kreds)
- authentication guidance (game correctly identifies a user, hacking protection)
- use of Kongregate's Statistics
- guest landing page
Intellectual Property and Asset Rights
Confirm that you have the necessary rights to all content included in your game.
This includes:
artwork, sprites, textures, and visual assets
music, sound effects, and audio files
fonts and UI assets
code libraries and development tools
third-party assets obtained from marketplaces
assets generated using AI tools
You should verify that:
the asset license allows commercial use
the license allows distribution within a game
any required attribution is provided
Developers are responsible for ensuring they have the necessary rights to distribute their game and all included content.
Suggested reading:
STANDARDS | Developer Content Standards
ASSETS | How can I safely use third-party assets (art, music, code) in my game?
ASSETS | What license types apply to game assets?
CONTENT | What content is allowed on Kongregate?
PROHIBITED | What content is prohibited on Kongregate?
AGE RATING | Are there age restrictions for games submitted to Kongregate?
PRIVACY | Who is responsible for complying with privacy laws?
DATA | What personal data responsibilities do I have as a developer?
NOTICES | As a Developer, what should I do if I receive a DMCA notice or regulatory request?
SUMMARY | Plain English summary of the Game License & Upload Agreement
Age Suitability and Game Description
The Kongregate platform is intended for players aged 13 and older.
Developers should ensure that:
their game is appropriate for players aged 13+ or older
the game description on Kongregate includes a clear age suitability guideline (for example, 13+, 16+, or 18+)
the age guidance is determined using a recognized rating reference where possible
Developers may wish to consult publicly available rating guidance such as those used by major game rating organizations when determining an appropriate age category.
Suggested reading:
AGE RATING | Are there age restrictions for games submitted to Kongregate?
Game Content and Platform Policies
Developers should confirm that their game complies with the Developer Content Standards, including rules regarding prohibited or restricted content.
Developers should review:
the game’s content and themes
player communication features
any user-generated or player-created content systems
Ensure the game does not include:
illegal content
copyright infringement
unauthorized use of trademarks or likenesses of any person
malware or malicious scripts
deceptive monetization practices
harmful or abusive material
any third-party advertising
outside login systems
non-Kongregate microtransaction systems
If your game includes IP or branding for which you have a formal license, you should include details of that license with your submission.
Suggested reading:
STANDARDS | Developer Content Standards
CONTENT | What content is allowed on Kongregate?
PROHIBITED | What content is prohibited on Kongregate?
CONTENT | Can content policies change?
STANDARDS | Developer Moderation & Enforcement Policy
Gameplay Stability
Before uploading verify that:
the game launches reliably
core gameplay systems work
purchases or monetization systems (if applicable) function correctly (note that only Kongregate monetization systems are allowed)
advertising systems (if applicable) function correctly (note that only Kongregate ad systems are allowed)
the game does not crash during normal play
Developers should be prepared to fix critical issues quickly if they arise after release.
Note that developers will automatically receive bug reports for their game by email from players, and are required to respond promptly to those emails and bugs.
Security
Your game should not:
collect unnecessary personal data
attempt to access unauthorized system resources
interfere with platform security
include hidden background processes
Security violations may result in removal from the platform.
Suggested reading:
STANDARDS | Developer Content Standards
STANDARDS | Developer Moderation & Enforcement Policy
SUMMARY | Plain English summary of the Game License & Upload Agreement
PRIVACY | Key Privacy Laws Game Developers Should Know
Player Data and Privacy
If your game collects analytics, telemetry, or player data, confirm that your data practices comply with applicable privacy laws:
provide a privacy policy in your game and also in your game description
collect only necessary information
secure player data appropriately
comply with applicable privacy laws
Developers should ensure that:
players receive appropriate privacy disclosures
personal data is processed lawfully
reasonable security measures are implemented
Where personal data is processed in connection with the Kongregate platform, the Data Processing Addendum (DPA) may apply.
Suggested reading:
PRIVACY | Key Privacy Laws Game Developers Should Know
PRIVACY | Who is responsible for complying with privacy laws?
DATA | What personal data responsibilities do I have as a developer?
CONTRACT | What is the Data Processing Addendum (DPA)?
CONTRACT | When does the DPA apply?
PRIVACY | What privacy laws does Kongregate comply with?
DATA | Who is responsible for player data?
PRIVACY | How is personal data protected?
DATA | What should developers do if a data breach occurs?
CONTRACT | How does Kongregate support compliance with the DPA?
PRIVACY | Can developers use Platform Data outside the Kongregate platform?
AI Tools and AI-Generated Content
If you used AI tools during development, review the terms that apply to those tools.
Developers should confirm that:
the AI service allows commercial use of generated outputs
the developer has the right to distribute the generated content
use of the AI tool complies with its terms of service
Developers remain responsible for ensuring that AI-generated content included in their game does not infringe the rights of others.
Suggested reading:
DATA | AI & Data Use – Developer Summary
AI | How can I safely use AI in my game?
Gameplay Systems Using AI
If your game includes AI-driven systems or procedural content generation, review how these systems operate.
Developers should ensure that these systems:
comply with applicable laws
comply with the Developer Content Standards
do not generate unlawful or prohibited content
Suggested reading:
DATA | AI & Data Use – Developer Summary
AI | How can I safely use AI in my game?
Player-Generated Content
If your game allows players to create or share content, including AI-generated content, developers may wish to review how those systems operate.
Developers should consider whether their game includes:
clear player guidelines regarding acceptable content
moderation or filtering systems where appropriate
Suggested reading:
AI | Do I need to disclose when my game uses AI-generated content?
Game Submission Materials
Before submitting your game, confirm that your submission materials are accurate and complete.
Be ready to include:
-
the game description including:
age suitability guidance
a privacy policy link if applicable
a declaration about any use of AI, if applicable
developer contact information (a valid email account for the account and another for player bug reports and communications)
payment information (how can we pay you any monies due -i.e. PayPal, ACH)
tax information (how we report any monies we pay you to tax authorities i.e. W9 in US, W8-BEN if outside US, tax withholding information if necessary outside the US)
any other required disclosures
Ongoing Responsibilities
After publishing a game, developers should:
monitor bug reports
respond to critical issues
maintain compliance with platform policies
update games as necessary for compatibility
Maintaining a stable game ensures the best experience for players.
Comments
0 comments
Please sign in to leave a comment.