Orrery has no accounts, no advertising and no third-party trackers. It does measure how the site is used, so the next thing built is the thing people actually reach for. This page says exactly what that means and lets you switch it off.
Checking your current setting…
Turning this off stops the usage analytics and the crash reports described above. It does not affect the server logs — those are part of serving the page at all. The choice is remembered in a single cookie on this device, and the page reloads so collection stops immediately rather than at the next visit.
Usage analytics run on a self-hosted Umami instance on our own server. No cookie is set, no profile is built, and nothing is shared with anyone. What it records:
There are no accounts, so there is nothing to log in to and no name, email address or password anywhere. The analytics themselves never store your IP address — it is used once, in memory, to derive an approximate location, then discarded. Nothing is sold, shared with an advertising network, or used to follow you to another site.
Separately from analytics, ordinary web-server access logs record every request — including your IP address, the page requested, and your browser's user-agent. The same is true at the edge for the analytics endpoint. These are standard operational logs kept on our own infrastructure for debugging and abuse handling: the log store keeps them for up to 30 days, and the edge logs rotate by size rather than age. They are not joined to the analytics data, are not used to build a profile, and the opt-out below does not switch them off — serving a page cannot happen without them. Cloudflare, which fronts the site, may also keep its own connection logs under its policy.
If your browser sends Global Privacy Control or Do Not Track, Orrery honours it automatically — analytics never start, and you do not need to touch anything here.
Umami sets no cookie at all. Orrery uses three functional cookies — your language pick, your Curator Tour position, and the analytics opt-out below — each listed in full on the credits page. A few browser-local settings (graphics quality, debug mode, offline downloads) are also stored on your device; they never leave it and are not part of any analytics.
When something breaks, the browser sends a crash report — the error, the stack trace and the page it happened on — to a self-hosted GlitchTip instance. It is there to fix bugs, and it is switched off by the same opt-out below.
Analytics and crash reports are self-hosted on infrastructure the project runs itself — no analytics provider, no third-party tracker, no advertising network. Traffic to the site and to the analytics endpoint passes through Cloudflare, which provides the CDN and terminates TLS in front of it.