> For the complete documentation index, see [llms.txt](https://docs.goodcrypto.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.goodcrypto.app/goodcryptox-vi/legal/privacy-policy.md).

# Privacy policy

Version 8 · 12 November 2026

**What changed:** Version 8: daily usage records now also count the accounts you added on each exchange that day, with no names or addresses. Version 7: no change to the privacy policy; the terms clarify unanswered Bybit orders, our broker code and possible fee earnings, API key expiry reminders and your agreement with the exchange. Version 6: Payment reads in Add credits now go to two or three public nodes for each network, the next asked only when one doesn't answer; on Tron the first is PublicNode, with TronGrid when it doesn't answer. Our server reads payments through node providers (Infura, dRPC and, on Solana, Helius) as well as the networks' public nodes; they receive our receiving addresses and the payment's transaction from our server, never your IP address or your goodcryptoX's number. Our server counts, for each goodcryptoX, the payment lookups that found nothing in an hour, to limit them, and deletes the count once that hour has passed. Version 5: Your data folder keeps traded-volume records, including observed trades placed outside goodcryptoX; clearing completed history keeps these records. Binance, if you connect it: its signed account requests and private streams, its public market data and its coin logos, and this installation's IP address (the proxy's while on), shown to you so you can allow it on your key, and whether it belongs to a hosting company, used only to sort the connection options. Bybit and Bybit EU address reads now use the exchange proxy while it is on, showing the address exchanges see. Sign in with Binance now passes through our service on Vercel in Hong Kong. It handles the sign-in credentials and approved IP addresses, and receives the new API key and secret only in encrypted form. The relay's temporary record holds the IPv4 address list you confirm (up to 30 addresses), which Binance receives; Binance's page then sends your browser back to goodcryptoX on your computer or your home network. Opening Referral program, or reading your codes, makes our server keep this installation's three referral codes with its public key, even if you never join or invite anyone. On an exchange without a builder fee, goodcryptoX sends our server our fee on each trade and reads your credits back; paying for credits goes through the services named below, and the payment is public. When you pay, goodcryptoX tells our server the payment's transaction at once and reads it from the network's public nodes; for an EVM payment, the server keeps the paying address and its transaction count. Paying in TRX on Tron also sends TronGrid the swap to USDT that the payment makes. Reading a payment wallet’s coins sends its address to the public nodes for its networks or to TronGrid, the EVM networks being checked to KyberSwap’s token list host, and Solana token addresses to Jupiter’s token information host. Your data folder also holds Binance keys, receipts of exchange agreements you accept through goodcryptoX, your credits and, while goodcryptoX checks a database or an import, a temporary copy of it. Connect directly at home, if you turn it on: goodcryptoX then answers directly at this computer's network addresses without our relay, usually over plain HTTP; its link is kept in your data folder (encrypted, with a hash of it) until you turn it off; the devices you add there are kept in your data folder as a hash of their secret, forgotten after 90 days unused or when you remove them, and a move-export leaves them out. Reown / WalletConnect: the page's address when you open the wallet window, a home-network address included, but no usage or error reports. Program pairing codes last up to 24 hours. The phone page comes from our server and runs in your browser. Version 4: access keys for AI apps and programs are kept encrypted in your data folder, so you can show them again; daily records say how much of the traded volume carried our fee, and an order filled without our fee is reported even with reports off. Version 3: Remote app and program connections, saved computer identities and their deletion, encrypted relay traffic and connection logs in test versions. Credits and referrals add fee/payment records, partner-key binding, payout addresses, requests and payments on our server. Reading a payment wallet’s coins sends its address to the public nodes for its networks or to TronGrid, the EVM networks being checked to KyberSwap’s token list host, the coins found there to KyberSwap’s price host, and Solana token addresses to Jupiter’s token information host.

goodcryptoX runs on your computer. GoodC International Ltd., British Virgin Islands, provides it under our [terms of service](https://docs.goodcrypto.app/goodcryptox-vi/legal/terms-of-service.md). You have no account with us, and goodcryptoX uses no analytics service or tracking.

## What stays on your machine

Your data folder holds accounts, receipts of exchange agreements you accept through goodcryptoX, encrypted trading keys and access keys, orders, trades, positions, bots, balances with a daily record of them, notes, settings, a proxy's login if you set one, chart layouts, logs, backups, downloaded updates and translations, and paired browser and program connections: each one's name, public key, and pairing and last-use times; browser connections also have a trading-permission switch. Devices you add over your home network are kept the same way, with a hash of their secret instead of a public key; so are your settings for Connect directly at home (on or off, and the addresses you saved) and, while it is on, its link: its value encrypted with your keys, so goodcryptoX can show it again, and a hash of it. If you linked Telegram, it also holds your bot’s token and message copies. A Binance account's API key sits beside them in a file only your user can read: on its own it can read that account's futures activity. If you trade on an exchange without a builder fee, the data folder also holds your credits: the balance, our fee on each trade and each day's total, and the payments and grants our server reports. Bybit’s API key is also kept in a file only your user can read; signed reads require the unlocked key store. Bybit’s reported permissions, IP list and expiry facts are kept with the local account record. Your system or a passphrase unlocks these keys; browser passkeys can sync through your own password provider. Logs stay for 14 days at most, within the size you set in Storage (200 MB by default); exchange traffic is compressed after each hour and kept for 7 days or three quarters of that size, whichever comes first. Display choices stay in your browser. The installation’s signing key identifies its messages to our servers, but cannot trade or withdraw. A copy of the data folder or a move-export file contains private data, the paired devices and connected computers included: keep it safe. A move-export file leaves out the devices added over your home network and arrives with that switch off, your saved addresses unused until you turn it on; a plain copy of the data folder keeps them. After a move, the earlier data stays in a `moved-<date>` folder in the data folder until you delete it. While goodcryptoX checks a database or an import, it works on a temporary copy in the data folder, with a small ownership file beside it; both are removed when the work ends, or at the next start if goodcryptoX was interrupted.

On another computer, the connector keeps a private signing identity for each installation in your user account's private local files, with connection names, the local address and connection preferences. It does not sync these files or store an access key or pairing code. Your app or program holds its own access key. Pairing lets the computer connect; the key controls what it can read or do.

The setup download or copied settings contain a one-use pairing code, valid for up to 24 hours. Anyone holding it can pair a computer until it is used, canceled or expires. That pairing lasts until removed in Devices; an access key is still needed to read data or trade. The expired code may remain in the file or settings. Keep live setup private.

If you turn on Connect directly at home, goodcryptoX answers directly at this computer's network addresses and at any address you save, without our relay; nothing of that traffic goes to us. The link that adds a browser there holds a code that stays the same until you turn the switch off: its value is kept encrypted with your keys and a hash of it beside your settings, and a move-export leaves the hash out, so the link does not work after a move. Anyone who has the link and is on your network can add a device while it is on; turning the switch off ends the link, and turning it on again makes a new one. A device added that way keeps a cookie in its browser for each address it opens, for 90 days from its last use unless the browser ends it sooner; the data folder keeps only a hash of its secret, and the device is forgotten after 90 days unused or when you remove it in Devices. Turning the switch off closes these connections but keeps the devices, which return when you turn it on. Over your home network the panel and your data travel as plain HTTP unless you put your own HTTPS proxy in front: anyone who can read or change that network's traffic can see them and take a device's sign-in. A browser or program that connects there, an access key it sends included, talks to this computer directly. goodcryptoX reads this computer's network addresses to decide which senders to accept and which link to show; it shows them only to your own devices, except that opening the wallet window on a page opened at such an address gives Reown / WalletConnect that page's address. An address, name or proxy you save is yours: whatever runs it sees what passes through it.

Your data folder also holds a daily record of your traded volume per account and origin, and a record of each trade we observe, including trades placed outside goodcryptoX. Clearing completed history keeps these volume records; removing an account without keeping history deletes its volume records.

## What leaves your machine

Each recipient below sees your IP address, except exchanges reached through a proxy and our partner-code server when the address read uses that proxy:

* **A proxy you set:** every exchange connection goes through it; the exchange sees its address instead of yours; it sees which exchange, when and how much, not the contents.
* **Hyperliquid:** account-data and market-data requests, signed orders and account actions, and wallet approvals. Its blockchain publicly records trades, orders, positions and our builder fees.
* **Binance, if you connect it:** signed account requests (the key's permissions, balances of each wallet, orders and fills) to its API hosts (api, fapi, dapi, papi and eapi on binance.com), each carrying the account's API key. Private account streams connect to ws-api.binance.com with the API key and a signature, and to fstream.binance.com and dstream.binance.com with a listen key; these connections stay open while goodcryptoX runs.
* **Bybit or Bybit EU, if you connect it:** signed key-information, account-information, wallet (the Funding wallet included), position, open-order, execution and fee-rate reads to api.bybit.com or api.bybit.eu, according to the registration you selected. Each carries that account’s API key and a signature; the private key or API secret stays local. The account's private stream connects to stream.bybit.com or stream.bybit.eu with the API key and a signature, and stays open while goodcryptoX runs. No other registration is tried with the key. The orders, cancels, leverage and margin-mode changes you or your bots make are sent there, each signed with the key; an order carries goodcryptoX's broker tag in a separate header. No transfer or withdrawal is sent.
* **Bybit public market data:** instruments, books, trades, prices and candles come from api.bybit.com or api.bybit.eu and the WebSocket hosts stream.bybit.com or stream.bybit.eu; these requests carry no account key, and market streams run only while something shown or watched needs them.
* **Binance public market data:** instruments, books, trades and candles come from api.binance.com, fapi.binance.com and dapi.binance.com, and the WebSocket hosts stream.binance.com, fstream.binance.com and dstream.binance.com; these requests carry no account key, and market streams run only while something shown or watched needs them.
* **Sign in with Binance, if you choose it:** our relay holds the existing Binance OAuth client secret. To complete sign-in, our relay uses a service we run on Vercel in Hong Kong. That service receives your consent code, the one-time proof used to exchange it, our Binance client secret, your short-lived access token, your account-status response and the IP addresses you approve for the new key. Binance encrypts the new API key and secret so only our relay can read them. Our code does not log or save the contents of these requests or replies. The relay exchanges your consent code and briefly sees the newly created trading key, then delivers that key encrypted to your installation. A temporary record holds the consent state, installation fingerprint, one-time public encryption key, the IPv4 address list you confirm and expiration, until exchange or ten minutes. The list holds up to 30 addresses you confirm; older versions use your installation's observed IPv4 address. Binance receives that list as the new key's allowed addresses. The browser return page sends your browser, with the code, back to goodcryptoX at the address you opened it at, on your computer or your home network, and makes no network request of its own. The consent state, which Binance and the temporary record see, carries that address (the port on your computer, or the private IP address and port on your home network) and the language goodcryptoX shows.
* **Our partner-code server, when goodcryptoX reads the address for a Binance key:** a request signed with the installation key, sent over IPv4 directly while the proxy is off or through it while on. The server answers with the IP address it sees, the proxy's while on, shown so you can put it on the key's address list, and whether it belongs to a hosting company, used only to sort the connection options; nothing of it is kept.
* **Hyperliquid’s and Binance’s websites:** requests for public coin logos, without your account or wallet: from Hyperliquid by coin name; from Binance its list of coin logos at most once a day, then each logo from its image host, bnbstatic.com.
* **Our partner-code server, when you add a Bybit or Bybit EU account with API keys:** a request signed with the installation key, sent over IPv4 directly while the proxy is off or through it while on. The server answers with the IP address it sees, the proxy's while on, shown so you can put it on the key's address list; nothing of it is kept.
* **Exchange-rate services (Frankfurter, jsDelivr, Cloudflare Pages):** a request for the day’s currency rates, with nothing that identifies you or your installation. Sent when you open the Base currency list and, while your base currency or a key’s limits are in another currency, at most every 12 hours.
* **GitHub:** version checks and update downloads, including the release channel and machine type. Docker installations download their image from its container registry; their updater asks it for a newer one every hour (every 5 minutes on Internal), with the server's own registry login where it has one.
* **Reown / WalletConnect:** when you open the wallet window, its list of wallets and their pictures come from `api.web3modal.org`, which sees the page's address (a home-network address included). A phone wallet connects through `relay.walletconnect.org` and `verify.walletconnect.org`; the signing requests sent to it are encrypted so that only your wallet can read them. When you connect, your wallet's address and network go to `rpc.walletconnect.org`. goodcryptoX turns off Reown's usage and error reports and gives the window its own font, so nothing goes to `pulse.walletconnect.org` or `fonts.reown.com`. A wallet provider you choose, such as Coinbase, may also receive connection data under its own policy.
* **The Solana and Tron wallet adapters:** their default network host, `rpc.walletconnect.org`, receives the selected network, wallet address and balance requests while connecting a payment wallet. Wallet connection and signing use the Reown / WalletConnect hosts above. The wallet you select may contact its own services under its own policy.
* **Telegram, if linked:** your bot’s messages, account-related alerts, shortcut actions and message requests.
* **Our Telegram setup server:** temporarily receives a new bot’s identity and the Telegram id of the account that created it, passes its token and that id to goodcryptoX (kept there until your chat is linked or you disconnect, so goodcryptoX can write to that account to link it, and only that account’s Start can) and once sets the new bot’s profile photo to our manager bot’s. Telegram lets our manager read or replace these bots’ tokens. Your own bot avoids this server; see [Telegram](https://docs.goodcrypto.app/goodcryptox-vi/goodcryptox-3.0/readme/telegram-alerts.md).
* **Our relay, while a browser, app or program is connected or pairing:** carries end-to-end encrypted traffic; it cannot read your access key, requests or replies. It sees connection identifiers, IP addresses, times and sizes, and keeps a routing identifier and your installation's last offline time. Public versions produce no connection log; Internal and Beta versions log connection events and an installation identifier, never traffic contents or IP addresses. The phone page at my.goodcrypto.app comes from our server and runs in your browser. For browser connections, our page stores the paired installation, a key that lets the open tab reconnect for 15 minutes, a service worker and cached goodcryptoX files.
* **Our reports server:** anonymous problem reports and daily usage records, with order/bot details, diagnostic events, system/version information, the running tier, traded volume, with the part that carried our fee, and how many accounts you added on each exchange that day, under a random installation number and its signing key. No keys, account addresses or names, balances or Telegram ids are included. A note you add is sent as written. A report you send yourself also carries goodcryptoX's recent log, with names, folder paths and network addresses removed; an account's earlier name can remain. Daily records add goodcryptoX's memory and processor use. Turning automatic reports off leaves only a daily sign that the installation exists, and a report of any goodcryptoX order filled without our fee, which we always receive because the fee is part of our terms. Internal test versions also send these figures, free disk and alerts once per run past an hour, even with reports off.
* **Our referral and partner server:** the first time you open Referral program or your codes are read, goodcryptoX sends its public key, and the server makes this installation's three referral codes and keeps them with that key, even if you never join a code or invite anyone. Joining a code sends the code, installation public key, version and signed order records with account addresses and order numbers. We read those accounts’ public trades to pay referrals and partners and to show each code’s users and volume; this reporting cannot be switched off. Adding a partner key sends it and the installation public key to show figures and link partner payouts to that installation; existing keys do this when the referral program starts. Saving a payout address or requesting payment sends the network, wallet address and request. **If you trade on an exchange without a builder fee:** your goodcryptoX's public key and, for each trade it places there, our fee and when we received it, under a number only your goodcryptoX can match to the trade; the fee shows the trade's value, and public trade data could match it to the trade. Never the account, the coin or your balances. This cannot be turned off while you trade there: it is how our fee is paid. goodcryptoX also asks the server, signed with the same key, for your credit balance and the payments and grants it found. When you pay, goodcryptoX tells the server the payment's transaction as soon as it is in a block, so your credits show at once; for a payment on an EVM network, the server keeps the paying address and its transaction count with the payment. When you add credits, the payment's transaction is public and carries your goodcryptoX's number, which links the paying wallet to your goodcryptoX; the server finds payments in the public records of each network it accepts, read through the networks' public nodes and node providers (Infura, dRPC and, on Solana, Helius), which receive our receiving addresses and the payment's transaction from our server, never your IP address or your goodcryptoX's number, and, for a GOOD purchase, reads the USDC it paid and the pool’s balances at that moment from the payment's public record.
* **Our news service, only if you subscribe:** your email address, for goodcryptoX news, on the website’s waitlist.
* **Our translations site:** requests for your chosen language, without an installation identifier; English needs no request.
* **Credit payments:** When you connect a payment wallet or its coins are read again, public nodes for its networks receive your wallet address to check its coins and balances. For an EVM wallet, goodcryptoX checks every supported EVM network. KyberSwap’s token list (`ks-setting.kyberswap.com`) receives each network being checked. Jupiter’s token information (`lite-api.jup.ag`) receives token addresses found in your Solana wallet, including accounts with a zero balance, and SOL's own, for its price. It also receives the token address when goodcryptoX checks a token for a Solana swap. KyberSwap (`aggregator-api.kyberswap.com`) receives your paying wallet address, coin, amount and network to quote and build an unsigned swap. Payment reads use the network’s public node (`ethereum.reth.rs`, `arb1.arbitrum.io`, `mainnet.base.org`, `mainnet.optimism.io`, `polygon-bor-rpc.publicnode.com`, `bsc-rpc.publicnode.com` or `api.avax.network`), with token contracts, payer addresses and transaction numbers. If that node doesn't answer, the same request goes to the network's next public node: `ethereum-public.nodies.app`, then `eth.blockrazor.xyz` for Ethereum; `arbitrum.drpc.org`, then `arbitrum-one-public.nodies.app` for Arbitrum; `base-rpc.publicnode.com`, then `base.drpc.org` for Base; `optimism.drpc.org`, then `optimism-public.nodies.app` for Optimism; `polygon.drpc.org` for Polygon; `bsc-dataseed.bnbchain.org`, then `56.rpc.thirdweb.com` for BNB Chain; `avalanche-c-chain-rpc.publicnode.com`, then `avalanche.drpc.org` for Avalanche. After you pay, goodcryptoX reads the payment's transaction from the same public nodes, the next ones included when the first doesn't answer. Your wallet signs; the public transaction carries your goodcryptoX installation number. KyberSwap’s prices (`token-api.kyberswap.com`) receive the network and the token addresses found in your wallet on it, to show each coin's value, and the network alone when goodcryptoX estimates a dollar token payment's network fee.
* **Jupiter, when you pay in another coin on Solana or buy $GOOD with it:** your paying wallet’s address, the coins and the amount, to quote and build the swap.
* **Solana’s public RPC endpoints (`api.mainnet-beta.solana.com`, then `solana-rpc.publicnode.com` and `api.mainnet.solana.com` when it doesn't answer):** requests for token details and a recent blockhash, and your unsigned payment transaction when a simulation is needed. That transaction includes your paying wallet and your goodcryptoX number. When paying on Solana, they also receive the paying address and selected coin for balance reads, and the transaction signature for status reads.
* **PublicNode (`tron-rpc.publicnode.com`), or TronGrid (`api.trongrid.io`) if PublicNode doesn't answer, when paying on Tron:** the paying wallet's public address and unsigned transaction data to prepare it, including the receiving address, the amount, the swap when you pay in TRX, and your goodcryptoX number. It also receives the paying address and selected coin for balance reads, the wallet-signed transaction when you send it, and its id for status reads. The transaction is public. goodcryptoX does not send a private key or sign this payment for you.
* **AI providers:** Anthropic may process reports and partner records for us. An AI agent you authorize can send data its access key permits to the model provider you choose, under that provider’s policy.

Our services run on Cloudflare, under its terms, and do not retain IP addresses except for the IPv4 address list you confirm (up to 30 addresses) and, when you sign in from your home network, the private address goodcryptoX is open at, in the temporary Binance sign-in record described above. A trade in an anonymous report can be matched to its public Hyperliquid address, which does not itself name a person.

## What we hold

Reports and daily records help us improve goodcryptoX; we keep them 180 days and retain aggregate totals. Referral and partner order records stay while we pay them; public trades stay 30 days after counting, or while needed for payment. We retain each installation's three referral codes with its public key, joined codes, partner links and binding attempts, payout addresses, networks, requests and payments. Credit fees, balances and grants stay permanently to prevent duplicate charges; credit payments stay 7 years for accounting. To limit payment lookups that find nothing, our server counts them per hour for each goodcryptoX and deletes the count once that hour has passed. We keep subscribed emails for news and correspondence to answer you. Our download link records each click’s source, chosen file, country and device kind in our records and Google Analytics. These retained records give us no trading keys; the one-request Binance sign-in handover is described above.

## Deleting your data

Removing an account without keeping its history restarts goodcryptoX to erase its local records; logs, shared wallet records still needed by another account, sent messages/reports and saved exports may remain. Settings › Installation › Storage can delete a removed account’s history, or completed history up to a chosen month, on this computer. Quit goodcryptoX and delete its data folder to remove that installation's local data and keys. Remove a device in Settings › Devices to delete it at once, a home-network device's secret hash included; its cookie stays in that browser until the browser clears it, and no longer works. On each computer used for remote apps or programs, delete the connector's saved files, downloaded setup and goodcryptoX connection settings separately. This does not erase the exchange’s public records, Telegram messages or copies already sent elsewhere. To delete our reports and daily records, email <info@goodcrypto.app> with the installation number shown in Reports; deleted within 30 days. Use the same address to leave the news list or ask about partner records. Your wallet can revoke the API wallet on the exchange.

## Changes and contact

We may publish a new policy; using goodcryptoX afterwards means you accept it. Check its version and date in Settings. Later versions briefly describe their changes under the date.

Questions: <info@goodcrypto.app>
