COINANOMALY

Privacy

Last updated: 24 September 2026

As the site stands today it is read, not joined: there is no account, no sign-up, no form and no payment. What follows is the whole of what happens to data when someone reads it.

Who is responsible

Virgio Tech Bilgi Teknolojileri Eğitim ve Danışmanlık Hizmetleri Ltd. Şti. operates coinanomaly.com and is the data controller under Law No. 6698 on the Protection of Personal Data (KVKK). Contact: info@coinanomaly.com.

What is collected

Page counts. The site counts how often each page was read and by how many readers. A stored count holds the date, the address of the page, the language it was served in, the language the browser asked for, the site that linked here and two numbers. Nothing else: no address, no identifier, no fingerprint, nothing that could be traced back to a reader.

How readers are counted without keeping anything. Telling one reader's second visit from a second reader needs the two to be distinguishable, and the only thing that distinguishes them is the IP address the request arrived from. So the address is used, in memory, for as long as it takes to answer one question — has this reader been seen today? — and is then gone. It is never written to disk and never stored. What is held for the rest of the day is the result of hashing it together with 32 random bytes drawn when the day began; that random value is never written down either, and is destroyed at midnight along with every hash made from it. Nobody, ourselves included, can turn one of those values back into an address or recompute yesterday's. The database receives a number of readers and nothing more.

Because of how it is done, the reader count understates rather than overstates. Restarting the software starts the day's counting over. Everyone sharing one mobile carrier address counts as one reader. One person using a phone and a laptop counts as two. Requests from crawlers that identify themselves are served normally and not counted at all.

The IP address is processed for this and kept for none of it; the legal basis for that momentary processing is the controller's legitimate interest in knowing how many people read the site, under KVKK Art. 5/2(f) and GDPR Art. 6(1)(f). Nothing is stored on the reader's device for it, so there is nothing here for a consent banner to ask about.

Server records. Like any web server, the machine serving this site records requests, and those records include the IP address of the visitor. They exist to keep the service running and to defend it against abuse, and they are kept no longer than 30 days before being deleted. The legal basis is the controller's legitimate interest under KVKK Art. 5/2(f).

Correspondence. If someone writes to us, we hold their message and address for as long as answering it and keeping a record of the answer requires.

Cookies

The site sets one cookie, lang, holding nothing but a language tag: en or tr. It remembers which language was opened, so the bare address opens in it next time. It lasts a year, cannot be read by scripts, and is sent only to this site. It carries no identifier and follows nobody.

There are no analytics cookies, no advertising cookies and no third-party cookies here, so a consent banner would have nothing to ask about. Any browser can refuse or delete this cookie; the site then simply falls back to the language of the browser.

Who else is involved

Running a website needs a few providers, and they are these:

  • Hosting. The servers this site runs on, which is where its data lives.
  • The network in front of it. A content delivery and security provider may serve the pages and absorb attacks; where one is used, requests pass through it before they reach us, and it sees the address they came from.
  • Mail. Correspondence sent to us is held by a mail provider on servers in the European Union.

What is not here, by decision rather than by accident: no advertising network, no analytics company, no social widget, no cross-site tracking of any kind. The site counts its own pages itself, as described above, and does not hand a reader to anyone.

Market data is fetched by our own servers from the exchanges, on a schedule of their own. Reading a page does not send anything to an exchange.

Rights under KVKK

Article 11 of KVKK gives everyone the right to learn whether their personal data is processed, to ask what has been done with it, to have it corrected or deleted, to object to conclusions drawn from automated processing, and to claim compensation for damage caused by unlawful processing. Requests go to info@coinanomaly.com and are answered within thirty days. A request must identify its sender; the formal requirements are set out in the Communiqué on Application Procedures to the Data Controller. Anyone dissatisfied with the answer may complain to the Personal Data Protection Board.

Changes

This page states what is done today, and the date at the top says when that was true. If the site later offers something that needs more — an account, alerts sent to a subscriber, an interface for programs, anything paid for — what it collects, why, and for how long will be written here before it opens, not after. Until then, the section above is complete.