huntgig.

Privacy, without the mystery

Transparent product rules for the HuntGig launch preview.

This draft explains the implemented product behaviour. It is not a substitute for approved merchant policies and applicable consumer rights.

Information used to operate the game

Organiser accounts store a name, email address, and a one-way password hash. Guests provide a nickname and receive a secure browser cookie. Room membership, answers, puzzle progress, hints, and server timestamps are saved so players can reconnect.

Purchases and personalisation

Purchase and provider payment references are stored for verification and reconciliation. HuntGig does not collect card details directly; checkout is handled by the payment provider. Personalisation text is visible only to the organiser and authorised room members at the relevant stage of the game.

Cookies and local storage

Essential HTTP-only cookies identify organiser sessions and guest membership. A currency preference cookie saves INR or USD when you choose; a country hint from the hosting platform can select the initial pricing currency. Local storage remembers your appearance, motion and sound preferences, private answer drafts, personal evidence notes, and an unsaved personalisation draft. Pending operation references use session storage to reconcile interrupted requests. Shared pins, evidence notes, readiness and accepted progress are stored with the room. No advertising cookies are intentionally added by this application. The payment provider has its own privacy practices.

Operational analytics

The server records product events such as demo starts, verified payments, room starts, and puzzle outcomes. Practice records the steps reached with a random run reference saved in this tab; replay starts a new reference. Practice measurements are not linked to your account. Help reports record a selected reason and chapter, without written answers or nicknames in report metadata. Private admin reports show aggregate progress and help counts. Revenue metrics use server-confirmed captured payments. No invented player counts or testimonials are used.

Anonymous product analytics

To learn which parts of HuntGig people use, the site records a short list of first-party events: visiting the home page, starting or finishing the demo, creating a room, a verified purchase, opening or accepting a challenge link, and starting or finishing the daily case. Each browser gets a random identifier kept in local storage; it is not a cookie and is not linked to your account, name or email. Events carry only the page path, a time, and simple values such as a case or difficulty, never answers, nicknames or other text you type. Events go only to HuntGig's own server and appear only as totals in a private admin report. If your browser sends Do Not Track or Global Privacy Control, no events are recorded. Clearing site data removes the identifier.

Required before launch

Data-controller details, a verified privacy contact, retention periods, deletion/export handling, hosting region, and provider agreements require operator review. Account deletion and export self-service are not implemented in this preview.

Contact & support →