FROO - Privacy

Last updated 22 September 2026.

The short version: FROO has no accounts and asks you for nothing - no email address, no name, nothing. The list of episodes you have ticked off is kept by your own browser, and that list never leaves your device unless you switch syncing on yourself.

What FROO stores about you

Nothing on our side. There is no sign-up, no login, no email address, no name, and no profile.

What the site does store, it stores in your browser, using a feature called local storage:

• Which episodes you have marked as watched, and when you marked them.
• Your preferences - whether spoilers and watched episodes are hidden on each franchise list, which series you have switched off on each list, whether you are rewatching a list and since when, whether you are offered the shortcut to mark earlier episodes, and which country the where-to-watch badges are for.
• Copies of the pages you have opened, from 22 September 2026, so they keep working without a connection. These are the same public pages everybody gets, held by your browser in its cache storage rather than local storage; nothing about you is in them, and none of it is sent anywhere. Clearing your browsing data for froo.watch removes them.

That data is not a cookie and is not sent with any request. Unless you turn on syncing, it never leaves your device and we could not read it if we wanted to. The flip side is that it is only on the device you are using: clearing your browsing data erases it, and Safari discards it after a week or two without a visit. You can save a copy of it, or load one back, under Preferences.

Syncing between devices

Syncing is off unless you switch it on, in Preferences. If you do, FROO keeps a copy of your watched list and your preferences on its server so your other devices can pick them up, and from then on it updates that copy by itself - a few seconds after you stop ticking, and again when you open a page. Nothing else is stored with it, and nothing is sent while syncing is off.

There is still no account. When you start syncing, your browser makes up a random 20-character code. That code is the only thing that identifies the copy - and we do not keep the code itself, only a one-way scrambling of it, so the stored copy cannot be traced back to a code, an email address or a person. We have no way of knowing who you are, and no way of finding your list from anything but the code.

Three things follow from that, and they are worth being blunt about:

• Anyone with your code can read and change your list. Treat it like a password. It is written into your exported file too, so that file deserves the same care.
• Nobody can recover it for you. Lose the code and the copy is unreachable, by us as well as by you. Keep it somewhere.
• A copy nobody has synced for two years is deleted automatically.

You can delete the stored copy whenever you like, with "Delete synced copy" in Preferences. That removes it immediately and for good.

Cookies and analytics

FROO sets no cookies of its own. Cookies do end up on your device all the same — four of them at most, all set by Cloudflare, all first-party to froo.watch, and every one of them named and described below. Two separate things count page views here, they are not equally intrusive, and so they are described separately. The first needs no permission and never has. The second does not run at all unless you say yes.

Cloudflare Web Analytics, since 26 August 2026. It counts page views, and it is worth being precise about what that is and is not.

• It sets no cookies and stores nothing on your device. There is no identifier of any kind, so it cannot tell whether two page views came from the same person, and cannot follow you to another site.
• What it sends is the address of the page you are on, the address you arrived from, how quickly the page loaded, and coarse details your browser announces anyway - the country, the browser and whether the screen is a phone or a desktop. It does not send your IP address on to anyone or record it against a visit.
• What it does not send is anything about your watched list, your preferences, your sync code, or anything you have ticked. None of that is readable from a page and none of it is involved.
• It is a script from Cloudflare, who already serve every page of this site, added to the page by them rather than written into it here. It loads from static.cloudflareinsights.com.

Why it is here at all: FROO had no idea whether anybody was reading it, which makes it impossible to know whether any of the work is worth doing. This is the least invasive way of answering that question that exists. If a cookieless page counter is more than you want, an ad blocker or Do Not Track will stop it, and the site works exactly the same without it.

Google Analytics, from 5 September 2026, and only if you agree to it. This one is the ordinary sort, and it does the thing the counter above deliberately cannot: it can tell that two page views came from the same person. It does that by putting an identifier in a cookie on your device. That is a real difference in kind rather than degree, which is why it is asked for rather than assumed.

• Nothing is measured until you agree. The first time you arrive you are asked, and until you answer, nothing is counted and no analytics cookie exists. Decline, or dismiss the box without choosing, and that stays true. One cookie does arrive before you have answered anything — Cloudflare’s tag manager sets its own, whichever way you eventually answer — and it is the first entry in the list below. Nothing on the site is withheld or degraded either way — every list, every tick box and the sync all work exactly the same.
• No Google script ever loads here, whichever way you answer. That is unusual enough to be worth stating plainly: the tag runs on Cloudflare’s servers rather than in your browser, so no page on this site fetches anything from googletagmanager.com or google-analytics.com, and Google is never in a position to see your browser directly. What reaches Google is sent on by Cloudflare afterwards.
• The cookies, all four of them. Two exist whatever you decide; the other two only if you agree. All four are first-party to froo.watch, so none of them is readable by another site.
  • cf_zaraz_client — set by Cloudflare’s tag manager the moment it loads, before you have answered the box and whichever way you answer it. It lasts about a year. Your browser’s own cookie inspector shows no value in it at all.
  • zaraz-consent — your answer, and nothing else: {"oDFu":true} if you agreed, {"oDFu":false} if you declined. It lasts about a year, and it exists so you are not asked again on every page. It is set whichever way you answer, because a refusal is worth remembering too.
  • cfz_google-analytics_v4 — only if you agree. The analytics tool’s own store, holding the identifier that lets it tell one visit from another and a note of how long you spent. It lasts about a year.
  • cfzs_google-analytics_v4 — only if you agree. The same tool’s store for this browsing session, holding a count of pages seen. It disappears when you close the browser.
• So what agreeing changes is the last two. Decline and what sits on your device is Cloudflare’s tag manager cookie and your recorded “no” — no identifier for analytics, and nothing counted.
• What is still not put on your device — no Google cookie, nothing from google-analytics.com or any other domain, and nothing in local storage or session storage. The only local storage this site uses is your own watched list and preferences, described at the top of this page, together with the saved copies of pages for offline use described there, and analytics never touches any of it.
• Cloudflare does not document three of these four. Their published cookie list covers the ones their security products set, and the Zaraz documentation covers zaraz-consent; cf_zaraz_client and the two google-analytics ones appear in neither. What is written above is therefore what can be seen in a browser looking at this site — the names, the values where they are visible, and how long each one lasts — rather than an explanation borrowed from somewhere else. That distinction is here because this page twice named cookies that turned out not to exist, having taken them from write-ups instead of looking.
• What it is used for is telling one person reading four franchise pages from four people reading one. That distinction is the whole reason it is here: the cookieless counter cannot draw it, and without it there is no way to know whether anybody comes back.
• What is counted besides page views, since 8 September 2026. A small, fixed list of actions, so it is possible to tell which parts of the site are actually used: following a link out to IMDb, Wikipedia, a fan wiki, a streaming service or one of the after-you-have-watched videos; opening a Notes popup, along with whether that popup had notes, a where-to-watch block and an after-you-have-watched link in it; ticking episodes, as a count; clearing a page; switching Hide Watched or Hide Spoilers; and starting, linking, exporting, importing, stopping or deleting a sync. Added on 12 September 2026: whether a search in the A-Z box found anything — yes or no, never what was typed; that the “Carry on watching” panel appeared, and whether it was expanded; and that a page was read for half a minute with the tab in front of you. Added on 21 September 2026: changing which series a list shows, as a count of how many are switched off — never which ones; for a search that found something, whether it matched a franchise or only an episode title — still never what was typed; starting or stopping a rewatch, as yes or no; and, from 22 September, following a link to subscribe to a calendar, opening FROO as an app installed on your home screen, and whether an offer to install it was accepted. Added on 24 September 2026: sharing how far through a list you are, as how you shared it — your device’s share menu or a copy — and from where on the page, never what the shared line said or where it went. That is the whole list, and it is enforced in the code rather than by intention — see froo_track in the site’s script.
• What it still does not see is which. No episode, no title and no row is ever named in any of that. “Marked 22 episodes as watched” is sent; “marked Buffy season 2, episode 14 as watched” is not, and there is no setting under which it would be. Your watched list itself is never sent. Neither is your sync code, in any form — not the code, not a hash of it, not anything derived from it; it goes nowhere near analytics, and the reasoning for that is written down in the site’s own repository rather than left as a good intention.
• Why the switches are in that list and the episodes are not. Whether you hide spoilers is a fact about how you use the site; which episode you ticked is a fact about your life. The first is worth knowing and the second is none of our business, and that line is the one the whole list is drawn along.
• It is loaded through Cloudflare Zaraz. The tag is assembled by Cloudflare, who already serve every page here, rather than being written into these pages, and your answer is enforced at that layer rather than by a script that has already loaded and is promising to behave.
• You can change your mind at any time. Reopen the choice and pick again. If you turn it off having previously agreed, measuring stops immediately, and clearing your browsing data removes the record of the answer along with everything else.

The honest reason there are now two: a page count told this site that people arrive, and nothing about whether any of them stay. It is also the measurement an advertising network asks to see before it will take a site on, and that is being looked into — so it would be silly to pretend the only motive here is curiosity. If advertising ever actually arrives it will be described on this page before it does, and the paragraph below still stands until then.

No advertising is shown on the site today. If that ever changes it will be described here first, and noted on the Updates page.

Where to watch

Franchise pages show where each episode can be watched. Working that out needs to know which country you are in, so the page asks this site’s own server, and the server reads the country from the request Cloudflare has already handled. That is the whole of it:

• It is this site asking itself. The request goes to froo.watch and nowhere else. No third party is involved and nothing is embedded from anybody — the availability data was collected in advance and is held here.
• What it sends is which franchise page you are looking at, and a two-letter country code. Nothing else, and nothing that identifies you.
• Nothing is written down. The country is used to choose which rows to send back and is then discarded. No log of it is kept, and it is not attached to anything else.
• You can override it in Preferences, which is worth doing if you are abroad or on a VPN. That choice is stored in your own browser like your other preferences.

The availability information itself comes from the Streaming Availability API by Movie of the Night, and is a snapshot rather than a live check — services add and drop things constantly, so treat it as a strong hint rather than a promise.

Calendars

Franchise lists with something still running offer a calendar of their newest episodes, from 22 September 2026. Subscribing gives FROO nothing about you: the calendar is a plain file, the same for everybody, and once you subscribe it is your calendar app — or the calendar service behind it, such as Google or Apple — that fetches it from time to time, the same way a browser fetches a page. There is no account, no address and nothing in the request that says who you are. Unsubscribe in your calendar app and the fetching stops. Choosing to subscribe is counted as one of the actions listed above, as a yes, never as which list or anything about you.

Where the site is hosted

FROO is served by Cloudflare. Like any web host, their servers keep short-lived technical logs of requests - including the IP address the request came from - in order to deliver pages and protect the site from abuse. We do not add anything to those logs and do not build profiles from them. The page counting described above is a separate thing from these logs and does not draw on them. Cloudflare describes what it retains in its own privacy policy.

The feedback form

The feedback page embeds a Google Form. That form is Google's, not ours, so visiting that page and using the form involves Google, and Google's privacy policy applies to it. Whatever you type into it comes to us. Please do not put anything in it you would not want us to have - it is a suggestions box, not a support desk, and we have no way to identify or remove an individual entry after the fact.

Apart from that form, the Cloudflare page counter, and Google Analytics if you have agreed to it - all three described above - no page on this site embeds anything from anybody else.

Links to other sites

The franchise lists link out to IMDb, Wikipedia and various fan wikis, and the site links to our page on X. Once you follow a link you are on somebody else's site, under their policy, not this one.

Children

FROO is a list of television programmes. It collects nothing from anybody, of any age.

Changes to this page

Any change to what the site stores will be described here and noted on the Updates page, which is the full log of everything that changes on FROO.

Getting in touch

Use the feedback form. FROO is run by Scorched Tortoise.