Privacy Policy
How PUNBIT measures visits and handles data when you read or play.
Last updated November 19, 2026 · questions to [email protected]
The short version
PUNBIT uses Cloudflare Pages to host the site and Cloudflare Web Analytics to measure traffic when enabled. Your theme, high scores and player preferences stay in your browser.
What is stored in your browser
Four things, all in localStorage on your own device, all written because of something you did:
punbit.theme— light or dark, written when you press NIGHT, so the site opens the way you left it.dendi.scores.<issue>— up to ten of your own runs on one cartridge: a score, an in-game time, and when the run ended. It is a scoreboard against yourself. There is no shared leaderboard, and nobody else can see it.punbit.playmode— whether an issue’s game opens over the story or beside it, written when you pick one, so the next issue opens the way you asked for.punbit.reelhint— one flag saying you have already been shown that a phone swipes from one game to the next, so the site stops saying it.
You can clear these settings on your device using the instructions in our Cookie Notice.
Web analytics
When Cloudflare Web Analytics is enabled, Cloudflare adds a small script to pages on punbit.com. It reports page paths, referring sites and measurements of how quickly pages load. Cloudflare shows us aggregate visits and page views, with breakdowns by country, device type and browser. We use those reports to understand which issues people read and how well the site performs.
The analytics script uses no cookies or browser storage and does not fingerprint visitors. See Cloudflare Web Analytics for details.
What the host records
The site is static files, served by Cloudflare Pages. Like any web server it processes ordinary request data — an IP address, the time, the path requested, the browser’s user-agent string — in order to deliver the page and absorb abuse. Cloudflare handles that data under its own privacy policy ↗.
Sharing, clips and links out
Share hands the issue’s title and link to your device’s own share sheet, or copies them to your clipboard if it has none. Save clip encodes the GIF inside your browser and hands you the file. Neither uploads anything, to us or to anyone else.
Every issue links out to the outlet that published the story. Following one of those links puts you on someone else’s site, under their privacy policy rather than this one.
Publishing to YouTube
When a cartridge gets a short clip on YouTube, it goes to this project’s own channel, uploaded by a tool of ours that uses YouTube API Services. That tool runs on a machine of ours, not on this site. Its only user is the person who runs it: it signs in to this project’s own channel, uploads a file, and reads nothing else. It is never given anything about you, because it never sees anything about you.
No page here asks YouTube for anything. There is no embedded player, no channel widget and no subscribe button, so reading an issue or playing a cartridge tells YouTube nothing about your visit. Watching the same clip on YouTube instead is a visit to YouTube, under Google’s privacy policy rather than this one.
Google sets out what it does with the data it holds — about the account that uploads, and about you if you watch there — in the Google Privacy Policy ↗. The authorisation our uploader holds for that channel can be withdrawn at any time from Google’s account permissions page ↗.
Subscribing
The only subscription is the RSS feed, which your reader fetches without telling us who you are. There is no mailing list — so there is no address of yours for us to hold, lose, or hand to anybody.
Your rights over your data
For privacy questions or requests about your data, write to [email protected].