Settings

CIPHER runs on Mainnet only. There is no test network to switch to, so a transaction can never be mistaken for one that settled real value when it did not.

Endpoints are configured at build time so credentials never live in browser storage. Only the host is displayed here — an endpoint's path and query string can carry an API key.

Your ElGamal and AES keys are derived from a wallet signature in this browser and held in memory. They are never written to disk and never transmitted. Locking, disconnecting or closing the tab clears them; the derivation is deterministic, so the same wallet always recovers the same keys.

CIPHER stores the selected network, any assets you added, and non-secret metadata about in-flight operations so an interrupted multi-transaction flow can be reconciled after a reload. No amount, balance or key material is ever persisted.

No third-party analytics script is bundled. If a deployment enables analytics, events carry only the operation name, the network, a rounded duration and a normalized error code — never amounts, balances, addresses, recipients or key material.