Privacy Policy

Last updated: November 6, 2026

This is a personal blog. I’m Uğur Çoban, and I run it on my own from Istanbul, Türkiye. Nothing is sold here and you don’t need an account to read it. The site still handles some personal data. Your IP address and browser details reach my hosting and security providers on every visit. Google Analytics and Jetpack Stats run on the pages. If you write to me, comment or subscribe, I get what you send. This page explains each of those uses: what data, why, the legal basis, who else receives it, how long it is kept and what you can do about it. It is a notice. It does not ask you to agree to anything.

Who is responsible for your data

The controller (the “data controller” under Turkish law) is Uğur Çoban, who runs this site as a sole proprietor registered under his own name with the Maslak Tax Office in Istanbul, Türkiye.

You can reach me through the contact form at https://ugurcoban.com/contact/. Privacy questions and requests go the same way, and I answer them in writing by email. KVKK applications have their own KVKK request form (in Turkish).

I have not appointed a data protection officer. I have not appointed a representative in the European Union or in the United Kingdom.

What this policy covers

It covers ugurcoban.com: reading posts, the contact form, comments and email subscriptions to new posts. It does not cover other websites I link to; they have their own policies.

The cookies are described in more detail in the Cookie Policy. The rules for using the content and the comment section are in the Terms and Conditions.

I live in Türkiye, so this policy starts from the Turkish Personal Data Protection Law (KVKK, Law No. 6698). Many readers are in the United States, the European Economic Area (EEA), the UK and Switzerland, so it also has sections for readers covered by the EU General Data Protection Regulation (GDPR) or the UK GDPR, and for readers in the US.

What I process, why, and on what legal basis

Each entry below covers one use of personal data. It says what data is involved, how it is collected, why, the legal basis under the GDPR and under KVKK, who receives it and how long it is kept.

Delivering the site: server and CDN logs

  • Data: IP address, browser user agent, the address of the page you request, and the date and time of the request. GoDaddy’s hosting platform also loads a small performance script (from img1.wsimg.com) that measures how fast the page loads in your browser.
  • How it is collected: automatically. Your browser sends this with every request. Requests pass through Cloudflare, which sits in front of the site, and then reach my host, GoDaddy.
  • Why: to send you the pages, keep the site running and find errors.
  • Legal basis (GDPR): legitimate interests, Art. 6(1)(f). My interest is running a website that works and stays online.
  • Legal basis (KVKK): Art. 5(2)(f), legitimate interest.
  • Who receives it: GoDaddy (hosting) and Cloudflare (content delivery network and security).
  • How long: GoDaddy and Cloudflare keep their logs for the periods set by their own terms.

Security and bot protection

  • Data: IP address, browser user agent, TLS fingerprint and similar technical signals. On the contact page and in the comment form, Cloudflare Turnstile processes your IP address, TLS fingerprint, user agent, and the site key and origin of the form. On the WordPress login page, failed login attempts are recorded with the IP address and the username tried.
  • How it is collected: Cloudflare sets a __cf_bm cookie on every response to tell people from bots. Cloudflare Turnstile runs a check on the contact form and the comment form. Jetpack Protect watches login attempts. GoDaddy’s WordPress security layer can show a captcha (from captcha.wpsecurity.godaddy.com) when traffic looks automated.
  • Why: to keep bots, spam and attacks away from the site, the contact form and the comment form.
  • Legal basis (GDPR): legitimate interests, Art. 6(1)(f). My interest is protecting the site and its readers from abuse.
  • Legal basis (KVKK): Art. 5(2)(f), legitimate interest. The KVKK Board’s cookie guidance treats security cookies as strictly necessary.
  • Who receives it: Cloudflare, Automattic (Jetpack Protect) and GoDaddy. Cloudflare also uses Turnstile signals, as a controller in its own right, to improve its bot detection. See the Turnstile Privacy Addendum.
  • How long: the __cf_bm cookie expires after 30 minutes without activity. Other security records are kept by each provider for the periods set by its own terms.

Visit statistics: Google Analytics 4

  • Data: the pages you view, how you arrived (referring site or campaign link), device and browser type, screen size, language, approximate location (country and city, worked out from your IP address) and, where the cookies are set, a random identifier stored in the _ga and _ga_1GCFPH8WPK cookies. Google states that GA4 does not log or store IP addresses.
  • How it is collected: Google Site Kit, a WordPress plugin, adds Google’s tag (gtag.js, loaded from googletagmanager.com) to every page. What happens next depends on where you are. In the EEA, the UK and Switzerland, analytics storage starts as “denied” and stays that way, so no Analytics cookies are set and the tag sends only cookieless pings to Google. In Türkiye, analytics storage also starts as “denied”, and a consent banner in Turkish asks whether you allow the Analytics cookies. They are set only after you click “Kabul et” (Accept). Until then, and if you refuse, the tag sends only cookieless pings. Elsewhere, for example in the US, the Analytics cookies are set when the page loads, and you can block them with the controls in the Cookie Policy. The section How Google Analytics behaves where you are explains this.
  • Why: to see which posts people read, where visits come from and what to write next.
  • Legal basis (GDPR): legitimate interests, Art. 6(1)(f), for the cookieless pings sent from the EEA, the UK and Switzerland. My interest is understanding how the site is used. No Analytics cookies are set for visitors there.
  • Legal basis (KVKK): Art. 5(2)(f), legitimate interest, for the cookieless pings sent from Türkiye before or without consent. My interest is understanding how the site is used. For visitors in Türkiye, the Analytics cookies and the data collected through them rest on your explicit consent, Art. 5(1), given in the consent banner. You can withdraw it at any time with the “Çerez tercihleri” (cookie choices) link at the bottom of every page.
  • Who receives it: Google LLC. Google explains its own use of this data on its page “How Google uses information from sites or apps that use our services.”
  • How long: the _ga cookies last up to 2 years. GA4 keeps event-level data for the retention period set in the property; GA4 offers 2 or 14 months for standard properties. Google says that setting does not affect standard aggregated reports.

Visit counts: Jetpack Stats

  • Data: IP address, browser user agent, the page address, the referring page, the time of the visit, browser language and country and, if you are logged in to WordPress.com, your WordPress.com user ID and username.
  • How it is collected: Jetpack’s stats script (from stats.wp.com) runs on each page. Jetpack’s documentation lists no cookie for it. It does not count visits from browsers that send a Do Not Track signal; I turned that setting on.
  • Why: to see simple view counts per post in my WordPress dashboard. I see totals, not who viewed what.
  • Legal basis (GDPR): legitimate interests, Art. 6(1)(f). My interest is knowing, in aggregate, which posts get read. If you prefer not to be counted, turn on Do Not Track in your browser.
  • Legal basis (KVKK): Art. 5(2)(f), legitimate interest.
  • Who receives it: Automattic Inc., the company behind Jetpack and WordPress.com.
  • How long: Automattic keeps the stats logs that contain IP addresses for 28 days (Jetpack Stats documentation). After that only aggregate counts remain.

The contact form

  • Data: your name, email address, subject and message. The form is also protected by Cloudflare Turnstile (see Security above).
  • How it is collected: you type it into the form at https://ugurcoban.com/contact/. Contact Form 7 sends it to my mailbox by email. The site does not keep a copy of the message in its database.
  • Why: to read your message and answer it.
  • Legal basis (GDPR): legitimate interests, Art. 6(1)(f): answering people who write to me. When you ask about working with me, Art. 6(1)(b): steps you asked for before a possible contract.
  • Legal basis (KVKK): Art. 5(2)(f), legitimate interest. When the message is about working together, Art. 5(2)(c): processing directly related to setting up a contract.
  • Who receives it: Google LLC, because my email runs on Google Workspace. GoDaddy and Cloudflare carry the form submission on its way, and the MailPoet Sending Service (WooCommerce Ireland Limited, servers in the United States) delivers the email to my mailbox.
  • How long: I keep messages in my mailbox while they are needed to deal with your request and any follow-up, and then delete them. If a message becomes relevant to a legal claim, I keep it until the claim is settled or can no longer be brought.

Comments

  • Data: name, email address, website (optional), the comment itself, your IP address, browser user agent and the time of the comment.
  • How it is collected: you type it into the comment form under a post. WordPress stores it in the site’s database together with your IP address and user agent. If you tick “Save my name, email, and website in this browser for the next time I comment”, WordPress also sets comment cookies in your browser for about one year. The box is unticked by default.
  • What is public: once a comment is approved, your name, your website link (if you gave one), the comment, its date and your avatar appear under the post for anyone to read. Your email address and IP address are not published.
  • Why: to publish your comment as you asked, to moderate the comment section and to keep spam out.
  • Legal basis (GDPR): legitimate interests, Art. 6(1)(f): running a moderated comment section without spam. Your comment is published because you submitted it for publication.
  • Legal basis (KVKK): Art. 5(2)(f), legitimate interest, for storage and moderation. For what you choose to publish, Art. 5(2)(d): data made public by you.
  • Who receives it: GoDaddy (the database host, which also keeps the backups), Automattic (Jetpack copies comments to send me notifications) and every reader of the post (the public part only).
  • How long: a comment stays with the post, together with its IP address and user agent, until you ask me to remove it or I remove it or the post. Copies in backups age out as described under Backups.

Avatars: Gravatar

  • Data: a hash (a scrambled, one-way form) of the email address you enter in the comment form. When anyone opens a post with comments, their browser loads the avatar images from Gravatar, so Gravatar also receives that reader’s IP address and browser details.
  • How it is collected: WordPress builds each avatar address from the email hash, and the browser requests the image from Gravatar’s servers.
  • Why: to show your profile picture next to your comment if you have a Gravatar profile.
  • Legal basis (GDPR): legitimate interests, Art. 6(1)(f): showing who wrote each comment in a familiar way.
  • Legal basis (KVKK): Art. 5(2)(f), legitimate interest. The data goes abroad; see the transfers section.
  • Who receives it: Automattic Inc., which runs Gravatar. See Gravatar’s data privacy page.
  • How long: I store nothing extra for avatars. Automattic keeps request data under its privacy policy.

Email subscriptions to new posts

  • Data: your email address, the list you joined and your subscription status, the time and IP address of your sign-up and of your confirmation, and, once emails reach you, when you open them and which links you click.
  • How it is collected: only if you enter your email address in a sign-up form on this site. The form passes it to MailPoet, a newsletter plugin that keeps the lists in this site’s own database. There are two lists: the form on English pages joins the list for new English posts, and the form on the Turkish pages under /tr/ joins a separate list for new Turkish articles. Each list gets only the new posts in its own language. You then get an email with a link to confirm your address, and new posts start only after you click it. A sign-up that is never confirmed is deleted after 30 days. To stop abuse, the form counts sign-up attempts from each visitor for one hour, using a one-way hash of the IP address rather than the address itself. The subscription sets no cookies.
  • Opens and clicks: each email contains a small image that tells MailPoet when it is opened, and its links pass through ugurcoban.com so MailPoet can count clicks before taking you to the page. Blocking images in your email app stops the open count. This uses no cookies. You can turn the counting off at any time with the link at the bottom of every email or on the Manage your subscription page, and you will keep getting the emails.
  • Why: to email you new posts, to keep a record that you asked for them, and to see which topics readers find useful. If you have not opened any email for 365 days, MailPoet marks your address inactive and stops sending to it.
  • Legal basis (GDPR): consent, Art. 6(1)(a), for the emails. You can withdraw it at any time with the unsubscribe link in every email. Legitimate interests, Art. 6(1)(f), for the sign-up and confirmation record, the abuse check and the open and click counts. You can object to these at any time, as explained below.
  • Legal basis (KVKK): Art. 5(2)(c) for sending the posts you asked for, and Art. 5(2)(f), legitimate interests, for the sign-up and confirmation record, the abuse check and the open and click counts.
  • Who receives it: GoDaddy, which hosts the database that holds the list, and WooCommerce Ireland Limited (Dublin, Ireland), part of Automattic, which runs the MailPoet Sending Service that delivers the emails. The Sending Service handles your address and each email on servers in the United States and erases its logs of sent emails after 3 months. See MailPoet’s data page.
  • How long: while you are subscribed. Every email has links to manage or end your subscription. After you unsubscribe, your address stays on the list marked as unsubscribed, so that you are not emailed again by mistake. Ask me and I will delete it completely.

Backups

  • Data: copies of the site’s database and files, which include comments and their metadata. Contact form messages are not in the database, so they are not in the backups.
  • How it is collected: my host, GoDaddy, copies the site’s files and database automatically every day.
  • Why: to restore the site after a failure, a mistake or an attack.
  • Legal basis (GDPR): legitimate interests, Art. 6(1)(f): not losing the site and its comments.
  • Legal basis (KVKK): Art. 5(2)(f), legitimate interest.
  • Who receives it: GoDaddy, which stores the backups as part of the hosting.
  • How long: GoDaddy keeps the daily backups for 30 days and deletes older copies automatically. A comment deleted from the site stays in older backups for up to 30 days.

Google Site Kit sets Google Consent Mode v2 with defaults that depend on where you are:

  • In all EU countries, Iceland, Liechtenstein, Norway, the UK and Switzerland: ad_storage, ad_user_data, ad_personalization and analytics_storage start as “denied”. The site shows visitors there no consent banner and no consent message, so these settings stay denied. Google Analytics sets no cookies for you. Google’s tag still loads and sends cookieless pings to Google. According to Google, these pings can include the page address, the referring page, the time, your browser’s user agent and screen resolution, and your IP address, which Google says it uses to work out your country and does not log or store.
  • In Türkiye: the same four settings start as “denied”, and a consent banner in Turkish asks whether you allow the Google Analytics cookies. If you click “Kabul et” (Accept), analytics_storage switches to “granted” and the Analytics cookies are set. If you click “Reddet” (Refuse) or make no choice, it stays “denied” and only the cookieless pings described above reach Google. ad_storage, ad_user_data and ad_personalization always stay “denied”, because the site shows no ads. Your choice is stored in your browser for 12 months, and the “Çerez tercihleri” link at the bottom of every page reopens the banner so you can change it. The Turkish notice is the KVKK Aydınlatma Metni.
  • Elsewhere, for example in the US: these defaults are not set to “denied”. The Google Analytics cookies are set when the page loads. You can refuse them through your browser settings and with Google’s Analytics opt-out browser add-on.

If I add ads or change how consent works, I will update this policy first. The Cookie Policy lists the cookies and explains how to refuse or remove them.

Tracking by other companies

Other parties can collect information about your online activity over time and across different websites when you use this site. Here that means Google, through the Google Analytics cookies, for visitors outside the EEA, the UK, Switzerland and Türkiye, and for visitors in Türkiye who accept the Analytics cookies in the consent banner. In the EEA, the UK and Switzerland no Analytics cookies are set. Google describes what it does with that data on its page “How Google uses information from sites or apps that use our services.”

Who receives personal data

Summed up from the entries above, these are the categories of personal information the site collects: identifiers (name, email address, IP address), online identifiers (cookie IDs), activity on this site (pages viewed, referring pages), device and browser information, approximate location, and the content you send (messages, comments).

These are the recipients:

  • Google LLC (US): Google Analytics, and Google Workspace for my email.
  • Cloudflare, Inc. (US): content delivery, security and Turnstile.
  • Automattic Inc. (US): Jetpack Stats, Jetpack Protect, comment notifications and Gravatar.
  • WooCommerce Ireland Limited (Ireland), part of Automattic: the MailPoet Sending Service, which delivers the newsletter emails and the emails the site itself sends, such as contact form messages.
  • GoDaddy: hosting of the site and its database, and the daily backups. GoDaddy Operating Company, LLC is a US company, and this site is hosted in its Europe data center.
  • Readers of the site: the public part of approved comments.
  • Authorities or courts: only when the law requires me to disclose data.

I do not sell personal information for money. The section on US readers below has more on this.

Transfers outside Türkiye, the EEA and the UK

I am based in Türkiye. Apart from WooCommerce Ireland Limited, which is in Ireland, the providers above are US companies that process data in the United States and in other countries where they operate. The MailPoet Sending Service also handles emails on servers in the United States.

If you are in the EEA, the UK or Switzerland, the site, which I run from Türkiye, collects your data directly. When that data goes on to these providers, the safeguards are:

You can check each company’s DPF status on the official Data Privacy Framework list. The DPF is in force, and a challenge to it is pending before the EU Court of Justice. For Google and Cloudflare, the SCCs listed above would stay in place if the DPF fell away.

Under KVKK, sending personal data to these providers is a transfer abroad (Article 9). This policy names each provider, the data it receives and the purpose. The Cookie Policy lists the controls that limit what reaches Google.

Your rights

If the GDPR or the UK GDPR applies to you

  • Access: ask for a copy of the personal data I hold about you.
  • Rectification: ask me to correct data that is wrong or incomplete.
  • Erasure: ask me to delete your data, for example a comment.
  • Restriction: ask me to limit how I use your data while a question about it is checked.
  • Portability: get the data you gave me, where I process it on the basis of consent or a contract, in a common machine-readable format.
  • Withdraw consent: where I rely on consent, withdraw it at any time. This does not affect what happened before.
  • Complain: to a data protection authority (see Complaints below).

I answer requests by email within 30 days.

Your right to object

You can object at any time, on grounds relating to your particular situation, to any processing I base on legitimate interests (GDPR Art. 6(1)(f)). That covers, for example, comment metadata, Gravatar, Jetpack Stats, the cookieless Google pings and the contact form. I will then stop, unless I have compelling legitimate grounds that override your interests or I need the data for legal claims. If you subscribed to new posts by email, you can stop those emails at any time with the unsubscribe link, without giving a reason.

If KVKK applies to you (Article 11)

Under Article 11 of KVKK, you have the right to:

  • learn whether your personal data is processed;
  • request information about it if it is;
  • learn the purpose of the processing and whether the data is used for that purpose;
  • know the third parties, in Türkiye or abroad, to whom it is transferred;
  • ask for it to be corrected if it is incomplete or wrong;
  • ask for it to be erased or destroyed under the conditions in Article 7;
  • ask that corrections and erasures be notified to the third parties who received the data;
  • object to a result against you that arises from analysis of your data solely by automated systems;
  • claim compensation if you suffer damage because your data was processed unlawfully.

How to make a request

Send a KVKK application through the KVKK request form (in Turkish). For any other privacy request, use the contact form at https://ugurcoban.com/contact/ and write “Privacy request” in the subject.

For a KVKK application, include:

  • your name and surname;
  • for Turkish citizens, your Turkish national ID number; for others, your nationality and passport or identity card number;
  • your residential or business address for notifications;
  • your email address and phone number, if you have them;
  • what you are asking for.

I may ask for more information if I need to confirm that the request comes from you. I answer every request by email, free of charge, within 30 days. If the answer runs over 10 pages, the KVKK Application Communiqué allows a fee of 1 Turkish lira per extra page.

Complaints

Your choices about cookies and tracking

You can block or delete cookies in your browser, and block Google Analytics with Google’s opt-out browser add-on. In the EEA, the UK and Switzerland, Google Analytics sets no cookies at all, and in Türkiye it sets them only after you accept them in the consent banner (see How Google Analytics behaves where you are). The Cookie Policy has the details.

Do Not Track

Jetpack Stats does not count visits from browsers that send a Do Not Track (DNT) signal. Google Analytics does not respond to DNT, and nothing else on the site changes when your browser sends it.

US readers: selling and sharing

I do not sell personal information for money. The site shows no ads. Outside the EEA, the UK, Switzerland and Türkiye, Google Analytics sets its cookies when a page loads, as described in Tracking by other companies. You can block them in your browser or with Google’s Analytics opt-out browser add-on. If you want to review or correct personal information I hold about you, such as a comment, use the request process in Your rights.

Automated decisions

I do not make decisions about you based solely on automated processing that have legal or similarly significant effects.

Children

This is a general-audience site about marketing and analytics. It is not directed at children under 13, and I do not knowingly collect their personal data. Comments and email subscriptions are for people aged 16 or older. If you think a child has sent me personal data, tell me through the contact form and I will delete it.

Giving me data is voluntary

Reading the site needs no data from you beyond what your browser sends on its own. The contact form and the comment form ask for a name and an email address. Giving them is up to you, but I can’t reply to a message or publish a comment without them.

Please don’t send sensitive data, such as information about your health, religion, political views or ethnic origin, through the contact form or in comments.

How the site is protected

Every page is served over HTTPS. Cloudflare’s security and bot protection sit in front of the site, Jetpack Protect guards the login page, and my host keeps daily backups so the site can be restored. No setup is completely secure.

Changes to this policy

This version takes effect on October 29, 2026. When I change this policy, I update the “Last updated” date at the top of this page. Continuing to read the site is not treated as accepting anything; this page stays a notice.