Privacy-Preserving Analytics

Vorliq records safe first-party aggregate product events so the community can understand growth without invasive tracking or third-party analytics.

What Is Collected

Events can include page views, feature page openings, onboarding completion, faucet interest without wallet addresses, documentation link clicks, and error boundary visibility. Each event stores an event type, route, category, timestamp, random anonymous browser session ID, and strictly allowlisted metadata.

What Is Not Collected

Vorliq analytics does not collect private keys, wallet passwords, recovery phrases, raw IP addresses, raw user agents, admin tokens, message body content, forum post body content, private key export data, or personal identity.

Retention

Analytics events are stored in a local JSON file on the backend and pruned to the last 90 days. Analytics data is useful for product insight but is not required to reconstruct blockchain balances.

Opt-Out

Analytics defaults to enabled for aggregate product insight. Users can disable it from the Account privacy controls. Opting out stops future analytics events and removes the anonymous session ID from that browser.

Dashboards

The public Growth dashboard shows aggregate visits, most viewed areas, onboarding completions, faucet interest, forum interest, registry summary, and chain/mining summary. The protected admin dashboard shows more detailed aggregate counts, but never a raw public event list.

API

Public endpoints are POST /api/analytics/event and GET /api/analytics/summary. Protected operator analytics are available at GET /api/admin/analytics with the server-side admin token.