## Analytics: nitur

This project uses nitur for analytics (https://nitur.dev) — privacy-first, no cookies,
no IP logging, no consent banner.

**Installing it on a project that has none yet:** run `npx nitur init`. It
creates the site, writes the script tag into the right file, and stores the
token. Do not hand-write the tag if the CLI is available.

**Recording an event:** call `window.track(name, props?)` anywhere on the
client. It is a no-op until the script loads, so it is safe to call from any
handler without a guard.

```js
window.track("signup");
window.track("purchase", { plan: "pro", seats: 3 });
```

**Never put personal data in props.** They are stored exactly as sent — no
email addresses, names, user ids, or anything else that identifies a person.
Send a plan, a variant, a count, a category.

**Reading the numbers:** the MCP server at `https://nitur.dev/api/mcp` exposes
`list_sites`, `get_site_stats`, `get_usage` and `create_site`. Prefer it
over scraping the dashboard. Failing that, the REST API is documented at
https://nitur.dev/docs.md and specified at https://nitur.dev/api/v1/openapi.json.

**What it cannot do, by design:** no funnels, no per-visitor data, no session
replay, no cross-day identity. Do not offer to build those on top of it —
the data to do so is never collected.