You did not see a cookie consent box in the corner of this site. You were not missing it. There isn't one, and the reason is simple: we have nothing to ask you about.
What we store
One cookie, called ts_lang. It holds a single piece of information: the language you picked. It is not written on its own either. It appears only when you click the language switcher and choose Turkish, English or German, so that your next visit opens in the same language.
If you sign in as a member, a session cookie is added. That one remembers you are logged in, and the panel cannot work without it.
That is the whole list.
What we do not run
- No analytics. No Google Analytics, no Tag Manager, none of it.
- No advertising pixels.
- No heatmaps, no session recording, no mouse tracking.
- Our fonts come from our own server. Opening a page does not send a request to another company for a typeface.
- No embedded maps. Some articles do carry video, and those load from YouTube's no-cookie domain, so nothing is written until you press play. Once you do, the video is YouTube's business.
So why is no banner needed?
Consent is required for cookies that are not necessary. A session cookie is necessary, you cannot log in without it. A language preference is an interface setting written by your own click. Neither of those falls into the group that needs permission, in Europe or in Turkey. What they do need is disclosure, and our cookie policy handles that.
The rules in the United States are built around selling and sharing personal information. Nothing is tracked here, so there is nothing to opt out of.
One thing we should say plainly: this is not legal advice. It is the decision we made for our own site. If your site runs trackers, your situation is a different one.
Why we chose it this way
Let us be honest, analytics would help us. We would like to know which article gets read and where people give up. But it has a price: a question put to every visitor, a box in front of the page, and a pile of data you then have to look after.
We are an agency that audits cookies on client sites. Running a tracker we do not need on our own site would not add up.
What do we use instead? We follow the search side in Search Console. It works on the server and writes nothing to your browser.
One more thing worth saying: this is not one developer's preference, it is a decision Türk SEM management took together. We talked it through, put what analytics would give us next to what it would cost the visitor, and settled on this. We hold our own site to the standard we apply on our clients' sites, because otherwise we would have no business auditing theirs.
What if that changes one day?
If we add analytics, the banner comes with it, and it comes built properly: not one line of tracking code runs before you say yes. When that day arrives we will update this article rather than delete it. That is what this section is for. You get to see the history of a decision, not only its result.
