Privacy Policy
Last updated 18 October 2026
The short version
- There are no accounts, emails or passwords. Your wallet address is the only identity Grid Master knows.
- We keep a copy of your vault settings and trade history in our database, tied to your wallet address. The blockchain keeps its own copy, in public and for good, and nobody can erase that.
- Anyone who knows a wallet address can look up that wallet's vaults and trades through our site. You cannot switch this off.
- We do not add any analytics, advertising or error-tracking service of our own.
- Delete Vault erases our database copy of a vault that held real funds. It does not touch anything on a blockchain.
This page describes what the software does today. It is not a statement that Grid Master meets any particular privacy law, and it is not legal advice. See also the Terms of Service.
1. Your keys stay with you
Grid Master is non-custodial software. It never asks for, receives or stores your private key or seed phrase. Your wallet signs messages and transactions on your own device, and the site only sees the result.
That does not mean we hold no keys. The keeper's key is the key of the bot that trades for your vault: it can trade through the router your vault is pinned to and it cannot withdraw. The people who run Grid Master also hold the keys of two multisigs. On Solana, 2 of 3 signers can replace the program's code. On Robinhood Chain, a 2-of-3 Safe sets the trading fee. The Security page sets out what each of these keys can and cannot do.
2. What we store
Our database holds the following, and nothing about you beyond it:
- Vaults.Your wallet address as the owner, the vault's address, the two tokens and their accounts, the strategy and its settings (price band, number of levels, trade limits, intervals), the chain, whether the bot is switched on, when the vault was created, and the transaction that created it.
- Trades. For each trade the keeper makes for a vault: the transaction signature, buy or sell, the tokens, the amounts, the price, the fee, which grid level fired, and when.
- An event log. One entry for each notable keeper event on a vault, such as a trade or a failed or uncertain attempt, with the details of it and which keeper instance handled it.
- Daily totals. For each vault and each day: the number of trades, the volume, the profit and the fees.
- Keeper housekeeping. Which keeper instance is looking after which vault, and when it last checked in. Plus lists of tokens we recognise, which contain nothing personal.
- An older invite list. A table for an earlier invite list (a wallet address and an optional note) still exists. Nothing in the website or the keeper reads it. Only two scripts the operators run by hand touch it.
A wallet address is not a name, but it is a permanent identifier. Anyone who knows which wallet is yours can follow everything attached to it.
3. What is public, whatever we do
- The blockchains. Every vault, deposit, withdrawal and trade is recorded on Solana or Robinhood Chain for anyone to read. Nobody, including us, can remove it.
- Our site repeats part of it, with no sign-in. Given a wallet address, the site returns that wallet's vaults and their settings. Given a vault address, it returns that vault's recent trades. These are the same records described above.
- The leaderboard. It is public. In the wallet view it shows a shortened wallet address (the first and last four characters) next to profit, volume, fees and number of trades, for any vault that has traded. There is no opt-out. Deleting a vault removes it from the board within a few minutes.
4. What we do not collect
- No name, email address, phone number, password, age or referral code. The database has no field for any of them. The one free-text field is the optional note on the older invite list described in section 2.
- No network (IP) address and no location in our database. Your address does reach our host with every request, and we use it in two ways without saving it: the country the host reports is checked to block restricted regions, and our servers count requests per address in memory, in one-minute windows, to slow down abuse.
- No analytics, advertising, tracking pixels or error-reporting services of our own. None is installed in the website or the keeper. Wallet libraries are third-party code, and some of them carry analytics code in their own dependencies (MetaMask's SDK, for one). We did not add it and cannot vouch for it. The site's security policy limits which services the page can connect to (see section 6).
- No copy of what you sign. When you approve a change, the signed message is checked and then dropped; only a one-time number is remembered, in memory, until it expires.
- No font host of our own. Our fonts are served from this site's own address. The site's security policy does still permit Google's font host (see section 6).
5. Cookies and browser storage
Grid Master's own code sets only the cookies below, and most visitors are sent none at all.
gm_platform. Only people who open the site with ?platform=seeker, which is what the Solana dApp Store app does. Remembers that this is the Solana-only version of the app, so it does not flash the other chain's screens. Lasts: One year, or until you open the site with ?platform=web.gm_admin_session. Only the people who run Grid Master, after they sign in to a private dashboard with an approved wallet. Ordinary visitors are never sent it. Keeps that sign-in alive. It is readable only by the server, not by scripts on the page. Lasts: 12 hours.
Grid Master also writes these records to your browser's local storage. They stay on your device and are not sent to us:
gridmaster:tos-accepted. That you ticked the Terms of Service box. The key includes your wallet address, so the box is only asked once per wallet. Lasts: Until you clear this site's data in your browser.gm_wallet_intent_solana and gm_wallet_intent_evm. Which chain you chose to connect, so the wrong wallet is not connected by accident. Lasts: Until you disconnect or clear this site's data.gm_vault_onboarding_seen. That you have already seen the one-time hint on an empty vault. Lasts: Until you clear this site's data.gridmaster.gridPresets.v1. Grid setups you chose to save, under the names you gave them. Lasts: Until you delete them or clear this site's data.gridmaster.pendingVaultCreates.v1. A vault creation that was interrupted (vault address, transaction hash and the settings you chose), so it can be finished instead of lost. Lasts: Cleaned out once a record is 30 days old.gridmaster.vaultMigrations.v1. Progress of moving a vault to a newer version, so an interrupted move can be resumed. Lasts: Cleaned out once a record is 30 days old.
The wallet libraries the site uses also keep their own records in your browser, such as the wallet you used last. You can clear all of this in your browser settings. The cost is small: you will be asked to accept the Terms again and your saved setups will be gone.
6. Other companies that see some of your data
Using Grid Master means some requests go to other companies. They have their own policies and we do not control them.
Where your records live
These three run the website, the database and the keeper, so they handle your records directly.
- Vercel. Hosts the website and its API, so it sees every request to them: your network (IP) address, the page or API address you asked for, and any wallet or vault address in that request. It may keep its own logs under its own policy.
- Neon. Hosts the database that holds the records listed under What we store, and may keep backups under its own policy.
- Railway. Runs the keeper, the always-on program that watches vaults and sends trades. It reads and writes the database, and its operating logs can include vault identifiers and transaction hashes.
Services your browser may contact directly
When you use the site, your own browser can call these. Each of them sees your network (IP) address, and we cannot see or control what they do with it.
- Solana RPC provider. Answers your browser's questions about the Solana chain (balances, your vault) and relays transactions you send. It sees your IP address and the wallet and vault addresses it is asked about. The site's security policy allows Helius, Alchemy and Solana's own public endpoints; which one is used is set in the site's configuration, not in this code.
- Robinhood Chain RPC. Robinhood Chain's public endpoint, which answers your browser's questions about that chain and relays transactions you send. It sees your IP address and the addresses it is asked about.
- DexScreener. Prices, token logos and the token search on the create screen. It sees your IP address, the token addresses your screen needs and whatever you type into the token search box.
- WalletConnect (Reown). On the app's wallet pages, the wallet-connection library contacts WalletConnect (Reown) for its configuration and wallet list, and relays the connection if you pick a WalletConnect wallet. It sees your IP address and, once you connect, the wallet you pick.
- Token logo hosts. A token's logo is shown from whatever web address that token's own data points to (its Jupiter or DexScreener listing, or its on-chain metadata). The site's security policy lets the page load images only from GitHub, Jupiter's image host (static.jup.ag), DexScreener and WalletConnect. If a logo is hosted at one of those, your browser fetches it from there and that host sees your IP address. The browser blocks a logo hosted anywhere else, and the site shows a placeholder instead.
Services our servers and keeper contact
These are called from our servers and the keeper, so they see our servers' network address and not yours. They are asked about tokens, prices, wallets and vaults.
- Jupiter. Finds swap routes. Our servers use it to check that a token pair can be traded, and the keeper uses it to build each Solana swap, so it sees the token pair, the amount and the vault address that will trade.
- DexScreener (servers and keeper). Token prices for portfolio values, the vault screens and the keeper's trading. It sees token addresses, not who is asking about them.
- RPC providers (servers and keeper). Our servers and the keeper read vaults and balances from the same kind of provider as above, and the keeper sends its trades through one. They are asked about wallet and vault addresses, and the request comes from our servers' network address, not yours.
- Birdeye (only if switched on). An extra price source for the keeper, used only when a Birdeye key is configured. It sees token addresses.
- Chainlink and Pyth price feeds. Not contacted directly. Where a vault uses one, the price is read from the blockchain itself through the RPC providers.
- Operator alert destination. Only if the operators set it up, Grid Master posts alert messages to a chat or notification address they choose, for example Telegram, Discord, Slack or ntfy. The website's keeper check sends a plain sentence when the keeper is late or the database cannot be reached, such as how long the keeper has been silent and how many active vaults are waiting. That text holds no wallet addresses, balances or keys. The keeper's separate monitor, when it is run with alerts on, can send an alert that names a vault and its chain. The address is a private setting, and nothing is sent anywhere until it is set.
As a guard, the site's security policy limits where the page can connect to or load images, fonts and scripts from. Besides this site itself, it allows: Helius (Solana RPC), Solana public RPC, Alchemy, Jupiter, DexScreener, Robinhood Chain RPC, WalletConnect (Reown), GitHub (token logos). It also allows Google's font host and Vercel's analytics script host, which no code in this repository names. The policy sets what the page is allowed to load, not what it did load, and wallet pop-ups are third-party code, so we cannot promise that none of them uses a host the policy allows. It does not cover your wallet software or the sites you click through to.
Your wallet software is a separate product with its own policy. Links to block explorers (Solscan, Blockscout) and wallet download pages take you to their sites, and once you click, they see you and not us.
7. Who at Grid Master can see it
The people who run Grid Master can read the database. A private dashboard, which needs an approved wallet to sign in, shows figures per wallet, such as how many vaults it has, how many trades they made and what fees were paid. Our server and keeper logs can include vault identifiers and transaction hashes. If the operators have switched on alerts, the keeper's monitor can also post an alert that names a vault to the chat or notification address they chose (see section 6).
8. How long we keep it
- There is no automatic deletion.Nothing in the website or the keeper removes records after a set time. A vault's records stay until its owner deletes the vault.
- Hosting logs and backups are kept by Vercel, Neon and Railway under their own policies. This code does not set those periods, so we cannot state them here.
- Blockchains keep everything for good.
- Your browser's records last as described in section 5.
9. Deleting your data
Delete Vaultis on the vault's Settings page in your dashboard. Your wallet signs the request, so only the owner can make it. It then removes the vault, its trades, its event log and its daily totals from our database. The vault disappears from your dashboard and, within a few minutes, from the leaderboard.
It will refuse, and change nothing, in any of these cases:
- The vault still holds any tokens. Withdraw them first.
- We cannot check the vault's balance on the chain at that moment. Try again.
- Your signature is missing, has expired, or was made for a different version of the Terms. Sign again, and accept the current Terms if you are asked to.
- For a vault on a live chain, we cannot verify your region, or it is one where we block real-money actions (see section 4).
- Too many requests came from your network address within a minute. Wait and try again.
It does not:
- close the vault on the blockchain, move any funds, or erase anything recorded on a blockchain;
- clear the records Grid Master keeps in your browser (see section 5);
- remove anything held in our hosts' logs or backups (see section 8);
- reach records of early test-mode vaults that never held real funds. Those are only marked closed, not erased.
10. How we protect it
- Creating, changing or deleting a vault record needs a signature from the vault's owner wallet, tied to that exact change and valid for only a few minutes.
- The site sends a content-security policy, blocks being embedded in other sites and limits what it tells other sites about where you came from.
- Requests to the API are rate-limited per network address, on a best-effort basis.
- The operator sign-in cookie cannot be read by scripts on the page, and an approved wallet is checked on every request.
No online service is completely secure, and we cannot promise that data will never be exposed.
11. Children
Grid Master is financial software and is not meant for children. It does not ask your age and has no way to check it, so keeping it away from children is up to you and to parents and guardians.
12. Changes to this policy
When this page changes, we change the date at the top. The date reflects what the code did when it was last checked.