Privacy

The short version

Reading the Atlas is anonymous. No account, no sign-in, no newsletter wall, no advertising, and no third-party tracker running in your browser. Two things are counted — page views and agent tool calls — using a privacy-focused analytics service, and one cookie remembers whether you chose the light or the dark plate. Nothing else about you is collected, and no data about you is sold, rented, or shared for advertising.

When you read a page

Human pages carry a counter from GoatCounter, an analytics service chosen because it sets no tracking cookies and builds no cross-site profile. The script is served from this domain rather than from the analytics host, so what your browser requests is a first-party address on agentic-atlas.dev and nothing else. What a count carries is the page path, the referring page if you arrived from one, and the coarse browser and screen facts the script reads — enough to know which plates are read and on what kind of device, and not enough to identify you.

Your network address is forwarded to the analytics service with the count so it can attribute the view to a country rather than to this server, and so the publisher's own visits can be excluded. GoatCounter's handling of that value is governed by its own privacy policy, not by this page. This site keeps no visitor database of its own.

The one cookie

A single cookie, atlas_projection, records whether you are reading in the light plate or the dark one. It holds one of exactly two words, it is set only when you use the projection control, it is scoped to this site, and it lasts a year because a reading preference is not a session. It carries no identifier, and nothing on this site reads it except the code that decides which plate to draw. There is no consent banner because there is nothing here to consent to: delete the cookie and the site simply forgets which plate you preferred.

When your agent consults the Atlas

The MCP transport is open and unauthenticated: there is no key to issue, so there is no account to attach a call to, and it carries no rate limit. Tool calls are counted the same way page views are — the tool that was invoked, the calling client's user-agent string, and the network address the call arrived from — so the publisher can tell which parts of the grammar are actually used. The content of a consultation is not stored: the arguments you pass and the payloads returned are not recorded, retained, or used to train anything. The Atlas is a read-only publication, and nothing an agent asks it changes what it serves anyone else.

Server logs

Like any web server, this one writes an access log: the path, the HTTP method and status, how long the response took, the user-agent, and which Release the response was served from. Logs are held by the hosting provider for their retention window and are read only to diagnose faults and outages. They are never joined to the analytics counts, and they are not used to build a profile of a reader.

Opting out

Any content blocker that blocks the counter request stops the page count. Reading with JavaScript disabled records nothing at all and costs you nothing: every page on this site renders in full without it, and the Markdown dialect at Accept: text/markdown never carries a counter. For agent traffic, the MCP transport records no more than described above and there is nothing to disable — the payloads are the same either way.

Questions, corrections, removals

If something here is wrong, unclear, or has drifted from what the site actually does, say so and it will be corrected: hello@agentic-atlas.dev. The same address handles any request to remove data associated with you, though in most cases the honest answer will be that none was collected. See the contact page for the other ways to reach the publisher.