Who controls this
This site is operated by AmpTrading, which decides what personal data is collected here and why. No company name beyond AmpTrading, and no postal or registered address, is published in this notice — if one is added later, this is the section it will appear in.
There is no privacy inbox to write to, and no account here to write in about — see Your rights for exactly what this site holds instead, and how to clear what your own browser keeps.
What is collected
Personal data reaches this site in two places. One only happens if you choose to use it; the other happens simply by visiting.
| Situation | What's collected | Where it's kept |
|---|---|---|
| Tracking a wallet | The address you type in. | Sent to this site's own endpoint each time you load it, and kept in your browser. |
| Always | Your IP address, browser user agent, and what you asked for and when. | Cloudflare's own request logs, as the host of this site. |
The wallet this site tracks continuously has a server-side record for a
different reason: its trade history sits on our own server, refreshed on a schedule, so
every visitor is served the same already-read data rather than each one asking the chain
again. Type a different address into the dashboard, though, and it reaches our server too
— the dashboard sends it to this site's own /api/portfolio endpoint, which
passes it to the wallet-data service described in Who else sees it
and caches the answer at the edge, keyed to that address, for the period given in
How long it's kept.
Purpose and legal basis
Sending and caching a wallet address is done because you asked this site to look that wallet up; it is necessary to do the thing you asked, when you asked for it.
The logging that happens simply by visiting rests on our legitimate interest in keeping the site running, and in noticing and stopping abuse of it.
Who else sees it
Cloudflare hosts this site, runs the functions behind it, holds the KV store the wallet records live in, and runs the five-minute tracker — Cloudflare is a processor for all of it.
The dashboard's figures come from our own server, not your browser: when you open it, our server asks a wallet-data service that indexes Robinhood Chain for that wallet's positions, PnL and activity, using our own credential. That request carries the wallet address you looked up and nothing else — your IP address is not part of it, because your browser never talks to that service directly.
Our server also asks the chain's own node, about every half minute, whether the tracked wallet has sent a new transaction; that request carries the wallet address only and nothing about any visitor.
The home page's live-trade band uses the same endpoint (/api/portfolio,
its active view). For it, our server makes two more kinds of request: it asks a
market-data feed for the names of newly listed coins on Robinhood Chain and for the price
and market cap of the coin being traded, and a price-history feed for that coin's recent
candles. Those requests name a coin, never a wallet, and nothing about you at all — they are
the same requests for everyone, made from our server. Their answers are kept on our server for
up to fifteen minutes, and the last good answer for up to three days as a fallback for when
a service is down. Your IP address is not sent to any of these services.
The fonts this site draws with are served from this site's own servers, not fetched from any third party.
The one most sites don't say: opening the home page already sends a request to another service, not only once you look something up. A moment after the page loads, your browser reads a wallet's history directly from Blockscout (the block explorer) to fill in the headline figures, the wallet being the one you looked at last on this browser, or a sample address if you have none saved. Looking up a different wallet on the home page reads from Blockscout again, still directly. It sees your IP address make that request, the same as any other site you visit would. The dashboard works differently: an address you look up there goes through our own server first, as described above.
Nothing here is sold, and there is no advertising or visitor-analytics tracking on this site.
International transfers
Cloudflare is a US company. Data described on this page may therefore be processed outside the EEA and the UK, under whatever transfer safeguards Cloudflare maintains for its own services.
How long it's kept
Whatever sits in your browser lasts until you clear it yourself; the cookies page lists everything this site keeps there and gives you a button to clear it in one step.
A dashboard lookup's answer is cached at the edge, keyed to the address you asked about, for up to three days before it's evicted or replaced by a fresher answer — see Who else sees it for what that answer contains.
Cloudflare's own request logs follow Cloudflare's own retention, not a schedule this site sets.
Your rights
Wherever you are, you can expect to have the right to:
- Access — see exactly what is held about you.
- Rectification — have it corrected if it's wrong.
- Erasure — have it deleted.
- Restriction — limit how it's used while something is disputed.
- Objection — object to processing based on legitimate interest.
- Portability — get a copy in a machine-readable form.
- The right to complain to your local data protection supervisory authority, regardless of anything on this page.
This site holds no account and no personal record about you on its own server. The only server-side data is Cloudflare's own request logs, kept on Cloudflare's schedule, and the public wallet addresses the tracker follows — themselves not personal data about you, since an address does not identify who is looking at it. Everything else described on this page lives in your own browser: the cookies page lists it and gives you a button that clears all of it in one step.
Someone else's wallet
If the address you paste in isn't your own, you are asking this site to assemble a picture of somebody else's financial activity — every trade, everything held, each sale matched back to what it cost.
The chain is public, so doing that is lawful: nothing here reads anything
that wasn't already visible to anyone who had the address. But the practical effect isn't
nothing. That address and its full trading history get cached in your browser, and on the
dashboard the address itself is sent to this site's own /api/portfolio
endpoint and on to the wallet-data service, exactly as if it were yours — see
What is collected.
Worth weighing before you enter an address that belongs to someone you know.
Children
This site is not directed at anyone under 16, and no attempt is made to knowingly collect data from anyone under that age. As above, it holds no account or personal record about any visitor, child or adult, to begin with.
Changes to this policy
This policy can change. The date at the top of this page says when it last did.