Correction and removal policy
A practical, good-faith channel for authors and rights holders without creating unnecessary bureaucracy.
Last updated: September 29, 2026
What may be requested
A creator or rights holder may request correction of attribution or metadata, replacement of an obsolete or unauthorized source URL, or removal of a listing or link controlled by SM64CDPY.
SM64CDPY can change its own catalog and links, but cannot delete files, pages, or search results controlled by GitHub, GameBanana, Google Drive, Dropbox, Coop DX Mods, or another third party. Separate requests must be sent to the provider that controls them.
Information to include
Identify the content by title and exact catalog or source URL; describe the requested action; explain your relationship to the work; identify the right or factual error involved; and provide a reliable reply address.
Include a good-faith statement that the information supplied is accurate and that you are the creator, rights holder, or authorized representative. A typed full name or established creator identity is sufficient to begin review; additional proportionate verification may be requested when authorship is disputed.
Review process and timing
The project aims to acknowledge a complete request within 7 calendar days and reach an initial decision or request missing information within 14 calendar days. Complex disputes or third-party dependencies may take longer.
When a report is credible and urgent, a link or listing may be temporarily disabled while it is reviewed. The project may notify the credited author or source and share the minimum necessary claim information so they can respond.
Outcomes and repeat issues
Possible outcomes include correcting metadata, replacing a source, adding clarification, disabling a link, removing a listing, restoring it after clarification, or declining an unsupported request with a brief explanation.
Repeated, substantiated infringement or repeated submission of malicious files may lead to removal of related sources from the catalog. Fraudulent, abusive, or knowingly false notices may be rejected and documented for project security.
Not a formal statutory agent
This voluntary process is intended to resolve catalog issues quickly and does not claim to replace any mandatory legal notice procedure that applies in a particular country. The project does not represent that it is a registered DMCA agent.
If a law requires specific statements or formalities, include them in the email. Nothing here prevents a person from contacting the external host that actually stores the disputed file.