What Hunch does with your data

Hunch never asks for your name, email, phone number, password, or private key. When you play, your wallet signs a message describing your decision, Hunch verifies that signature, and stores the public key that signed it.

Hunch does not collect information that tells us your real-world name or identity. A public key or blockchain address can, however, be linked to a person elsewhere if that person has publicly associated it with themselves.

Depending on the experiment, Hunch stores:

• the public key that signed the decision
• the signature
• the exact message that was signed
• the payout address
• the blockchain address that actually paid, when there was one
• your decision
• your prediction
• the stake and amount involved
• whether the round used your own NIM or Hunch-provided NIM
• the time of the decision
• the transaction hash when a transaction settles
• a small amount of technical round metadata needed to run and verify the experiment

This information is used to run the experiment, verify commitments, settle NIM, prevent abuse, and produce the real results Hunch shows.

Hunch uses real past decisions in Results, Research, and Live. For example, Live may show that someone kept 100% of a Split round, or that a Trust participant returned a particular amount.

These public examples contain the decision, not your public key, device identifier, name, or other identity information. Hunch deliberately separates the behaviour from the identity.

Trust and Ultimatum are blind until both players have committed. Before that point, neither player can see the other’s decision.

Once both sides have committed, the experiment reveals the decisions and calculates the result. This is necessary for the experiment to work, and is enforced by the server, not just by the interface.

Nimiq Pay can provide Hunch with a per-origin device identifier. Hunch uses it only as an anti-abuse signal, to limit how many Hunch-funded rounds can be played from one device. It helps stop someone from creating fresh wallet keys to repeatedly use the house-funded pool.

It is not used as your identity and is not part of your signed decision. Hunch does not use it to track you across other websites or apps.

Your Results history and unfinished round shortcuts are stored in your browser’s local storage, not as an account on Hunch’s servers. Hunch keeps up to 30 recent Results entries on that device.

Clearing browser storage, using private browsing, or switching devices can remove those local shortcuts and Results. It does not delete the actual round records stored by Hunch.

Hunch’s own code does not use:

• tracking or advertising cookies
• Google Analytics or Meta pixels
• fingerprinting
• location data
• biometric data
• advertising profiles
• cross-site tracking

Hunch does not sell your data or share it with advertisers or data brokers.

When NIM moves on the Nimiq blockchain, the transaction is public by design. A transaction can reveal the sending address, receiving address, amount, timestamp, and transaction hash through a block explorer.

Hunch does not control this visibility. It is a property of the blockchain itself.

The builder has a password-protected admin tool used to operate Hunch’s house-funded rounds, review payouts, and investigate abuse. This can expose public wallet keys, device identifiers, round counts, payout records, and other information needed to operate the system.

It does not give the builder access to a player’s private wallet keys. This access exists to operate the product, settle NIM, prevent abuse, and keep the house-funded pool solvent. It is not used to build personal profiles.

Hunch runs on Vercel. Hunch’s own application code does not read or maintain a separate analytics profile about visitors. The hosting provider may process ordinary request and infrastructure information as part of operating its service.

Hunch keeps round records because its Research, Live, and reveal experiences are based on real past rounds. Completed and settled rounds are retained.

Unanswered two-player rounds can become expired after 48 hours, but expiry changes their status rather than deleting the record.

There is currently no self-serve way to delete a round. If you have a specific privacy request, contact the builder through the GitHub repository.