HomePrivacy policy

Privacy policy

The short version

This site runs without tracking cookies. There is no account, no newsletter and no contact form. What follows is everything that happens technically when you read a page.

Who is responsible

See the imprint

Server logs

Our server records the usual request data — IP address, time, the page requested, browser and referring page — to keep the site running and to spot abuse. Log entries are deleted after 14 days at the latest, and we do not use them to build a profile of you.

Cookies and analytics

We set no advertising or tracking cookies. If the site operator turns on an analytics tool, its script is named in the page source and its own privacy policy applies; with analytics off, nothing of the kind is loaded.

Market data (bubble map, charts, coin check)

Price and token data comes from public market data providers (GeckoTerminal, DexScreener, Jupiter, RugCheck). Our server calls those APIs and caches the answers, so your browser only ever talks to our server and none of your data reaches the providers. Token logos on coin check pages are loaded from the providers' image servers without a referrer.

Embedded videos

A YouTube video loads only after you click its preview. Until then, nothing is requested from YouTube. Once you click, your browser connects to YouTube (Google) through youtube-nocookie.com, and Google's privacy policy takes over from there.

Advertising and affiliate links

Ads are served by our own server, with no profiling and no cookies. Clicks are counted through a redirect on our server — a counter, nothing personal. After the click you are on the advertiser's site and their privacy policy applies.

Local storage

Your browser keeps a few technical preferences on your device, such as the bubble map range you picked. That data stays on your device and is never sent to us.

Your choices

Write to us at the address in the imprint if you want to know what we hold about you, or want it corrected or deleted. Since there are no accounts here, that is usually limited to server log entries, which age out on their own.