Lawful media workflows only.

1. Appropriate uses

Examples may include:

• downloading your own uploaded media or production assets;
• saving media where the rights holder has granted permission;
• retrieving public-domain or appropriately licensed material while complying with attribution and licence terms;
• creating an accessibility, archival, review or research copy where the law clearly permits it; and
• testing FrameFetch with media specifically created or licensed for software testing.

You are responsible for determining whether your intended use is lawful.

2. Prohibited uses

Do not use FrameFetch to:

• infringe copyright, performers’ rights, privacy, publicity, contract or other rights;
• bypass DRM, paywalls, authentication, subscription controls, access tokens, geographic controls or technical protection measures;
• access private, removed, leaked, confidential or non-public media without authorisation;
• download or distribute child sexual abuse material, non-consensual intimate media, unlawful extremist material or other illegal content;
• harass, stalk, dox, threaten or exploit a person;
• build an unauthorised bulk archive, scraping operation or commercial redistribution service;
• misrepresent FrameFetch output as proof of ownership, authenticity or licence;
• resell, sublicense, share or automate access to a FrameFetch account or Pro entitlement; or
• help another person evade this policy, a quota, suspension or source-site restriction.

3. Browser cookies and authenticated sources

The local companion can optionally ask yt-dlp to read cookies from a supported browser. This is off by default. Use it only for an account you control and only where the source permits the requested download.

Do not upload, export, sell or share browser-cookie files through FrameFetch. Do not use another person’s cookies, session, subscription or login. Cookie access does not authorise bypassing DRM or contractual restrictions.

4. Protecting the service

Do not:

• probe, scan, exploit or attempt to gain unauthorised access to FrameFetch, its providers or another user’s jobs;
• send malware, shell instructions, hostile URLs or payloads intended to escape the allowed yt-dlp option set;
• overload inspection, download, payment, ticket or authentication endpoints;
• evade the one-guest, three-member or 100-per-24-hour Pro allowance;
• interfere with the local loopback token, origin restrictions or one-time entitlement ticket; or
• reverse engineer the service except to the extent applicable law expressly allows.

5. Enforcement

FrameFetch may reject a URL, rate-limit requests, preserve relevant evidence, remove a cloud object, restrict an account, revoke active sessions or suspend service where reasonably necessary to investigate or stop misuse.

Serious or repeated violations may result in permanent account termination and, where legally required, disclosure to rights holders, providers, regulators or law enforcement. Enforcement decisions consider context and should not be read as a legal finding about ownership.

6. Report suspected misuse