The Hold

Legal & trust

Privacy Policy

This Policy explains what The Hold processes to run collections, profiles, competitions, analytics, and non-custodial trading—and which choices you control.

Last updated: September 15, 2026

1. Scope

This Policy applies to The Hold product surfaces and supporting services. It does not control a wallet, blockchain, liquidity venue, routing provider, or other third party you choose to use. Public blockchain activity remains governed by the network and may be permanently visible.

2. Wallet and ownership data

The Hold processes wallet addresses, verification challenges and signatures, wallet-session records, verified wallet associations, blockchain holdings, token balances, verification times, and sync status as needed to:

  • verify that a user controls a selected wallet;
  • maintain a session and link verified wallets to a user on The Hold;
  • read and aggregate supported holdings, build collection state, verify lifecycle ownership, and calculate Monthly XP events;
  • administer leaderboards, contest eligibility, and abuse protections;
  • prepare, validate, submit, track, and reconcile a wallet-authorized swap.

The Hold does not request or process your seed phrase or private key. Verification signatures prove wallet control; signed swap transactions are processed only when you choose to authorize a trade.

3. Public display

The Hold wallet addresses are not intended for display on public collector-profile or leaderboard surfaces. Public blockchain transactions may still expose addresses independently of The Hold, and a user can choose to share an address elsewhere.

The Hold public routes are designed not to expose wallet identifiers, internal user identifiers, exact token balances, portfolio value, session credentials, or authentication material.

4. Collector profile data

A collector profile can include a permanent username, display name, bio, selected avatar style, visibility choice, and chosen showcase entries. The Hold also derives privacy-safe collection totals, completion information, and earned achievements from verified collection history.

  • Public: permitted profile details, collection summaries, achievements, and showcase information can be opened by other users.
  • Private: the collector profile, collection details, showcase, and achievements are not publicly browsable.

5. Monthly contest data

Monthly Contest Participation is separate from profile visibility and starts off. The Hold processes consent time, acquisition receipts, fee evidence, lifecycle opportunities, XP events, score timing, standing, cutoff eligibility, and finalized winner records to run the competition fairly.

If a private-profile collector explicitly opts in, The Hold may publicly display only their username, contest rank, XP, qualifying activity count, and Top 5 or winner status. Their wallet address, exact balances, portfolio value, exact holdings, private collector profile, showcase, and private achievements remain hidden from the Monthly XP leaderboard.

Turning participation off removes an active standing and eligibility for any announced season prize but does not erase current private XP, achievements, or previously finalized contest results.

6. Collections, XP, achievements, and standings

The Hold processes current and prior verified collection entries, supported token identity, holdings verification time, confirmed The Hold acquisition and fee evidence, executed valuation, lifecycle transitions, XP events, achievements, monthly standings, and final winner data.

Active state reflects a current supported holding at the latest successful verified sync. Discovered state is persisted collection history, not proof of a fee-qualified acquisition. External holdings do not create Monthly XP or contest-qualified collection slots.

7. Trading data

To provide non-custodial swaps, The Hold processes the connected wallet, selected assets, amount, Jupiter order and fee information, short-lived wallet-signed order data when needed for safe execution retry, the public transaction signature, confirmed slot and block time, actual execution amounts, and limited handoff or recovery state. The Hold uses these records for fee collection, idempotency, rate limits, status recovery, verified holdings reconciliation, and acquisition receipts.

Confirmed transaction details also exist on the public Solana blockchain. The Hold does not control public-chain retention.

8. Privacy-safe product analytics

The Hold uses PostHog for a limited set of deliberately coded product events. The current implementation disables broad autocapture, automatic page views, heatmaps, exception capture, and session recording. It uses in-memory browser identity and an opaque The Hold analytics identifier for an authenticated session.

The analytics allowlist is designed not to intentionally send wallet addresses, signatures, verification challenges, session credentials, exact balances, transaction payloads, portfolio value, email addresses, bios, or private contest/profile data. GeoIP enrichment is disabled. Providers may still receive ordinary request metadata needed to deliver and secure their service.

9. Browser and local state

The Hold uses browser memory and limited browser storage where needed for interface state and secure handoff or recovery flows. Wallet software may maintain its own connection state under its privacy practices. The Hold Discovered collection history is associated with the verified The Hold user record; clearing browser data does not represent deletion of that persisted history.

10. Technical and operational data

Hosting, security, network, and application systems may process ordinary request and diagnostic information such as timestamps, route requests, response status, device or network metadata, rate-limit signals, error classifications, and infrastructure logs. The Hold uses this information to operate, protect, debug, and improve reliability. Sensitive values should not be intentionally written to public-facing logs.

11. How data is used

  • operate wallet verification, sessions, collections, profiles, XP, achievements, and leaderboards;
  • administer Monthly XP participation, standings, finalization, and prizes;
  • request, recover, and reconcile non-custodial Jupiter swaps;
  • detect fraud, manipulation, unauthorized access, abuse, and technical failures;
  • maintain service reliability, understand privacy-safe product use, and improve The Hold;
  • meet applicable legal, security, integrity, and operational obligations.

12. Service providers and disclosure

The Hold relies on providers for wallets, the Solana network, RPC and blockchain data, pricing, swap and liquidity routing, hosting, security, and analytics. Those providers may process the data needed to perform their role. The Hold may also disclose information when reasonably necessary to comply with law, protect rights or safety, investigate fraud or abuse, enforce terms, or support a business or service transition.

Data sent directly to a public blockchain is public by design and may be copied or analyzed by others.

13. Retention

The Hold retains data as necessary to operate the service, preserve collection and achievement history, maintain contest and transaction integrity, protect security, resolve disputes, enforce agreements, and meet applicable legal or operational needs. Different records have different lifecycles; short-lived challenges, sessions, and handoff records need not be retained for as long as finalized competition or collection-integrity records.

14. Your choices

  • Choose a public or private collector profile.
  • Turn Monthly Contest Participation on or off independently.
  • Disconnect a wallet session through The Hold and use wallet controls to manage the wallet connection.
  • Choose whether to authorize any transaction in your wallet.
  • Manage browser data and wallet-provider data through your browser or wallet, understanding that this does not automatically remove persisted server or public-blockchain records.

15. Security

The Hold uses technical and organizational safeguards intended to reduce unauthorized access, manipulation, and disclosure. No internet, wallet, software, or blockchain system can eliminate every security risk. You remain responsible for protecting your wallet, private keys, seed phrase, devices, and approvals.

16. Privacy requests and questions

Email privacy@cryptodexlabs.com for privacy questions or to start a request about your The Hold information. No X account or connected wallet is required to start a request.

Describe the request and include your collector username if you have one. Share only the information needed to explain the request; you do not need to attach identity documents, wallet balances, or a full transaction history to your initial email.

Depending on applicable law and the nature of the record, you may request access to, correction of, or deletion of information associated with your The Hold account. The Hold may need proportionate proof of wallet or account control before acting. A request may be limited where data must be retained for security, fraud prevention, transaction or contest integrity, legal obligations, or where information is recorded on a public blockchain or in an immutable finalized winner record.

Never email a seed phrase, private key, password, verification signature, signed transaction, session cookie, or recovery link. Any necessary account-control verification will be explained separately. Do not approve a transaction or transfer funds for a privacy request.

When you email us, we receive your email address and the information you choose to include. We use this correspondence to handle your request; email routing and mailbox providers also process it to deliver and store the message. The retention principles above apply to this correspondence.

The official The Hold X account (opens in a new tab) remains a source of public announcements, not the required channel for privacy requests. Do not post private request details publicly.

17. Changes to this Policy

This Policy may be updated as The Hold, its providers, or applicable requirements change. The posted “Last updated” date identifies the current version.