Terms & risk disclosures.

This document is a proposed set of terms for the hedge interface, prepared for review. The operating legal entity, contact address, governing law, dispute forum, and effective date have not been supplied. This draft is not represented as a finalized agreement or a statement of existing legal obligations.

Before adopting these terms, the operator must confirm its identity, applicable jurisdictions, eligibility restrictions, privacy disclosures, and enforceability with qualified counsel. Current feature availability is described separately in the documentation and may change.

hedge provides an interface for quote-aware token creation, allocation preferences, and market information on Solana. It interacts with independent wallets, Raydium LaunchLab, RPC services, metadata publishing services, and other third-party infrastructure.

The interface is not a bank, brokerage, exchange guarantee, investment adviser, or issuer guarantee. Third-party services have their own terms, charges, availability, and risks. A token displayed or inspected through hedge is not thereby endorsed or verified as lawful.

The proposed terms require users to have legal capacity and lawful authority to use the relevant services in their jurisdiction. Use must comply with applicable financial, sanctions, consumer-protection, intellectual-property, and other laws.

Creators are responsible for determining whether an offering, token, promotion, fee arrangement, or distribution requires registration, disclosures, restrictions, or professional advice. No jurisdiction-specific eligibility age or geographic access rule is asserted by this draft.

Users are responsible for protecting their wallet keys, account credentials, and devices and for reviewing every signing request. hedge never requires a recovery phrase or private key to connect a wallet.

Account-owned presets do not establish wallet ownership, creator status, or onchain fee entitlement. Users must not impersonate others, access another person’s account, or attempt to bypass authorization or platform checks.

A signed metadata message authorizes publishing, not a launch transaction. A launch requires separate transaction approval. Users should inspect the mint, quote asset, amounts, platform, and costs before signing.

Blockchain transactions can be irreversible, fail, expire, or confirm after a delay. Multi-stage launches can partially complete. Simulation, estimates, or a successful submission do not guarantee final confirmation or a specific outcome.

The interface cannot cancel confirmed onchain actions. Users must inspect existing submitted signatures before retrying an uncertain or partial operation. This draft makes no promise of refunds, recovery, or compensation.

Platform and creator fee rates are read from verified configuration and are distinct from protocol charges, network fees, account rent, liquidity effects, and optional purchases. Values shown before signing may change with current configuration and network state.

Allocation preferences do not change native fee beneficiaries or initiate background transactions. The intended Claim & Convert flow requires eligible fee authority, review, and wallet approval. Its execution remains unavailable until verified adapters are connected.

No fee display, token creation, graduation, or saved preset guarantees revenue, claim eligibility, a conversion price, or profitability.

Tokens may be highly volatile, illiquid, manipulated, fraudulent, or worthless. Losses can include all assets committed, network fees, and additional transaction costs. Quote assets can also lose value, depeg, be frozen, or face issuer and protocol risks.

Pairing against a stablecoin, staking asset, commodity-linked asset, or treasury-linked asset does not provide token collateral, redemption rights, insurance, or a safety guarantee. Planned assets are not verified launch support.

Smart-contract defects, compromised keys, malicious token authorities, chain congestion, forks, oracle errors, third-party outages, and regulatory changes can affect access and outcomes. No invented safety score replaces independent diligence.

Creators must have the rights and permissions required for token names, tickers, descriptions, artwork, links, and other submitted material. They must not misrepresent affiliations, impersonate a project, or publish illegal, deceptive, or infringing content.

Wallet-authorized metadata publishing sends artwork and metadata to third-party IPFS infrastructure. Content-addressed material may be publicly accessible, copied, cached, or retained after a canceled launch. Do not publish personal secrets or information you expect to be removable.

No transfer of artwork ownership, content license, takedown promise, or pinning-duration guarantee is established by this draft. Those operator policies require separate legal approval.

The proposed terms prohibit fraud, deceptive promotion, market manipulation, intellectual-property infringement, malicious uploads, unauthorized access, credential theft, and attempts to defeat transaction safeguards.

Users must not use the interface to exploit other users, overload services, conceal unlawful activity, or present unverified data as hedge-endorsed information. Legitimate security research should avoid accessing private information or moving funds without authorization.

Market information is informational only and can be incomplete, delayed, or unavailable. Names and tickers are not unique identifiers. Users should verify full mint addresses, pool attribution, permissions, and onchain transaction status.

Features may be blocked where configuration or services are unavailable. The interface does not guarantee continuous access, complete indexing, execution, returns, liquidity, or future support for a catalog asset.

Nothing in the interface or these draft terms is personalized financial, tax, or legal advice. Obtain independent professional advice when appropriate.

Wallet addresses, transactions, token metadata, and pool activity can be public onchain or through IPFS. Account sign-in and preset storage are separate from that public blockchain activity.

Wallet, account, RPC, publishing, and hosting providers may process information needed for their services. A finalized privacy notice must identify the operator, actual data practices, retention, legal bases where applicable, rights, and verified contact channels. This draft does not substitute for that notice.

Any final warranty disclaimer, limitation of liability, indemnity, suspension policy, dispute process, and governing-law clause must be assessed under applicable law. This draft does not invent a liability cap, mandatory arbitration, waiver of statutory rights, or an operating jurisdiction.

The operator must establish how final terms are accepted, communicated, dated, and updated. No acceptance is collected through this draft page.

A verified legal and support contact has not been provided. No address, email, or ticket-submission service is invented here. The final agreement must include confirmed operator and contact details before adoption.