Kometa Services

×

Notes on Privacy

OAuth Token Pages

Plex, Trakt, MyAnimeList, and SIMKL OAuth pages are fully client-side OR they use a Kometa-controlled client ID. You log into the remote site and that site sends some data back. Your tokens are exchanged directly between your browser and the respective service's API. If you use the "Bring Your Own" option and provide your own client_id and secret, those tokens do not traverse our server. No user token data is sent to or stored on this server.

FlickList OAuth uses a third pattern: its API doesn’t support cross-origin browser requests, so your browser talks to a same-origin passthrough on this server that forwards each request to FlickList untouched. Your key is never stored here — it only passes through.

WeTrakr OAuth uses the same passthrough pattern as FlickList: its API doesn’t support cross-origin browser requests either, so your browser talks to a same-origin passthrough on this server that forwards each request to WeTrakr untouched. Your tokens are never stored here — they only pass through.

Metadata Services

AniDB, SIMKL, and IMDB services cache metadata on this server to improve performance. No personal data is collected or stored. Only publicly available metadata is cached.

Analytics

This site uses Plausible Analytics, a privacy-friendly, self-hosted analytics service. It collects anonymous, aggregated data only — no cookies, no personal data, no fingerprinting.

Source Code

The source code for this project is available on Github for review or self-hosting. Doing so may require you to create additional applications to take the place of the official Kometa apps.

Contact

Questions? Open an issue on GitHub or discuss it on Discord.