Terms of use

Effective 1 April 2026. These terms cover access to this node. They do not cover the content itself, which is governed by whatever agreement you have with the party that issued your link.

1. Scope

This node delivers bytes on behalf of content owners. It does not hold accounts, does not sell anything, and has no relationship with you beyond serving a request that carries a valid signature. Where these terms and the content owner's terms disagree about the content, theirs apply.

2. Permitted use

Requesting content for which you hold a valid signed link.
Reading the health endpoint at a reasonable interval for monitoring purposes.
Fetching these pages and the files they reference.

3. Prohibited use

Attempting to forge, extend or brute-force a path signature.
Enumerating paths, probing for unlisted endpoints, or scanning the host.
Automated retrieval at a rate that degrades service for other clients, including parallelised whole-catalogue downloads.
Redistributing delivered content outside the terms of the party that issued your link.
Presenting this node as your own infrastructure, or proxying it to third parties as a service.

4. Rate limits

Limits are applied per source address and are deliberately not published in detail, because publishing them invites tuning against them. When you exceed one you receive 429 with a Retry-After header; honour it. Clients that ignore Retry-After are blocked at the network layer, which is less pleasant for everyone than backing off.

5. Logging and retention

Request logs contain the source address, the requested path, response code, byte count and timestamp. They are kept for 14 days for operational and abuse purposes and are not used for profiling or advertising. There are no cookies set by this host and no third-party resources loaded by these pages, so there is nothing here to track you with.

6. Availability

No availability commitment is made to you by this node. It is one cache among several and may be drained, rebooted or removed at any time; requests are expected to move to another node without your involvement. If you have an availability commitment, it is with the content owner and covers the service as a whole, not this machine.

7. Liability

To the extent permitted by applicable law, the operator is not liable for indirect or consequential losses arising from use of this node, including losses arising from an interrupted or degraded stream. Nothing here limits liability that cannot be limited by law.

8. Changes

These terms may change. Substantive changes take effect fourteen days after the date at the top of this page is updated. Continued use after that date is acceptance.

Security issues are handled separately and always welcome — see security.txt. Reporting a vulnerability in good faith is never treated as a breach of section 3.