⚒ DEFI WARLORD FORGE
privacycanon·always current

// Privacy Briefing

// The honest rundown of what the Forge sees, where it sends it, and what it can't see. No cookie banner theatre. No lawyer waffle. Read the list, make the call.

The Forge is a scanner that happens to run as a website. Websites see things. Most sites hide exactly what, behind paragraphs of legalese and a cookie wall. This page does the opposite. Every data flow the Forge touches is listed below, in plain English, with the outside party that touches it named. Read the list. If any of it crosses a line, close the tab.


// What The Forge Collects From You

The Forge does not use cookies. It does not run a session database. There is no account, no email, no password, no wallet-connect. The site does not know who you are, and it is built that way on purpose. If you mint a Courier code, the Forge stores one carried copy of your board against a hash of that code — still no account, still no identity, and it never reads what's inside.

Things stored in your browser — sent nowhere unless you mint a Courier code (see below):

  • localStorage keys, in full — this is the exact list the Courier would carry, rendered from the allowlist in the code itself so it cannot fall out of date:forge:watchlist:rates:v1, forge:watchlist:spot:v1, forge:watchlist:pin-meta:rates:v1, forge:watchlist:pin-meta:spot:v1, forge:watchlist, forge:watchtower:spot:v1, forge:watchtower:rates:v1, forge:hidden-tokens, forge:hidden-tokens:rates:v1, forge:hidden-tokens:spot:v1, forge:hidden-venues, forge:spot:hidden-venues, forge:watchlist:order:rates:v1, forge:watchlist:order:spot:v1, forge:watchlist:sort-mode:rates:v1, forge:watchlist:sort-mode:spot:v1, forge:sfx:v2, forge:motion:v1, forge:timeframe, forge:view-mode, forge:sort-key, forge:war-front-line.These remember your pins, your pin history, your logged sizes, your board layout and sort preferences, your hidden lists and your sound, motion and display preferences between reloads. Clear your browser storage and they're gone. No server copy exists unless you minted a Courier code.
  • A few more keys never leave this browser and are never carried: your Courier code itself (forge:courier:code:v1 and its companions) and, if you ever added exchange API keys, the encrypted keystore. Those are refused by the Courier in code.
  • Transient React state for the current page — search input, open modal, which card you expanded — dies the moment you refresh. Sort order is not in that list — the sort you pick on a board is saved to the keys above and survives a refresh.

// The Courier — Opt-In, And Only If You Ask

The Courier carries your board from one browser to another. It is off until you press GET CODE. Nothing about you is stored before that, and nothing is stored for anyone who never presses it.

  • What it holds: one carried copy of the localStorage keys listed above — every one of them, and nothing that is not on that list. Pins, pin history, logged sizes, board layout and sort preferences, hidden lists, and sound/motion/display preferences.
  • When it updates: while you hold a code, the copy is refreshed a couple of seconds after you change something on the board. You do not press anything. On another browser holding the same code, a reload takes the newer copy whenever that browser has no changes of its own. If both have changed, neither one is overwritten — the panel tells you, and waits for you to carry it across yourself.
  • What it never carries: your exchange API keys or any credential. Those are refused in code, on both ends, and never leave your device — with or without a Courier code.
  • What the Forge reads: nothing. The copy is stored as opaque bytes. The Forge never parses it, never indexes it, and never looks inside it.
  • What identifies it: a hash of your code — never the code itself. There is still no account, no email, and no name attached. Anyone holding the code can fetch the copy, so treat it like a key.
  • How long: 90 days after you last use it, then it is deleted. BURN THE CODE deletes it immediately and leaves no record that it existed. The Forge never tells you or anyone else whether a given code is still alive — a wrong code and an expired one get the identical answer, deliberately. The panel warns you from your own browser when this device has not carried in a while.

// What Gets Sent To The Backend

Every data request the dashboard makes is anonymous. The backend logs standard request metadata — URL path, timestamp, response status — and the request IP is visible to whatever host the backend runs on. No user identifier is attached. The backend does not store any mapping from IPs to behaviour.

If you paste an address into the Portfolio page, that address is sent to the backend and relayed to Zerion so their indexer can return the portfolio data. The backend caches the result keyed by the address for ten minutes. No cookie is set. No cross-session correlation happens. Another visitor pasting the same address gets the same cached response — the Forge does not know it's the same person, and it does not try to find out.

// Third-Party Services

The Forge talks to outside APIs. Each one is named explicitly so nothing is buried.

Perp venue APIs — Hyperliquid, dYdX, Paradex, Aster, Lighter, Vertex, Extended, Backpack, Pacifica, Ethereal. The backend scrapes each one on a ten-second pulse for funding rates and open interest. Your browser never contacts these APIs directly; the backend is the only client. You are not identified to any venue.

Zerion — only called when you paste an address into the Portfolio page. Your IP is not forwarded; the backend is the client. Zerion sees the address you pasted. See Zerion's own privacy policy for how they treat it.

Llama RPC (eth.llamarpc.com) — called from your browser every thirty seconds to fetch the latest Ethereum block number for the footer. No account, no key, no user identifier. Your IP is visible to Llama. If this matters to you, disable JavaScript for that domain or block it in uBlock.

YouTube (RSS + thumbnails) — the homepage shows the newest video from the Forge's channel. The feed is read server-side, at most once every fifteen minutes for the whole site, so your visit never triggers a request to Google and YouTube never sees your IP. The thumbnail is proxied through this site's own image handler for the same reason — your browser fetches it from us, not from Google. Video thumbnails are proxied through this site, so your browser never contacts YouTube just by loading a page. A video player loads only if you explicitly click play — at that point the video streams from YouTube's servers (youtube-nocookie.com), which may set cookies of its own from then on. If the feed is unreachable the card simply does not render.

Plausible analytics — loaded only when the environment flag NEXT_PUBLIC_ANALYTICS_ENABLED is true. Plausible does not set cookies, does not fingerprint, does not collect personal data. It records pageviews and referrer only. No goals or custom events are configured. See plausible.io/privacy for their own terms.

Sentry error monitoring — optional, gated by environment flag. If enabled, a JavaScript error on the site sends a stack trace and the request URL to Sentry. The URL is scrubbed of query strings before it leaves the browser, so Portfolio addresses never appear in the error payload. Session replay and profiling are explicitly disabled. IPs are not collected. If a production deployment does not set the Sentry DSN, no error data leaves your browser at all.

Forge Swap subdomain swap.defiwarlordforge.app hosts the actual swap surface (multi-DEX routing via 0x, cross-chain + XMR via Houdini, PulseChain + Railgun via LibertySwap). It is operated by the Forge under the same policies as this site. When you click TRADE on a share card or BUY SPOT on the carry table, you land there in a new tab; your wallet connection happens on that subdomain, not here.

// Hosting Infrastructure

The frontend is served from Vercel. Vercel sees request metadata — IP, User-Agent, referrer, path. Vercel's built-in analytics is disabled; the Forge does not use it. The backend is reached through Cloudflare, which sees the same kind of request metadata and applies standard network logging. Neither provider has a user account tied to the Forge visitor, and the Forge does not export any server logs to third parties beyond what is named above.

// What The Forge Cannot See

Because there is no account, the Forge cannot correlate your visit today with your visit next week. Because there are no third-party trackers, the Forge cannot follow you off-site. Because there is no wallet connect, the Forge does not know which wallets belong to you. Pasting an address into the Portfolio page tells the backend which address you asked about — not whether the address belongs to you.

// Your Controls

Clear your browser storage for this domain and every stored preference is wiped. Block the JavaScript for eth.llamarpc.com and the footer block-height readout goes dark — nothing else breaks. Block plausible.io and pageview analytics stops; nothing else breaks. Use a VPN or Tor if you don't want Vercel or Cloudflare to see your actual IP. The Forge works the same either way.

// Changes To This Page

This page changes when the data flows change. A new third- party integration gets listed here before it ships. A new tracker is not added silently — if the Forge adds one, it shows up in the list above first.

// Contact

Questions about data handling go to @BartertownC on X. DMs are open.