ZONE//LAB — Privacy Summary
Updated: 2026-08-28

ZONE//LAB does not include advertising trackers or cross-site behavioral tracking.

Aggregate traffic statistics (V5):
- ZONE//LAB counts site visits and active sessions to provide aggregate statistics at /ZoneLabCounter.
- The Cloudflare backend receives the connecting public IP address as part of the normal HTTP request, converts it immediately into a one-way HMAC hash, and does not store the raw IP address.
- The hash is used only to distinguish unique public IPs for aggregate counts. People sharing the same public/NAT IP may therefore count as one unique IP.
- Repeat visits are counted separately from unique IPs.
- Short-lived random session IDs are used only for the “online / active sessions” metric and are automatically considered offline after a short inactivity window.
- Daily pseudonymous unique records are retained only as needed for rolling 365-day statistics; all-time totals retain only aggregate counts plus one-way hashed unique identifiers.
- The counter does not use advertising cookies, fingerprinting, geolocation, camera, microphone, or cross-site tracking.

Local browser storage:
- Language/UI preferences, tactical notes and the “do not show again” fan-project notice preference may be stored locally in cookies/localStorage on your device.
- A random session identifier may be kept in sessionStorage while the tab/session remains open for online-presence counting.

Optional PUBG API features:
- If you use Player Stats or Match Analysis, the player name/account lookup you submit is sent to the ZONE//LAB Cloudflare backend and then to the official PUBG Game Data Service.
- The PUBG API key is intended to be stored only as the encrypted Cloudflare secret PUBG_API_KEY and is not exposed in client-side HTML/JavaScript.
- Short-lived Cloudflare/API caching is used to reduce rate-limit pressure and improve responsiveness.

ZONE//LAB does not intentionally request camera, microphone or geolocation permissions.