Technical disclosureCODE-LEVEL AUDIT · 2026-09-01

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.

JUSTYPE uses localStorage

The current 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.v2

Token details, full prompt, rules, unrecognized text, image data, supply, pair, description, and social URL

project.local-tokens.v2

Browser-created local profiles, rule configurations, and deterministic illustrative market fields

project.stakes.v1

Local numeric stake values by token slug

What the application code does not include

The audited source contains no first-party analytics, advertising pixels, telemetry client, error-reporting SDK, RPC request, wallet-provider request, public application API request, or server-side product database integration.

Wallet connection, real launch, trading, and staking flags are disabled. The current product does not receive a wallet address or transaction through those paths.

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.

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.

Third-party destinations

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.

Your controls

You can clear the current draft inside the product or remove JUSTYPE site data in your browser settings. There is no cloud deletion request for local-only 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.