Cookie Policy

Effective date: 30 July 2026 | Last updated: 27 October 2026

This policy explains the cookies and similar technologies used on oguzerol.com, what they are for and how to manage your preferences. It has been prepared with reference to the Turkish Personal Data Protection Authority’s Guidelines on Cookie Practices.

1. Data controller

Oğuz Han Erol (sole proprietorship registered in Türkiye)

Göztepe Mah. Tepegöz Sk. İkar İş Merkezi 1 İç Kapı 8, 34730 Kadıköy / Istanbul, Türkiye

Göztepe Tax Office | Tax ID (VKN): 3670133479

oguz@oguzerol.com | +90 549 654 64 89

A cookie is a small text file saved to your browser when you visit a website. It lets the site remember you, keep your preferences and measure how it is used. In this policy “cookie” also covers pixels, web beacons, local storage and similar tracking technologies.

Cookies are distinguished in two ways:

First-party / third-party: is the cookie set by this Site, or by another organisation such as Google or Meta?
Session / persistent: is it deleted when you close the browser, or does it stay for a set period?

On your first visit a cookie panel appears at the bottom of the page. The “Accept” and “Reject” buttons are equally prominent, next to a link to this policy. Your choice is stored in your browser’s local storage (localStorage, key oe_cerez_onayi) as “accept” or “reject”. The panel works the same way on the Turkish and English pages.

If you reject, or have not yet chosen: Meta Pixel and the Meta Conversions API do not run. Google tags (Google Analytics 4 and Google Ads, delivered through Google Tag Manager) do not write cookies. Only the strictly necessary technologies (4.1 below) are used.
If you accept: Google tags run in full and Meta Pixel and the Meta Conversions API start (4.2 and 4.3 below).

Google Consent Mode v2: Google tags are delivered through Google Tag Manager (container ID GTM-5DBXXCD, loaded from the Site’s own domain via Cloudflare). By default ad_storage, ad_user_data, ad_personalization, analytics_storage and personalization_storage are set to “denied”, while functionality_storage and security_storage are “granted”. When you accept, the first five become “granted”. Please note: if you reject or have not chosen, Google tags do not write cookies, but by the way Consent Mode works, cookieless, aggregate measurement signals may still be sent to Google. These signals are not used to identify individual visitors, yet some connection data (for example an IP address) does reach Google’s servers.

Meta: Meta Pixel (pixel ID 4582499955214965) and the server-side Meta Conversions API, which runs through the Site’s own /api/m endpoint, start only if you accept. After acceptance these events are sent: page view (PageView), a click on a WhatsApp / phone / email link (Contact), and browsing five different pages in one session (ViewedFivePages). For the last event a local record named oe_oturum is kept in your browser. If you submit the contact form and have accepted, the email address, phone number and name from the form are hashed with SHA-256 and sent to Meta as a “Lead” event; if you have not accepted, this event is not sent.

You can change your choice at any time. The “Cookie settings” button at the end of the legal links at the bottom of the page reopens the panel. If you accept and later reject, the Meta cookies (_fbp, _fbc) are deleted and the page reloads. Withdrawal takes effect from the moment you withdraw; it does not retroactively delete data already processed. To ask for deletion of data already sent to Meta, see the application route in the Data Protection Notice.

Required for the Site to work, stay secure and remember your preferences.

Cookie / technology	Party	Purpose	Duration
`oe_cerez_onayi` (localStorage)	First party	Remembering your choice in the cookie panel (“accept” / “reject”)	Until you clear browser data or change the choice
`oe-theme` (localStorage)	First party	Remembering your light / dark theme preference	Until you clear browser data
Cloudflare security cookies (e.g. `__cf_bm`, `cf_clearance`)	Third party	Distinguishing bot traffic, blocking attacks and abuse	Set by the provider (typically 30 minutes – 12 months)
Cloudflare Turnstile	Third party	Protecting the contact form and the /analiz (analysis) tool from automated submissions	Page session / set by the provider

4.2. Analytics and Google advertising cookies (cookies are written only if you accept)

These relate to the Google Analytics 4 and Google Ads tags loaded through Google Tag Manager. They are used to measure how the Site is used, to see which advertising produces results and for remarketing. If you have not accepted, these cookies are not written (for Consent Mode’s cookieless signals, see section 3).

Cookie	Party	Purpose	Duration
`_ga`, `_ga_<container ID>`	Google Analytics 4	Distinguishing visitors and sessions	Set by the provider (typically 24 months)
`_gcl_au` and similar Google Ads cookies	Google Ads	Matching an ad click to a conversion, remarketing	Set by the provider (typically 90 days)
`IDE`, `test_cookie` (doubleclick.net)	Google	Ad delivery and performance measurement, when remarketing is in use	Set by the provider

4.3. Meta cookies (only if you accept)

Meta Pixel and the Meta Conversions API start only when you accept. They are used to measure advertising and to be able to show ads to relevant audiences on Meta’s ad network.

Cookie / technology	Party	Purpose	Duration
`_fbp`	Meta	Identifying the browser for ad measurement and remarketing	90 days
`_fbc`	Meta	Recording the click if you arrived by clicking a Meta ad	90 days
`oe_oturum` (localStorage)	First party	Counting how many different pages you browse in one session (for the five-page event); only after acceptance	Until you clear it; the counter resets after 30 minutes of inactivity
`fr`	Meta (facebook.com)	Ad delivery and measurement on Meta’s own domain	Set by the provider (typically 90 days)

4.4. Embedded content and external links

Some pages contain an embedded YouTube video. When the player loads, YouTube / Google may set its own cookies; this content is not separately blocked by the choice in the cookie panel. Pages without an embedded video do not load it.

About the WhatsApp link: The WhatsApp button on the Site sets no cookie; it redirects you to WhatsApp. Once you start a conversation, that exchange takes place on Meta’s infrastructure and is subject to Meta’s own privacy terms. If you have accepted, clicking the button is sent to Meta as a “Contact” event.

Outside Türkiye: The servers of service providers such as Google, Meta and Cloudflare may be located outside Türkiye (for example in the United States); see the Data Protection Notice for details.

5. Managing your preferences

On this Site

Click the “Cookie settings” button at the end of the legal links at the bottom of the page to change your accept or reject choice at any time.

In your browser

All browsers let you view, delete and block cookies:

If you block strictly necessary cookies at browser level, parts of the Site may not work correctly.

Through the advertisers’ own tools

6. Data processed via cookies, and your rights

Data processed through cookies may qualify as personal data. For the legal bases, international transfers and your rights under Article 11 of Law No. 6698, see the Data Protection Notice. For general data practices, see the Privacy Policy.

7. Changes

This policy is updated when the technologies used on the Site change. The current version is always published on this page and the date at the top is updated. The cookie list may differ slightly from what you actually see in your browser; if you notice such a difference, please let me know at oguz@oguzerol.com .

8. Contact

Oğuz Han Erol