murattunalı.

Privacy.

Murat Tunalı Last updated:

This site uses no cookies, does not track human visitors and runs no analytics. The only thing counted is requests from AI crawlers. The only flow of personal data goes through the contact form. Every statement below describes the site’s measured behaviour.

In short

  1. Cookies → none
  2. Analytics / tracking → none
  3. AI crawlers → counted: agent name and path only, no IP
  4. Data collected → the form only: name, email, message
  5. Storage → no database on this site; the message is delivered as email
  6. Third parties → Cloudflare (hosting) · Web3Forms (form delivery) · hCaptcha (only on form interaction)
  7. WhatsApp → a link only; no data reaches Meta unless you click
  8. AI agent tools (MCP) → read-only, nothing recorded

What data we process

Only what you type into the contact form yourself: your name, your email address and the text of your message. Unless you fill in the form, you leave no personal data on this site. The site never asks for your location, phone number, date of birth or anything similar, and reads nothing of that kind from your browser.

Your message is not written to a database on this site. The request goes to a Cloudflare Worker running server-side; the Worker forwards the message to the Web3Forms service, and Web3Forms delivers it as an email to murat.tunali@murattunali.com.tr. In other words, your message lives in a mailbox, not in a user database.

Cookies and browser storage

This site sets no cookies. Measured: document.cookie stays empty even after interacting with the form. localStorage is not used. That is also why there is no cookie consent banner — there is no cookie to consent to.

There is one technical exception, in sessionStorage: mt.dither carries the click position to the next page during the page transition and is deleted the moment it is read. It carries no identity, is never sent to a server, and is deleted when you close the tab.

AI crawlers

A single counter runs on this site and it counts AI crawlers only. When a request arrives identifying itself as a known AI agent — GPTBot, ClaudeBot or PerplexityBot, for example — the server records two things: the agent’s name and the path requested. No IP address, no browser fingerprint, no session identifier and no referrer is stored. A request that does not identify itself as an AI agent never enters this counter, so as a human visitor you do not appear in it at all.

The reason for the counter is consistency: this site measures and publishes how other sites answer AI crawlers, and not measuring its own traffic would be inconsistent. The counter records page and root-file requests only; stylesheet, script, font and image requests are not counted.

Tools for AI agents (MCP)

This site offers a read-only tool endpoint that AI agents can call (/mcp, Model Context Protocol). The tools only return data already published on this site: the guide list, glossary search, case measurements and the site’s own measurement ledgers. The endpoint records nothing; the AI crawler counter above does not count this address. The “prepare a brief” tool neither sends nor stores the message: it only validates it and produces an email link that a human sends.

The machine reading tool

A site address you type into the tool page, or into an evidence station in the guides, goes to this site’s server (a Cloudflare Worker); the server reads that address under its own identity, returns the result to your browser and stores neither the address nor the result. Each read gives up after six seconds, follows at most four redirects and reads at most 400 kilobytes; local addresses, IP numbers and this site itself are never read. To prevent abuse, reading requests are limited to twelve per minute per IP address; the counter holds only the request times of the last minute, the IP address is the counter’s name and is written nowhere. The server of the site being read may see our request in its own logs; the request header carries this tool’s name and address.

The same path applies to two more tools: the visibility check (reads the signals that can keep a page out of Google) and the redirect checker (follows each line of an old address list). Both read the addresses you enter from this site’s server under its own identity and store neither the addresses nor the results. Because the redirect checker reads up to twenty addresses at once, four addresses count as one read on the counter.

Third parties

Hosting runs on Cloudflare. Like any web server, Cloudflare keeps technical logs; these can include IP address, browser information and the address requested, and are processed for security and service continuity. We do not read those logs to build personal profiles.

Form submissions are delivered through Web3Forms (app.web3forms.com). The relay happens server-side; your browser never makes a direct request to Web3Forms.

The moment you touch a form field, hCaptcha loads (Intuition Machines, Inc.). Its job is to filter out automated submissions, and to do so it processes IP address and browser signals. hCaptcha does NOT load on page open — only on form interaction. So if you read the contact page and leave, hCaptcha never runs.

Fonts are served from this site’s own server. No request is made to Google Fonts or any comparable font service.

The site also carries a WhatsApp link. It is only a link: unless you click it, no request goes to WhatsApp and no data reaches Meta while the page loads. When you do click, the conversation starts in the WhatsApp app, and from that point WhatsApp’s (Meta’s) own privacy terms apply. The link carries `rel="noreferrer"` — which page you came from is not passed on.

Retention

Form messages are kept in the mailbox for as long as the correspondence requires. They are deleted when you ask for them to be deleted. Server log retention follows Cloudflare’s own policy.

Your rights

Under Article 11 of Turkey’s KVKK and Articles 15–22 of the GDPR you have the right to learn whether data about you is being processed, to request information if it is, to have it corrected or erased, and to object to the processing.

To exercise any of these rights, an email to murat.tunali@murattunali.com.tr is enough. Nothing beyond identity verification is required, and the request is free of charge.

Changes

This text describes what the site actually does; if the behaviour changes, the text changes with it. When it does, the update date at the top of the page moves forward.