Privacy
What this site collects, and what it does not. Last updated 31 October 2026.
What we do not take
No payment details — nothing on this site is for sale and there is no checkout. No personal information: no name, email address, password, wallet connection or exchange API key is asked for anywhere. There are no accounts today, so there is nothing to register for and nothing to sign into. If that changes, this page changes with it.
Analytics
Two counters run in your browser here: Cloudflare Web Analytics and PostHog. Cloudflare's has been permitted since 27 August 2026; PostHog's since 31 October 2026, when it replaced Google Analytics. They answer different questions, which is the only reason both are here: Cloudflare's says whether anybody loaded a page, cheaply and without a cookie, and stops there. PostHog's says which page a reader went to next and what they clicked — the number that decides which of the fifty contract pages is worth writing more about. Neither one sets a cookie or stores anything in your browser. Each is described below, separately.
Cloudflare Web Analytics
A script Cloudflare injects into this site's pages at its edge. It was blocked by this site's Content-Security-Policy until 27 August 2026 and is now allowed by it.
What it sends: the page's origin and path, the referring page if your browser supplies one, and page-load timings taken from the browser's own Performance API. Cloudflare states that it "does not collect or use your visitors' personal data" and that it "does not track individual end users across our customers' Internet properties" — their documentation.
Those are their words. These are measurements, made on 27 August 2026 and repeatable by anyone:
| Claim | How it was checked, and how you can |
|---|---|
| It sets no cookie and no browser storage | The beacon's source contains no document.cookie, no localStorage, no sessionStorage and no indexedDB — fetch the script named in this page's markup and search it. Loaded on a live site running the same beacon, the page ended with zero cookies and zero storage keys. |
| It does not send the query string | The beacon reads location.pathname and location.origin and rebuilds the URL from those two. It never reads location.href or location.search; neither string appears in the file at all. This is the reason the calculators below are unaffected by it. |
| It does not fingerprint | No canvas, no audio context, no device enumeration in the source. What it reads is the Performance API, which reports how long the page took to load and nothing about you. |
| The data goes to this domain, not a third one | The measurement is posted to /cdn-cgi/rum on this origin, so this counter sends nothing to a third party. The site's connect-src is no longer 'self' alone: it also names PostHog's two EU hosts, because the second counter does post off-origin. That difference is set out below. |
Two hosts are permitted to serve a script here: static.cloudflareinsights.com
and eu-assets.i.posthog.com. There is no third — you can read the whole
policy in this page's response headers.
PostHog
Google Analytics was removed from this site on 31 October 2026, and PostHog took its place.
PostHog is product analytics made by PostHog Inc., and what it collects here is stored in the EU, in Frankfurt. It sets no cookies and stores nothing in your browser — no local storage and no session storage. What it records: the pages you view, clicks on links and buttons, the page that referred you, your browser and device type, your screen size, and how fast the page loaded.
Your IP address is not stored. PostHog hashes it together with your browser's user agent and a salt that changes every day, uses the result only to count unique visitors for that day, and then discards it — so a visit today cannot be linked to a visit tomorrow. There are no session recordings. Nothing here identifies you, nothing is used for advertising, and nothing is sold. What is recorded is kept for up to one year. The legal basis is legitimate interest: knowing which pages are read is how this site decides what to write and what to fix.
Two details are this site's own, and both are in /analytics.js, the file that
starts it. Every address PostHog is given is cut to the origin and the path before it is
sent, so figures in a calculator's URL never reach it. And clicks inside the
watchlist's table — its pin buttons and its rows — are
left out of click recording, so the coins you pin are not part of what it sends.
Since 12 November 2026 the same file also names what a reader does, so that the site can see which paths through it work: which link was followed (the page's path, or the other site's host), that a calculator or the map answered a question and how many fields were filled — never the figures — that the search was used and which result was chosen — never what was typed — a chart time switch, a table sort, a first touch on a chart, a copy, and a watchlist pin or unpin without the coin. These are grouped under a profile keyed by the same daily hash, so it holds only these events and ends when the salt changes; it is never given a name, an email or any other identifier.
The library comes from eu-assets.i.posthog.com and is fetched after
the page has finished — on your first scroll, tap or key, when the browser goes
idle, or three seconds in, whichever comes first — and what it records goes to
eu.i.posthog.com. That is a speed measure: the library is about 108 KB
over the wire, more than most pages here. Blocking either host stops it completely, and
nothing else on this site depends on them. There is no consent banner: nothing is stored on
your device, and nothing PostHog records identifies you.
An arrival count on this site's own server
Each page ends with a one-pixel image from this site, /arrive. When your browser
loads it, the server adds one to a daily tally: the date, the page, the host of the site or the
utm_source the link came from, whether the page was typed or bookmarked, linked
from another site or reached from a page of this one, phone or desktop, and the two-letter
country Cloudflare reports. No script runs, no cookie is set, and no IP address, browser string
or identifier is written, so a row cannot be tied to a person. It counts only browsers that load
the page, which is what separates a reader from a program that fetches the page and leaves.
Cookies and local storage
| Name | Kind | Purpose | Expires |
|---|---|---|---|
rail | Cookie | Whether you collapsed the sidebar. Two possible values; not an identifier | 1 year |
coinliqui.pinned | Local storage | The coins you pinned on your watchlist. Never sent anywhere | Until you clear it |
Two entries, both this site's own, and neither holds an identifier. Neither counter adds
anything to this list: the two Google Analytics cookies, _ga and
_ga_5Y4ZENWMQJ, went with Google Analytics on 31 October 2026, and a
browser that visited before then may still hold them until they expire or you clear them.
Clearing your browser data removes everything here and the site behaves the same without it.
The calculators
The calculators compute in the page and store nothing. Their forms
submit as GET, so the values you enter appear in the page's own URL — which is
what makes a result shareable, and also means those numbers reach ordinary web-server
request logs. Nothing links them to you, but if you would rather a real account balance did
not appear in a log line, use a representative figure.
Those request logs are the only place the values go. Both counters are given the origin and
the path and nothing else — Cloudflare's rebuilds the URL from those two, and PostHog's
loader cuts every address in an event down to them before it is sent — so a figure typed
into a field named capital is not part of what either one sends. That is a
measurement of the requests, not an assurance.
It has not always been true, and this page said it had stopped when it had not.
The Google tag sends the full URL of every page view — query string included — unless it is
told otherwise, and it was not told otherwise. That was the case from the day the tag first
went in, through its removal on 19 August 2026, and again from its restoration on
27 August; the paragraph here described it in the past tense throughout those last four
days, saying the sending had ended when the tag came out. It had not: the tag came back.
Measured on 31 August 2026, loading the position-size calculator with figures in
its URL produced a request to Google carrying that whole URL, those figures included. On the
same day the tag was configured with page_location set to the origin and the
path — the rule the Cloudflare beacon already followed — and re-measured. Nothing about the
request logs above changed; what changed is that Google no longer receives the query string.
Hosting
This site runs on Cloudflare. Serving a page means Cloudflare handles the request itself — your IP address, the page asked for, the browser string, the response status — and keeps aggregate traffic and security metrics from it. That much is true of any web host and is not optional for a site that is served at all.
The measurement script described above is Cloudflare's too, and it is injected by the host rather than written into this site's source: it appears in the HTML after this site's code has finished with the response, and it does so whenever a client asks for the page the way a browser asks for it. It was blocked here until 27 August 2026 and is permitted now. Apart from the two counters described above, nothing off-origin can serve a script, receive a fetch, or load an image on any page here.
Contact
Questions about any of this, including a request to delete data associated with your visits: hello@coinliqui.com.