~/privacy what this site counts
What this site counts, and why
The site’s own counter keeps one cookie on your device: a random id that tells a returning visit from a new one, for 13 months. You can switch it off below. I count visits to see which parts people read and play with, and to know who found the three keys. Google Analytics 4 runs as well, with its own cookies: what it collects is below, with a switch to turn it off.
- When you visit
- The page and its language. The site or app that sent you, only its name (google.com, not the search; Instagram or LinkedIn when the page opened inside their app), and campaign tags in the link (utm_…, or a short ?s= / ?ref= tag, which is removed from the address at once). Phone, tablet or desktop, a rough screen width, light or dark theme. Which sections you reached and how long each stayed on screen, and what you tried: the LIBRAIN story, Spot the risk, the projects window, the globe, the flag quiz, the tape deck, the key hunt, and links that leave the site.
- If something breaks
- If the page hits an error or loads slowly, the error (without links, emails or codes) and its loading times go with it, along with whether your device runs the 3D in its lighter mode. That is how I find what breaks on which phones.
- Where from
- Country, region and city, as Vercel, the site’s host, reads them from your IP address. The address itself is never stored.
- How you’re counted
- As a code made fresh every day: a one-way hash of your IP address and browser, mixed with a random value that is deleted when the day ends. On its own it counts you once a day and can’t recognise you tomorrow; telling that you came back is the device cookie’s job (next). While the page is open and in view, it sends a small “still here” signal every 20 seconds, and one more when you switch away or leave.
- Returning visits
- To tell a returning visit from a new one, the counter’s answer puts one cookie on your device:
em_did, a random number that means nothing by itself. It lasts 13 months from your first visit (later visits don’t extend it). It belongs to erenmutlu.me, so the portfolio and the LIBRAIN demo share it, and it is only ever sent back to the counter; scripts on the page can’t read it. The server keeps a keyed hash of it, never the number itself, next to your visits. That shows me that someone came back, how often, and how they found the site each time (first from LinkedIn, later typed in, say), and nothing else: it isn’t matched with Google Analytics or anything outside this site, and it isn’t shared. It is set without asking first. Switch it off below and the cookie is deleted, never set again in this browser, and your earlier visits are unlinked from it; “Forget this device and stop remembering it” deletes everything recorded with it and switches it off. With Global Privacy Control or Do Not Track it is never set. After 13 months, visits lose the link. - The key hunt
- Find all three keys and your finder code is recorded. Download your finder’s card or press “Send it to Eren”, and the name you typed on the card goes with it. Leave the name empty if you’d rather not.
- Not tracked
- If your browser sends Global Privacy Control or Do Not Track, nothing is sent at all, neither to the site’s own counter nor to Google Analytics, and the device cookie is never set. Bots and automated browsers aren’t counted either.
- Google Analytics 4
- Alongside the site’s own counter, Google Analytics 4 runs once a page has finished loading. It sets its own cookies (_ga, _ga_…) to tell repeat visits apart, and sends Google the pages and sections you view, what you try (the list above, but never a name or a finder code), your rough location and device, and how you found the site. Google signals and every advertising feature are switched off. Google keeps this data for 14 months. Switch it off below at any time; it never loads when your browser sends Global Privacy Control or Do Not Track.
- The LIBRAIN demo
- The demo at librain.erenmutlu.me is counted the same way, by the same counter and under the same rules: which screens and features are used, the runs started and how they ended (never your questions, your API keys or the answers), and links that leave it. A visit to both sites on the same day counts as one visitor.
- What I look at
- Each day’s visits one by one: where from, how long, which sections, which links. I look for visits that read Experience or open the CV, to know whether a link I sent was read. It never changes what you see. It can’t follow you anywhere else; on this site, with the device cookie, I can see your earlier visits next to today’s.
- Who sees it, for how long
- The site’s own counts: only me. They are kept in a database in Frankfurt (Neon), next to the site’s server (Vercel), and deleted after two years; the link between visits and a device goes after 13 months. Nothing is sold, shared or used for ads. Google Analytics data is held by Google, as described above.
- Why it’s allowed
- For the site’s own counting: a legitimate interest in knowing how the site is used (KVKK art. 5/2-f, GDPR art. 6(1)(f)), with as little data as that takes. The device cookie is set without asking first; you can switch it off below at any time, and it is never set when your browser sends Global Privacy Control or Do Not Track. Your name only if you type it.
- Your data
- Write to erennmutlu@outlook.com and I’ll show you or delete what is stored about you. A finder code makes it easy to find. For this device, “Forget this device and stop remembering it” below deletes it at once.
updated 22 November 2026 · Türkçe