webgoex
Table of contents

webgoex Privacy Policy

Last updated: August 29, 2026

This draft is product copy and not jurisdiction-specific legal advice. The project owner must complete legal review before a public Mainnet launch.

1. Overview

webgoex is a wallet-verified AI access and participation gateway built on BOT Chain. This Privacy Policy explains information that may be processed when you visit the website, connect and verify a wallet, use a session, view a Genesis record, submit a Boost transaction, or follow an external link.

2. Public Blockchain Information

Wallet addresses, contract addresses, transaction hashes, blocks, timestamps, BOT values, balances, and smart-contract state may be public blockchain information.

When you submit an optional Boost, webgoex may retrieve and display this information through BOT Chain RPC and Explorer services. Disconnecting the wallet does not delete public blockchain records.

3. Wallet Connection and Verification

webgoex does not receive or store your seed phrase, private key, wallet password, keystore file, or recovery information.

To verify wallet control, webgoex may generate a one-time challenge and ask you to sign a readable message containing information such as the domain, URI, wallet address, purpose, Chain ID, nonce, issuance time, and expiration time.

The verification signature does not itself transfer BOT or approve tokens. You should still read every message before signing and confirm that the domain and purpose are correct.

The service may process the signed message, signature, recovered address, verification result, timestamps, nonce metadata, and security logs as needed to prevent replay, fraud, and abuse. The production implementation should minimize retention of raw signatures and nonces.

4. Application Profile and Points

After successful verification, webgoex may store an application profile containing:

  • public wallet address;
  • Chain ID;
  • verification time;
  • base Points;
  • Boost Points;
  • total Points;
  • Boost transaction hash and block;
  • reconciliation status;
  • record creation and update times.

Webgoex Points are application records. They are not an ERC-20 token or wallet asset.

5. Sessions and Cookies

webgoex may use an essential secure session cookie to keep a verified wallet session active. The production cookie should be HttpOnly, Secure, and configured with an appropriate SameSite policy.

Essential session cookies are required for authentication and transaction reconciliation. Non-essential cookies or analytics should not be enabled unless disclosed and lawfully configured.

6. Information Stored in Your Browser

To recover a pending Boost after a refresh, webgoex may store limited metadata such as:

  • wallet address;
  • Chain ID;
  • transaction hash;
  • contract address;
  • submission time.

Browser storage is not the authoritative Points ledger. Clearing browser storage does not remove public blockchain records or the server-side application profile.

7. RPC, Explorer, Database and Hosting Providers

Requests may be processed by configured wallet providers, WalletConnect, BOT Chain RPC providers, Explorer services, database providers, rate-limit services, Vercel, domain providers, content delivery services, and other infrastructure that is actually enabled.

These providers may process technical information such as IP address, browser data, request time, requested resource, and network information under their own terms and policies.

8. Analytics

webgoex should not use non-essential analytics unless they are actually configured and disclosed.

Analytics must not intentionally receive seed phrases, private keys, raw signatures, session secrets, full transaction calldata, or other unnecessary sensitive data. Full wallet addresses should be avoided or transformed when event measurement does not require them.

9. AI Prompts and Workloads

The foundation release does not provide live AI prompt execution, model training, compute rental, or workload routing. It should not collect AI prompts or private workloads for features that do not exist.

Any future AI functionality requires an updated privacy disclosure covering providers, retention, training use, cross-border processing, confidentiality, and deletion controls.

10. Personal Identity Documents

The foundation release does not require passports, identity cards, face scans, biometric templates, legal names, home addresses, phone numbers, or email accounts.

Do not submit private identity documents unless a future feature explicitly requests them under an updated policy and consent flow.

11. Retention

The project should define retention periods for nonce metadata, security logs, sessions, application profiles, reconciliation records, support requests, and analytics before production use.

Public blockchain information remains available according to network rules. A request to delete application data cannot delete public BOT Chain transactions.

12. Security

No wallet, website, signature system, database, RPC service, smart contract, network, hosting provider, or security control can be guaranteed completely secure.

Never provide a seed phrase or private key to webgoex or anyone claiming to represent webgoex.

13. International Processing

Infrastructure providers may process data in countries other than your own. Applicable provider terms, legal bases, and safeguards may vary.

14. Changes

This policy may be updated when the product, infrastructure, data practices, or legal requirements change. The effective date should be shown on the website.

15. Contact

Display a contact email only after the project owner provides and verifies a real address.