Skip to content
MetaTana

These docs are for MetaTana 2.0, coming soon

On this page

Provider Policy

Skyhook turns on a provider only after checking its terms. The app being able to talk to a provider does not mean Skyhook uses it.

Why this exists Every metadata source has its own terms for commercial use, caching, attribution, and proxying. Skyhook only proxies providers whose terms permit the way MetaTana would use them. This page describes that boundary.

Provider Checks

Before a provider is used in hosted Skyhook flows, MetaTana needs to understand:

  • whether commercial use is allowed
  • whether server-side proxying is allowed
  • whether caching is allowed
  • what attribution is required
  • whether results can be returned to Pro users
  • whether artwork or ratings have special restrictions
  • whether the provider has to stay local-only

Metadata Only

Skyhook is metadata-only. It uses only licensed metadata and artwork sources.

Provider support stays limited to rights-safe metadata, artwork, ratings, playback compatibility, local NFO and sidecar readers, and work on files you own.

Attribution

Provider attribution stays visible where required. The website carries the required TMDB non-endorsement notice and TheTVDB attribution. The app shows which provider supplied each value, and credits the provider directly where its terms require it.

Local-Only Cases

Some integrations run only in the app on purpose. Local-only does not mean unsupported. It means Skyhook does not proxy or store that provider's data unless a later provider-policy decision allows it.

Going deeper Providers for the per-provider role matrix, and Hosted metadata for what Skyhook serves vs what stays local.