# Paczesny Analytics

> Cookieless behavioral analytics for Next.js — click heatmaps, scroll depth, user journeys, and funnels, with no consent banner needed by design. Live insight into how people actually use your site, without the compliance overhead a consent banner implies.

## Key links

- [Landing](https://analytics.blonie.cloud/) — product overview and live demo panel
- [Live demo](https://analytics.blonie.cloud/demo) — explore a real dashboard, no login required
- [Register](https://analytics.blonie.cloud/register) — create an account and add your first site
- [Login](https://analytics.blonie.cloud/login) — sign in to an existing account
- [Install snippet](https://analytics.blonie.cloud/#install) — one-component, zero-config tracker setup
- [Privacy policy](https://analytics.blonie.cloud/privacy-policy) — how data is processed (cookieless, de-identified)
- [Terms of Service](https://analytics.blonie.cloud/tos) — terms governing use of the platform

## For agents and API clients

- [OpenAPI 3.1 spec](https://analytics.blonie.cloud/api/v1/openapi.json) — machine-readable API description
- [Interactive API docs](https://analytics.blonie.cloud/api/v1/docs) — Scalar reference for the public Read API v1
- [MCP endpoint](https://analytics.blonie.cloud/api/mcp/streamable-http) — hosted Model Context Protocol server (Bearer `pak_` key)
- [MCP server card](https://analytics.blonie.cloud/.well-known/mcp/server-card.json) — SEP-2127 description of the MCP server
- [API catalog](https://analytics.blonie.cloud/.well-known/api-catalog) — RFC 9727 linkset pointing at the spec and docs
- [JS API reference: commerce events](https://analytics.blonie.cloud/docs/track): paczesny.track() plus the four commerce events, with field tables and example payloads

Authenticate API and MCP requests with a scoped `pak_` API key sent as
`Authorization: Bearer <pak_...>`.

## Privacy model

Paczesny Analytics is cookieless by design. Visitors are identified by a backend-computed
hash with a daily-rotating salt:

    visitorId = sha256(siteId + ip + ua + dailySalt)   # truncated to 32 hex chars

- The raw IP address is never stored.
- Because the salt rotates daily, the identifier cannot track a user across days.
- The identifier is de-identified (not "anonymous") — it cannot be attributed to a natural person across days.
- No cookies are set and no consent banner is needed by design — your own legal review always has the final say.
- Raw events are retained for 30 days.

## What it is / who it's for

An analytics platform for product owners and developers who want behavioral
insight — click heatmaps, scroll depth, user journeys, and funnels — without a consent
banner, and without the compliance overhead one implies. It also surfaces Site Health
(Lighthouse + field data) and JavaScript error tracking, all live. Natively built for
Next.js: drop one component into your root layout and the data flows in within minutes.
Ask Claude about your traffic — connect the hosted MCP server with `claude mcp add`.
Built on Next.js and Appwrite.