TR EN

Cookie Policy

Last updated: 27 October 2026

A cookie is a small note a site leaves in your browser. Two strictly necessary cookies are always set here. If you allow Google Analytics, Google’s script writes two measurement cookies on this domain as well; if you do not, it writes nothing.

The cookies on this site

All of them belong to this domain and all of them stay inside your browser. The two necessary cookies hold only the choice you made. The Google Analytics cookies carry a random identifier: it holds no name or email address, but it links visits from the same browser together.

CookieWhat it doesLifetimeType
cdr-langRemembers the language you chose, so the bare domain takes you straight there.1 yearStrictly necessary
cdr-cerezRemembers your answer to the cookie banner, so the question does not come back on every page.180 daysStrictly necessary
_gaA random identifier Google Analytics uses to tell your browser apart. Set only if you allow it.180 daysAnalytics (consent required)
Cookie starting with _ga_Session state Google Analytics uses to follow your current visit. Set only if you allow it.180 daysAnalytics (consent required)

One record that is not a cookie: your display preference

When you press the light/dark button in the top bar, your browser saves your choice in its own local storage under the name cdr-mod. It is not a cookie: it never reaches the server, it stays in your browser and it has no expiry; it remains until you delete it or return to your system setting with the same button. If you never press the button, nothing is written and the site follows your operating system's light or dark preference.

A second record that is not a cookie: the newsletter card

The first time you visit, a newsletter card opens in the bottom right corner. When you press its close button or subscribe through it, your browser saves this in its own local storage under the name cdr-bulten; the value is only “kapandi” (closed) or “abone” (subscribed). That record is how the card knows not to open again. It is not a cookie: it never reaches the server, it stays in your browser and it has no expiry; it remains until you delete it. If your browser has local storage switched off, the same value is kept only while the tab stays open (sessionStorage).

The record does not identify you and does not contain your email address. If you subscribe through the card, CDR Türkiye handles your address exactly as it does for the form in the footer, as the KVKK notice describes.

A counter that uses no cookies: Cloudflare Web Analytics

Every page on the site runs a small counter script from Cloudflare. The script comes from static.cloudflareinsights.com and sends which page opened, where you came from, your country, browser, operating system and device type, and how long the page took to load to cloudflareinsights.com. It leaves no cookie or local record in your browser and does not recognise you from one visit to the next, which is why the banner does not ask about it. The count is made by Cloudflare, Inc., which already hosts the site.

A check that uses no cookies: Cloudflare Turnstile

The contact page runs Cloudflare’s Turnstile script. It comes from challenges.cloudflare.com and sends some technical signals from your browser to Cloudflare to confirm that the form is being sent by a person. It does not read what you type into the form and sets no cookie on this domain. It is a security measure against abuse of the form, so the banner does not ask about it, and it loads on no other page.

What the site does not use

The list is long because the site leaves out a great deal:

  • No analytics cookies without your consent: the Google Analytics cookies are set only when you choose Accept.
  • No advertising or targeting cookies.
  • No social plugins, share or like buttons or embedded video. Links to the official LinkedIn and YouTube accounts and videos are plain links: they send nothing until you click, and once you do, that platform’s own policy applies.
  • Fonts come from the site’s own server, not a CDN.
  • No login, no basket, no profile: the site has no notion of an account.

What the banner does and does not claim

The banner you see on your first visit asks one thing: may Google Analytics run? The two necessary cookies sit outside that question, because the site needs them to work and to remember your choice, and necessary cookies do not require consent.

The banner went up while there was nothing on the site to refuse, so that the consent mechanism would be ready on the day the first measurement script arrived. That day has come: Google Analytics loads only if you allow it through this banner.

If you chose Accept before Google Analytics was added, the banner asks again: the site had no Google Analytics then, and your answer did not cover it. If you chose Reject, your answer stands and Google Analytics does not load.

What accept and reject actually do

The mechanism is real. Google Analytics enters the page in an inert state and only becomes live if you accept. If you reject, the script never runs and no request goes to Google: what is blocked is the script itself, not merely the data it would send.

Rejecting breaks nothing. No page depends on consent: every article, every diagram and the newsletter form behave the same either way.

The site does have to remember a rejection; otherwise the question would come back on every page. That is why cdr-cerez, the cookie holding your answer, counts as strictly necessary too.

Changing your mind

The “Cookie preference” button at the bottom of every page reopens the banner, and you can switch your answer whenever you like.

If you switch from Accept to Reject, the site stops Google Analytics on that page and deletes the cookies whose names start with _ga. Data already sent to Google remains subject to Google Analytics’ two-month retention period.

You can also delete all of these cookies in your browser settings. The site then forgets your language and your cookie answer, and the banner comes back; nothing else is lost.

With JavaScript switched off

The site works without JavaScript: navigation, the newsletter form and all content stay in place. Only the contact form needs JavaScript, for its security check; without it, write to contact@cdrturkiye.com. The banner does not appear either, because there is nothing to ask: browser-side scripts start both the cookies and the two counters, and with no script there is no cookie and no count.

Questions

Cookies matter for data protection as well. The KVKK notice sets out what CDR Türkiye processes, on what legal ground, and what you can ask of it.

KVKK Notice