Privacy Policy

1. Who is responsible

JustSendIt (sendrh.com) is run by its pseudonymous maintainers as an unincorporated fan project with no company behind it. For anything about your data, write to SendRH@Atomicmail.io.

2. What we store, and why

The site keeps one database. This is what is in it about you, and what each thing is for.

We do not store your date of birth, your government identity, your card details, your seed phrase or your private keys. The site never asks for them and cannot use them.

Holder counts are read from the chain itself: the site keeps a ledger of every token's Transfer events, folded into per-wallet balances. Those wallet balances are public chain data (the same thing the block explorer shows) and are not tied to any account. A community's "supply held by members" figure is the total of its members' linked wallets in that ledger — one number, rounded to two significant figures, and shown only once three or more members have linked a wallet, so it can never be read back to any one person's balance.

The Scanner keeps a record of every token address anyone scans — the token, the pool it was pasted as (if any), when it was first and last scanned, how many times, and the last profile read from the chain — so a coin one person scanned pulls up for everyone. That record holds nothing about who scanned it: no account, no session, no IP. The "recent scans on this device" list on that page lives only in your own browser and is never sent to us.

3. What is public

Your username, avatar, bio, level, badges, Send Power totals and rankings, follows, posts, comments, reactions, uploads, pinned tokens, community memberships and Send Calls are visible to anyone who can reach the site, including people without an account and search engines. Your profile page and your invite ticket (if you make it public) have their own URLs.

A Send Call is permanent by design: it cannot be edited or deleted once posted. If you chose to attach a wallet address to it, you can detach the address later, but the call itself stays. Deleting a post removes it from the site, but copies other people made or that caches hold are outside our control.

Your email address, linked wallet addresses (unless you attach one to a Send Call or share your wallet yourself), tracked wallets, mutes, IP hashes, two-factor settings and sessions are never shown to other users.

4. Wallets and the blockchain

Connecting a wallet is read-only. To link one you sign a message with it; the message says what it authorises and never moves funds or grants token approvals. We keep the address, not the signature.

A wallet that cannot sign can be linked instead by a burn: within an hour of starting the proof, you send the exact dust amount of $SEND the site shows you from that wallet to the burn address yourself, and we read that transfer on the public chain. We keep which wallet you were proving, when its hour opened and closed, the amount it asked for (and a different amount, if one arrived), and the burn's transaction — encrypted, and only for a week after the proof ends. The burn itself, like every transfer, stays on the public chain for good: anyone can see that the wallet sent it, though nothing on the chain says which account it proved.

Robinhood Chain is a public blockchain. Balances, transfers and swaps of any address on it are visible to everyone, and we read them: to verify that a linked wallet holds what the participation check asks for, to work out holder boosts and OG badges, to watch the first day after a verified buy, and to show balances and swap history on the tracker. We read; we never write to the chain on your behalf.

For Diamond Hands we also watch, on the same public chain, the wallets you send $SEND or $GWC to from a linked wallet or from a wallet you unlinked (including the wallets a batch-send contract passes them on to), and any wallet you unlink: a sale from one of them resets your streak just as a sale from a linked wallet does, while moving coins never does. Unlinking a wallet takes it off your account and out of sign-in, but not out of this watch; deleting your account ends it.

The swap widget on the home page talks to your own wallet software and to the chain directly from your browser. We do not see your transaction until it is public on the chain like any other.

5. IP addresses and abuse prevention

Your IP address is used in two ways. In memory, it keys rate limits (how many requests, sign-in attempts or uploads one network can make in a window); those counters are not written to disk. In the database, it is stored only as a keyed hash (a blind index) against your sign-up, the Send Calls you post, community memberships, communities you start, alerts, and each try at an email address that already belongs to another account (that one rations how many in-use addresses one network can try), so the site can notice one network running many accounts; it is also kept with each Rocket Run flight flown without an account, to cap guest flights per network each day; the same kind of hash is also stored with Send Squad memberships and the squads you start, where no check reads it yet; section 9 says how long each is kept. Nothing is kept for your last sign-in, your posts, proposals or votes. We do not store the readable address, and we do not use it for location or advertising.

The server's own logs record request errors and rate-limit warnings; they are not analytics and are not shared.

6. Cookies and browser storage

We set only the cookies the site needs to work:

Your browser's local storage holds preferences that never leave your device: colour, motion and sound settings (the ⏸ in the menu bar pauses motion and the site's sound effects together), which dashboard tab you had open, which chart you picked for tokens (on-chain, Dexscreener or CoinGecko), the slot machine's score, spin count and sound setting, the hidden ghosts (easter eggs) you have found and any not yet banked, whether you turned Google Analytics off in this browser, and similar conveniences. There are no advertising cookies. Cloudflare Web Analytics (section 7) sets no cookie and reads nothing from this storage; Google Analytics, when it is on, sets only the cookies in the table above.

7. Other services your browser talks to

Pages load Cloudflare's Web Analytics beacon, a small script Cloudflare adds to each page as it serves it. It reports to Cloudflare which page loaded and how fast, with the page you came from. Cloudflare states that it “does not use any client-side state, such as cookies or localStorage” (so the cookie table above is complete), that it does not fingerprint visitors by IP address or browser, and that it does not record query strings; Cloudflare sees your IP address exactly as it already does for every request it serves. Everything else is served from this site: the fonts are served from this site. Token pictures, live prices, and the wallet history the tracker and your profile show are fetched by our server and passed on to you, so Dexscreener, Blockscout and the image hosts never see your IP address or the wallets you look at.

Google Analytics, when the operator has turned it on. Once you have answered the 18+ question with yes, each page loads Google's tag from www.googletagmanager.com, and your browser tells Google Analytics which page you opened — its address without anything after a ? or #, and its title; a member's profile, a post or a Send ID is sent only as that kind of page, and a community or a Send Squad without its name — the page you came from (trimmed the same way), your device type, browser, screen size and language, and roughly where you are, which Google works out from your IP address. It records page views only: Google's automatic extras (outbound link clicks, site search, form interactions, file downloads, video and scroll events) are switched off in its settings. Google Signals and ad personalisation are switched off too, so the visit is not linked to a Google account or used for advertising, and nothing that identifies you — your name, account, email or wallet — is sent. It never starts before the 18+ question is answered yes, or after an answer of under 18, and it does not load on the admin page or in a browser that sends Global Privacy Control or Do Not Track. The operator sees totals — visitors, pages, where visits came from, countries, device types — not who you are. Google handles this data under its own privacy policy (policies.google.com/privacy).

Once this page has loaded, this line shows whether Google Analytics runs in your browser, with a switch to turn it off.

Token charts are the site's own, drawn from the chain. If you switch a chart to Dexscreener or CoinGecko (its GeckoTerminal charts), your browser loads that company's chart from dexscreener.com or www.geckoterminal.com, so that company sees your IP address and which pool you are looking at, under its own privacy policy. Nothing is loaded from either until you pick it, the frame is removed when you switch back, and your pick is remembered only on your device (section 6). Each button shows only when that site lists the pool: our server asks them, with the pool's address alone, so your browser does not.

The other exception is the swap and wallet-connect flow: while you swap, your browser reads your balance, the swap quote and the transaction status from the Robinhood Chain public RPC (rpc.mainnet.chain.robinhood.com). That service sees your IP address and your wallet address — the same service the wallet app you connected already talks to. Explorer links go to robinhoodchain.blockscout.com; chart and pair links go to Dexscreener. Links to wallets, bridges and exchanges (for example MetaMask, Rabby, Rainbow, Trust Wallet, Coinbase Wallet, Phantom, Relay, MoonPay, OKX) open those services, which have their own policies. Following a link is your choice.

If the site is served through a content delivery network such as Cloudflare, that network sees your IP address and the pages you request in order to serve them and to block attacks.

8. Services our server talks to

The server reads public market and chain data from Dexscreener, the Robinhood Chain RPC and Blockscout (token pairs, prices, liquidity, balances, swap history), GoPlus Security (automated contract flags and holder counts, asked about token addresses only), CoinGecko's GeckoTerminal and Dexscreener (whether they list a pool, so a token's chart offers only the charts that exist, and which tokens match a name typed into a search — the words typed, nothing about who typed them), Dextools listing data when the operator has set it up, a public price feed for ETH, and public stock-quote endpoints for the HOOD ticker shown on the site. These requests carry no information about you: they are about tokens and addresses, made from our server, not your browser. That includes the wallet history the tracker and your profile show, and the token pictures on every page: the services asked see our server, never you. If the operator has enabled sign-in with Google, Facebook, X or Instagram, the sign-in itself is completed with that provider. If the operator runs the Telegram bot, messages you send it go through Telegram.

Sendy, the helper in the corner, is the one other place something you type leaves this server. When you ask Sendy a question, our server sends that question, the page you are on and the last few messages of that chat to Anthropic, the company whose model writes the answer, together with the public text of this site so the answer can be specific. Nothing about your account goes with it — not your name, email, wallets, points or history. We keep the question and the answer, without who asked (no account, no address), so that an answer readers rate as helpful can be reused for the next person; a thumbs-up or down on an answer is counted the same way, and a per-address count limits abuse. Sendy is also given figures the site already shows to everyone — the boards, community sizes, recently scanned tokens, and the $SEND and $GWC market reading — so it can answer with them. Anthropic's handling of what it receives is described in its own privacy policy. Sendy's tips and greeting are shown by your browser and send nothing anywhere.

We do not sell, rent or trade personal data, and we do not share it with advertisers or data brokers. We would disclose data only where the law requires it, or to investigate abuse of the site.

9. How long we keep things

IP addresses are never stored — only a keyed hash of each, and no hash outlives the record it was stored with; the ones a check reads are erased as soon as that check no longer needs them: the one recorded with a Send Call is erased eight days later, once the same-network ring check can no longer look at it; the one recorded when an account is created is erased after 90 days, so the limit on accounts per network counts the last 90 days; the ones recorded with a community or Send Squad membership, a community or Send Squad you started or an alert last as long as those do and go with them; the one recorded when an email address already in use by another account was tried is erased after 30 days. The site does not keep a hash of the network you last signed in from, or of where a proposal or a vote came from.

Pictures and videos you upload are stored without their location and device data: GPS tags, camera make and model and similar fields are removed from photos (a photo keeps only its orientation), and location and metadata boxes are blanked in videos. A file whose structure cannot be read is refused rather than published as it is.

Sessions expire after 30 days, or when you end them. Wallet sign-in challenges expire after ten minutes. A burn proof (section 4) is deleted a week after it ends. An upload that is never attached to a post is deleted after thirty minutes. Notifications are trimmed so only the most recent of each kind are kept. Rate-limit counters live in memory and vanish on their own. Public content stays until you delete it or your account is deleted. The Diamond Hands record of moves out of your wallets (section 4) is deleted once each move is settled and 30 days old. A Rocket Run flight flown without an account loses its IP hash after two days and is deleted after 30 days, unless an account took it. Everything else stays for as long as your account exists.

Earlier versions, so a mistake can be undone. When your Conviction Plays, posts, comments, Send Calls, profile (name, picture, bio, colours, social handles), Diamond Hands streak, community and Send Squad memberships, follows, watchlist or post alerts are changed or deleted, the earlier version is kept, so the operator can put it back if something goes wrong — at your request, or after a fault. Only the site's admin can see these versions, from the admin page; they never include passwords, sign-in secrets, wallet addresses, IP hashes or anything else stored encrypted. What a moderator takes down is not kept. They are kept for as long as your account exists (the newest 5,000 per account), and deleting your account erases them with everything else — including other members' records of following you or turning on alerts for you.

The operator keeps database backups for disaster recovery — the last 30 days, and the first of each month for the last 12 months — on a separate disk. Every backup is written without IP hashes, sign-in sessions and challenges, the visitor-counting keys, guest Rocket Run flights, the Diamond Hands record of moves, burn proofs and tried-email records (the full copy of the database made just before each weekly encryption-key change is cleared of them moments after it is made), so none of those is kept longer than this section says. A deleted account can persist in a backup until that backup is rotated out, at most about a year.

10. Deleting your account

You can delete your account yourself from your profile: Settings → Account → Delete account. You will be asked to prove it is you (your password, or a signature from a wallet already linked to the account, or your current second factor). Deletion removes your identities, sessions, tracked wallets, holder state, notifications, mutes, follows, points ledger, uploads and posts; the files behind your uploads and your profile, header and background pictures are removed from disk, and, where the operator has configured it, purged from the content delivery network. Your social handles, IP hashes, age confirmation, balances and preferences are erased from the account. Reactions and votes you left on other people's posts are removed. Community memberships end. A proposal you drafted is deleted; one that was already put to a vote keeps its result, because other members voted on it, but its title and text are replaced with "[deleted]". Invite codes you have not given out are deleted and stop working, including one somebody has redeemed but not yet used to finish signing up. The earlier versions kept of your data (section 9) are erased.

What deletion does not undo: Send Calls are permanent by design and remain, shown under a placeholder name of the form "deleted-123" with an empty profile; wallet addresses that verified an account for the participation check or earned an OG badge stay recorded (as a hash) so the same wallet cannot verify another account; and invite codes you handed out that were already used stay used.

If you cannot sign in, email SendRH@Atomicmail.io from the address on the account and we will verify you and delete it by hand.

11. Your rights and how to use them

Depending on where you live you may have rights to access, correct, delete, restrict or export your data, or to object to how it is used. You can see and change most of what we hold on your profile page, end sessions there, unlink wallets there (a wallet you unlink is still watched for Diamond Hands sales until the account is deleted — section 4) and delete the account there. For a copy of the data we hold about you, a correction we do not offer in the interface, or any other request, email SendRH@Atomicmail.io from the address on your account; we will answer as soon as we reasonably can and will never charge for it. If you think we have handled your data wrongly you can also complain to the data protection authority where you live.

12. Security

Emails, wallet addresses, two-factor secrets and holder-verification detail are encrypted at rest with a key kept outside the database. Passwords are hashed with scrypt. Session tokens are hashed before storage. Two-factor codes are accepted once. Security changes (linking a wallet, turning two-factor on or off, changing the email or password) require you to prove ownership first and produce a notification in your bell. No system is perfectly secure, and we make no guarantee; if you believe there has been a breach involving your data, tell us at SendRH@Atomicmail.io and we will investigate and tell you what we find.

13. Age

JustSendIt is not for children: you must be 18 or older to make an account. We do not knowingly collect data from anyone younger, and we will delete an account we learn belongs to someone who is.

14. Changes to this policy

If we change what we collect or how we use it, we will update this page and its version date, and for a change that matters we will tell you on the site or by email. The current version is always at sendrh.com/privacy.

15. Contact

Email: SendRH@Atomicmail.io. Put "privacy" in the subject line and include your account name.