Leahnaya/hackdex-website
1
0
Fork 0
mirror of https://github.com/Hackdex-App/hackdex-website.git synced 2026-10-20 23:02:33 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

docs: correct AI disclosure requirements and creator notice (#97)

Browse Source
This commit is contained in:
Jared Schoeny
2026-09-26 11:46:58 -06:00
committed by GitHub
parent 462f82887d
commit 8c28123801
3 changed files with 15 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/announcements/terms-1.1.0-ai-correction.json Normal file
View File

@@ -0,0 +1,6 @@
{
"id": "terms-1-1-0-ai-disclosure-correction",
"ready": false,
"title": "Correction: Hackdex AI disclosure requirements",
"message": "Hi,\n\nWe need to correct two details in our previous email about the updated Hackdex Terms of Service.\n\nAI use in coding must also be disclosed. Our earlier email said general programming was exempt. That exemption has been removed. Disclosure covers AI-generated or AI-modified content and code included in your hack or its Hackdex page, including work you edited afterward or received from contributors.\n\nDisclosures will use a dedicated AI disclosure form instead of a section in your hack's description. The form will let you declare the extent of AI use and will be available by October 3, 2026. Every creator will need to complete it, even if no AI was used. If you already added a disclosure to your description, please complete the form once it is available.\n\nAI use remains allowed with disclosure so players can make an informed choice. Credits still belong in a Credits section of your hack's description or on a publicly accessible credits page linked from that section.\n\nThe dates are unchanged. The updated Terms take effect on October 3, 2026. Hacks submitted before that date have until November 2, 2026 to meet the credits and AI disclosure requirements. New submissions must meet those requirements from October 3.\n\nSorry for the confusion caused by the earlier email. We've corrected the Terms and FAQ to reflect these requirements.\n\nTerms: https://www.hackdex.app/terms\nFAQ: https://www.hackdex.app/faq\nYour hacks: https://www.hackdex.app/dashboard"
}

10
docs/legal/TERMS.md
View File

@@ -58,15 +58,13 @@ Creators must:
Every hack must have a clearly labeled Credits section on its public Hackdex page. This section must name the hack's contributors and credit the creators or sources of reused assets and code, or link to a complete, publicly accessible credits page. Creators must keep credits accurate as the hack is updated and comply with any attribution requirements attached to material they use. Credits do not replace permission or other rights required to use that material.
### AI-generated content disclosure
### AI disclosure
Creators must clearly disclose AI-generated content included in their hack or its public Hackdex page. The disclosure must appear in a labeled section of the hack's description, identify the types of content affected, and remain accurate as the hack or page is updated. This requirement applies to content generated in whole or in part by AI, including generated content that is later edited or supplied by another contributor.
Creators must complete Hackdex's AI disclosure form for each hack, accurately declaring the extent of AI use, including when no AI was used. Keep the disclosure accurate as the hack or its public Hackdex page is updated. A disclosure in the hack's description does not replace completing the form.
Content requiring disclosure includes graphics, music, sound effects, story, dialogue, translations, and event scripts. Event scripts include instructions that control NPC actions, cutscenes, dialogue, item interactions, and other in-game events, even when those scripts contain no generated dialogue.
Disclosure is required for content and code generated or modified in whole or in part with AI and included in the hack or its public page. This includes graphics, music, sound effects, writing, translations, event scripts, and general programming, even when later edited or supplied by another contributor. Disclosure of AI use for brainstorming and unused experiments is optional when no AI-generated or AI-modified content or code is included in the hack or its page.
AI assistance with general programming, such as engine changes, bug fixes, development tools, or implementing game systems, does not require disclosure. This exception does not cover AI-generated event scripts or other content listed above. Brainstorming and experiments that do not result in AI-generated content being included in the hack or its page do not require disclosure.
Disclosing AI use does not exempt content from the credits requirement, other provisions of these Terms, or third-party rights.
Disclosing AI use does not exempt content or code from the credits requirement, other provisions of these Terms, or third-party rights.
## 7. Content Moderation

16
src/app/faq/entries.md
View File

@@ -39,7 +39,7 @@ Use the [Discover page](/discover) to search for hacks or filter by tags, base R
Download activity is the only input to popularity and trending rankings. Placement does not represent a staff recommendation.
### Does Hackdex allow AI-generated content?
Yes, with disclosure. Creators must identify AI-generated content in a labeled section of their hack's description so you can decide whether you want to play it. This includes graphics, music, dialogue, and event scripts. AI assistance with general programming does not require disclosure.
Yes, with disclosure. Creators must disclose AI use in both content and code through Hackdex's AI disclosure form. Their disclosure appears on the hack's page to help you decide whether you want to play it.
We believe a blanket ban can encourage creators to hide AI use. Requiring disclosure gives creators room to be honest and helps players make an informed choice. Disclosed content must still follow our credits and content rules. See [what creators need to disclose](#ai-disclosure) for details.
@@ -124,23 +124,17 @@ Yes. Every hack must have a clearly labeled Credits section in its Hackdex descr
Keep your credits up to date and follow any attribution requirements for material you use. Giving credit does not replace permission to use someone else's work. This requirement is part of [Section 6 of the Terms of Service](/terms#6-creator-responsibilities).
### What AI use do I need to disclose? {#ai-disclosure}
Add a clearly labeled "AI disclosure" section to your hack's description if the hack or its Hackdex page includes AI-generated content. State which types of content were generated, such as graphics, music, sound effects, story, dialogue, translations, or event scripts. This includes content generated in part by AI, content you edited after generation, and generated content supplied by contributors.
Complete Hackdex's AI disclosure form for each hack, even if you have no AI use to declare. Follow the guidance in the form to describe the extent of AI use, and keep your answers up to date. You do not need an AI disclosure section in your description, but a description note does not replace the form.
Event scripting counts even though it is written as code. For example, an AI-generated event script that makes an NPC walk toward the player, displays an exclamation mark, and gives an item requires disclosure, even if it contains no generated dialogue.
Disclose content and code generated or modified with AI that is included in your hack or its Hackdex page. This includes graphics, music, writing, translations, event scripts, and general programming, even a single bug fix. Count work you edited afterward or received from contributors.
AI assistance with general programming, such as engine changes, bug fixes, development tools, or implementing game systems, does not require disclosure. Brainstorming and unused experiments do not require disclosure when no generated content is included in the hack or its page.
A useful disclosure names the affected content. For example:
> AI was used to generate the title screen artwork and event scripts for some NPC interactions.
Keep this section accurate as you update your hack or page. A disclosure does not exempt the content from our credits or content rules. See [Section 6 of the Terms of Service](/terms#6-creator-responsibilities) for the full requirement.
Disclosure of AI use for brainstorming and unused experiments is optional when no AI-generated or AI-modified content or code is included in the hack or its page. Disclosure does not replace credits or exempt your hack from our content rules. See [Section 6 of the Terms of Service](/terms#6-creator-responsibilities) for the full requirement.
### Who retains ownership of submitted hacks?
Creators retain ownership of their work. Hackdex serves as a distribution and discovery platform. Specific rights and responsibilities are outlined in the Terms of Service available on the platform.
### Are there content guidelines for submissions? {#content-guidelines}
Yes. Submit Pokémon ROM hack patches that you have the right to share, include credits, and disclose AI-generated content as described above. Hacks are subject to approval before they become public, and must continue to follow the rules after approval.
Yes. Submit Pokémon ROM hack patches that you have the right to share, include credits, and disclose AI use through the dedicated form as described above. Hacks are subject to approval before they become public, and must continue to follow the rules after approval.
We prohibit targeted harassment, threats, derogatory attacks against real people or groups, hate speech, and discriminatory abuse. This includes dehumanizing people or promoting hatred, discrimination, or violence based on characteristics such as race, ethnicity, nationality, religion, disability, sex, sexual orientation, or gender identity. These rules cover content inside the hack as well as its title, description, screenshots, cover images, and other page material.