Public website privacy.
This public information site is designed to minimize unnecessary data collection.
Public browsing
The public project pages do not require a wallet connection to read contract information, documentation or project disclosures.
Optional MetaMask connection
On the public wallet page, MetaMask can expose an authorized public address so the browser can display NXVR and ETH balances on Ethereum Mainnet. Public addresses and blockchain balances are public information. Nexavira never requests a seed phrase, recovery phrase or private key.
Account wallet verification
Inside a signed-in Nexavira account, a player may link a MetaMask address by signing a one-time verification message. The public address, verification timestamp and challenge record are stored so the platform can prove wallet ownership and send approved redemptions to the verified destination. The signature does not authorize token transfers, approvals or spending and is not a blockchain transaction.
Ethereum RPC providers may process blockchain read and signature-verification requests under their own privacy policies. Nexavira does not store a wallet private key or recovery phrase.
Game and anti-abuse records
Game runs, mission progress, reward balances and redemption history are stored with the player account. To enforce the one-account-per-person/device policy and reduce automated or multi-account reward abuse, the platform may process network and device signals such as IP address, a first-party device identifier and browser/device characteristics. A shared public IP by itself is not treated as proof that two accounts belong to the same person. Persistent anti-abuse records store one-way keyed hashes of these identifiers rather than the raw values. These signals are used for account-registration controls, gameplay limits and redemption risk review.
Account security and access history
For signed-in player accounts, Nexavira may retain a security history containing login/registration timestamps, an encrypted copy of the network IP address, a keyed IP hash, browser/operating-system information and an anti-abuse device identifier. The administrative security view may also display an approximate city, region, country, timezone, network provider/ASN and approximate latitude/longitude inferred from the IP address. IP-based geolocation is approximate and is not GPS or a street-level location.
When IP geolocation is enabled, the IP address may be sent over HTTPS to the configured IP-geolocation provider solely to obtain the network-location/security fields. Access-history retention is limited by the platform configuration.
Security rate limiting
To reduce password guessing, automated registrations, wallet-verification abuse and support spam, the platform may keep short-lived security counters associated with keyed hashes of network, account or session identifiers. These counters are used only for abuse prevention and expire or are periodically removed.
Server logs
Web hosting providers may process standard technical logs such as IP address, browser information, timestamps and requested pages for security and operational purposes.
Contact email
If you contact Nexavira by email, the information you provide is used to respond to your request and maintain relevant correspondence.
Third-party links
External websites such as Etherscan apply their own privacy policies.