When you visit this site, a few things happen automatically — your browser sends us some basic technical data, like your IP address, browser type, the pages you looked at, and roughly how long you spent on them. We collect this through standard analytics tools. It's not glamorous information, but it helps us understand what's working on the site and what isn't. We don't ask for your name or email just to read a review.
If you choose to contact us — through a contact form or by email — then yes, we'll have whatever you decided to share with us. That might be your name, your email address, and whatever message you sent. We keep that information only as long as it takes to respond to you and sort out whatever you got in touch about. We're not building a database of readers here.
We also use cookies. Some are strictly necessary for the site to function at all. Others are analytics cookies that track aggregate behavior — not individual profiles. You can adjust cookie preferences through your browser settings at any time, and the site will still work if you do.
Honestly, the uses are pretty limited. The technical data we collect automatically gets used to monitor site performance, fix errors, and get a general sense of which content is being read. We look at it in aggregate — page views, session lengths, that sort of thing — not at individual users moving through the site one by one.
If you contacted us, we use your details to reply. That's it. We don't add you to a mailing list, we don't pass your email to third parties, and we don't use it for advertising purposes. Once the conversation is resolved, we don't have much reason to hold onto it.
We may share anonymized, aggregated data with analytics providers — but that data can't be traced back to any individual. No personal information is sold. Ever. That's a line we're not interested in crossing, and we want to be clear about it upfront.
This site uses a small number of third-party tools to keep things running. Google Analytics is one of them — it helps us track traffic patterns without identifying individual visitors. Google has its own privacy practices, and if you're curious about how they handle data on their end, their documentation covers that in detail. We configure Analytics to anonymize IP addresses where possible.
Some pages on this site may contain affiliate links to online casinos. Clicking those links may set cookies from those third-party sites — that's outside our control. We don't receive any personal data from those clicks, just aggregated reporting on whether a click happened. What those external sites do with your data once you land on them is governed by their own privacy policies, not ours.
We may also use a content delivery network to serve the site faster. These services may log request data including IP addresses as part of normal operation. Again, this is standard infrastructure stuff, not targeted data collection.
Depending on where you're based, you may have certain rights over your personal data. If you're in the European Economic Area, the UK, or California, for example, you likely have the right to request access to any personal data we hold about you, ask for it to be corrected or deleted, or object to certain types of processing. These rights aren't just theoretical — we take them seriously.
If you want to make a request, get in touch with us directly. We'll do our best to respond within a reasonable timeframe. There are cases where we might not be able to delete data immediately — if we're legally required to retain it for a period, for instance — but we'll explain that clearly if it applies. We won't make it difficult.
You also have the right to lodge a complaint with a data protection authority in your country if you feel your rights haven't been respected. We'd genuinely prefer to sort things out directly first, but that option is yours to use if needed.
Privacy policies aren't really set-and-forget documents. As the site evolves, as tools change, as regulations shift — the way we handle data may need to shift too. When that happens, we'll update this page to reflect the current reality. The date of the most recent revision will be visible at the top of this page.
We won't notify every reader individually when something changes — that's just not practical. But we do encourage you to check back here occasionally if this kind of thing matters to you. We'll try to write changes in plain language rather than dense legalese, so it's actually readable.