Skip to content
Guides Factory
Theme

Legal

Privacy Policy

There is no account here and no form that sends us anything, so this is a short page: what a web request leaves behind, what the advertising and analytics tags do, and what stays in your browser.

Last updated: 5 September 2026

What we collect

There is no account to create. One form on this site sends something to us — the suggestion box — and what it sends is described in its own section below. Everything else is the ordinary record of a web request, plus what the analytics and advertising tags collect.

  • Request data: your IP address, browser and device type, the page you asked for and the page you came from. This is what any web server receives, and it is what our host processes to deliver the page and to block abuse.
  • Guide views: opening a guide increments its public view counter. Our API briefly remembers the requesting IP — about fifteen minutes — so a reload is not counted twice, and then forgets it. The counter itself is a number per guide, with nothing attached to it.
  • Analytics and advertising: whatever Google Analytics, Google AdSense and Adcash collect. The two Google tags follow the consent defaults described below; Adcash does not.
  • In your browser only: your theme choice and your ticked checklist rows. These are written to local storage on your device and are never transmitted to us.
  • Email: if you write to us, we keep the message and your address for as long as it takes to deal with it.
  • The suggestion box: the text you typed and the time you sent it. See below.

How we use it

To serve the pages, to keep the site up, and to see which guides are read and how far — which is how we decide what to cover next. Advertising pays for the catalogue, so the site carries ads and measures them.

We do not sell personal data, we do not buy it from brokers, and we build no profile of you ourselves. We do not send marketing email, because we have no list to send it to.

Cookies and local storage

Two different things are at work here, and only one of them is a cookie. Your theme choice and the checklist rows you tick are kept in your browser's own local storage: they never reach our servers, they are not tied to an identifier, and clearing site data removes them. Nothing on this site needs them to be set before you can read a guide.

The cookies come from the three tags the site loads: Google Analytics, which measures which guides get read and how far; Google AdSense, which serves the advertising that pays for the catalogue; and Adcash, a second advertising network running alongside it. All three can set cookies and read them on later visits.

What happens before you answer depends on where you are. In the EEA, the UK and Switzerland the two Google tags start switched off: they measure in aggregate, nothing is written to your browser, and no advertising profile is built. The consent prompt in those countries is Google's own certified tool rather than ours, because that is what serving advertising there requires. In a further set of countries whose law also asks first — Brazil, Canada, Japan, South Korea, Turkey, Ukraine and others — this site shows its own prompt, and nothing advertising-related runs until you answer it.

Everywhere else the tags run by default, and you can switch them off at any time through "Your Privacy Choices" at the bottom of any page. If your browser sends a Global Privacy Control signal we treat that as a refusal, in every country, without your having to ask twice.

Adcash cannot read Google's consent signal, so this site holds it back directly: its script is not loaded onto the page at all until the answer above is yes. Your browser's own cookie controls and any tracker blocker stop all three, everywhere.

Who else is involved

Four parties see anything, and this is the whole list. Two of them are Google, and both follow the consent state described above. Adcash does not read that signal, which is why its script is withheld from the page entirely rather than asked to behave. Transfers outside the EEA rely on standard contractual clauses.

  • Cloudflare: serves every page and every image, and so processes the request data described above.
  • Google Analytics 4: which pages are read and how far. IP truncated at collection.
  • Google AdSense: the advertising on the site, and the measurement of it.
  • Adcash: a second advertising network, serving ads alongside AdSense and setting its own cookies to do it.

Your rights

If you are in the EEA, the UK or Switzerland, the GDPR and its equivalents give you the right to access the data held about you, correct it, delete it, restrict or object to its processing, and complain to your local supervisory authority.

If you are in California, Colorado, Connecticut or another US state with a privacy law, you have the right to opt out of the sharing that advertising measurement involves. "Your Privacy Choices" at the bottom of any page is that control, and we honour a Global Privacy Control signal from your browser without being asked.

In practice there is very little here to act on: we hold no account, no profile and no contact details for you unless you have emailed us. A request about the data an advertising or analytics tag holds is best made to that company — Google or Adcash — whose own controls sit outside this site; we will help where we can. Consent you have given can be withdrawn at any time through "Your Privacy Choices", through the same prompt that asked for it, or through your browser's cookie controls.

Ask anything, including a deletion request, at support@guides-factory.com, and we will answer within thirty days.

Contact

Questions about this policy, a data request, or a takedown notice go to support@guides-factory.com. Security reports go to security@guides-factory.com — we will confirm receipt within two business days.

This page describes how the site works today; it is a plain-language statement of practice, not legal advice.