Legal · draft
Back to markets →This draft explains the categories of information the public beta needs to operate wallet-authenticated market and support flows.
Beta information
This information describes the current beta and is still under review. Availability depends on your eligibility and the restrictions of the connected services. For assistance, use in-app Support.
Depending on the feature you use, GG Markets may process a connected wallet address, a signed wallet-authentication session, market and order references, on-chain transaction references, and the settings needed to keep a request tied to the correct wallet session.
If you contact support, the beta stores the category, subject, message, optional reply email, ticket status, and replies from support. Support tickets are designed to expire from the durable inbox after 90 days.
Never send a private key, seed phrase, recovery phrase, wallet signature, password, API credential, or other secret to GG Markets support. The support form does not provide attachments and rejects common secret-like material. If a message contains a secret, rotate or revoke it through the appropriate wallet or service immediately.
Information is used to authenticate the wallet session, show wallet-scoped balances and activity, prepare or reconcile an action you explicitly review, prevent duplicate or abusive requests, answer support requests, and maintain limited operational evidence.
GG Markets should only receive the minimum information needed for the requested feature. The market venue, bridge providers, wallet providers, RPC providers, and infrastructure vendors may process information under their own policies when a feature calls them.
Support records are stored in a configured server-side Redis store and expire after 90 days. Limited operational events are retained for up to 30 days. Unresolved withdrawal and redemption recovery records are retained until reconciliation; they are not automatically deleted simply because time has passed.
Wallet and trading sessions use cookies, including encrypted trading authorization credentials. Browser storage holds preferences and recovery references. The app processes the signatures needed for reviewed wallet actions, but does not need your private key or seed phrase. Infrastructure providers may process request metadata such as IP addresses, including for geographic eligibility checks.
Support does not accept attachments. Public blockchain records and records held by venues or infrastructure providers follow those systems' retention practices and may not be deletable by GG Markets.
Requests about access, correction, or deletion can be raised through Support. Public blockchain records and records held independently by other services may not be changeable or removable.
When website analytics is enabled, you can allow or decline optional Google Analytics cookies. The Google tag loads only after you allow it. Analytics measures page visits and general device and referral information; our page-view integration excludes URL query strings and fragments and does not send wallet addresses, balances, signatures, or support messages as event fields. Google processes analytics information under its own privacy policy. You can change your choice using the analytics preferences on this page; declining stops future measurement in this browser but does not delete previously collected data.
When PostHog product analytics is configured, the browser also sends page paths and launch-funnel events such as match views, wallet connection, trading setup, deposits, and orders. Those events do not include wallet addresses, email addresses, or order amounts. Session replay may be included and masks form inputs; it can be turned off without removing the other product events. PostHog processes that information under its own privacy policy.
For wallet-scoped support, sign in with the wallet used for the issue and use the Support page. Do not put a different wallet address in the form to look up another person's tickets.
Include only the information needed to explain your request. If you cannot authenticate your wallet, use the support contact shown on this page when available.