Cookie Policy
Last updated: 12 July 2026
Cookies are small text files a website stores in your browser. Ours are few, boring, and fully described below — a shorter read than most of our episode verdicts, and with fewer arguments.
1. The cookies we use
| Name | Type | Purpose | Lifespan |
|---|---|---|---|
| db_cookie_toast | Essential (local storage) | Remembers whether you tapped "Go on then" or "No thanks" on our cookie notice, so we don't nag you on every page. | Until you clear your browser storage |
| db_read_counts | Analytics (optional) | Counts, anonymously, which episode write-ups get read so we know whether long verdicts are worth the typing. | 12 months |
| db_visit_ref | Analytics (optional) | Records whether a visit arrived via a direct link or a search engine — no personal details, just a category. | 30 days |
2. What we don't do
No advertising cookies. No cross-site trackers. No fingerprinting. No third parties peeking over your shoulder while you read about a bouncing bell. The optional analytics cookies are set only if you accept them, and the numbers they produce are aggregate counts that could not identify you even if we tried — which we won't, because we're busy losing at The Laughing Stack.
3. Managing cookies
You have three easy options:
- Decline on the notice — tap "No thanks" on our cookie pop-up and only the essential preference entry is stored.
- Browser settings — every modern browser lets you block or delete cookies for specific sites; check the privacy section of your browser's settings.
- Clear storage — clearing your browsing data for joranesk.pro removes everything we've stored, including your notice preference (so the pop-up will greet you again like an over-friendly dog).
4. Changes
If we ever add or change a cookie, this table gets updated first and the change gets a mention on the show. The date at the top of this page always tells you when the policy was last touched.
5. Questions
Anything unclear? Email [email protected] with the subject "Cookies" and Tom will reply with more detail than you asked for. See also our Privacy Policy for how we handle personal information generally.