Privacy-Safe Analytics Policy

Pizza x402 uses lightweight, cookie-free web analytics on the public website to understand documentation engagement and conversion intent.

Data minimization rules

The website analytics setup must follow all of the following:

• No cookies are set for analytics.
• No personal data is collected (no names, emails, phone numbers, wallet addresses, or IP enrichment fields).
• Event properties are limited to route and intent metadata only.
• Analytics data is used for product/UX decision support, not user profiling.

What we track

1. Docs entry events

Event: docs_entry

Triggered when a visitor loads /docs or any /docs/* route.

Captured properties:

• path (page route)
• domain

2. Conversion-intent click events

Event: conversion_intent_click

Triggered when users click tagged CTAs (for example: docs exploration, payment-flow review, merchant onboarding entry).

Captured properties:

• intent
• section
• destination
• sourcePath
• domain

Instrumentation controls

Analytics script source and domain can be overridden with public env vars:

• PUBLIC_ANALYTICS_ENABLED (default: true)
• PUBLIC_ANALYTICS_DOMAIN (default: pizzax402.com)
• PUBLIC_ANALYTICS_SCRIPT_SRC (default: plausible tagged-events script)

Verification checklist

1. Build and inspect page source for analytics beacon:

npm run check:analytics

2. Run fixture proof to verify gate failure behavior:

npm run check:analytics:fixture

3. Manual dashboard validation:

• Open pizzax402.com and click at least one CTA tagged with conversion_intent_click.
• Confirm both docs_entry and conversion_intent_click appear in the analytics dashboard event feed.