Ivaronix

Privacy

What Ivaronix stores, where it stores it, and what it cannot see. Production runs on 0G Aristotle mainnet (chainId 16661); Galileo testnet (chainId 16602) is kept live for developer iteration.

What we record

Every action you run produces a receipt: a signed, chain-anchored record on a ReceiptRegistry contract (V3 for the receipt-type slots admitted post-B-V2-32; V2 for legacy slots 0-9). Receipts are public by design — they are how a third party proves you ran the work claimed.

A receipt body is canonical-hashed (RFC-8785 JCS) and contains:

What we cannot see

Cookies + sessions

iv-session · 1 hour TTL, HMAC-signed with IVARONIX_SESSION_SECRET. Issued after a SIWE sign-in. iv-siwe-nonce · 5 minute TTL, single-use, prevents replay during the handshake. Both cookies are httpOnly + sameSite=strict.

Third-party analytics

None. No Google Analytics, Plausible, Mixpanel, Segment, or cookie-based tracking. The only network traffic Studio makes is to 0G RPC, 0G Storage, and the configured 0G Router endpoint.

Operator-as-proxy

Public chain reads (the /global ticker, dashboard refreshes) are made by the operator wallet so your wallet address does not appear in the indexer logs for unrelated reads. See READ_PROXY_PRIVATE_KEY / IVARONIX_READ_PROXY_KEY in the .env template for details.

Verification

Every claim above maps to source code. Repository: github.com/Pratiikpy/ivaronix. Receipts can be re-verified independently with ivaronix receipt verify --tee-independent.