Privacy notice

What we keep, in plain words. Updated 24 October 2026.

· the words are the served page’s; this page gives them the kit’s shape and names every source

Sources: every sentence above is the served page’s (clown.world.lol/privacy, updated 14 October 2026) or /account’s; this page adds a shape, the sources’ names and the erase control (B-227). A change to the words is dated here before it applies.

Details

The details below name every read, browser note and erase control the site uses today.

What we never record

• Your name, phone number or a password. The public site never asks for them. An email address is kept only if you choose to create an account (below); nothing on the site needs one, and no password exists anywhere on it. The one place a name is kept is the beta testers' page, and only for the people we hand a tester code to — what it keeps and for how long is under Beta testers below.
• Your raw wallet address, your keys, or anything you sign. Connecting a wallet happens between your browser and that wallet; connecting does not let us move anything.
• Third-party trackers, pixels or analytics. None are wired to this site. When error reporting is turned on, errors are sent to Sentry after wallet addresses, trade quotes and URL query strings are removed. Otherwise this site sends no error reports or measurement to anyone.
• Cookies on the public site. When you arrive via a tracked link, the public site sets one first-party cookie, cw_src, after page load to remember the link that brought you here. It is not used for advertising and cannot be read by scripts on the page. You can also ask for a cookie: the old design of the home page stays reachable until 31 October 2026 at ?classic=1, and asking for it sets one first-party cookie, cw_classic, holding only the digit 1, so your next visits show the old design too. It expires after 30 days, ?classic=0 removes it, it is sent only to this site and it is not used for advertising. An earlier preview cookie, cw_race, is no longer read, and the home page removes it if your browser still holds one. When account sign-in is switched on (it is not yet), signing in sets one first-party cookie, cw_account, described under Accounts below, and nothing else on the site sets one apart from cw_classic and cw_src above. Beyond that, the only cookies this site can set are cw_context and cw_session, and the endpoints that set them accept only loopback requests — on the same machine, at 127.0.0.1. They are first-party, set by our own server, cannot be read by scripts on the page, and are not used for advertising. While such a session is live our server also keeps a record of it, and that record holds the wallet address you proved; the record is not a key and cannot move anything.

Why

So the home page and the aisles rank coins the way you shop, and search remembers what you look for. The same lines are also counted across everyone, never with who: when enough people are shopping at once, a page every visitor can open shows the searches typed here in the last few minutes, word for word in lower case (an email, or an address typed among other words, is taken out first; a search that is nothing but a coin's address is kept and shown whole, because a pasted address is read as a coin lookup, never as yours), and the coins tapped and watchlisted, with their counts; our own operator page counts visits, carts and buys in totals. That is the whole use. We do not sell, share or rent any of it.

How long

180 days. A job runs every night and deletes every line older than that. It logs only how many lines it removed, never which ones. The same job sweeps the beta testers' rows on the same clock, as Beta testers below says.

How to erase it

Connected wallet: connect the same Solana wallet and tap Erase my data. Your wallet signs a short message that says exactly that — World: delete my shopping events, your address and the time; we check the signature and delete every line stored under your wallet's hash. Gone within a minute.

Anonymous visitor: tap Forget this browser. It clears the local id and the notes below, so nothing recorded so far can be tied to you again.

Beta testers

This section covers the beta report page at /beta, the named tester desks and project chat at /beta/chat. The code-based report page asks for the tester code we gave you. The named desks and project chat have their own entry points.

Reports you send. A report can include the public wallet address you enter, your thumbs-up or thumbs-down answer and your optional note. Your answers to the task's questions and the description of what happened are sent with the report. A public address is not a private key, but it can identify public activity on a chain. Enter only an address you intend to include in your report.

Attachments and questions. Screenshots you attach are sent with the report. Check them for personal information before sending. A question sent from project chat includes the tester name you selected or the name of the desk you opened. Do not put a recovery phrase or a private key in a report, screenshot or chat message.

What it records. The name we wrote down when your code was made — the first name or handle we know you by, nothing more. The tasks we post to you. Your answers to a task's questions and any question you ask us, as you typed them, with the time. With each report, the browser's own description of itself (its user-agent string, cut to 300 characters), how wide its screen was, and which build of the site you were testing. No IP address is stored with any of it: the server counts requests per address for a minute to stop guessing, and keeps nothing of that.

How long. Reports, questions and tasks are deleted by the same nightly job as everything above, 180 days after they were written. Your name stays for as long as your code is live, and goes 180 days after the code is revoked. The job logs only how many rows it removed.

How to erase it. Ask the person who gave you your code, or write to the address under Who we are: we revoke the code and delete your rows by hand, and the revoked code cannot be used again. Forget my code on the page removes the code from your browser; it does not delete what you have sent.

Notes in your browser

The site keeps notes in this browser. Except for the one id named first, they never leave it: nothing in this group is sent to us or to anyone else, and none of it can move anything.

Campaign attribution can also leave a preference note, cw_ads_opt_out, in local storage when you opt out of remembering the link that brought you here. It holds only the digit 1, stays until you clear it, and stops the site writing a new cw_src note.

One key in local storage is different, because its contents do leave the browser: cw_sid, the random id the site's usage beacon sends with the events listed above, so your visits can be told apart from other browsers without a name, an email or a cookie. It is not your wallet and cannot move anything. While a wallet is connected the beacon also sends its address, and our server keeps only a salted hash of it, never the address itself. Forget this browser or clearing this site's storage gives you a fresh id.

In local storage, which stays until you clear it: cw.settings (your trading, display and privacy choices), cw.watchlist (the coins you put on your watchlist from the home page or an aisle page — a list of their mint addresses) and cw.watchlist.migrated (a one-time note that the older watchlist was carried over), one cw.copies.notes. key per coin, ending in its address, when you tap Note to self on a look-alike, cw.cart (the cart lines you selected, including coin, chain and spend amount), cw.bought (each buy made here that landed: its receipt id, the coin, your wallet's public address and how much of the coin arrived — the sell sheet sells from it, never from your whole balance) and cw.bought.seen (the receipt ids already counted, so one receipt is counted once), a cw.bought.out. key per sale, ending in that sale's quote id (the buy it sells from and how much of it that sale holds or sold, so those coins are not offered again), cw.history (the coins you marked “Not for me”, including when the 30-day hide began and any Undo), cw.recent_searches (the last eight things you typed into the header search), cw.thumb (your thumb-side setting — Left, Right or Auto — and, under Auto, the count of taps by the side of the screen they started from, which is how Auto decides), cw.wallet (the wallet you connected — its name and its public address, per chain, and which one is in use — so the top strip, the portfolio and the buy box all read the same connection and it is still there after a reload; no key is ever in it, and Disconnect deletes it), cw.mc.active (which of two connected wallets the strip shows), cw.wallet-kept (which wallet you chose to keep connected, so the "connected from your last visit" note does not come back), cw.visits (how many times this browser has opened the site, so the "add to home screen" sheet can offer itself once, on the third visit) and cw.install.asked (when that sheet last opened by itself, so it waits at least seven days before asking again), cw.firstrun (the note that the three first-run marks were dismissed, so they are not shown again on this device), cw.firstone (up to 50 wallet-address hashes recording that the first-buy sizing note was shown — not the addresses themselves, kept only in this browser so the note appears once per wallet), cw.pitch (the connect pitch's own note — how many times you have come back, when the pitch was last shown, and whether you answered it), cw.watch-address (a public wallet address you typed into the connect pitch to see your coins read-only — nothing is signed, and the usage events carry only which kind of address it was, never the address), cw-pitch2 (when this browser first saw the site, when it was last asked to save its setup with an account, and how many installed-app sessions it has opened — so the ask is made at most once every 14 days), cw.account-prefs (the thumb-side and default-spend picks you make before signing in, saved to the account you sign in to, and afterwards a copy of that account's own two picks, kept on this device until you sign out or the session ends), cw.alert-reads (the last two reads of each coin the alerts page previewed for you - the coin's facts and when they were read, never a wallet address - so a move is judged between two reads) and cw.alert-fired (when each previewed alert last showed, so the same one shows at most once an hour), cw.coin.look (the previous reading for each coin you opened, keyed by its mint address: the time, traded-at reading and pool liquidity, so the coin page can show what changed since your last look; at most 64 coin entries, with the oldest readings removed first), cw.lastLook (what the seven rules and the overall number of each coin on your watchlist said when you last left the page, and when, so the page can mark what changed since you looked - never a wallet address), cw.watch-alerts (which of the four alert causes you switched on for each coin on your watchlist; nothing is sent from it), cw.alert-lines (the traded-at lines you drew on /alerts), cw.watch-wallets (the public wallet addresses you chose to follow on /portfolio, read-only) and cw.journal (the one-line notes you typed in a coin's sheet, never sent), and cw-proto4 (the older front page's one note — your cart, watchlist and alert choices, filters and sort, the amounts you set on a coin and the coins you opened). The TV preference is cw.tv.auto (auto-advance on this device: 1 on, 0 off; clearing restores on). Keys the older front page wrote may still sit in your browser although nothing on the site writes or reads them now: cw-mvp-v1 (its sample wallets, orders and settings), cw-welcome (its first-visit welcome sheet), cw-chains-v1 (its chain switches) and clown.mb01.synthetic.receipts.v1 (the synthetic receipts its standalone preview wrote for itself).

A watchlist link you share carries coin addresses after the # in the link, the part your browser never sends to us.

In session storage, which the browser drops when the tab closes: cw.home.1h (the last hour's home feed this tab already drew, so coming back after the phone discarded the tab can show those coins while a fresh read is asked), cw.wallet-told (whether we already told you a wallet was remembered, this tab only), cw-series-absent (a ten-minute note that the chart-series route did not answer, so the page does not ask it again on every reload), cw.chip_answers (which search chips the shop can answer — the size of the answer and when it was read, kept for 30 minutes in this tab so a second open of Search does not ask again) and one cw.gate. key per coin, ending in that coin's address, written when you open the warning on a coin that did not clear the floor (so the warning you opened stays open on that coin until the tab closes). The older front page also wrote cw-basket (the lines in its cart), clown.mb01.view (the sample view it last opened), cw2-floor (the age floor picked on its home screen), q, chain, cat and sort (the search text, chain, category and sort picked there) and one key per listing for the controls set on it: the amount and the quantity, the speed for the order, the paying asset, the portion you are selling and the asset you want back — none of which the site writes now.

One key in session storage is different in the same way cw_sid is, and only the operator's own page at /ops writes it: cw_ops_bearer, the access credential pasted into that page or the session it was issued after a wallet signature, held so the page can ask our server for its numbers. It is sent to our server with each of that page's requests and with nothing else, it is never written to local storage, a cookie or the address bar, and the browser drops it when the tab closes. A browser that has never opened that page never holds it. The admin console at /admin keeps its own key the same way, cw_admin_bearer: the session an admin wallet was issued after signing a message, sent only to our server and only with that page's requests, never written to local storage, a cookie or the address bar, and dropped when the tab closes.

One key in local storage is different in the same way, and only the beta testers' page at /beta writes it: cw_beta_code, the tester code you typed into that page once, kept so the page can show you your task without asking again. It is sent to our server with each of that page's requests and with nothing else, it is never in the address bar or a cookie, and the page's "Forget my code" button removes it. Our server keeps only a one-way digest of the code, never the code itself. A browser that has never opened that page never holds it.

The same beta page also keeps cw-beta-wallet-address, the public wallet address you typed into its address field, so the field is filled when you return on this device. Opening the page does not send that remembered address; submitting a report sends the address you choose in its form. Clearing this site's storage removes it.

Tester desk notes on this device

The named desks remember the public wallet address you entered in a local-storage key beginning desk-wallet- and ending in the desk's name. This fills the address field when you return on this device. Opening the desk does not send that remembered address as a report; submitting a report sends the address you choose in its form.

Dave's checklist keeps desk-dave-done-tests-v1, a list of test ids you marked done on this device. The list helps choose the next Android or PC task. The checklist reads the public task catalog again when you mark a task done or check for new tests. That local completion list is not a submitted report.

These notes stay until you clear this site's browser storage. Clearing them does not delete reports, attachments or questions you have already sent. To request deletion of submitted beta records, use the contact instructions under Beta testers above.

Accounts (optional)

You can use the whole site without an account. If you choose to create one — by a six-digit code we email you, or by signing in with Google or Apple — we keep your email address and a random handle, and nothing else about you: no name, no password, no phone number. An account is a convenience: it signs you in and receives mail. It never holds funds, never signs anything and can never add, replace or recover a wallet — only your wallet's own signature can link it to an account, and linking sends no transaction.

What the email is used for. To send you the sign-in code, and, once you have turned them on, the alerts you choose. Nothing else. No marketing list, no sharing, no selling. Mail is sent through Brevo, our email provider, which receives the address and the message in order to deliver it.

How long. For the life of the account plus 30 days. The sign-in code itself is never stored — only a keyed hash of it, for ten minutes. A session lasts 30 days and can be ended at any time with Sign out, which revokes it on our server.

The cookie. Signing in sets one cookie, cw_account: a random session credential, first-party, unreadable by scripts on the page, sent only with requests to this site, expiring after 30 days. Our server keeps only a one-way hash of it. A short-lived cw_oauth cookie carries the Google or Apple round-trip state for ten minutes and is then cleared.

Deleting the account. From the account sheet, Delete my account (POST /api/v1/auth/account/delete, signed in) marks the account deleted at once: every session is revoked and every wallet link and pending code is removed immediately; the email address and handle are purged 30 days later. This is separate from your shopping events, which are keyed to your wallet's hash, not to the account, and are erased by Erase my data above (DELETE /api/v1/me, by wallet signature). To remove everything, do both.

Not yet. Phone numbers and text messages are not part of accounts today (see Text alerts, below). Where a Google or Apple sign-in is declined by the provider, the sheet says so and Email works; neither provider receives anything from us beyond the sign-in request.

The bots

Some of the activity you see on the site comes from our own simulation bots. Their lines are tagged as bots and are left out of your numbers and of every trend we show you.

Where orders go

When you buy, the order is routed through Jupiter and LI.FI. You sign every order in your own wallet; we never hold your coins. The same names appear when you connect.

Text alerts

Text alerts are not available today. Nothing on this site sends a text and nothing stores a mobile number.

When they launch, you would opt in yourself, by entering your number and confirming it. Alerts would carry the coins and checks you choose, and they would be an alert channel only: never used to sign you in, and never used to recover an account.

We would not share a mobile number, or your opt-in data and your choice of alerts, with anyone, and we would not sell either: a mobile number is never shared with or sold to third parties for marketing.

Message frequency would vary with the alerts you set, and message and data rates may apply. You would reply STOP to any message to cancel, or HELP for help. Turning alerts off would delete the number rather than set it aside.

Hosting

Our hosting provider processes every request in order to serve this site, and it may keep request logs of its own — the address you connect from, the time, the path and your browser — under its own policy. The host is Railway. This notice makes no claim about what Railway keeps.

If this changes

This notice describes what the site collects today. If anything is added that keeps an email address, a phone number or anything else about you, this notice is updated first, and it is dated above.

Who we are

This site is operated by Rebel Dividends, INC. Write to us at mad@world.lol.