Privacy Policy
Effective 17 November 2026. This is the privacy policy for gardenflouer.com, run by GardenFlouer, online since 2012 and reachable at chris@gardenflouer.com.
Most privacy policies are written to be scrolled past. I would rather you actually read this one, so it is in plain English and it says specifically what this site does, not what some template thinks a website might hypothetically do someday.
Here is the short version. There are no accounts on this site. There is no login, no newsletter, no shopping cart and nothing to buy. The one form here is the contact form, and the only thing it needs from you is the message itself. I do not sell your data, I do not trade it, and I do not have a mailing list to add you to even if I wanted one (I do not). What I do have is a small stack of ordinary web tools, analytics, a host, and advertising, and every one of them touches a little bit of information. The rest of this page is me naming each one, telling you exactly what it sees, and pointing you at the switch that turns it off.
Google Analytics 4
This site runs Google Analytics 4, measurement ID G-GLJXV6LGPC, loaded through the standard gtag.js script. It is the thing that tells me whether anybody actually read the MissingNo. article or whether I wrote 4,000 words for my cat.
What it collects: page views and the pages you moved between, an approximate location derived from your IP address (country and region level, not your doorstep), your device type, screen size, browser, operating system, referring site, and how long you stayed. It sets cookies in your browser to tell one visit apart from the next. I look at all of this as totals on a dashboard. I am not sitting here reading individual sessions, and Analytics does not hand me your name or email because it does not have them either.
On the Lab tools, the Arcade games and the work tools, Analytics also records which button you pressed: the tool’s name, the action (things like answer, share or battle start) and a few details that go with it, such as the game mode, your score, or a calculator’s result. None of it includes your name or email. Some tools keep their settings in the page address so a link can be shared, and like every page address, that address is part of the page view Analytics records.
Google acts as a data processor here and their handling is covered by the Google Privacy Policy. If you would rather not be counted at all, Google publishes a browser add-on that opts you out of Analytics on every site, not just mine: tools.google.com/dlpage/gaoptout. Install it and my numbers go down by one. Honestly, that is fine, the number was never the point.
Cloudflare Web Analytics
Alongside Analytics I run Cloudflare Web Analytics, which is the privacy-first option in this stack. It uses no cookies, it does not fingerprint you, and it does not follow you to any other website. It reports aggregate numbers only, things like how many people loaded a page and roughly how fast it loaded for them.
There is nothing to opt out of here because there is nothing tied to you in the first place. It is a tally mark, and tally marks do not know who you are.
Cloudflare, the host and CDN
The whole site is served from Cloudflare's edge network. That means every request you make for a page here passes through Cloudflare's servers before it reaches anything of mine, and Cloudflare processes that request, including your IP address, in order to actually deliver the page, cache it near you, and block the usual internet nonsense (bots, floods, people poking at things they should not poke at).
Cloudflare keeps this kind of request data for security and performance reasons under their own terms, described in the Cloudflare Privacy Policy. Worth knowing: there is no home server in this picture. Nothing you send here lands on a machine in my house, by design.
Google AdSense and advertising cookies
This site carries ads through Google AdSense, publisher ID ca-pub-3251057340018716. They pay for the domain, the coffee, and the hours of ROM disassembly, and they are the reason this whole library is free to read with no paywall in front of it.
Here are the statements Google requires every AdSense publisher to make, stated plainly:
- Third-party vendors, including Google, use cookies to serve ads based on your prior visits to this website or other websites.
- Google's use of advertising cookies enables it and its partners to serve ads to you based on your visit to this site and other sites on the internet.
- You may opt out of personalized advertising by visiting Google Ads Settings.
Third-party vendors other than Google may also serve ads here, and you can review and control a much wider list of them at youradchoices.com, or, if you are in Europe, at youronlinechoices.com. Your Google-specific ad controls live at My Ad Center, where you can see which interests Google thinks you have and turn personalization off entirely. Google explains how it and its ad partners use information from sites like this one on its partner sites page.
To be clear about what I get out of this: I see aggregate earnings and impression counts. I do not receive your browsing history, your interests, or anything that identifies you. The ad choices are yours and the controls above are the real ones.
Your browser's local storage
The tools in the Lab and the games in the Arcade use localStorage, which is a small box of data your browser keeps on your own device. It is how the battle simulator remembers your team, how a tool remembers the last settings you picked, and how a game remembers you already beat that level.
Apart from the one game score described in the next section, none of it is sent anywhere. Not to me, not to Google, not to anybody. It sits on your machine, it is readable only by this site, and clearing your browser data wipes it instantly (which will also wipe your progress, so, you know, be intentional about that).
The game score tally
When you finish a round of one of the Arcade games, or your counted Daily Champion battle in the Lab, the page sends this site three things: which game, which mode, and your final score. The site adds one to an anonymous tally of how often each score comes up, which is how a game can tell you something like "Better than 62% of 143 Daily scores." No name, no cookie, no IP address and no time is stored with a score, so nothing in the tally points back to you, or even to the day you played. If you reload a finished Daily, the page asks where that same score stands, which sends the score again but records nothing new.
To keep anybody from flooding the tally with fake scores, the server counts the requests coming from each network address for ten minutes at a time, in memory only. That count is never written down, and it is dropped soon after its ten minutes are up. The tally also keeps a running total of how many scores arrived in the current ten minutes and the current day, with nothing about who sent them.
Link battles in the Battler
The Battler can link two players, the way a cable linked two Game Boys: Battle a friend sends a link or a six-letter code, and Find an opponent pairs you with whoever else is searching. Everything else in the Battler runs in your browser, but a link battle cannot: while the battle is on, your team and each move you pick travel through this site’s server (a small program at Cloudflare) to the other player, and theirs come to you the same way. The server hands them on and writes none of them down. No team, name, code or move is stored, and the room is gone once you both leave.
Two small things are kept, and neither says who you are. The matchmaking queue notes the time a battle started, so the Battler can say how many trainers found a battle in the last half hour; it only ever counts the last half hour, and older times are deleted the next time it updates. And when someone has waited 20 seconds for an opponent, or a link battle starts, the site may post one fixed line to a private Discord channel of mine, such as “A friend battle started.”, at most 40 times a day. That line never carries a name, team, room code or address. Like every request here, the connection itself passes through Cloudflare, as described above.
Counting AI readers
When an AI assistant or an AI crawler fetches a page here, say ChatGPT looking something up for someone, or Bing's crawler, the site adds one to a count kept with Cloudflare: which bot it was (by the name it calls itself), which page, when, and whether the page loaded. That is how I can see which pages AI tools read. It only happens when the request names itself as one of those bots, so a person visiting in a browser is never counted, and no IP address, browser details or anything else about the request is stored with it. Cloudflare keeps these counts for three months.
Counting where visits come from
Ad blockers hide a lot of visits from Analytics, so the site also keeps its own plain count of page visits. When a person loads a page here, the site adds one to a count kept with Cloudflare: which page, when, the site that sent you (only its name, like google.com or reddit.com, never the page you were on there), the campaign tags in the link if it has any (the utm_source, utm_medium and utm_campaign bits you sometimes see on shared links), your country, and whether you are on a phone, a tablet or a computer. That is the whole list. This count sets no cookies, stores no IP address and no browser details, and nothing in it can tell one visitor from another. Bots and crawlers are not part of it. Cloudflare keeps these counts for three months.
My own visits are left out of this count and out of Analytics. My browsers carry a small flag named gf_me, kept in a cookie and in local storage for this site only, that tells the site it is just me checking my own pages. Your browser never gets that flag unless you set it on purpose.
The contact form
The contact page has a form for sending me a message. It asks for three things: your name and your email address, both optional, and the message. Without an email address I can still read what you wrote, but I have no way to answer it.
When you press send, the site passes your name, email address and message straight to a private Discord channel of mine. The site keeps no copy: nothing you wrote is stored here or on my own server, or written to a log, and it does not go to any AI, including the AI tools that help me run the site. Discord keeps the message the way it keeps any other message, so Discord's privacy policy applies to it too, and it stays there until I delete it. Think of it as about as private as an email, and please do not send anything you would not put in one.
To keep the form from being flooded, the site counts how many messages arrive from each network address. It never stores your IP address for this. It turns the address into a scrambled code (a salted hash) using a key that changes every day, and throws the code and the key away when the day is over. It also keeps a running total of how many messages have come in, and nothing else about them. The form also has a hidden box that only robots fill in, and it turns away a message sent faster than a person could write one.
When a message goes through, Analytics records that the contact form was used, and nothing about what you wrote.
YouTube embeds
Some pages embed videos from my YouTube channel. Those embeds use the youtube-nocookie.com domain, which is YouTube's privacy-enhanced mode: it does not set tracking cookies for personalized advertising unless you actually press play. Once you hit play, you are interacting with YouTube, and Google's privacy policy governs from there.
Things this site does not do
- No accounts, no passwords, no logins.
- No newsletter and no email capture.
- No purchases, no payments, no card data. Nothing here is for sale.
- No selling, renting, or trading of personal information to anyone, ever.
- No sharing of data beyond the companies above, each doing the job described: Google, Cloudflare, Discord, and the ad companies that serve ads here through Google AdSense.
- No AI reading your contact form message. Everything in it except the message is optional, so you decide what I know.
If you are in the EU or the UK (GDPR)
Under the GDPR and the UK GDPR you have rights over your personal data, and two legal bases apply here. Legitimate interest covers the basics of running a website: serving you the page you asked for, keeping it secure, and understanding at an aggregate level which articles people find useful. Consent is the right basis for advertising and analytics cookies, and I want to be straight with you about where that stands: this site does not show a cookie consent message yet, so those cookies can be set as soon as a page loads. Until a consent message is live, you can make that choice yourself. Block or clear this site's cookies in your browser, install the Analytics opt-out add-on, and turn off personalized ads with the links above. Nothing here will nag you to turn them back on.
Your rights include the right of access (ask what is held about you), the right to erasure (ask for it to be deleted), the right to object to processing, the right to rectification, and the right to restrict processing. In practice I hold almost nothing that could identify you beyond what you chose to send me through the contact form, so most requests resolve to "there is nothing here with your name on it," but you are entitled to ask and I will answer honestly and within a month. Email chris@gardenflouer.com. For data held by Google or Cloudflare rather than by me, their own policies linked above describe how to make a request directly to them, which is faster than routing it through me.
You also have the right to lodge a complaint with your local data protection authority if you think something here is being handled badly. I would appreciate an email first so I can fix it, but that right is yours regardless.
If you are in California (CCPA and CPRA)
I do not sell your personal information. I have never sold it, there is no arrangement under which I would, and there is no "Do Not Sell" toggle here because there is nothing to toggle off.
California residents have the right to know what categories of personal information are collected, the right to request deletion, the right to correct inaccurate information, and the right not to be discriminated against for exercising any of those rights. The categories collected here are the ones described above: internet activity such as page views and inferred approximate location from an IP address, through the third-party services named, and whatever you choose to write in the contact form. To make a request, email chris@gardenflouer.com.
Children
This site is not directed at children under 13, and I do not knowingly collect personal information from anyone under 13. There is no signup here and no profile to fill in. The only form is the contact form, where a name and an email address are optional, which removes most of the ways a site would collect that information in the first place.
If you are a parent or guardian and you believe a child has somehow provided personal information through this site, email me at chris@gardenflouer.com and I will delete whatever there is to delete. I write about a game from 1996 that a lot of us met as kids, so I take this one seriously.
Changes to this policy
If the tools on this site change, this page changes with them, and the new version gets posted right here with an updated effective date at the top. I am not going to email you about it (no list, remember), so the date line is the honest signal. Material changes will be described plainly rather than buried in a paragraph of legalese.
Questions
Privacy questions, data requests, or "hey, this section is out of date" corrections all go to the same place: chris@gardenflouer.com. A real person reads it. More on how to reach me is on the contact page, and the rules for using the writing and tools here are on the terms of use page.