The short version
Online 1v1 and four-player 2v2 need guest identities and shared match state. The bot tutorial and Practice Range stay local and do not join online queues. There are no ads, analytics trackers, chat, or payments in this version.
We do not request access to your location, microphone, camera, or contacts. Network infrastructure still receives your IP address when you make a request. The landing page’s interactive aim preview runs only in your browser; its angles and shots are not saved or sent to the online game service.
1. Your guest identity
The game creates a random guest ID and a secret guest credential so the service can recognize your session and authorize your actions. The server stores the random identity and a hash of the credential, not an email address or a real-world name.
- In the browser: the guest credential is kept in
sessionStorage, scoped to your tab’s session. It survives a refresh in that tab. Closing the tab normally ends that session; browser session restoration can affect this behavior. A new session may receive a new guest identity. - On iPhone: the guest credential is stored in the device’s Keychain. This lets the native app recognize the same guest across app launches.
Do not share this credential or include it in a support message. Other players cannot see it.
2. Data needed for online play
The Superapp Cloud online service uses Supabase-backed storage to run matchmaking and authoritative duels. The service—not your device—decides whether a shot hits, breaks cover, or ends a round.
| Data | Purpose |
|---|---|
| Random guest ID, generated alias, credential hash | Recognize and authenticate your guest without an account sign-up. |
| Queue tickets and selected 1v1/2v2 mode, team seats, readiness, connections, match and round state | Pair real rivals, coordinate shared starts, and handle disconnects. |
| Match timing, movement parameters, inputs and actions, ammunition, cover state, alive/eliminated status, team scores and results | Resolve play consistently for all two or four players and prevent duplicate actions. |
| IP addresses and request diagnostic logs processed by server infrastructure | Security, abuse prevention, troubleshooting, and service operation. |
Request logs may include timing, request metadata, and error information. They are operational records, not advertising analytics. We do not use them to build an advertising profile.
3. What stays on your device
Browser sound and tutorial preferences are saved in localStorage. The native app stores its sound preference, selected online mode, Practice Range setup, and first-launch tutorial-seen flag locally. These preferences remember your setup, whether sound is enabled, and whether you completed or skipped the tutorial. The browser keeps the current search ticket and its 1v1/2v2 mode in per-tab sessionStorage for refresh and reconnect.
Offline practice gameplay and scores never go to the cloud. The guided bot tutorial and browser Practice Range are separate from the online queue. Their shots, bot behavior, hit tallies, and practice results stay local. Range setup and results are held only in this page’s memory, not saved to browser storage.
The marketing and policy pages do not include analytics, advertising scripts, embedded third-party media, or tracking pixels. The game’s local storage is for identity and preferences, not cross-site tracking.
5. Retention and your choices
Server records are kept as needed for matchmaking, match integrity, security, service operations, and applicable legal obligations. No fixed deletion schedule is promised. Closing a browser tab, clearing storage, or removing the app does not itself delete server-side guest or match records.
You can clear this website’s local browser storage through your browser settings. This removes browser preferences and can end access to your current guest identity. Avoid doing this during a match. Native Keychain storage is separate from app preferences; uninstalling the app is not a guaranteed way to erase it or cloud records.
Depending on your location, you may have rights to request access, correction, or deletion of data associated with your guest identity. Such requests require contacting the service owner and may require verification that the identity is yours. Some records may need to be retained for security or legal reasons.
The owner’s support contact is not yet configured. A working request channel must be published before public release. Check Support for contact availability; do not send credentials to an unverified address.
6. Contact and policy changes
Questions about this policy or deletion requests should go to the service owner through the verified contact on the support page. The owner’s contact details are currently pending; there is no confirmed support email on this website.
We will update this page when data handling changes. New features, service providers, or contact details may require a policy revision. This policy describes the guest-based, no-ads, no-payments version of 360 Sniper Showdown.