AniBridge Legal Notice
Version: 2026-03-23
AniBridge is open source software. This notice explains the project's legal boundaries, notice-routing expectations, and baseline responsibilities for maintainers, contributors, redistributors, operators, and users.
This document does not create immunity from takedown procedures, platform enforcement, civil claims, or mandatory law.
Related documents:
1. Purpose and Scope
This notice applies to repository-controlled materials and project-controlled distributions, including source code, documentation, release artifacts, and official project assets maintained in the AniBridge repository.
It does not govern the conduct of third-party services, third-party hosting providers, third-party client applications, or independently operated deployments except to describe the project's boundaries and the operator responsibilities that remain outside maintainer control.
2. Relationship to the Software License
AniBridge is distributed under the repository's stated software license, currently BSD 3-Clause unless a specific component states otherwise.
This notice is a policy and boundary-setting document. It does not amend, replace, narrow, or expand the software license grants for the project code, except where mandatory law requires a different result. If there is a conflict between this notice and the applicable software license on questions of copying, modification, or redistribution of repository code, the license controls.
3. Non-Affiliation and No Endorsement
AniBridge is not affiliated with, endorsed by, sponsored by, or operated by any third-party portal, hoster, streaming platform, licensor, or rights holder that may be referenced in documentation, configuration examples, or user workflows.
Third-party names, marks, domains, and product references are used only for identification, compatibility description, or operator-supplied configuration context. All rights in those names and marks remain with their respective owners.
4. Technical Characterization and Limits
AniBridge is software that provides compatibility and automation surfaces, including Torznab-style and qBittorrent-compatible APIs, metadata handling, internal routing descriptors, and optional STRM or proxy-assisted workflows.
That technical role does not itself determine legality. Actual legal exposure depends on the operator's deployment, the source and status of the material being accessed, applicable terms and access controls, and the law of the relevant jurisdiction.
AniBridge does not by itself:
- grant rights in any work;
- represent that any referenced content is licensed or authorized;
- become the operator of third-party catalogs, hosters, delivery networks, or client applications;
- convert technical reachability into legal authorization.
Technical reachability is not legal authorization.
5. Separation of Control
AniBridge maintainers control only repository-contained materials and the software behavior implemented in the AniBridge codebase and official project artifacts.
AniBridge maintainers do not control:
- third-party portals, hosters, CDNs, or other upstream infrastructure;
- the presence, legality, availability, or provenance of third-party media;
- user or operator configuration, credentials, cookies, tokens, or routing;
- user-run deployments, exposed endpoints, retention settings, or downstream integrations;
- third-party client behavior after the software is deployed.
Complaints about third-party hosted media, third-party stream delivery, or third-party catalog operation must be directed to the operator that controls the relevant service or hosting layer, not to AniBridge maintainers, unless the complaint concerns repository-contained material.
6. Operator and User Responsibilities
Users and operators are solely responsible for lawful deployment, configuration, integration, access behavior, storage, disclosure, and ongoing operation.
That responsibility includes assessing and complying with, as applicable:
- copyright and neighboring-rights law;
- anti-circumvention, DRM, TPM, or access-control rules;
- computer misuse, unauthorized-access, and anti-automation restrictions;
- contract terms, including platform terms of service and usage policies;
- privacy, data-protection, retention, security, export-control, and jurisdiction-specific requirements.
The existence of an adapter, API shim, internal routing descriptor, STRM file, or proxy workflow does not reduce those obligations.
7. Prohibited Uses and Unsupported Deployment Patterns
AniBridge must not be used to support conduct that is unlawful or unauthorized under the governing facts and law, including use intended to:
- infringe copyright or related rights;
- bypass authentication, payment restrictions, geo-restrictions, or other access controls without authorization;
- circumvent DRM, TPMs, or similar technical protection measures, or traffic in tools or materials primarily intended for that purpose;
- operate large-scale unlawful extraction, replication, redistribution, or re-publication workflows;
- expose or share secrets, session material, decryption material, or other credentials that the operator is not entitled to use or disclose.
This section does not legalize conduct outside these examples. No disclaimer can legalize unlawful conduct or override mandatory law.
8. Rights-Holder Notices and Repository Scope
AniBridge maintainers can review repository-contained materials such as source code, documentation, images, and other project assets. They cannot remove or disable third-party hosted media or third-party services they do not control.
If a complaint concerns repository-contained materials, use the process described in Rights-Holder Notice.
If a complaint concerns GitHub-hosted repository content, GitHub's own legal and platform processes may apply independently of this document. This notice does not prevent a claimant from using GitHub's reporting channels, and maintainers cannot promise any particular platform outcome.
9. Logs, Metadata, and Operational Data
AniBridge may process or emit operational data such as request metadata, URLs, file paths, provider identifiers, diagnostic logs, job history, and integration state. Depending on deployment context, that information may be personal data, confidential business information, or legally sensitive operational data.
Users and operators are responsible for lawful collection, minimization, retention, access control, disclosure, redaction, and deletion of such data. Before sharing logs or diagnostics, review them for credentials, tokens, URLs, and other sensitive information.
10. Contributors and Redistributors
Contributors may submit only material they are entitled to contribute. Redistributors must preserve the applicable software license notices and must not misrepresent AniBridge as affiliated with or endorsed by third parties.
Contributor expectations for provenance, prohibited submissions, and remediation are stated in Contributor IP and Submission Rules.
11. Warranty and Liability
AniBridge is provided under the warranty and liability framework stated in the applicable software license. Except as required by law, the project is provided on an "as is" basis without additional warranty as to legality, fitness, availability, accuracy, non-infringement, or suitability for any operator's use case.
Maintainership of the repository does not create responsibility for third-party services, user deployments, user configuration choices, or claims arising from operator conduct. Nothing in this notice creates any obligation for the maintainers to defend, indemnify, or insure users or operators against such claims.
12. No Legal Advice; No Override of Law
Nothing in the repository, documentation, issues, discussions, or community channels is legal advice. Obtain advice from qualified counsel for any use case that may implicate copyright, anti-circumvention, contract, privacy, or cross-border compliance issues.
No disclaimer, policy page, or repository notice can legalize unlawful conduct, override mandatory law, or guarantee protection from enforcement, takedown, or litigation.