Privacy

Can you Survive?

5 questions. 60 seconds. Prove you would survive.

Current data use

No account or player registration is required. The game does not show ads, process payments, or add third-party analytics or tracking SDKs.

Local gameplay data

Optional nicknames, leaderboard results, and local survival trend history are stored in your browser localStorage. They stay on the device and browser where you play unless the browser clears local data.

Local trend history

Your recent play history, including scenario, score, survival title, survival time, and timestamp, is stored locally on your device for the survival trend display.

Optional anonymous server analytics

If the deployed backend is configured, the game may send anonymous game start and result events for aggregated admin analytics. These analytics may be stored in a Google Sheet controlled by IETC Training & Consulting. Approximate country, region, city, or timezone may be derived from server geolocation context. The game backend must not store or display raw IP addresses. A server-side salt is required to hash an anonymous repeat visitor key.

The analytics event row may include timestamp, event type, scenario, score result details, approximate location, hashed visitor key, and browser user-agent. No account or player registration is required.

Admin dashboard

The admin dashboard is intended to show aggregated participant counts, approximate locations, scenarios, scores, and trends. It should not expose raw IP addresses, player registration data, or secret admin tokens.

Sharing

The share buttons can open external platforms selected by the player, including WhatsApp, X/Twitter, LinkedIn, Facebook, Snapchat, TikTok, native device sharing, and clipboard copy. Those platforms are optional and have their own policies.

Store policy placeholders

Privacy policy URL: TODO_REAL_URL_REQUIRED. Support URL: TODO_REAL_URL_REQUIRED. Replace these placeholders before store submission.

Future changes

This page must be updated before adding third-party analytics, ads, accounts, payments, push notifications, backend leaderboards with personal data, or external SDKs. This page is not legal advice.