Privacy
Effective October 12, 2026 · app.openhedge.xyzThis notice explains the data used by OpenHedge accounts, funding and model activity. OpenHedge is operated by HedgeFund DAO, an organization registered in Singapore, which is responsible for this data. See also the Terms and Conditions.
Google account access
Google sign-in provides your verified email address and a unique Google account identifier.
We use them to create your OpenHedge account, authenticate you and recover the same account
when you sign in on another device. OpenHedge requests the openid and
email scopes. It does not request access to Gmail messages, Google Drive,
contacts or your Google password.
Account and financial records
OpenHedge stores your account identifier, funding address, sessions, deposit and withdrawal instructions, transaction references, accounting records and account performance. These records support account access, transaction reconciliation and your balance and activity displays. Trading rules use market and wallet activity; Google identity data is not an input to the trading model.
Sessions and security
Essential browser cookies maintain your login and protect the Google sign-in flow. Browser storage also remembers interface preferences. Request metadata and security records are used to limit abuse and investigate account problems. Signing out revokes the active application session. Do not share wallet credentials or sign-in codes with support.
Product diagnostics and support
We record predefined interaction events for sign-in, deposits, withdrawals and support, along with a random browser-tab reference and, when signed in, your verified account identifier. These records help diagnose problems and understand where journeys stop. They do not contain wallet signatures, private keys, amounts, full URLs or free-form error messages. Browser events are observations, not proof that a financial transaction completed. Contacting support opens your email app; you review and send the message yourself.
Services involved
Google processes authentication. Vercel delivers the application, and Railway hosts the account backend and database. Funding routes may use Relay and blockchain infrastructure providers. Trading uses Hyperliquid. These services receive the information necessary for their respective functions; funding and trading routes use wallet and transaction information rather than your Google email as the destination identity.
Public blockchain activity
Wallet addresses, transfers and onchain transaction records can be publicly visible. Public blockchain records cannot be erased by deleting an OpenHedge account. Your Google identity is kept in the account database; it is not deliberately written into blockchain transaction records by the application.
Retention and requests
Account and financial records are retained to operate the account, reconcile transactions and investigate security or accounting issues. For access, correction or deletion requests, contact telleria.gerardt@gmail.com from the email used for your account. Identity must be verified before account information is disclosed or changed. Deletion requests do not remove public blockchain records, and unresolved balances or transactions require reconciliation before the associated account records can be closed.