Last updated · July 15, 2026
Cookies and trackers
This page gives a clear and simple overview of the cookies, local storage, and technical trackers used by WatchTrack.
What this page covers
WatchTrack uses different technical mechanisms to operate the service, remember certain preferences, and keep useful local data on your device.
This page is provided for information purposes. It is not meant to be a fully contractual list of every browser-level behavior, but it describes the main trackers and local storage used in the app.
Simple table of cookies and trackers
| Name or category | Type | Purpose | Indicative duration |
|---|---|---|---|
| Supabase authentication cookies | Cookies | Keep the user session active, secure sign-in, and allow access to the account. | Varies depending on the session and authentication renewal managed by Supabase. |
| watchtrack_guest | Cookie | Remember guest mode and apply the related access limitations. | 7 days. |
| watchtrack_region | Cookie | Store the chosen or detected TMDB region for the catalog and watch providers. | About 1 year. |
| wt_timezone | Cookie | Store the browser timezone for consistent date and time display. | About 1 year. |
| watchtrack-query-cache | IndexedDB | Store some local app cache, including TMDB metadata, search results, and library-related data useful for navigation. | Until cache deletion or local storage refresh. |
| watchtrack_import_job_id | sessionStorage | Reconnect the interface to an import job while the browser session remains open. | Until the tab is closed or the session storage is cleared. |
| watchtrack_announcements_* / watchtrack_import_notification_* / watchtrack.importPrompt.dismissed.* | localStorage | Store some local interface state such as dismissed announcements, import notifications, or onboarding prompt state. | Until locally deleted or replaced by a new value. |
| Umami | Audience measurement script | Limited audience measurement to understand overall site usage and improve the product. | Depends on the Umami service behavior and retention applied on the analytics side. |
| Web push and service worker | Browser storage / service worker | Support PWA installation, app-related technical caching, and push notifications if enabled. | Varies depending on the browser, installation state, and service worker lifecycle. |
Strictly necessary technologies
Some of these mechanisms are strictly necessary for WatchTrack to function properly: user session, region memory, timezone, PWA behavior, continuity of an ongoing import, or local technical caching.
Audience measurement
WatchTrack also uses Umami in a discreet way to measure overall site usage and improve the product.
This page mentions that use for information purposes only, without detailing a specific user-control mechanism here.
Page updates
This page may change if WatchTrack adds, removes, or updates some cookies, local storage, or technical tracking mechanisms.