SERVICE TERMS
Terms of Service
These terms set the ground rules for using Hashnab's public search, account features, connected-provider tools, and API.
Effective August 26, 2026
1. What Hashnab provides
Hashnab is a search and indexing interface. It can combine film and television metadata with results from configured index sources. When you sign in and connect a supported debrid provider, Hashnab can also check provider availability, synchronize provider library metadata, or ask that provider to process a selected release.
Hashnab does not host the media files named by search results. A title, release, info hash, availability result, or provider action shown by Hashnab does not grant any right to obtain or use content.
2. Accounts, sessions, credentials, and API keys
You are responsible for activity performed through your account and for protecting your password, active sessions, Hashnab API keys, and third-party provider credentials. Do not publish or share those secrets. Revoke a key, session, or provider connection when you no longer trust it.
API keys can be limited by scope and expiry. A connected provider remains governed by the provider's own account rules, limits, and authorization terms.
3. Acceptable use
You may use Hashnab only in a lawful way. In particular, you must not:
- use the service to access content when you do not have the legal right to do so;
- interfere with the service, other users, authentication, or security controls;
- evade access controls, request limits, provider limits, or API-key scopes;
- submit malicious input or attempt unauthorized access to systems or account data; or
- use a third-party integration in violation of that provider's terms.
4. Metadata, indexes, and debrid providers
Hashnab depends on third-party sources and services. These may include metadata catalogs, public datasets, configured index sources, and debrid providers. Their terms and privacy practices apply separately. They can change, remove, reject, rate-limit, or misreport data without Hashnab controlling that decision.
When you ask Hashnab to check or send a release through a connected provider, you direct Hashnab to make the corresponding request to that provider using your connection.
5. API use
Use the API only through documented routes and with a key you are authorized to use. Respect the key's scopes, expiry, and rate limits. The live reference at /api reflects the running backend, but operations and response shapes may change as the service evolves.
6. Search results and service availability
Search and metadata records can be incomplete, stale, duplicated, or incorrect. Cached debrid availability can change after it is observed. Hashnab may be degraded or unavailable during maintenance, provider failures, capacity limits, or security work. Verify important details with the original source before relying on them.
7. Changes and access
These terms may be updated when the service or its integrations change. The effective date at the top identifies this version. Access may be limited when reasonably necessary to protect users or the service, enforce these terms, address abuse or security issues, or respond to legal obligations.