Privacy

What this site collects: as of today, nothing

Most privacy pages describe a policy. This one describes the code — what the site actually loads and stores in your browser right now, which is unusually little, and what will change if measurement is ever switched on.

Current state

No analytics, no cookies, no third-party requests

Long Horizon is static HTML served from GitHub Pages. There are no accounts, no logins, no forms, no comment system and no newsletter. There is nowhere for your data to go because there is no server of ours to send it to.

ThingStatus on this site
CookiesNone. The site sets no cookie of any kind, which is why you are not being asked to consent to one.
AnalyticsNot running. The measurement code is present but has no account token configured, so nothing loads and no request is made. See below.
AdvertisingNone. No ad network, no tracking pixel, no retargeting.
Affiliate linksNone currently on any page.
Third-party fonts, scripts or CDNsNone. Every stylesheet, script and image is served from this site's own address. The page makes no request to any other domain unless you click an outbound link.
Social embedsNone. No YouTube, X or Facebook embeds, which are the usual silent trackers.
Your browser

What is stored locally, and why it never reaches us

The site uses your browser's localStorage for a few conveniences. This data stays in your browser on that device. It is never transmitted anywhere, is not readable by this site's operator, and is deleted when you clear site data.

KeyWhat it holdsWhy
lh-theme"dark" or "light"So the theme you picked survives to the next page.
lh-calcThe numbers you last typed into the calculatorSo the calculator reopens with your figures instead of the defaults. Written only when you press Save.
lh-no-analytics"1", if you set itSuppresses analytics for you specifically, if analytics is ever switched on.

None of these identifies you. None of them is a cookie, so none of them is sent with any request. You can inspect all three in your browser's developer tools.

Hosting

What GitHub sees, which is not within this site's control

The site is hosted on GitHub Pages. Like any web host, GitHub's servers receive the ordinary details of your request — your IP address, the page requested, your browser's user-agent string — in order to deliver the page to you. That happens at the hosting layer and is governed by GitHub's privacy statement, not by this page. This site's operator does not receive, see or store those logs.

This is worth stating plainly rather than leaving out: "we collect nothing" is true of this site and untrue of the internet. Something always sees the request.

If measurement is switched on

What will change, in advance of it changing

The site is built to use Cloudflare Web Analytics if and when counting visitors becomes worth doing. It is currently inert: the provider is selected in the code but the account token is empty, and both are required before a single request is made. You can confirm this yourself in your browser's network tab — there is nothing to block.

When it is enabled, this is what it will and will not do:

  • No cookies and no identifier. It counts page views without storing anything in your browser and without assigning you a visitor ID.
  • No cross-site tracking. It cannot see where you went before or after this site, and builds no profile of you.
  • Aggregate only. Page, referrer, country, browser and device type — as counts, not as records of individual visits.
  • A script from static.cloudflareinsights.com will load, which will be the first third-party request this site makes. Content blockers stop it.
Opting out in advance. Run this once in your browser's console on this site and analytics will never load for you, now or later:
localStorage.setItem("lh-no-analytics", "1")

Cloudflare Web Analytics has no custom-event capability, so even when enabled the site cannot record which links you clicked. If that ever becomes necessary, it would mean a different provider, and this page would say so before the change, not after.

Advertising

There is none — and how you would know if that changed

No page on this site currently carries advertising, affiliate links or sponsored content, and nothing is collected for advertising purposes.

The site is built so that a commercial link cannot appear quietly. Any affiliate link is tagged in the page source, and the site then adds a visible badge at the link itself and generates a disclosure notice in that section automatically. Because the notice is generated from the links rather than written by hand, it cannot claim a relationship that does not exist, and it cannot go missing when one does. That design exists to satisfy Japan's stealth-marketing rule (景品表示法, in force since October 2023), the FTC's endorsement guides, and Korea's 표시광고법 — all of which require an advertisement to be identifiable where the reader meets it, not in a footer.

Affiliate links, if added, would be outbound links to a third party. Once you click one, you are on their site under their privacy policy, not this one.

Your rights

There is no data to request, correct or delete

Rights of access, correction and erasure under the GDPR, Japan's 個人情報保護法 and Korea's PIPA all operate on personal data held by an operator. This site holds none. It has no database, no mailing list and no record of who visited. If analytics is switched on it will remain aggregate and non-identifying, which means there is still no individual record to hand over or erase.

The data stored in your browser is yours and is removed by clearing site data for this domain, with no request to anyone needed.

Questions about this page — including "is this actually true?" — go to the site's public issue tracker. The entire site, including every script described here, is public source code: you can read what it does rather than take this page's word for it.

This page last updated: 12 September 2026. If the site's behaviour changes, this page changes in the same commit.