Privacy

Last updated: November 2026

The short version: the website is static and has no analytics, the plugins have no telemetry, and the only public data is what the protocol and the ads service need to work.

This website

Static files served by Caddy. No account system, no analytics, no advertising pixel. Fonts, scripts and images come from this host; the only outside request is the public RPC described below. The server keeps standard access logs for operational security, including IP addresses; they rotate and are not used for profiling.

Cookies and local storage

One functional cookie, NEXT_LOCALE, records the language you pick and is written only when you use the language menu. Your theme is stored in localStorage under genkaku_theme; the plugin language override is stored under genkaku.locale. None of these is used for tracking, so there is no consent banner.

Reading the chain

The homepage asks a public Solana RPC for one account value, directly from your browser. That provider sees your IP address. We do not proxy or log the request. With JavaScript disabled the number renders as a dash and nothing is sent.

The plugins and the ads service

Neither plugin reports usage to us. They read the chain through a public RPC, reach peers through the seed relay, and fetch a sponsored catalog from the ads service. An impression report contains the creative id, the category, the worker wallet that served the session and a per-run random id — never the prompt, the answer or a user identifier. The ads service stores the creative images it serves.

Prompts and outputs

Inference runs on the worker you choose; the marketplace does not store prompts or outputs. The worker operator can see what it serves. Through the seed relay, the relay operator can see connection metadata — addresses, timing, volume — but not the encrypted content. Choose a worker you are willing to trust.

On-chain identity

A worker’s wallet and peer ID are public by design. Locators are optional; by default the worker plugin does not publish your public IP address. Publishing one is explicit and permanent.

Agent wallet access

The agent token is a local file, mode 0600, next to the plugin keys. Wallet policy, approvals and limits stay on your machine; approval decisions are not sent to us. The token is not an OS sandbox: an agent running as the same user may still reach local routes.

Deletion

On-chain records cannot be deleted. Off-chain state is yours: delete ~/.dsh/genkaku/ to remove keys, preferences and the wallet policy. Access logs expire through rotation.