Content disclosures give you, as a creator, the ability to keep users informed of important context about your project and ensure the health and safety of your users and our community.

Our goal is to allow creators to be transparent with their users, and we expect that creators engage with this system, eager to be honest and up-front regarding their project's content. Disclosures may also be required by our moderation team.

This list provides general guidelines regarding the expectations and intended purpose of each content disclosure.

We ask that creators properly disclose when generative AI has contributed a substantial role in the creation or publication of a project's content.

Refer to our article on AI usage for more information on our regulations.

Select this option when content utilizes a significant amount of AI-generated code.

Not sure if this applies to your content? Refer to our regulations on AI-generated content.

If a project distributes any AI-generated or AI-assisted assets such as textures, models, or logos, this must be disclosed.

If a project contains text generated with AI, such as dialogue, names and descriptions of content, or translations, this must be disclosed.

If a project page's contents, such as the description, summary, or changelogs, are AI-generated, this must also be disclosed.

This does not apply to using generative AI for spelling or grammar checking, or using machine translations that utilize some LLM features. For text that is generated on-the-fly, such as chat integrations or live translations, refer to the next disclosure type.

If a project depends on generative AI to function, such as through connecting to a local or online LLM or TTI model, this must be disclosed.

If a project concept is designed or primarily inspired by generative AI's output, this should also be disclosed.
​

Note that if a project is fully AI-generated, Modrinth may reject it or disable its availability through search.

If a project contains advertisements, sponsorships, or promotions of other works, this must be disclosed. This may include sponsored chat messages, non-relevant server list additions, main menu buttons, etc.

Advertisements that are relevant to the content and unobtrusive, such as links to a Modrinth profile, do not require disclosure. Similarly, advertisements that are unobtrusive and pro bono or otherwise have no monetary value, such as requests to support charitable causes, do not require disclosure.

This disclosure does not pertain to advertisements in a project's page, such as sponsored banners in the description.

If a project contains features that are unlocked only through spending real-world money, this must be disclosed. This may include unlockable content, locked features that require a paid license, cosmetics, or ranks.

Providing donors with off-platform alternate content such as early access builds or higher-resolution content does not require disclosure.

​Note that we expect all content advertised on a project's page to be available to users. Projects that are locked entirely behind a paywall are not permitted on Modrinth.

If a project collects usage data, or sends data to third parties, this behavior must be disclosed. This may include usage metrics like the Minecraft versions being used with the content, the hardware of the machine running the content, or the player count of servers with the content installed.

We expect that creators make it clear who has access to collected telemetry, and whether or not the data is anonymized when relevant.

Transitive data that is not stored in any way does not need to be disclosed.

Data transfers that are expected in a project's functionality, such as registries sent to Minecraft servers, user configuration synchronization, or other features that would be made obvious through the existence of the project, does not need to be disclosed.

Transferring superfluous data not required for the functionality of a project, such as user or instance information (or "metrics"), should be disclosed, even if its creator does not have direct access to the stored data.

Data sent to third parties that store or collect data in a way that is not obvious, not selected by the user, or is otherwise opaque to users, must be disclosed. When disclosing that data is collected by third parties, it is recommended to provide a link to the relevant service's own usage or privacy policy.

Creators may provide a list of data stored and collected, or link to their project's privacy policy or similar disclosure document.

The consent model tells users how a project's telemetry functions.

This option provides a simple way to credit and provide attribution for upstream content.

Creators must disclose when a project uses the work of others, if a project is a fork of an existing project, when the included content requires a public display of attribution by license or usage rights, or in any other context where proper credit may be required by Modrinth's Content Rules.

If a project is inspired by other works but does not derive any code, assets, etc. from the original work, this should not be disclosed.

If a project is an add-on to a different project, or any derived code or assets included are a natural consequence of compatibility or interoperability with a different project, this should not be disclosed. Instead, the project's required or optional dependencies should be correctly specified when creating new versions.

If the inclusion of external work is relatively minor, in-content attributions such as class header comments or file signatures would be more appropriate.

If a project can reasonably be expected to display content that may be dangerous or uncomfortable to certain individuals, this must be disclosed.

This disclosure must be used only where appropriate. A general rule of thumb is that creators should warn users if their project contains flashing images or patterns reasonably expected to take up more than 25% of the screen, oscillating faster than 3 times per second, or lasting for longer than 5 seconds.

This does not apply to unanticipated interactions or unintentional sequences such as bugs. However, we do recommend attempting to reduce or avoid these if possible.

If a project interacts with the user's system outside of the context of the game, especially in unpredictable or unanticipated ways, this must be disclosed.

This may include the unexpected reading, writing, or modification of files on the user's system, such as changing the desktop background, shutting down the system, connecting to other programs, or accessing a microphone or camera.

This does not include saving screenshots to alternative locations, reading or modifying configuration files, or any functionality that is naturally expected from the intended behavior of a project.

Creators can mark their project as archived if they no longer plan to update or maintain the project. Archived projects remain discoverable through search and can still be downloaded.

If disclosed content is only relevant to some but not all versions of a project, such as if its content has since changed, creators should focus on ensuring that disclosures are relevant to the latest or most played version of your project.

Important safety disclosures such as external system interactions, photosensitivity, or telemetry should be present on a project if any distributed version contains said functionality. Similarly, if any distributed version is derived from another project that requires prominent attribution, the disclosure must remain.

In any of these cases, creators are encouraged to mention which versions these disclosures apply to.

If a project is a fork of another project, any content contributed by the fork or the original project should be disclosed unless said content has been removed from the fork.

For example, a source project that contains telemetry should have that disclosure carried over to its forks, unless that telemetry has been removed.
​
For more information on disclosing the usage of generative AI when creating a fork, please refer to our regulations on AI usage.

Modpacks are not expected to copy over the disclosures of included content. It is the responsibility of creators to properly disclose the content of their mods, resource packs, etc., rather than modpack authors.

However, modpacks should disclose relevant custom content that requires any of the above disclosures, such as self-developed mods or functionality provided by KubeJS scripts.

External content does not require a derivative work disclosure. Instead, attribution for external content should be specified through the project's permission settings.

Any information that can be accurately and appropriately provided in a content disclosure must be added to the appropriate disclosure.

If you've been publishing your content on Modrinth for a while (thank you), then you already know we've required similar disclosures in your project's description before the release of the content disclosures.

While creators are welcome to keep or add disclosure information to their project's description, we generally recommend avoiding doing so and encourage using content disclosures instead.

While we do hope to enable creators to safely publish the content they desire, all projects are still subject to Modrinth's Content Rules and the safety and fair use standards enforced by our content moderation team.

​
​