Skip to main content

Privacy policy

Last updated: October 9, 2026

Important — please read. This Privacy Policy ("Policy") explains what information chain.wtf collects when you use chain.wtf, its subdomains, applications and related interfaces (together, the "Interface"), including the chain.wtf developer platform (the "Developer Platform"), how we use it, and the choices you have. It forms part of our Terms of Service. Capitalised terms not defined here have the meaning given in the Terms of Service.

Summary (not legally binding)

This summary is provided for convenience only. The full Policy below controls.

  • chain.wtf is self-custodial and runs on the Base blockchain. Your wallet address is your identity. We do not ask players for their name, postal address or government ID.
  • Every wager, outcome, payout and transfer is recorded on a public blockchain. Anyone can see it, and nobody, including chain.wtf, can change or delete it.
  • Our servers keep copies of that public on-chain data so the Interface is fast to load. Those copies add no private information to what is already public.
  • Sign-in and embedded wallets are provided by Privy. Your login email or social account stays with Privy; chain.wtf does not store it.
  • We collect personal account data, such as email addresses and GitHub details, only from game developers who sign up for the Developer Platform.
  • We use product analytics to improve the Interface. We do not sell personal information.
  • Questions or requests: support@chain.wtf.

1. Who we are and what this Policy covers

1.1 chain.wtf operates the Interface and publishes the Protocol. References to "chain.wtf", "we", "us" and "our" mean chain.wtf in that role. References to "you" mean the person using the Interface or the Developer Platform.

1.2 This Policy covers information processed through the Interface and the Developer Platform. It does not cover the Base blockchain, wallet software, or third-party services you reach through the Interface. Those are governed by their own terms and privacy policies.

1.3 Games published by third-party developers run inside the Interface. Their on-chain activity is covered by this Policy in the same way as any other wager. A third-party developer does not receive your personal information from chain.wtf.

2. Public blockchain data

2.1 The Protocol runs on the Base blockchain. When you use it, your wallet address, your Smart Vault address and every transaction you make are permanently and publicly recorded on-chain. This includes wagers, outcomes, payouts, deposits into and withdrawals from liquidity pools, token transfers, affiliate referrals and credit purchases.

2.2 This data is public by design. It can be read by anyone using a block explorer or their own node, without any involvement from chain.wtf.

2.3 chain.wtf does not control the blockchain and cannot alter, hide or delete on-chain data, including in response to a deletion request. Before you transact, consider that your on-chain activity may be linked to you by anyone who learns which wallet address is yours.

3. Information we process when you play

3.1 Sign-in and wallets

3.1.1 Sign-in to the Interface and the embedded wallet are provided by Privy. You can sign in with an email address or with a Google, X (Twitter) or Discord account, or connect an existing wallet. Privy processes those credentials under its own privacy policy. chain.wtf receives your wallet address from Privy. We do not store your email address or social account details for player accounts.

3.1.2 When you create a Smart Vault, the Interface generates a session key in your browser. Its private key is kept only in your browser's local storage and is never sent to chain.wtf.

3.2 Indexed on-chain data

3.2.1 We index public on-chain data into our backend database (hosted by Convex) so the Interface can show your bet history, live wins, leaderboards, game statistics, balances and liquidity pool activity quickly. This includes wallet addresses, Smart Vault addresses, wager amounts, payouts, game addresses and timestamps.

3.2.2 These records are copies of public blockchain data. They are kept for as long as the Interface displays them, and they are rebuilt from the blockchain whenever needed.

3.3 Usernames

3.3.1 You may choose a display username. Usernames are not recorded on-chain. We store the username together with your wallet address and the time of your last signed update. Usernames are shown publicly next to your activity, for example on leaderboards and in live wins.

3.4 PvP chat and voice

3.4.1 PvP lobbies may offer text chat and voice. To admit you to a lobby's chat, we store a short-lived session record containing your wallet address, the lobby identity, the sign-in method used and timestamps. These sessions expire automatically.

3.4.2 To prevent abuse of read-only access for logged-out spectators, our web server derives a keyed one-way digest from your network address. Only that digest is stored, for a rate-limit window of about one minute. Your raw IP address never enters our database.

3.4.3 Text messages are delivered by Ably and are not stored in our database. Ably retains lobby messages for up to 30 days so recent messages can be shown to participants. Voice is delivered in real time by LiveKit. chain.wtf does not record voice.

3.4.4 If a moderator removes a message, blocks a participant or closes a room, we keep an audit record of that action, including the affected wallet address, for 30 days. We also keep hourly counts of chat and voice activity for 30 days. Those counts contain no wallet addresses, messages, audio or device information.

3.4.5 To decide whether you may post in chat, we compute your total lifetime wager from public on-chain data.

3.5 Analytics and diagnostics

3.5.1 We use PostHog and Google Analytics to understand how the Interface is used and to find errors. They record events such as pages viewed, a game round opened or revealed, a Smart Vault created and checkout steps, together with technical information such as browser type, device type, approximate location derived from your IP address, and error reports. These events do not include your wallet address. The providers use cookies or local storage to recognise a returning browser.

3.5.2 You can limit analytics with your browser's privacy settings, by blocking third-party cookies, or by using a content blocker. The Interface keeps working when analytics are blocked.

3.6 Data stored in your browser

3.6.1 The Interface stores a small amount of data on your device to work properly. This includes the Smart Vault session key, the affiliate address from a referral link you followed, game preferences, your language, the sidebar state and a sign-in hint. This data stays in your browser. You can delete it at any time by clearing your browser's site data. Clearing the session key means you will need to authorise a new one.

3.7 Hosting, infrastructure and swaps

3.7.1 The Interface is hosted by Vercel. Like any website, the hosting provider processes your IP address and request details to deliver pages and protect against abuse.

3.7.2 The Interface reads the blockchain through RPC providers, which receive the wallet addresses and transactions your browser asks about.

3.7.3 Cross-chain swaps and top-ups in the checkout are provided by LI.FI. When you use the checkout, LI.FI receives your wallet addresses and the details of the swap you request.

3.8 Promotions

3.8.1 Some promotions are run with partners such as TaskOn. When a partner asks whether a participant met a promotion's conditions, it sends us a wallet address or a Privy login email. For an email, we ask Privy for the linked wallet addresses. We check the public on-chain record and reply only with whether the conditions were met. We do not store the request.

4. Information we process on the Developer Platform

4.1 The Developer Platform lets game developers build, test and publish games. If you only play games, this Section does not apply to you.

4.2 Account. When you sign up, we store your email address, your name and either a hashed password or the profile your GitHub account shares with us (name, email address and avatar). For each signed-in session, we store a session token, your IP address and your browser's user agent.

4.3 GitHub. When you install our GitHub App, we store the installation, the GitHub account login it belongs to, and the repositories, branches, commit identifiers and commit messages of the projects you connect. To build your game, we check out its source code, keep an archived snapshot of the source and build output, and keep the build logs.

4.4 Projects and submissions. We store your projects, builds, the game metadata you publish (name, description and image), deployed contract addresses, transaction hashes, code hashes, review decisions and the reasons given for them.

4.5 Linked wallets. If you link a wallet to receive revenue share or authorship, we store your wallet and Smart Vault addresses together with your developer account.

4.6 AI review. Before a game is published, its source code may be reviewed automatically by an AI model provided through the Vercel AI Gateway or Amazon Bedrock. We store the review findings.

4.7 Test environments and play-tests. Test environments run your game in a sandbox hosted by Vercel. Automated play-tests can capture screen recordings, browser traces, console errors and notes from the session. These artifacts are stored in Amazon Web Services and shown to you and to the reviewers of your submission.

4.8 Developer balance. We keep a ledger of your developer balance, including deposits and withdrawals (which are also recorded on-chain), usage and any virtual credits granted to your email address.

4.9 Audit log. We keep a record of administrative actions taken on your projects and submissions, including the email address of the person who took them.

4.10 Developer Platform data is stored in our backend database (hosted by Convex) and in Amazon Web Services. Published games, their contracts and their catalog listings are public.

5. How we use information

5.1 We use the information described in this Policy to:

  1. (a) operate the Interface and show you your activity and the Protocol's public state;
  2. (b) run PvP chat and voice, enforce chat eligibility and moderate abuse;
  3. (c) operate the Developer Platform, including building, reviewing, testing, deploying and paying out for games;
  4. (d) detect, prevent and investigate fraud, abuse, security incidents and breaches of the Terms of Service;
  5. (e) assess eligibility and comply with legal obligations, as described in the Terms of Service;
  6. (f) understand how the Interface is used, fix errors and improve our products; and
  7. (g) answer your support requests.

5.2 Where the law requires a legal basis for processing, we rely on performance of our agreement with you (Sections 5.1(a) to (c) and (g)), our legitimate interests in running a secure, reliable and improving service (Sections 5.1(d) and (f)), and compliance with legal obligations (Section 5.1(e)).

6. How we share information

6.1 We do not sell personal information, and we do not share it for cross-context behavioural advertising.

6.2 We share information with service providers who process it on our behalf and under their own security obligations. These include Convex (backend database), Vercel (hosting, sandboxes and AI gateway), Amazon Web Services (storage, key management and AI models), Privy (sign-in and embedded wallets), Ably (chat), LiveKit (voice), PostHog and Google (analytics), LI.FI (swaps), GitHub (Developer Platform integration) and blockchain RPC providers.

6.3 We may disclose information where we believe in good faith that it is required by law, regulation or a valid legal request, or necessary to protect the rights, property or safety of chain.wtf, our users or others.

6.4 If chain.wtf is involved in a merger, acquisition or sale of assets, information may be transferred as part of that transaction. This Policy will continue to apply to it.

7. Retention

7.1 We keep information only as long as we need it for the purposes in Section 5:

  • On-chain data is permanent and outside our control.
  • Indexed copies of on-chain data and usernames are kept while the Interface displays them.
  • PvP chat sessions and sign-in challenges expire automatically, and spectator rate-limit digests are deleted after about one minute.
  • Chat messages are kept by Ably for up to 30 days. Moderation audit records and chat metrics are kept for 30 days.
  • Developer Platform account, project and build data is kept while your account is active and for a reasonable period afterwards to meet legal, accounting and security needs.
  • Analytics data is kept according to the retention settings of PostHog and Google Analytics.

8. Your rights and choices

8.1 Depending on where you live, you may have the right to access, correct, delete or export your personal information, to object to or restrict certain processing, and to withdraw consent. To make a request, email support@chain.wtf. We may need to verify that a wallet or account belongs to you, for example by asking you to sign a message, before acting on a request.

8.2 We will delete or anonymise the off-chain information we hold about you where the law requires it. We cannot delete or alter on-chain data, and the indexed copies of it will continue to reflect the public blockchain.

8.3 Developers can ask us to delete their Developer Platform account at support@chain.wtf. Games already published on-chain remain on-chain.

8.4 You can manage your Privy sign-in data through Privy, and you can clear data stored in your browser at any time as described in Section 3.6.

8.5 If you are not satisfied with our response, you may have the right to complain to your local data protection authority.

9. Security

9.1 We protect the information we hold with access controls, encryption in transit, hashed credentials and server-held signing keys, and we limit what we collect in the first place. No system is completely secure, and you are responsible for keeping your wallet, devices and credentials safe.

10. International transfers

10.1 Our service providers operate in several countries, including the United States. Your information may be processed outside the country where you live. Where required, we rely on appropriate safeguards for those transfers.

11. Children

11.1 The Interface is intended only for adults who meet the eligibility requirements in the Terms of Service. We do not knowingly collect information from anyone under 18. If you believe a minor has provided us information, contact support@chain.wtf and we will delete the off-chain information we hold.

12. Changes to this Policy

12.1 We may update this Policy from time to time. We will publish the updated Policy on the Interface, and the "Last updated" date at the top shows when it last changed. Continuing to use the Interface after a change takes effect means you accept the updated Policy.

13. Contact

13.1 For questions or requests about this Policy or your information, contact support@chain.wtf.