Trust and safety
Contact FreeMinecraftMods
Use this page for correction requests, copyright concerns, creator-credit fixes, broken links, and general website questions.
Contact
Email: contact@freeminecraftmods.com
Include the project title, official source URL, what needs to be changed, and proof of ownership if you are requesting a creator-credit or removal update.
Creator credit corrections
If a listing credits the wrong author, send the official project page or profile page and the corrected author name. The goal is to credit creators clearly and link players back to official sources.
Support scope
What to include in a useful message
FreeMinecraftMods can correct project metadata, remove unsafe or disputed media, update source links, review creator-credit problems, and answer questions about site policies. The site cannot provide official support for a third-party mod, pack, server, launcher, or platform, so messages should focus on the page or policy issue that FreeMinecraftMods can actually fix.
For a project correction, include the FreeMinecraftMods page URL, the official source URL, the exact field that appears wrong, and the replacement value you believe is correct. For an unsafe-link report, include the page URL, the link label, and what happened after opening it. For creator ownership, include a public creator profile, project page, or proof code that can be verified without asking for private account credentials.
Response priorities
- Unsafe redirects, malware-risk reports, and copied project pages should be reviewed first.
- Wrong creator credit, broken official links, and outdated compatibility details should be corrected when the source evidence is clear.
- Privacy, data deletion, and account questions should identify the email address or account involved, but should not include passwords, private keys, or launcher credentials.
- General feedback is welcome, especially when it points to a page that feels unclear, thin, duplicated, or hard to verify.
Related pages: corrections policy, DMCA and copyright, privacy policy, and project review method.
Last reviewed: July 5, 2026.
Routing guide
Where each kind of request should go
Use one email thread per issue when possible. A broken source link and a creator ownership dispute may involve the same page, but they often need different evidence. Keeping the request focused makes it easier to confirm the source, update the listing, and avoid accidentally changing the wrong project.
For low-value or duplicated content reports, include the page that feels weak and explain what would make it more useful: missing comparison notes, outdated version context, unclear source attribution, absent screenshots, or a page that should be merged into a stronger hub. These reports are treated as quality feedback, not as ordinary votes for or against a project.
For account questions, identify the account email and the page where the issue occurred. For privacy questions, describe the data choice or deletion request without sending passwords, authentication codes, private keys, private financial details, or launcher account credentials. For Minecraft gameplay support, use the relevant guide page first; if the guide is missing an important situation, send that as editorial feedback.
Examples of useful page-specific reports include a mod page that links to the wrong loader file, a creator profile that combines two unrelated authors, a category page that lacks enough selection guidance, a guide that omits a common error message, or a project visibility label that is unclear. Those details help the site fix the exact page instead of guessing from a broad complaint.