Privacy

Anonymous progress

If you use the tracker without an account, your Road state stays in this browser's localStorage. That includes watched titles, episode checkpoints, saved movie positions, schedule settings, per-title date changes, postponed titles, diary entries, missions, achievements, reminder preferences, Beginner Mode, Experience Mode, motion preferences and your theme choice. It never leaves your device unless you explicitly export a file.

Accounts and sync

Optional accounts are for cross-device synchronisation only, and are never required to use the tracker. If you sign in with an email link, we store your account identifier, an optional display name, and your tracker state — including watched titles, episode checkpoints, saved movie positions, schedule settings, per-title date changes, postponed titles, diary data, missions, achievements, reminder/share preferences, Beginner Mode, Experience Mode, motion settings and your theme. Row-level security means only your own signed-in session can read or change those rows; nobody else can see your progress.

The first time you sign in on a device that already has progress, we ask before combining anything — nothing is overwritten without your choice. After that, changes sync in the background, and anything you do offline is saved locally and uploaded once you reconnect.

Saved progress inside a title

Episode checkpoints and Save My Place movie positions are progress markers, not proof that a title is complete. For movies, we store the number of minutes you entered plus the time that position was last updated. Marking the movie watched clears that saved position; an Undo can restore the prior position. These values are included in local backups and, when you are signed in, sync with the rest of your tracker state.

McuWatch does not read playback history from a streaming service and does not measure what you watched automatically. Saved positions are only what you deliberately record.

Your watch diary

The diary stores, per title, an optional date you watched it, a 1–5 rating, favorite and “would watch again” flags, and a private note. Without an account these stay in your browser only. Signed in, they sync with the rest of your tracker state under the same row-level security, so only your session can read them.

Private notes are exactly that: they never appear in shared progress cards, share codes, page metadata, feedback or admin screens, agent (MCP) responses, logs or analytics. Titles you marked watched before the diary existed are shown with an unknown date — we never invent one. Clearing diary details never un-marks a title as watched.

Achievements are worked out from that same tracker data on your device. All we store is the badge identifier and the moment you earned it — never a note, an email address or an account identifier — and it syncs with your tracker state under the same protections.

Schedule reminders

Reminders are optional and off until you turn them on. We store only your reminder preferences — on/off, day-of and day-before times, and quiet hours — plus a short list of keys recording which schedule reminders have already been shown, so the same nudge is not repeated. Those keys are built from a title ID and a scheduled date and are pruned automatically.

Notification text contains public title names and dates from your own schedule only. It never includes diary notes, ratings, favorites, your email or any account identifier, and reminder data is not sent to analytics, feedback, admin tools or agent integrations. Notifications are generated on your device while the site is open or installed; there is no background push service.

Share cards

If you choose to show achievements on a share card, we store up to three public achievement IDs as a share preference alongside your other tracker settings. Cards are drawn on your device and contain public achievement names and progress only — never unlock dates, diary notes, ratings, favorites, your email or any account identifier.

Site analytics

If site analytics are switched on, McuWatch loads Umami to count page views and campaign referrals such as X or Bluesky. Umami uses no cookies or cross-site tracking. Referral tags are restricted to a short source label and are removed from links copied through the Share dialog. We never send title progress, diary notes, searches, schedules, account data or email addresses. If analytics is not configured, no analytics script loads. If your browser sends a “Do Not Track” signal, we honor it and load nothing. Ad blockers and privacy extensions can also block analytics without affecting the app.

Hosting telemetry

Our hosting platform may load its own operational scripts to measure sessions, page loads, performance and errors. Those scripts are controlled by the host and may run even when McuWatch analytics is disabled or your browser sends Do Not Track. McuWatch does not intentionally send your watched titles, diary entries, schedule, email address or account identifier through those scripts. We will update this notice if the host changes or the site moves to another provider.

Road Live

The homepage can show roughly how many browser sessions are on the Road right now. Your browser joins an anonymous presence channel while the site is open, and nothing is written to the database: there is no visitor history, no location, no account identity and no way to tell who anyone is. Presence is ephemeral — your session leaves the count when it disconnects and the realtime service removes it, which can take a short moment after you close the tab. To avoid counting the same browser once per open tab, a random dedupe token is stored locally in your browser and replaced each day; it is never an account or device identifier and is never stored on our side. If the connection fails, the indicator simply hides itself rather than showing a number.

What we never do

• We never sell your progress or any other information.
• We never use analytics or presence to identify you, and we never send your watched titles, diary notes, ratings or email to any analytics service.
• Shared progress cards contain only your public watch stats — no account details.
• We never pass your progress, diary, schedule, email or account identifiers to advertising partners.

Deleting your data

Use “Reset checks” on the tracker, or clear this site's data in your browser settings, to remove local progress instantly. Signed in, Account settings has a “Delete my account” option that permanently removes your profile, tracker state and sign-in access, and can also clear the copy stored in this browser. Deletion is immediate and cannot be undone.

Feedback

• Feedback can be submitted anonymously — no account is required.
• Your account identifier is stored with a submission only when you are signed in while sending it.
• A contact email is optional and used only if the creator needs to follow up.
• Technical details (browser user-agent, viewport size, app version, current route, whether you are signed in, and whether the app is installed) are included only when you tick the opt-in checkbox. Passwords, payment details, precise location, browsing history and authentication tokens are never collected.
• Feedback is private and visible only to authorised project administrators. It is never sold, shared, or displayed publicly.
• Signed-in visitors can delete their own submissions.
• To limit spam, a random identifier stored in your own browser is hashed and used to count submissions. Raw IP addresses are never stored.
• Please do not submit sensitive personal information in feedback.

Credits

Poster artwork and title metadata are provided by TMDB. This product uses the TMDB API but is not endorsed or certified by TMDB. Poster images load in your browser directly from TMDB's image servers (image.tmdb.org). Like any website that serves images, TMDB receives your IP address and basic request details when your browser loads a poster.

Calendar export

Calendar export is one-way and optional. The .ics file is generated entirely in your browser and never uploaded. If you use an "Add to Google Calendar" link, the event name, date and description travel to Google in the link you open — no account is connected and McuWatch receives nothing back.

Advertising

McuWatch shows ads served by Google AdSense to help cover hosting costs. Ads appear only in clearly labelled “Advertisement” spaces on public pages such as the homepage, the Road and our guides. Ads never appear on sign-in, account, settings, data, support or this privacy page, nor inside dialogs or your progress tracker.

Third-party vendors, including Google, use cookies to serve ads based on your prior visits to this website or other websites. Google's use of advertising cookies enables it and its partners to serve and measure ads, and to show personalised ads based on your visits to this and other sites. You can learn how Google uses information from sites that use its services, read Google's advertising policy, and opt out of personalised advertising in Google Ad Settings.

Where the law requires it (for example in the EEA, the UK and Switzerland), a consent message from Google's certified consent tool appears before personalised ads load, and you can change your choice at any time.

Your tracker progress, schedule, diary, email address and account identifiers are never passed to ad components. If you use an ad blocker, the tracker, sync and sign-in work exactly the same. You can keep using the tracker fully, for free, without contributing money.

Payments and support

McuWatch does not directly process payments. The Support button simply opens PayPal in a new tab, where PayPal's own privacy policy and terms apply. We never receive or store card numbers, bank details or any payment credentials, and we cannot control what information PayPal independently collects or displays. Supporting the project is entirely optional and unlocks nothing.