Legal

Privacy Policy

Last updated: 14 sections

Greenwood has no accounts and no trackers of its own. This page lists, service by service, what data does leave your browser when you use it, and why.

Contents14 sections

In short

  • No accounts, no cookies of our own, no analytics or ad trackers of our own. We don’t sell personal data.
  • Your wallet address and your transactions are public, permanently, on the blockchain.
  • Some services receive technical data such as your IP address, and some also your wallet address: the Robinhood Chain RPC endpoint, WalletConnect (loaded on every page), ENS lookups, your wallet, and the GeckoTerminal chart on token pages.
  • Settings and wallet-connection data are kept in your browser’s storage, on your device.

01Who we are and what this covers#

This Privacy Policy explains what personal data is processed when you use the Greenwood Launchpad website and app (the “Interface”), operated by [Entity name] (“Greenwood”, “we”, “us”), and which third-party services receive data along the way. Where data protection law uses the term, [Entity name] is the controller of the limited data we process ourselves.

It covers the Interface only. The blockchain, your wallet and the third-party services described below handle data under their own policies. Our Terms of Use also apply. Questions: [Contact email].

02What we collect, and what we don’t#

What we don’t collect. Greenwood has no user accounts, sign-up or login. We don’t ask for your name, email address, phone number or identity documents. We don’t run analytics, advertising, tracking pixels, session recording or error-reporting tools of our own, and the Interface sets no cookies of its own.

What the Interface does process:

  • Technical request data. Like any website, our servers and our hosting provider receive your IP address, browser user agent and the address you request when your browser loads a page or calls one of our server routes (see section 6).
  • Your public wallet address. When you connect a wallet, the Interface learns its public address and uses it in your browser to show balances, prepare transactions and look up your ENS name. We don’t store it on our servers, but requests that contain it go to some of the services in section 4.
  • Your transactions. Transactions you sign go from your wallet to the blockchain, where they are public (see section 3).
  • Token content. If you launch a token, your transaction publishes its name, ticker and metadata (description, logo, links) on the blockchain.
  • What you send us. If you contact us by email, X or Telegram, we receive what you send, such as your email address or handle and your message, and use it to reply.

03Public blockchain data#

Robinhood Chain is a public blockchain. Your wallet address and every transaction it makes (launches, trades, approvals, fee collections), with amounts and times, are recorded permanently and can be seen by anyone, for example in a block explorer. Wallet addresses are pseudonymous, but they can be linked to you, for example if you share your address or use it with a service that knows who you are. Neither we nor anyone else can change or delete blockchain data.

The Interface reads this public data and displays it: token creators, trades, volumes and holders. Our analytics page also lists the 25 wallet addresses with the highest trading volume on Greenwood pools, with their volume, number of trades and number of tokens traded. If you have a concern about how your address appears in the Interface, contact us at [Contact email]. We cannot remove anything from the blockchain itself.

04Services that receive data#

Using the Interface makes your browser, or our servers, contact the services below. Each one receives the data listed and handles it under its own policy, which we do not control.

Robinhood Chain RPC endpoint

Who
rpc.testnet.arc.io, the public endpoint of Robinhood Chain Testnet, which is run by its network operators (their terms (opens in a new tab)) and served through Cloudflare. If we configure another Robinhood Chain RPC provider, it receives the same data.
When
On every page, repeatedly while it is open: this is how the Interface reads the blockchain.
Receives
Your IP address, user agent and our site’s address. The requests can include your connected wallet address (to read balances), the tokens and pools you view, and the hashes of your transactions (to follow their confirmation). Cloudflare may set its __cf_bm bot-management cookie. Your signed transactions do not go through this endpoint: your wallet sends them through its own provider.

Our RPC relay

Who
Our own server route (/api/rpc), which forwards to the same Robinhood Chain RPC endpoint.
When
Only as a last resort, if your browser blocks direct requests to the Robinhood Chain RPC endpoint.
Receives
It forwards only the body of read requests, which can include your wallet address. Your IP address and browser headers are not passed on, so the Robinhood Chain RPC endpoint sees our server instead of you. It refuses transactions, and our code does not log or store the requests. Our hosting provider’s logs still apply (section 6).

ENS name lookup

Who
Ethereum mainnet RPC providers: eth.merkle.io, with Alchemy (eth-mainnet.g.alchemy.com) as a fallback, currently through a shared default key of the Scaffold-ETH 2 toolkit, so Alchemy records these lookups under that key’s account, not Greenwood’s.
When
After you connect a wallet, to show your ENS name and avatar instead of your address.
Receives
Your wallet address, IP address and user agent. If your ENS profile has an avatar, your browser loads it from wherever that profile points, which can be any web host or IPFS gateway.

WalletConnect (Reown)

Who
Reown, formerly WalletConnect (Reown’s privacy policy (opens in a new tab)).
When
On every page load, before you click “Connect”, because the wallet-connection software starts with the page. Again when you open the wallet list or connect through WalletConnect.
Receives
On load: a start-up event with a WalletConnect project identifier (currently a shared default of the Scaffold-ETH 2 toolkit, so Reown records this traffic under that project, not Greenwood’s), our site’s domain, a random client identifier and your user agent (operating system and browser version), plus your IP address. The list of wallets and their icons is loaded from Reown’s servers. If you pick WalletConnect, its verification service receives our site’s origin, and once you are paired, encrypted session messages pass through its relay between the Interface and your wallet. Reown’s privacy policy says it may collect your IP address, full wallet address, client ID, user agent and country or region. It also stores data in your browser (section 5).

Your wallet

Who
The wallet you choose: MetaMask, Coinbase Wallet, Ledger, Rainbow, Safe, or a wallet connected through WalletConnect.
When
When you connect it and whenever you sign.
Receives
Our site’s address and the transactions and messages you are asked to sign, plus whatever the wallet collects under its own policy. Your wallet sends your signed transactions to the blockchain through its own RPC provider. Without its browser extension, Coinbase Wallet opens keys.coinbase.com, run by Coinbase.

GeckoTerminal price chart

Who
GeckoTerminal, operated by Gecko Labs Pte. Ltd., Singapore (terms (opens in a new tab), privacy policy (opens in a new tab)).
When
When you open a token page, where the chart is an embedded frame.
Receives
The token’s address (in the chart’s URL), your IP address, user agent, and our site’s address as the referrer. Inside its frame, GeckoTerminal loads its own tools, which we observed to include New Relic, Bugsnag, Cloudflare Web Analytics and Maze, and stores identifiers such as NRBA_SESSION and bugsnag-anonymous-id. Its privacy policy also covers cookies, web beacons and Google Analytics. We don’t control what the frame loads.

Token images and creator links

Who
Any web host chosen by a token’s creator, or the ipfs.io gateway (Protocol Labs) for IPFS images.
When
When a token’s logo is shown and it is hosted off-chain. Logos added through Greenwood’s launch form are stored on the blockchain inside the token’s data and load without any third-party request, but anyone can launch a token with an image link that points anywhere.
Receives
Your IP address, user agent and our site’s address as the referrer. Creator websites and social links are ordinary links: they receive data only if you click them.

Etherscan

Who
Etherscan (api.etherscan.io).
When
Our server contacts it to verify the source code of launched tokens (after a launch, or when a token page is opened) and to build the analytics page.
Receives
Server to server only: the token’s address, the chain, the token’s source code and launch parameters, and our API key. No visitor data.

Team tools

Who
Hugging Face (image generation) and the jsDelivr CDN (emoji artwork).
When
Only on our token-idea page, a team tool that is not linked from the site but can currently be opened by anyone who has its address.
Receives
Hugging Face receives text prompts and a random number from our server, with no visitor data. jsDelivr receives the IP address and user agent of whoever opens that page.

Links you click

Who
X, Telegram, the Robinhood Chain explorer, arc.io and other sites we link to.
When
Only when you click a link to them.
Receives
What any website receives when you visit it, under its own policy.

Our fonts are bundled with the site and served by us: your browser does not contact Google Fonts or any other font service.

05Browser storage and cookies#

The Interface sets no cookies of its own. It and the wallet libraries it uses keep a few values in your browser’s storage, listed below. They stay on your device: our servers do not read them. Session storage is cleared when you close the tab; the rest stays until you clear your browser data.

greenwood:board-layout

localStorage

Greenwood. Remembers whether you view the board as a grid or a table.
greenwood:sidebar-collapsed

localStorage

Greenwood. Remembers whether the sidebar is collapsed.
greenwood:intro-seen

sessionStorage

Greenwood. Remembers that you closed the welcome popup, for this tab only.
greenwood:create-draft

sessionStorage

Greenwood. Carries a token draft (name, ticker, description, logo, starting market cap) from our token-idea page to the Create page. It is removed as soon as the Create page reads it.
greenwood:idea-lab-v2

sessionStorage

Greenwood. Keeps the idea cards, including images, of our token-idea page during the tab session.
greenwood_research_results_v1

localStorage

Greenwood. Remembers test tokens launched from our research page.
scaffoldEth2.selectedContract

sessionStorage

Greenwood. Remembers the last contract picked in the developer contract page.
wagmi.storewagmi.recentConnectorIdwagmi.injected.connectedwagmi.<connector>.disconnected

localStorage

wagmi (wallet library). Remembers your wallet connection, the network and the last wallet used, so it can reconnect.
rk-versionrk-latest-idrk-recentrk-ens-name-<address>WALLETCONNECT_DEEPLINK_CHOICErk-transactions

localStorage

RainbowKit (wallet menu). Remembers the last and recent wallets you picked, caches your ENS name for 3 hours, and stores the mobile wallet link you chose. The recent-transactions key is not used by Greenwood.
WCM_VERSIONWALLET_CONNECT_V2_INDEXED_DB

localStorage, IndexedDB

WalletConnect (Reown). The WalletConnect SDK’s keys, pairings, sessions and a random client identifier. Written on the first page load, before you click anything.
-CBWSDK:*-walletlink:*

localStorage

Coinbase Wallet SDK. Coinbase Wallet session data. Written only if you connect with Coinbase Wallet.

Third-party cookies and storage. The Robinhood Chain RPC endpoint may set Cloudflare’s __cf_bm cookie, and the GeckoTerminal chart keeps its own storage inside its frame (see section 4). Your browser may block some of these.

06Our servers and hosting#

Greenwood has no database and keeps no visitor records. Our server routes are the RPC relay, token verification, analytics, an image tool for our token-idea page, and a research tool (/api/research) that signs Robinhood Chain Testnet transactions with the Greenwood team’s own test wallets. None of them logs or stores visitor data. They keep only short-lived, in-memory copies of public data: the analytics results for about two minutes, and the list of tokens already sent for verification.

The site is hosted by [Hosting provider]. Our hosting provider may log basic request data, such as IP address, requested URL (including its query parameters), user agent, time and response status, to run and secure the service, and keeps those logs under its own retention rules.

07How we use data, and what we never do#

We use the data described above only to:

  • run the Interface: read the blockchain, show tokens and balances, and prepare your transactions;
  • keep it working and secure, for example by limiting the size of requests to our RPC relay;
  • answer your messages; and
  • comply with the law.

We do not sell or rent personal data, show ads, or build profiles of visitors.

Where laws such as the GDPR apply, we rely on our legitimate interests in running, securing and improving the Interface and in showing public blockchain data, on providing the Interface you choose to use under our Terms, and, when you contact us, on answering your request.

08Sharing and international transfers#

We share data only:

  • with the service providers described in section 4 and section 6, as needed to run the Interface;
  • when the law requires it, or to protect rights, safety and the Interface; and
  • with a successor, if the operation of Greenwood is transferred.

These providers may process data in countries other than yours, including the United States and Singapore, where data protection rules may differ from those where you live.

09How long data is kept#

  • We keep no visitor data ourselves.
  • Browser storage stays on your device until you clear it (session storage until you close the tab).
  • Hosting logs are kept by our hosting provider under its own rules.
  • Messages you send us are kept as long as needed to handle them and keep a record.
  • Blockchain data is permanent.

10Children#

Greenwood is for adults (see Terms, section 2). It is not directed at children, and we do not knowingly collect their data. If you believe a child has sent us personal data, contact us so that we can delete it.

11Your rights#

Depending on where you live (for example under the GDPR, the UK GDPR or Californian law), you may have the right to access, correct or delete your personal data, to restrict or object to its processing, to data portability, and to withdraw any consent you gave. You may also complain to your data protection authority.

Because we have no accounts or visitor database, we usually hold nothing we can link to you. Data held by the services in section 4 is under their control, so contact them directly for it. Blockchain data cannot be changed or deleted by anyone.

To make a request, write to [Contact email]. We may need to check that the request comes from you, for example by asking you to sign a message with your wallet. Signing a message never requires your seed phrase or private key: never share them.

12Security#

Our server code stays minimal and stores no visitor data, which limits what could ever leak. No system is completely secure, though, and you are responsible for the security of your devices and your wallet.

13Changes to this policy#

We may update this policy, for example when the Interface or the services it uses change. The new version is posted on this page with a new “Last updated” date. We may also point out significant changes in the Interface or on our official channels.

14Contact#

GreenwoodLaunchpad

One click to launch, zero launch fee. Meme tokens on Robinhood Chain, paired with ETH.

© 2026 Greenwood. All rights reserved.

Greenwood is a non-custodial interface to smart contracts on Robinhood Chain. It never has access to your keys or the assets in your wallet: you create and sign every transaction in your own wallet, and once a transaction is confirmed no one, Greenwood included, can cancel or reverse it. Trading fees wait in Greenwood's fee contract, which has no owner, until anyone pays them out to the token's fees recipient and the protocol treasury. Greenwood is not a bank, broker, exchange, custodian or investment adviser, and nothing on this site is financial, legal or tax advice. Tokens are launched through public contracts by their creators, and the Greenwood team may also launch, hold or sell tokens from its own wallets. All of them appear here automatically, so listing, ranking or featuring a token is not an endorsement. $WOOD is Greenwood's own platform token: the Greenwood team launched it with its first-generation launchpad and has since withdrawn its liquidity. The “Official” label only shows that it comes from the team; it is not a recommendation. Tokens, $WOOD included, are highly speculative and can lose all their value. You are responsible for your decisions, your wallet and the laws that apply to you.

Greenwood is an independent project built on Robinhood Chain. It is not affiliated with, endorsed by or sponsored by Robinhood Markets, Inc. or its affiliates, by the operators of the Robinhood Chain network, or by Universal Navigation Inc. (Uniswap Labs). Robinhood is a trademark of Robinhood Markets, Inc. $WOOD is not ETH, the network's native token, and it is not issued or endorsed by Robinhood Markets. Greenwood pools use the Uniswap v4 protocol; Uniswap is a trademark of Universal Navigation Inc. Other company names, tickers and logos belong to their owners and are used only to identify them; no affiliation with those companies is implied.