Cookie Policy

1. In short

This site has no cookie consent banner, because it uses no cookie that needs consent. Every cookie below is strictly necessary to run the site or completes something you did yourself; none is for measurement or advertising, and none is sent to a third party. Some of your settings are kept not in a cookie but in your browser’s own storage; those are listed below too.

This page is derived from the code: every row below is what the site actually writes, not what it intends to. The list was checked against the code again on 22 October 2026, when the cookie banner was removed.

2. The one exception: the TradingView chart in the VIX box

If you press “Show on TradingView” in the VIX box on the US equities page, TradingView’s chart loads: your browser connects to TradingView, runs its code, and TradingView may use its own cookies and measurement (Snowplow) on its own domain. Those are not our cookies and are not in the tables below; TradingView’s privacy policy applies: https://www.tradingview.com/privacy-policy/.

If you do not press it, your browser sends TradingView no request at all. Your choice is not stored: the chart is removed when you press “Close” or leave the page, and you are asked again the next time.

3. Our own counter

Not a cookie, but it belongs here. When you open a news or a KAP page, your browser sends one request to our own API and that page’s counter goes up by one. What is stored is exactly this: page_views(page_type, item_id, views) — the kind of page, the id of the item, and one integer total. No person id, no session id, no timestamp; no cookie and no browser storage is used for it. The counter knows how many times a page was opened, not who opened it, and it does not depend on consent. The request goes to our own server: as with every request your IP address reaches that server, and it is kept in memory to stop the same page being counted repeatedly and to cap requests from one source. It is never written into the counter, never written to disk, and is lost every time the service restarts; only a limited number of entries is held, and the oldest drops out when that number is reached. Like every visit, this request’s address and your IP address also land in the server access log, whose period is in section 9 of the Privacy Policy.

4. Cookies

All of them are strictly necessary: they run the site or complete something you started. That is why none of them depends on consent.

5. Browser storage

These are not cookies: they sit in your browser’s own storage, are never sent to our server, and carry no identity. You can clear all of them at any time with your browser’s setting for deleting site data.

6. The old cookie banner

Until 22 October 2026 the site had a cookie banner with three classes (strictly necessary, analytics, preferences). It was removed because the permissions it asked for no longer switched anything: the TradingView panels it switched on and off had left the site. If the mergen_consent cookie that banner wrote is still in your browser, it is no longer read; it deletes itself when it expires (6 months at most), and you can delete it from your browser straight away if you prefer.

7. Third parties and transfers abroad

When a page shows live crypto prices, your browser connects directly to Binance’s public price stream; that connection sets no cookie, but your IP address reaches Binance. If an error happens in your browser, the error report is sent to Bugsink directly from your browser. These, and the VIX chart, are described in section 6 of the Privacy Policy.

The site itself runs on servers in Germany (Hetzner, Nuremberg), the membership infrastructure is Supabase (EU), and sign-in emails are sent via Resend/Amazon SES (Ireland). Fonts are served from our own origin — no request goes to Google.

The Turkish version of this document governs; this English text is provided for convenience.