ChefsPost

Privacy Policy

Short version: this site is one person — me, Hannah — running a kitchen-gear review blog on a basic hosting stack with one analytics tool. What's below is the actual list of what happens when you load a page on chefspost.com. If anything is unclear, the email at the bottom is the one I read every day.

What I collect

When you load a page here, the hosting provider records the request — IP address, browser, the page itself, a timestamp, and the referring URL. That is the same baseline log file almost every website creates, and is required for the server to function. I don't run signup forms, comment sections, or user accounts. No email, name, or password is stored anywhere on my side.

Cookies

One cookie type: a visitor/session identifier used by the analytics tool described below. No advertising cookies. No remarketing pixels. No cross-site tracking. Block cookies in your browser if you want; nothing on the site breaks.

Analytics

I use an analytics service to collect anonymized usage data (page views, browser type, country code, referrer). No personally identifiable information is collected. The service does not pass any of this to advertisers, and I do not use it to build a profile of you as an individual visitor. I open the dashboard maybe once a week, mostly to see which gear reviews are landing and which ones I might as well have written for myself.

Affiliate links

Some outbound links here are affiliate links — meaning I get paid a small commission when you buy through them, at no extra cost to you. I don't collect or store any data about which links you click; that's strictly between you and the merchant. Commission does not change which products end up reviewed or how I write about them. For more on how the editorial side handles affiliate relationships, see my Editorial Policy.

Data retention

Server logs: 30 days, then deleted. Individual analytics session data: purged within 30 days. Only the aggregate (page-view counts per article per month) is kept beyond that window, and the aggregate contains nothing tied back to a specific visitor.

Your rights

If you are in the EU/EEA, the UK, or California, you have specific rights over personal data that might relate to your visit. I extend the same handling to anyone else who asks. Under GDPR Articles 15-22:

In practice, because I do not run accounts and the analytics is already anonymized, there is usually nothing personal on my side to access or erase. The email below is still the channel if you want to confirm.

Contact about privacy

Email me at hannah@chefspost.com with the word "privacy" anywhere in the subject. I read this inbox daily and usually reply within a couple of days. There is no separate privacy team — it's me, on a laptop, in Madison.