Privacy Policy

This Privacy Policy describes what information Gloam (“we,” “us”) handles when you use gloam.trade, the Gloam app, the API, the hosted MCP server and Glim, our Telegram helper (the “Services”). It describes how the Services work today. Blockchain transactions are public by nature unless a privacy protocol applies, and even then, guarantees are limited.

1. Testnet only

Gloam runs only on test networks: Tempo Moderato testnet and Robinhood Chain testnet. The tokens you use with it are test tokens with no value. Do not send real funds to any Gloam address or contract.

2. What Gloam never has

Gloam is self-custodial. Your wallet's keys stay in your wallet. Your private balance lives in your browser: your notes, their secrets and your receive keys are made and kept there, and proofs are made in your browser too. We never receive your keys, your seed phrase or your note secrets.

We never hold your funds. Money in the Gloam vault contract leaves only with a valid proof, and there is no admin withdraw. Any change to how proofs are checked needs three days of public notice on chain.

We will never ask for a seed phrase or private key. Never share them with anyone claiming to represent Gloam.

3. On-chain data

Activity on public blockchains is visible to anyone. The public addresses you connect, the transactions you send and their hashes are shared with the network by design. Private features reduce what is visible on explorers, but metadata, timing, amounts at deposit and cash out, and third-party infrastructure may still reveal information. We do not control the networks.

Your browser talks to each network's RPC nodes and explorers directly. They see your IP address and the addresses you look up, under their own policies. When the app shows your public wallet's recent activity, our server asks the Robinhood Chain testnet explorer for that address.

4. Usage data

Gloam product counts. When you reach a step in the app, such as connecting a wallet, finishing a deposit, sending privately, making a proof or applying to test, your browser sends a short event to gloam.trade/api/collect. It holds the event name, the page, the referring address (its site and path, never its query string), the time, and a few safe details such as the network, the kind of proof or a count. Our server adds your browser's user agent (the line that names your browser and system). It drops anything that could be an amount, an address, a name, a label, a note or a proof, even if a browser sends it. No cookie or ID is used, and your IP address is not kept with the event. These counts run only if you choose “Accept all” in the cookie banner. We keep the latest 5,000 events, daily totals for 120 days, and running totals. We may also post the events to a private team chat.

Claim-link counts. To see whether payment links reach people, the app adds 1 to one of four daily totals: a claim link was made (once its payment lands), a claim link was opened in Gloam, a claim link was claimed, and someone who claimed a link made their own first payment. The request carries only which of the four it is. It has no cookie or ID, and nothing about the link, the amount, the people involved or your wallet, and our server keeps no IP address or browser details with it. Your browser remembers on its own which links it already counted, so the same one is not counted twice. Because these totals cannot say who did what, they run whether or not you accept the cookie banner. We keep the daily totals for about 13 months.

Vercel Web Analytics. Our hosting provider, Vercel, counts page views for us. It runs only if you choose “Accept all” and sets no cookies. Vercel says it tells visits apart with a hash of the request that it discards after 24 hours, and records the page, the referring site, your rough location (country, region, city), and your browser, operating system and device type. We cut the page link at the first “?” or “#” before it is sent, so the details in a payment request or proof link never reach Vercel.

Our visit count (optional). Only if you choose “Accept all,” the site also sends us a visit event when it loads (the page you land on and the referring address), and which network you view on the Transparency page. It holds the same fields as the product counts and is kept the same way.

Rate limits. To stop abuse we count requests per IP address. The address is hashed before it is counted, and each count expires on its own: within minutes for most limits, and within two days for daily ones.

Request logs. Our hosting provider keeps standard request logs (time, path, IP address and response status) for no more than 30 days. A path can include a public wallet address, for example when the app looks up that wallet's activity. Our server code also writes short logs, such as the product counts above and error messages, and an error message can include details of the request that failed.

5. Cookies and local storage

We set no advertising or tracking cookies. The only cookies we set are sign-in cookies for the partner portal and the team's admin page. The app keeps your private balance, settings and preferences in your browser's local storage, and none of it is sent to us except an encrypted recovery backup if you turn recovery on (section 8). Details and your choices: Cookie Policy.

6. The relay

When you send privately or cash out, the app can submit the transaction for you from a Gloam relay account, so your wallet does not appear next to it on a block explorer. You can turn this off and send from your own wallet.

The relay receives the proof and its public inputs. For a cash out these include the amount, the asset and the address you cash out to, which become public on chain anyway. For a private send it sees no amount and no recipient. A payment message it posts for you is encrypted for the recipient, and the relay cannot read it. The relay never receives your keys, your note secrets or your private balance, and it cannot change where money goes: the most it can do is refuse to submit.

Beyond the transaction itself, which is public on chain, the relay keeps only a hashed rate-limit count and, for about three minutes, a lock on each spend so the same proof is not sent twice. Relaying is free on testnet.

7. Sanctions screening

Before a deposit, a trade or a cash out, we check the public wallet address involved against a copy of the US Treasury's OFAC list of sanctioned digital currency addresses. The check runs in your browser, then again on our server and in the relay. We may also ask Chainalysis's free sanctions API about the address. When that is on, Chainalysis receives the address. On Tempo we also read the stablecoin issuer's transfer policy from the chain. We do not log the addresses we screen, and the answer is only allowed or blocked.

8. Recovery backups

If you turn on recovery, your browser encrypts your private balance (the notes it can spend and its receive keys) with a key made from your wallet's signature or your passkey, and stores only that encrypted copy on our servers. We can't read it, and it is filed under an id that doesn't reveal your wallet. It stays until you turn recovery off in Settings, which deletes it. Anyone who gets your recovery signature or passkey could open your backup, so only sign the recovery message on gloam.trade.

9. Tester applications

If you apply at gloam.trade/testers, we keep what you send: your name, Telegram and X handles, the network you want to test, your device and wallet, your note, and your EVM address, which we pay tester rewards to or, for volunteers, use to match you to your testing on chain. We also note when you applied and whether you hold a paid or a volunteer spot. We use it to let you into the private testers group, to match testing to testers and to pay rewards, and for nothing else. Only the Gloam team can read it. Your IP address is not kept with your application; the rate limit holds a hashed copy for up to two hours. We delete applications 90 days after the testers program ends, or sooner if you ask at hello@gloam.trade.

10. Glim, our Telegram helper

Glim is a bot in the Gloam Telegram group (t.me/gloamhq). It reads the messages posted in the group, not only the ones sent to it, so it can answer questions, save bug reports, and remove scams and pasted secrets. It does not reply to private messages, except from the team.

Anthropic. Glim uses Anthropic's API to write its answers. To answer a message, it sends Anthropic the message, your Telegram first name, the last few messages in that topic (first names and text), and any picture you post or ask it about, such as a screenshot. A quick check of whether a message needs an answer also sends the message text. Anthropic processes this to write the reply, under its own terms. Payment codes, claim links and Gloam addresses are replaced with labels before any text is sent.

What Glim keeps. In our database, Glim keeps the last few messages of each topic (first name and text) for about six hours, so follow-ups make sense. It keeps bug reports for the team: your Telegram user ID, username, first name, the topic, the text and a link to the message (the latest 500 are kept). It keeps the text of the questions it answered, without names, for about two days, and Anthropic turns them into a daily summary for the team. It keeps questions it handed to an admin (first name, topic, text and link) for about three days, and hourly counts of messages, joins and leaves, with Telegram user IDs, for three days. It also keeps new members' first names until the next welcome message, and short flags tied to your Telegram user ID, for a day at most, so it does not repeat itself. It does not store pictures.

Secrets. Glim never stores text that looks like a seed phrase or private key, and deletes a message that shows one when it can. A picture is sent to Anthropic before Glim knows what it shows, so never post a seed phrase or private key, in text or in a screenshot.

Telegram's own privacy policy covers everything you post on Telegram.

11. Partner portal and API

To sign in to the partner portal, you sign a message with your wallet (Sign-In with Ethereum). We keep your wallet address, the partner name and website you enter, the payout addresses and fee settings you choose, and your API keys. API keys are stored only as hashes, so we can check a key but cannot read it back. For each transaction made with your key we record the network, the kind, the transaction hash and the time, and for deposits and cash outs the asset and amount, which are public on chain. We never record a note, a secret, the recipient of a private send or a private amount. A sign-in cookie keeps you signed in for up to 7 days.

12. Hosted MCP server (gloam.trade/mcp)

The hosted MCP server lets AI clients such as Claude, ChatGPT and Cursor read information about Gloam and plan actions. It never holds funds, never signs transactions, and refuses any tool call that looks like it contains a private key, recovery phrase or note secret.

Tool inputs and outputs. What a tool call carries, such as the details of a payment request or a proof you ask it to check, is processed in memory to answer that one call and is not stored. We do not receive your conversation with the AI client, only the tool calls it sends.

Rate limiting. To prevent abuse we count requests per IP address. The address is hashed before it is counted, and each count expires within two minutes.

Request logs. Our hosting provider keeps standard request logs (time, path, IP address and response status) for no more than 30 days. Request bodies are not logged.

The local server. The Gloam MCP server you run yourself (npx @gloamtrade/mcp) runs on your own machine. Its keys, spending limits and encrypted notes stay there, and we never receive them.

13. Messages you send us

If you write to us by email, on X or on Telegram, we keep your message and your contact details so we can reply.

14. How we use information

To operate and improve the Services, secure systems, debug issues, understand aggregate usage, run the testers program, communicate about the product, and comply with law. We do not sell your personal information.

15. Sharing and service providers

These providers process data for us, each as described above:

• Vercel: hosting, request logs and Web Analytics.
• Upstash: our database, for tester applications, recovery backups, partner accounts, Glim's records, usage counts and rate-limit counts.
• Anthropic: writing Glim's answers and daily summary.
• Telegram: runs the group and delivers its messages to Glim.
• Chainalysis: sanctions checks, when we turn them on.
• The Tempo and Robinhood Chain testnet RPC nodes and explorers, and Tempo's fee sponsor when you use Tempo Wallet.
• WalletConnect (Reown), only when you choose Use a wallet app: its relay passes encrypted messages between the page and your wallet app and sees your IP address. It does not start otherwise.

The wallet you connect is run by its maker under its own terms. We may also share data with professional advisors, or with authorities when the law requires it.

16. Retention

We keep each kind of data for the time stated above. Where no time is stated, such as partner accounts and running totals, we keep it while the Services run. On-chain data persists for the life of the network.

17. Security

We use reasonable technical and organizational measures, but no method of transmission or storage is fully secure. You are responsible for securing your own devices and wallets.

18. International transfers

Services may be hosted in multiple regions. By using them, you understand information may be processed outside your country.

19. Your choices

You can disconnect your wallet, choose “Essential only” in the Cookie Policy, turn the relay off, turn recovery off (which deletes your backup), and clear this site's data in your browser. Depending on your jurisdiction, you may have rights to access, correct, or delete personal data we hold off-chain. Contact us to exercise those rights. We cannot change or delete data on a blockchain.

20. Children

The Services are not directed to children under 18 (or the age of majority where you live). We do not knowingly collect their data.

21. Changes

We may update this Policy by posting a new version with a revised date.

22. Contact

Privacy questions: hello@gloam.trade or @gloamtrade.