Know what stays local.
Know what is public.

Practice ends with this page.

Labelled example-wallet runs exist only in JavaScript page memory. No localStorage, cookie, backend or network is used to keep them. Clearing practice memory or reloading removes all local rounds, moves and positions. Practice never produces a transaction or consumes Gas.

Connection is not a maze action.

Connect Wallet asks a compatible extension for a public account. The extension controls that consent. It does not start/reset a run, approve tokens, send assets, sign a message or submit a transaction. No private key or seed phrase is collected.

No deployment is configured. Actual chain reads, estimates and writes remain disabled. A future configured adapter would request state and fees from the wallet's network and separately ask the wallet to confirm an exact reviewed action.

Reset is not deletion.

Future chain records expose wallet address, round, position, move count, completion, transaction data and timing. Reset changes the current run but does not remove earlier public events or third-party copies. This is not encrypted or anonymous. Do not infer one wallet is one person.

Ordinary website requests.

This website serves its original scene video, scene-frame still, Inter font, standard icons and Ethers runtime from the same site. Ordinary requests download those files; no remote finance service, analytics, account database, email collection or application backend is used. The homepage explains the project, while wallet access and all maze actions stay on the separate maze page.

Wallet/browser extensions and network providers have their own policies outside this local Demo. Source-access permission is not a media copyright transfer.

A deliberately narrow scope.

No public deployment, privacy guarantee, real-world navigation, reward, service entitlement or independent audit is claimed. A project contact and X account are pending; an unrelated brand's account is not substituted.

The project paper describes the prepared rules and current limitations. Any later deployment needs separate review and explicit authorization.