Privacy policy

Who this service is for

EthVanity is currently an access-controlled tool for the authorized team. The pages, editorial documents and generation APIs require the team credentials. This notice describes that private deployment; it does not describe an anonymous public service.

Generation requests and results

The service processes requested address patterns and generation results. The backend can process and retain generated addresses and associated private key material in its configured storage. It is therefore not a browser-only or zero-retention service.

Access to the site does not make generated key material appropriate for publication. Keep keys and recovery material out of public records, screenshots, shared documents and support messages.

Technical data and traffic source

Requests can include technical metadata, generation timing and traffic-source information. The source feature records the referring domain, supported campaign parameters and the landing-page path when they are available. It classifies missing source information as direct or unknown.

The acquisition cookie lasts up to 30 minutes. It is configured as Secure, HttpOnly and SameSite=Lax. It does not store full referring URLs or advertising click identifiers. Source labels are indications supplied by the request and are not verified identities.

The analytics script uses a random browser identifier in localStorage and session attribution in sessionStorage. It measures page paths, supported campaign tags, referring domains, device category, active time, scroll depth and conversion events. A session expires after 30 minutes of inactivity. The tracker respects the browser Do Not Track setting. Clearing browser storage can reset recognition.

The restricted statistics dashboard also reads recorded public addresses and queries their native SOL or ETH balances through blockchain RPC providers. It displays aggregate counts and balance coverage. This statistics view does not retrieve private keys.

Hosting, computation and storage

The configured deployment uses Vercel for the websites, a private VPS gateway and backend, RunPod for generation jobs, and Supabase for configured backend storage. These services process data needed for their respective roles.

Operational notifications are sent to the configured team Signal group. The notification formatter excludes fields labelled as private keys, secrets, seeds or mnemonics. This notification rule does not mean that the generation backend never handles or stores key material.

Access and retention

Team credentials restrict access to this deployment. They should only be shared with authorized team members. No automatic deletion deadline is promised here: retention and deletion depend on the backend storage and its operational configuration.

Requests concerning stored team data should be directed through the existing internal team channel. Do not include private keys or recovery phrases in the request.

Changes to this notice

This notice should be reviewed when data collection, storage, providers or the access model changes. A future public release would require a review of the published notice and the actual deployment before removing access controls.