This policy explains what HEIST collects, why, how long it is kept, and what you can do about it. HEIST is built on data minimisation: the game needs an identity and a wallet, and it asks for nothing else.
01What we collect
We collect only what the service needs to function:
- Account data — the username you choose, the method you signed in with (wallet, Google, or X), and the date the account was created.
- Wallet data — public wallet addresses linked to your account, the wallet type, and the chain. For a managed wallet, an encrypted signing key. We never hold the private key of an injected browser wallet.
- Authentication data — for social sign-in, the provider's account identifier and, where the provider supplies it, an email address and display name. We do not receive your password.
- Gameplay data — matches, results, stakes, payouts, and per-match statistics such as kills, hacks, and objective time.
- Transaction data — transaction hashes, amounts, and status for entries, payouts, and refunds.
- Technical data — the minimum required to serve a request and secure it, such as an IP address and user agent in server logs, and error reports when something fails.
02What we do not collect
- We do not collect your government identity, date of birth, address, or phone number.
- We do not read your wallet's other assets, your transaction history outside HEIST's contract, or your balances on other chains.
- We do not sell personal data, and we do not share it with advertising networks.
- We do not collect precise location data.
03Why we process it
- To operate your account and let you sign in.
- To run matches: place you in matchmaking, start a game, and determine a result.
- To settle stakes: verify deposits, attest the result, and pay the winner.
- To display your profile, match history, and the leaderboard.
- To prevent fraud and abuse — duplicate accounts, collusion, and settlement abuse.
- To diagnose faults and keep the service secure and available.
04How it is stored
Account, wallet, match, and transaction records are stored in a managed Postgres database. Managed-wallet signing keys are additionally encrypted with AES-256-GCM using a key held outside the database, so a database dump alone is not enough to sign for a user. Session state is held in a signed, httpOnly cookie.
05Blockchain data is public and permanent
Stakes and payouts are recorded on a public blockchain. Wallet addresses, transaction amounts, and transaction hashes are visible to anyone, permanently, and cannot be deleted, amended, or hidden by HEIST. If you stake USDC, that record exists independently of this policy and outside our control.
Deleting your HEIST account removes our records. It does not, and cannot, remove anything already written to Arc Mainnet.
06Third-party services
- Arc network and its RPC provider — to read balances and submit settlement transactions.
- A managed Postgres provider — to host the database.
- Google and X — only if you choose to sign in with them. They receive the fact that you signed in to HEIST; they do not receive your gameplay data.
- Hosting infrastructure — to serve the application.
Each of these providers processes data under its own privacy policy.
07Cookies
HEIST uses two strictly necessary cookies: a signed session cookie that keeps you signed in, and a short-lived sign-in nonce that protects wallet sign-in against replay. Neither is used for advertising or tracking, and there is no third-party analytics cookie.
08Retention
- Account and profile data is kept while your account is open, and removed when you close it.
- Match and transaction records are kept while your account is open so your history and the leaderboard remain accurate.
- Server logs are short-lived and used for security and fault diagnosis.
- Onchain records are permanent and outside our control (see clause 05).
09Security
Signed, httpOnly session cookies; server-side validation of every stake, result, and payout; parameterised database queries; encrypted managed-wallet keys; and escrow settlement enforced by a contract rather than by an operator. No system is perfect — if you believe you have found a security issue, report it privately rather than exploiting it.
10Your rights
Depending on where you live, you may have the right to access, correct, export, or delete the personal data we hold about you, and to object to certain processing. You can see most of it directly in your profile and match history. To make a request, contact us through the channel published in the application; we will respond within the period required by applicable law.
11Changes and contact
Material changes to this policy will be reflected in the “last updated” date above. Questions can be raised through the support channel published in the HEIST application.