JUSTYPE
Profile
Technical disclosureCODE-LEVEL AUDIT · 2026-09-03

What stays in your browser—and what may leave it.

This disclosure describes the current application code. It is not presented as a complete legal privacy policy because operator, retention, and legal-processing details are not defined in the repository.

01

JUSTYPE uses localStorage

The frontend saves product state to localStorage so drafts and local profiles survive a refresh in the same browser. The application does not currently use cookies or sessionStorage for product state.

project.watchlist.v1

Token slugs you watch

project.create-draft.v4

Token details, full prompt, rules, unrecognized text, image data/URL, pair, launch mode, creator-revenue setting, description, website, and social URL

project.local-tokens.v3

Browser-created local profiles, rule configurations, and pair identity

project.classic-launch-profiles.v1

Receipt-verified launch record and associated frontend draft for launches made in this browser

project.stakes.v1

Local numeric stake values by token slug

The draft reader can import previous v2/v3 keys into v4. The local-token reader can import v2 into v3. Missing or unknown pair values migrate to ETH.

02

Wallet connection adds a separate browser and network layer

JUSTYPE uses Reown AppKit with WalletConnect and Wagmi to establish an EVM account session. When you open the connection experience or connect, the wallet layer can contact Reown/WalletConnect infrastructure, the selected wallet or injected provider, and the configured Robinhood Chain RPC. The connected public address and connection status become available to the page so the header and Profile can show the account.

Automatic reconnection is enabled. A fresh browser QA session observed the following library-managed storage. These entries are separate from JUSTYPE’s five product stores, and their exact schema may change between library versions. A wallet extension or mobile wallet controls its own storage.

@appkit/*

Active network, namespace, connector, connection, identity, balance, and portfolio cache state

wagmi.store

Wagmi connection state used for reconnection

wagmi.recentConnectorId

The most recently used wallet connector

WALLET_CONNECT_V2_INDEXED_DB

WalletConnect pairing and session records in IndexedDB

03

What JUSTYPE itself does not include

The audited source contains no first-party analytics, advertising pixels, telemetry client, error-reporting SDK, or server-side product database integration. AppKit analytics, email/social login, on-ramp, built-in swaps, send, receive, and transaction history are disabled in JUSTYPE’s configuration.

JUSTYPE does expose same-origin launch, market, and trade API routes. Launch/market routes send public chain identifiers, account/token addresses, PoolIds, transaction hashes, and log/read requests to the configured Robinhood RPC. Trade routes send quote, approval, and swap parameters to Uniswap's Trading API from the server only when UNISWAP_API_KEY is configured; the key is not sent to the browser.

Disabling analytics does not eliminate the operational requests required to show wallets, create a WalletConnect session, reconnect, or communicate with a configured provider. JUSTYPE does not state a retention period for Reown or a wallet provider. Read Reown’s privacy policy for Reown’s own disclosures.

04

Browser features used on request

The token Share control may use the browser’s Web Share API or clipboard after you activate it. What happens next depends on your browser, operating system, and the app or destination you choose.

Geist fonts are declared through Next’s font system and are self-hosted by the built application; visitors do not need to request the font from Google.

05

Hosting and connection data are a separate layer

Requests to JUSTYPE pass through nginx and the Next.js server. The proxy configuration forwards normal connection information, including client IP headers. The repository does not define access-log retention, backups, operator identity, or legal processing terms, so this page does not claim that server logs do not exist or promise a retention period.

Your browser, device, network, DNS resolver, TLS/certificate infrastructure, and hosting provider may process normal connection metadata outside the JUSTYPE application code.

06

Third-party destinations

Browser and integration QA observed or established the code paths below while initializing AppKit, connecting a test-injected wallet, reading a local Robinhood fork, launching there, and exercising the optional trade-service boundary. The exact request path varies with the connection method, wallet, environment, and configured services.

api.web3modal.org

AppKit wallet and connection infrastructure

rpc.walletconnect.org

WalletConnect RPC infrastructure

pulse.walletconnect.org

WalletConnect/Reown SDK service

fonts.reown.com

Fonts used inside the AppKit connection interface

rpc.mainnet.chain.robinhood.com

The configured Robinhood Chain RPC

trade-api.gateway.uniswap.org

Conditional server-side quote/approval/swap requests when a Uniswap API key is configured

The hostnames show where requests can go, not what each party retains. The Uniswap endpoint is conditional and no API key was configured for the browser fallback QA. JUSTYPE does not infer or promise Reown, WalletConnect, Uniswap, RPC, or wallet-provider retention behavior; each party applies its own terms and data practices.

The official community link opens X, whose own terms and data practices apply. A creator can save a social URL in a local profile; opening it sends you to that external site. JUSTYPE does not control those destinations.

07

Your controls

You can disconnect through the connected-account view and remove JUSTYPE site data in browser settings. Clearing site data can remove both JUSTYPE product state and wallet-library session state; your wallet may retain its own connection record until you remove it there as well.

You can clear the current draft inside the product. There is no cloud deletion request for JUSTYPE’s local-only product state because JUSTYPE does not hold a server copy in the current architecture.

Before sharing a screenshot or support report, remove prompts, token images, social links, or other information you do not want to disclose publicly.