Analytics

Every artifact opens on its Analytics tab, for anyone who can edit it. The owner sees a strip of figures over the last 30 days — views, readers, named readers, the peak day, and when it was last viewed — with a daily trend beneath. Below that, Recent activity lists each reading session and submission: who, when, which version, and where (path, device, country, browser). Bots are hidden unless you include them.

Readers are counted per day: the visitor digest is salted daily, so somebody returning on another day counts twice. A reader is named only when they signed in with an address.

Views

A small beacon reports four things only the page knows: how long it was visible, whether anyone touched it, which path, and the referrer. Everything else — device class, operating system, browser — is derived by the worker from headers it observed, because a page the platform did not write could forge anything it asserts.

The visitor's address is never stored — it goes into a hash and out of scope in the same expression.

Errors

When an artifact throws in somebody's browser, the fault is recorded, deduplicated and kept for 90 days. No screen shows them yet, and nobody is notified.

Not the same as collected data

Collecting what a visitor types is a different feature — see Collecting data. Analytics is what the platform observes about a request; collected data is what the page asks for and the visitor chooses to give. They are counted, stored, read and erased separately.