DMCA and Rights-Holder Contact

This page is for rights holders and representatives who believe that repository-controlled material in AniBridge should be reviewed, revised, or removed.

If practicable, contact the project first for repository-specific complaints:

• Email: dmca@zacklack.de

1. What This Contact Route Covers

This contact route is intended for complaints about repository-controlled materials, including:

• source code;
• documentation;
• images and repository assets;
• official release materials published from this repository.

It is not a takedown route for third-party hosted media, third-party streaming services, or user-run deployments outside repository control.

2. Preferred Order of Contact

Where the concern is about repository-controlled material, claimants are encouraged to email the project first.

That project-facing contact is voluntary and practical, not mandatory. It does not waive any rights, extend any statutory or contractual deadline, or preclude a claimant from using GitHub's own legal channels where appropriate. Where platform action is sought, a claimant may also wish to consider the notice-and-takedown framework commonly associated with 17 U.S.C. § 512.

3. What to Include

Please include enough detail to allow a prompt and responsible review. If a claimant intends a submission to function as a formal DMCA notice, the submission should contain the information ordinarily associated with 17 U.S.C. § 512(c)(3).

In practical terms, please include:

• your name and contact information;
• the capacity in which you are acting;
• the specific repository material at issue, with exact URLs, file paths, commit SHAs, tags, or release references where possible;
• identification of the allegedly infringed work or right;
• a concise explanation of the issue;
• the action requested;
• any urgency, court order, or other legal-process context that matters.

Do not send passwords, session cookies, tokens, or unrelated personal data unless strictly necessary.

4. What Happens Next

For repository-controlled materials, maintainers may:

• review the identified material;
• request clarification;
• revise, remove, or disable repository-contained material;
• refer the claimant to GitHub's own process where platform action is the correct path.

Any review is undertaken without admission, waiver, or concession as to infringement, authorization, fair use, jurisdiction, or remedy. Maintainers cannot promise a specific timetable or outcome.

5. GitHub Process Still Exists

GitHub controls GitHub-hosted repository access. A direct notice to the project does not replace GitHub's own DMCA, legal review, takedown, counter notice, or reinstatement procedures.

If the complaint requires GitHub platform action, GitHub's own process may still be necessary and may operate independently of any direct contact with the project.

Where GitHub removes or disables access to repository material through its own process, GitHub may also apply its own counter-notice and reinstatement procedures under the platform rules and the applicable statutory framework, including 17 U.S.C. § 512(g).

6. Scope Reminder

AniBridge maintainers cannot remove or disable third-party hosted media or third-party services they do not control. Complaints about those systems should be sent to the operator of the relevant platform or host.

For more detail on repository scope and complaint routing, see the Rights-Holder Notice and the Legal Notice.

7. Reference Points

This page is written with reference to:

• 17 U.S.C. § 512, including § 512(c)(3) and § 512(g); and
• GitHub's published DMCA takedown and content-removal guidance.