A scorecard for a night out. It keeps names and swigs, and not much else.
Last updated 13 August 2026
Pub Golf is a personal project, not a company. It is run by one person, who is the data controller for anything below, and who can be reached at glynfinck@gmail.com.
Joining a round needs a code and a name: no account, no email, no password. You get an anonymous session so the database can tell your card from everyone else's.
The name you type is the whole record. Type a nickname and that is genuinely all we have.
Hosting a round needs a Google sign-in. From it we store:
Google also returns your email address, and our authentication database holds it because that is where a Google sign-in puts it. Nothing in the app reads it, and Pub Golf never sends email. There is no mailing list, no notification, no password reset, and no mail server configured at all. If that ever changes, this page changes first.
The card, essentially: swigs per hole, penalties and who called them, mulligans, handicaps, and the pubs on the course with their Google Place ids. Plus the times things happened, because the hole timer is a shared deadline everyone counts down to.
Courses you build are stored against your account: a name, the pubs, their order and their par.
Searching for a pub sends your search text to the Google Places API from our server. To aim that search at the right city, we read the approximate location your network gives away: city-level, from the request headers, never stored.
The map can also ask your browser for your exact position. That is the browser's own permission prompt, it is always your choice, and the coordinates are used to frame that one search and then discarded.
Google's own terms apply to what they do with a query. We send them the words you typed and roughly where to look, and nothing that identifies you.
The caddy is the paid extra that plans a course for you. What you type into it — the area, the kind of night, the hole count, and anything you add in your own words — is sent to an AI provider that generates the card. Today that is Anthropic, reached through Vercel's AI Gateway; both are processors acting for this project.
Nothing identifying goes with it. Not your name, not your account, not your email. What the model sees is the brief and a list of real pubs near where you said, and it never invents one — it picks from what Google returned.
We keep a record of each planning session: the brief, the card it produced, what it cost us to run, and a note of the steps the caddy took to get there — which pubs it chose, which it ruled out and why. That record is what lets us answer “this course is wrong” when you tell us so, and it is how the caddy gets better at the job. It is yours, it is visible to nobody else, and it goes when your account does.
The pub data itself is not kept that long.Google's descriptions, ratings and review snippets are held only for as long as you are working on that course — about half a day — and are then deleted by a job that runs every hour. If you come back later to change the course, the caddy fetches them again rather than keeping an old copy.
What does stay is the pub itself: its name, address and map position, in a shared list this app keeps so that a course, a scorecard and a round played years apart all point at the same door. It holds nothing about you and nothing about a night out — the same handful of facts a street sign carries — and it is shared across everyone rather than kept per person.
Payment is handled by Stripe, on Stripe's own page. Card numbers, wallets and billing addresses never touch this app — we never see them and never store them. Stripe is a processor acting for this project, and their own notice governs what they hold.
What goes to Stripe from here is your account's id, so their answer can be matched to the right person, and which thing you are buying. Not your name, not your email, not anything about a round.
What comes back and is kept is the record of the purchase: which thing, how much, in what currency, when, and Stripe's own reference for it. That is the receipt — it is what proves you paid if anything goes wrong, and it is kept as long as your account is, because a purchase you cannot evidence is a purchase you cannot get refunded.
The report goes to a publicissue tracker, so the sheet says so before you send. What you write is printed there; what stays private is everything that would identify you or your round — your name, your account, your browser and its languages, and above all a round's join code, which is stripped out before anything leaves. The issue says whether you were on a phone or a desktop, because that is what a layout bug needs, and nothing narrower than that.
A report filed from a course the caddy planned also records which planning session — and which card in it — the report was about, so we can look at what went wrong. Those links stay on our side and never appear on the public issue.
One cookie, holding your session. That is what keeps your seat at a round when you lock your phone.
No analytics, no advertising, no third-party trackers, and nothing that follows you off this site.
Rounds are stored in a Postgres database hosted by Supabase in London, and the app is served by Vercel. Both are processors acting for this project.
Data stays until it is deleted. A host can delete a round, which takes its scores with it, and you can ask us to delete everything tied to your account.
Email glynfinck@gmail.com and it will be done. That is a person answering rather than a button, and a self-serve control is on the way. Until it lands, this is the honest description of the route.
Under UK data protection law you can also ask what is held, have it corrected, or have a copy of it. Same address, same answer.
Pub Golf scores a drinking game and is not for under-18s. See the terms.
If this page changes, the date at the top changes with it. There is no archive; it is a page in a repository, and its history is the repository's.