Cookie policy

Last updated 18 September 2026

Cookies are small files a site asks your browser to keep. gazete.tv sets none that follow you. Today the site stores only what it needs to show you the page you asked for, in the way you asked for it, so there is no consent bar to click away.

The short version

Nothing on gazete.tv tracks you, and nothing here is handed to an advertising network.

The advertising slots are our own images, served from our own domain. No ad script, no ad server, no advertising identifier.
Audience measurement is cookieless and aggregate: we count pages, not people, and store nothing that could be tied to you.
What is kept on your device is functional: the theme you picked, the edition you read, the stories you saved. You asked for each of those by using the site.

None of that needs your permission under the Turkish KVKK or the European ePrivacy rules, so we show no consent bar. We would rather not ask a question whose only honest answer is “there is nothing to allow”.

What is stored on your device

Everything below is set by gazete.tv itself, holds no identifier for you as a person, and is readable only by your own browser. All of it is necessary in the sense the law uses: functional, asked for by you, and not used for anything else. “Local storage” is a store in your browser that is never sent with a request; only gz_lang is a cookie, and it is ours.

gz-theme — light or dark, whichever you picked. Local storage, kept until you clear your browser data.
gz-lang — the edition you chose in the language menu. Local storage, same lifetime.
gz_lang — the same two-letter code as a first-party cookie, so that opening gazete.tv sends you straight to your edition. It holds the code and nothing else, and lasts one year. This is the one entry our server reads, and only for that.
gz-lang-bar — that you have dismissed the “read this in your language” bar, so it does not come back. Local storage.
gz-saved, gz-follow, gz-read — the stories you saved, the threads you follow, and which stories you have already opened, so a card can be marked as read. Lists of story ids on this device. Local storage, kept until you remove them or clear your browser data.
gz-searches — your recent searches on this device, so the search box can offer them again. Local storage.
gz-city, gz-sport, gz-fx, gz-fx-dir, gz-fx-amount, gz-fx-period, gz-stats-period, gz-editor-open — small display preferences: the city for prayer times, the sport you last looked at, the currency, the period on the statistics page, whether the editor’s note is open. Local storage.
gz-consent — your answer to the consent bar, on the day there is one to answer. Local storage, valid six months, then asked again.

There is no session cookie for reading, because there is no session: the pages are static files.

Neither exists yet. When they do, two more entries appear, and both are necessary: without them a signed-in reader would be signed out on every page.

gz_session — that you are signed in, as a first-party cookie, HttpOnly, Secure and SameSite=Lax, holding a random session identifier and nothing about you. Set only after you sign in with Google or Apple, cleared when you sign out, and expiring after 30 days of not being used. Necessary: this is the sign-in.
gz_member — whether the account is a current member, as the App Store or Google Play reports it, so the page can be built without the advertising slots. First party, the same lifetime as the session, holding a yes or a no. No payment data: we never receive any. Necessary: it is what makes the thing you paid the store for work.

Neither is an advertising or a measurement cookie, neither is shared with anyone, and neither needs consent, because they do only what you asked for by signing in.

A member is shown no adverts, so no advertising cookie or identifier is ever set for a member — not today, when there are none for anyone, and not on a day when the advertising flag is on for everyone else.

Server logs are not cookies

Our host records each request — the address it came from, the time, the page — whether or not you have any cookies at all. That is described in the privacy policy and it cannot be switched off, because a web server cannot answer a request it never receives.

If we ever need to ask

The switch is one file, src/config/consent.ts, with three flags: third-party advertising, measurement that sets an identifier, and third-party embeds such as a video or a post from another site. All three are off.

If the publisher turns one on, the site changes with it on the same day:

A consent bar appears at the bottom of the page, with two buttons. Only necessary is the default and the emphasised one; that is the house rule and it does not change. Accept all is the other.
Tags in the category that needs permission ship parked and inert, and are made live only after you press “Accept all”. Until then they are not loaded, not requested, and set nothing.
Your answer is kept under gz-consent with the date you gave it, stands for six months and is then asked again. It never leaves your device.
A cookie preferences link appears in the site menu and on this page, so you can change your mind from anywhere. The change takes effect on the next page you open.
This page gains an entry for every cookie or identifier the new partner sets, who that partner is, and what they do with it. Those partners act as their own data controllers for their own processing, and their own notices say what they keep.

Even then, choosing “Only necessary” leaves the page whole: the advertising slots fall back to the fixed images from our own domain, with no script and no identifier, exactly as they are today.

Your browser

Every browser can block or delete cookies, and most can block third-party cookies entirely. Doing so will not break gazete.tv: nothing on the site needs a cookie to work. You will simply pick your theme and your edition again on the next visit.