Skip to content
MetaTana

These docs are for MetaTana 2.0, coming soon

On this page

Privacy And Data

Skyhook receives only the data it needs for each request.

The boundary in one sentence Your library, media files, folder paths, and local provider keys never leave your machine. Skyhook receives only the request data needed for the specific hosted call, for example sampled frames and hints for AI Vision, or search terms for hosted metadata.

Local Data Stays Local

The local app owns:

  • folder paths
  • media files
  • local database
  • sidecar files
  • local provider keys
  • local playback destination details

Hosted features receive only the request data the feature needs.

AI Vision Data

AI Vision uses sampled frames and reviewed hints. It never uploads the full video file to identify a title.

Local file paths are removed or reduced to safe hints before anything is sent.

Ask AI And Translation Data

Hosted Ask AI sends the file name, its folder name, the file's length and the catalog's search results for that title. It never sends the full path or the file. Hosted metadata translation sends the title and overview text being translated. Both go to MetaTana and on to the AI model provider that answers.

Hosted Metadata Data

Hosted metadata requests can include metadata search and enrich facts such as title, year, media type, provider IDs, and language preferences. They never include the rest of your library.

Anime Lookups

Anime scans look up titles on AniList, a free public anime database, even when you have not added any keys. MetaTana sends only the search title or an AniList ID to AniList and loads anime artwork from its image server. No file paths, file names, or library details are sent. This keeps anime matching working out of the box.

Provider Keys

MetaTana's own provider keys stay on its servers. The app receives metadata or artwork results, never those keys.

Support Reports

Use Send a report on Help for normal reports. It sends the answers you type, any error code or request ID, and, with Include app details on, the app version, platform, install type, and the page it was opened from. It does not attach files, screenshots, logs, paths, or diagnostics.

When sharing extra details or deliberately opening a public issue:

  • redact tokens and provider keys
  • redact one-time email codes
  • avoid full local paths when not needed
  • describe the request type and provider state without pasting secrets
  • include rows from Activity or Library health only when they explain a local failure
Going deeper Export report in the ⋯ menu on Activity saves a JSON summary of recent work with secrets removed and paths shortened. The masking is best effort, so read it before sharing. See Activity.