I’ll be honest with you from the start. This site, claudecodeai.blog, exists because I kept bumping into the same walls while working with Claude Code and decided that writing it all down was more useful than keeping it in my head. It’s a personal blog, not a startup. There’s no team behind it, no data scientists in a back room, and no product roadmap that depends on knowing your life story.
What this site collects and why
If you just read an article
The web server logs that a request came in from an IP address at a particular time. That happens automatically on every server on the internet — it’s more like a till receipt than a surveillance file. I’m not personally reading through those logs to figure out who you are. They roll over on whatever schedule my hosting provider uses and then they’re gone.
I use basic analytics to understand things like which articles are getting read and whether anyone makes it to the end of a post. That tells me whether a topic is worth following up on. It’s not tied to your name or any identity — it’s just numbers that help me write better content.
If you leave a comment
You’ll enter a name and an email address. The name shows up next to the comment publicly — whatever you put in is what people see, so using a first name or a username is completely fine. The email stays private and is used by WordPress and spam filtering (Akismet runs in the background) to make sure you’re a real person rather than a bot trying to drop links everywhere.
Your IP address is also logged alongside the comment. That’s standard comment moderation practice, not an attempt to track your physical location. If you ever want a comment deleted or changed, reach out and I’ll sort it.
If you use the contact form
Whatever you write comes to me by email. I won’t forward it, won’t share it, and won’t add your address to any list. I reply when a reply makes sense, and that’s the end of it.
Cookies
WordPress places a handful of cookies of its own. If you comment and save your details for next time, a cookie remembers that. If there’s a logged-in session — that would only be me as the admin — there’s a session cookie for that too. Standard WordPress behavior.
Any embedded third-party content — a YouTube video, a tweet, a GitHub gist — can load its own cookies when the page renders. I have no control over what those platforms track on their end. If that’s a concern, a browser extension like uBlock Origin handles most of it without you needing to do anything else.
Google AdSense and advertising
This is the section worth paying attention to if you care about ads.
I use Google AdSense to display ads on this site. Google is what’s called a “third-party vendor” — they serve ads based on your browsing history and interests, and they use cookies and similar technologies to do that. The ad you see on this page might be different from what someone else in a different country or with different browsing habits sees.
Here’s what that means practically:
- Google may use cookies to serve ads based on your prior visits to this site and other sites across the web.
- You can opt out of personalized advertising by visiting Google’s Ads Settings.
- You can also opt out through the Network Advertising Initiative opt-out page.
- Alternatively, you can visit aboutads.info to opt out of personalized ads from third-party vendors.
I don’t control which ads Google chooses to show. I’ve set the site up with AdSense and let Google handle the targeting. What I can tell you is that I’m not sending Google any information that personally identifies you — Google builds its own picture of users based on their own data.
For a full breakdown of how Google collects and uses data from ads, you can read Google’s Privacy & Terms page.
Third-party services I use
Running any website means depending on other companies for the basics. There’s a hosting provider keeping the server online, possibly a CDN making pages load faster in different parts of the world, and email infrastructure for notifications. They access data only to the extent they need to do their jobs. I’m not passing anyone a list of readers and saying “here’s a marketing database, go nuts.”
The services most relevant to this site are:
- Google AdSense – for displaying ads (see full section above)
- WordPress / Automattic – the platform this site runs on
- Akismet – spam filtering for comments
- Web hosting provider – server infrastructure and logs
How long things are stored
Comments stay up until I delete them or you ask me to remove yours. Server logs cycle through on the host’s schedule — usually somewhere between a few weeks and a couple of months. Backups exist for disaster recovery, which means older data might sit in a backup archive for a while before it’s fully gone. That’s just how backups work, not a deliberate decision to hang onto your information.
If you’re visiting from outside the US
My hosting and the main tools I use are US-based. If you’re in Europe, the UK, or anywhere else, your data may cross borders simply because that’s how the internet works. I’m running a small personal blog, not a multinational operation, but I’m flagging it because certain privacy laws — GDPR included — require transparency on this point.
Your rights
If you’ve left a comment and want to know what information is attached to it, want it corrected, or want it removed entirely — email me and I’ll take care of it. I’m one person running this site, so you’ll get an actual reply, not a ticket number.
If you’re in the EU or UK, you have rights under GDPR or the UK equivalent — including the right to access, correct, or delete personal data I hold about you. Same process: just email me.
Contact: contact@claudecodeai.blog