Privacy
traceme.dev, operated by traceme ("we"), shows public blockchain data. It keeps as little about you as it can, and it has no advertising and no trackers.
Last updated
Traces are public
A trace shows only public Solana data. Every trace gets a permanent link that anyone can open, signed in or not. Traces don't expire, and they aren't kept only on your device.
A trace never says who owns the wallet it starts from: it calls it the starting wallet.
Notes are private, comments are public
Notes you add to a trace are private: only you can read them. Comments are public: anyone can read them, and only signed-in people can write them.
Signed-in people can like or dislike a comment, one vote each. Everyone sees how many likes and dislikes a comment has; nobody is shown who voted.
Your account
You don't need an account. If you want one, sign in with a code sent to your email. traceme never asks you to connect a wallet.
Your account gets a random public name, such as swift-otter-42. Others see that name, never your email or any part of it.
Kept in your browser
These are kept in your browser's local storage. traceme's server never reads them.
| Key | What it holds |
|---|---|
tm:prefs | Your settings: theme, currency, explorer, motion and shortcuts. |
tm:history | Your last 100 visits and searches, for the History page. |
tm:notices:<trace id> | The notices you hid on a trace, one key for each trace, so they stay hidden when you come back. |
tm:layout:<trace id> | Where you moved cards on a trace’s graph, one key for each trace, so they stay there when you come back. Only this browser has it: everyone else sees the trace’s own layout. |
- Key
tm:prefs- What it holds
- Your settings: theme, currency, explorer, motion and shortcuts.
- Key
tm:history- What it holds
- Your last 100 visits and searches, for the History page.
- Key
tm:notices:<trace id>- What it holds
- The notices you hid on a trace, one key for each trace, so they stay hidden when you come back.
- Key
tm:layout:<trace id>- What it holds
- Where you moved cards on a trace’s graph, one key for each trace, so they stay there when you come back. Only this browser has it: everyone else sees the trace’s own layout.
You can clear your history on the History page. When you sign in, it is added to your account's history, so you see it on every device.
What the server handles
When a page needs data, traceme's server asks the traceme API for it and passes on your IP address. The API uses the address only to count each visitor's daily limits. It never stores or logs the address itself: it keeps a keyed hash of it, a one-way code made with a secret key, and deletes that once the day's limits are over.
If you sign in with an email code, the API sends the code through Cloudflare's email service. Your email address is in plain form on the API only while the code is sent; the API keeps it only as a keyed hash, to find your account next time. The code is kept only as a keyed hash too, and deleted once it expires. Cloudflare, which delivers the email, keeps its own record of it for up to 31 days: your address, and the code in its subject. A code stops working once it is used, and within minutes.
No trackers
traceme has no advertising, no analytics and no third-party trackers. Its pages load nothing from other sites. Links to other sites, such as block explorers, open them only when you follow them. Besides the page you open, traceme tells them only that you came from traceme.dev: never the page you were on, the trace you were reading or anything about you. The one exception is “Post on X” on a trace: only when you choose it, X receives that trace’s link, to put in your post.
Your data
In Settings you can export what traceme keeps about you as JSON: your traces, notes and history, and the comments, reports and votes you made. You can also clear your history and notes there.
For anything else about your data, such as a question or a request, write to privacy@traceme.dev.