Rights-Holder Notice for Repository Materials

Version: 2026-03-23

This page explains how repository-specific complaints should be routed. It is limited to materials controlled in the AniBridge repository and official project-maintained distributions.

It does not cover third-party hosted media, third-party platforms, or external services that AniBridge does not own or operate.

1. What AniBridge Maintainers Can Review

AniBridge maintainers can review complaints about repository-contained materials, including:

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

AniBridge maintainers cannot remove or disable content hosted by third-party portals, hosters, CDNs, or independent deployments outside repository control.

2. Where Third-Party Media Complaints Belong

If your complaint concerns third-party hosted media, stream delivery, catalog entries, embedded players, or services not controlled by the AniBridge repository, direct your notice to the operator of the relevant platform or host.

Sending that kind of complaint to AniBridge maintainers will not remove the third-party content because the project does not control that infrastructure.

3. What to Include in a Repository-Specific Notice

A repository-specific notice should include enough detail to evaluate the request responsibly:

• your name and contact information;
• the capacity in which you are acting, including authority to act for the relevant rights holder where applicable;
• identification of the repository material at issue, preferably with exact URLs, file paths, tags, releases, or commit references;
• identification of the work, asset, or right allegedly infringed;
• a concise explanation of why the repository material should be removed, revised, or reviewed;
• the action requested;
• any facts relevant to urgency, sensitivity, or legal process.

Do not send passwords, raw secrets, session credentials, or unrelated personal data unless strictly necessary for the request.

4. Optional Pre-Notice Contact

For concerns relating to repository-contained material, the preferred initial contact route is dmca@zacklack.de. Where practicable, claimants are encouraged to contact that address before or alongside a platform notice so the repository material can be reviewed directly and, where appropriate, clarified, revised, removed, or otherwise addressed without avoidable escalation.

This request is intended as a practical, good-faith resolution path for repository-controlled material only. It is voluntary, not mandatory. It does not require any claimant to delay or forgo a platform notice, legal notice, or other available remedy, and it does not apply to third-party hosted media, third-party services, or infrastructure outside repository control.

5. GitHub Platform Process

GitHub controls access to GitHub-hosted repository content. If you are sending a formal copyright complaint about repository materials on GitHub, GitHub's own legal reporting channels may be the appropriate process and may operate independently of any direct notice to project maintainers.

A project-facing notice does not replace GitHub's own review, takedown, counter notice, or reinstatement procedures.

6. Project-Level Handling

For repository-controlled materials, maintainers may, in their discretion:

• review the identified material;
• request clarification or supporting information;
• revise, remove, or disable repository-contained material;
• refer the claimant to GitHub's platform process where that is the proper channel.

Maintainers cannot promise a specific timetable or outcome and cannot resolve complaints about infrastructure they do not control.