# Privacy and measurement

The readiness guide asks for a goal, ABN status, GST status, and accounting tool.
It does not ask for an ABN number, name, email, bank details, or account credentials.
The Worker does not store guide answers.

The Worker sends event counts to Cloudflare Workers Analytics Engine when the Pages binding exists.
One response event records the product, route type, HTTP status, and a broad client class.
The client class says only whether the user agent declares a known search or AI crawler.
It does not prove that an AI agent read or understood a page.
The Worker does not store a question, answer, IP address, email, ABN, or full user agent in these events.
Successful HTML pages set a secure, HTTP-only site-session cookie for 30 minutes.
The cookie stays on the visitor's browser. Its value is not sent to event storage.
Each HTML page records a page view, but only the first page without that cookie records a site session.
Declared crawlers do not receive the cookie or add site sessions.
Blocked cookies and unrecognized bots can affect these counts. A session is not a unique person.
Download events count only successful file responses. Landing events separate 200 responses from password challenges.
API and MCP events include failed responses, including rate limits.
Button events count an intent to open an AI app, sign up, or contact LUCA.
They do not prove that a person sent a prompt, signed up, or sent a message.

Analytics Engine can sample events at high volume. Reports must use `_sample_interval` weights and identify weighted totals as estimates. Do not present an estimated total as an exact count of people or agents.

When both sites bind the same D1 database, it also stores hourly event counters.
Each row stores a brand, event type, route or action name, HTTP status, broad client class, and count.
It does not store IP addresses, prompts, URL queries, or full user agents.
The admin portal calls these exact *recorded event* counts.
Counts begin when the binding and schema are active. A failed counter write can leave a gap, so the portal shows its coverage limit.
The public event endpoint reports button intent. An automated client can also call it within the API rate limit.

The test deployment uses `noindex` headers and a `noindex` meta tag. Its `robots.txt` allows agents to read public guides and tools without search indexing.
The live deployment can enable search indexing after LUCA reviews the product facts.

Cloudflare Web Analytics can measure page traffic after the new account owner creates a token.
The token is not in this prototype.
Workers Logs and Traces help diagnose failures.
Their retention and access settings need approval in the new account.