Pageview counts

Pages load PostHog. It counts visits, and whether people arrived from an AI tool such as ChatGPT. It is set not to store cookies: the data is kept in memory for that visit only, so there is no cookie banner. This repository does not include Google Analytics, a tag manager or Meta Pixel.

PostHog may collect the page address, the referring site, campaign parameters such as utm_source, a rough location from the IP address, and basic browser details. That data is processed in PostHog’s US cloud. The guide uses it for aggregate counts. It is not used to build a profile you can log into, because there is no login. Questions go to hello@mikelitman.me.

What stays in your browser

The homepage stores a few things in localStorage on your device, so a refresh can remember them. They are not posted to the guide’s server. The keys in the homepage script are:

  • pubFavs and pubVisited — pubs you mark as saved or visited, for the passport and badges.
  • pubStreakData — the week streak calculated from those visits.
  • booking_clicks — a local note when you follow a venue’s own booking link.
  • pubVisitCount — how many times this browser has opened the guide.
  • pubTheme — a light or dark preference on pages that still offer the toggle. The current homepage clears this key.

Clearing site data for pubguidelondon.com removes them. The guide cannot see that data on the server, because it never leaves the browser.

Location, maps and weather

“Near me” and “Where next?” call the browser’s geolocation API only if you use those controls. The coordinates stay in memory for that visit so the page can sort the pubs already loaded. They are not written to localStorage and not sent to a London Pub Guide server. If you refuse permission, those features stop and the rest of the guide still works.

Opening the map loads Leaflet from unpkg and map tiles from OpenStreetMap. Your browser then requests those tiles directly from OpenStreetMap, which sees the usual connection data for a tile request. The homepage also fetches London’s weather summary from wttr.in (the city, not your position) to suggest a kind of pub for the weather.

Newsletter and pub suggestions

The Friday newsletter form posts your email address to Buttondown (buttondown.com/api/emails/embed-subscribe/londonpubguide). Buttondown stores it so they can send the list. The form opens in a new tab. Unsubscribing is handled by Buttondown’s own links. The guide does not keep a separate copy of that list in this repository.

The “Know a pub we’re missing?” form is a Netlify Form named pub-suggestion. It sends the pub name, an optional area, a short note on why it is worth the trip, and an optional email address. Netlify stores the submission so it can be read. A hidden honeypot field is included to catch simple bots. You can suggest a pub by email instead, at hello@mikelitman.me, and skip the form entirely.

Fonts and other requests

Pages load typefaces from Google Fonts. That request goes to Google and carries the usual connection data. There is no payment processing, no customer account, and no sale of a mailing list by this site. Venue websites linked from a pub page are other people’s sites, with their own policies.

This site does not publish a postal address. Privacy questions go to hello@mikelitman.me. The publisher is Mike Litman, London, behind The London Pub Guide and the Cultural Capital Labs project line used in the footer.