Skip to main content
WORMIFI
Last updated July 30, 2026

Privacy and analytics choices

Wormifi's analytics layer is optional. It stays off unless a real Google Analytics 4 Measurement ID is configured and you choose to allow analytics.

What optional analytics can measure

If you allow analytics after it is configured, Wormifi can send page views, acquisition source and campaign fields, selected control type, game-mode starts, confirmed live connections, tutorial progress, numeric solo-run results, replay use, and share-button attempts.

Google Analytics may also process standard browser, device, session, referring-site, and approximate location information as described in Google's own Analytics privacy documentation.

What Wormifi deliberately does not send

  • Your arena or player name.
  • A room number or reconnect token.
  • A challenge token.
  • The full query string or URL fragment.
  • User-provided profile data, email addresses, or uploaded photos.
  • Advertising-personalization or Google Signals permission from the game code.

Your choice

The choice is stored in your browser under wormifi.analytics-consent.v1. Wormifi also respects a browser Do Not Track signal by leaving analytics off.

Current activation boundary

The source code contains a consent-gated integration, but no Measurement ID is stored in this repository. The site owner must configure the property, publish a verified contact method and retention settings, and validate the deployed data stream before treating analytics as active.