What we collect, and why

What we actually collect

Very little, and none of it identifies you. There is no form anywhere on this site — no account, no newsletter, no search box — so there is nothing you could type in for us to store even if we wanted to.

Google Analytics storage stays off unless you accept it. Before then, Google's tag runs with consent denied: it sets no analytics cookie or persistent browser identifier, though it may send a cookieless measurement ping. If you accept, it records the ordinary things — which pages were viewed, roughly which country the request came from, which site or search sent you, what kind of device — and sets a cookie so two page views in one visit count as one visit. You can change your mind in either direction, at any time, on the analytics page, which also explains what we use it for.

There is one exception, and it is deliberately narrow. When you click a link to buy a ticket, we record a single anonymous line: which deck, which ticket partner, where on the page the link was, what verdict was showing, which date it was for, and the time. That is the whole row. It contains no IP address, no browser or device information, no cookie and no identifier of any kind — two different people clicking the same link produce two identical, indistinguishable lines.

We keep it because it is the only way to learn which advice actually helps: whether people act on a MAYBE, or whether a recommendation to go somewhere else is useful. It cannot be traced back to a person, and it is not used to build a profile, because there is nothing in it to build one from.

Cookies

The site itself sets no cookies unless you accept analytics. Nothing else here needs one — there is no login, no cart, and no preference to remember between visits. The ticket-click record described above needs none either, which is exactly why it cannot tell one visitor from another.

The single exception is Google Analytics, and only after you have accepted it: it sets a _gacookie to recognise one visit across several pages. Decline, or simply never answer, and that cookie is never set. Your choice itself is kept in this browser's local storage rather than in a cookie, so it never travels with a request, and clearing site data resets it to off.

Ticket links, and what the partner sees

Some links on this site go to ticket sellers — currently GetYourGuide and Headout — and we may earn a commission if you book. It never affects a verdict: the score and the VIEW/MAYBE/SKIP answer are computed before any link is attached, and the code that makes decisions is prevented from reading anything commercial at all.

Those links pass through /go/ on this site first, which is where the anonymous click line above is written, and then forward you to the partner. The link we send carries codes identifying us as the referring site, so the partner can pay the commission — it says the click came from ViewOrSkip, not who you are. Once you are on the partner's site you are covered by their privacy policy, and they will typically set their own cookies. We have no visibility into what you do there beyond whatever aggregate totals they report back to us.

Hosting and request logs

The site is rendered and served by Cloudflare, our hosting provider. Like any host, Cloudflare necessarily processes standard connection information to deliver each page — the kind of request log (IP address, requested URL, timestamp, user agent) any web server generates simply by answering a request. We don't separately collect, read or store that data ourselves; it exists at the infrastructure level, under Cloudflare's own privacy terms, purely as a byproduct of serving the page you asked for.

Contact

Questions about this page, or about what Cloudflare's request logs hold, can go to privacy@vieworskip.com. If what we collect or run changes, this page will say so before that ships, not after.