Privacy Policy

This privacy page explains how TokenOps/BEX handles information connected to burn tracking, project visibility, wallet-based project actions, on-chain payment verification and transparency services.

Information We May Process

• Public wallet addresses used for authentication, project actions or payments.
• Public blockchain transaction references and on-chain verification results.
• Project profile information submitted by users, such as names, links, descriptions, logos and contact details.
• Technical data such as browser context, device type, timestamps, request metadata and error logs needed to operate the service.
• Communication details voluntarily submitted for support, project review or claim handling.

Wallet Credentials

TokenOps/BEX never asks for private keys, seed phrases, wallet passwords or recovery credentials. Users sign messages and transactions in their own wallet interface.

How Information Is Used

Information may be used to provide BEX pages, verify transactions, process project claims, maintain trust and activity records, detect abuse, provide support, improve reliability and comply with operational or legal requirements.

Server Logs, Core Statistics And Optional Analytics

Necessary server and security logs: Hosting and security systems may temporarily process request time, requested resource, IP address and browser request headers to deliver the service, diagnose failures and prevent abuse. These operational records are separate from reach statistics and are not used to create a cross-site visitor profile.

Immediately aggregated core statistics: TokenOps/BEX sends a first-party count for a closed page category such as the TokenOps home page, a Panther partner page or the BEX entry page. The count contains only that fixed category. It uses no analytics cookie, browser storage, visitor or session ID, full URL, query, referrer, wallet, mint, claim, project or search value. The server adds one count to the current UTC day and does not store the request IP address or User-Agent in the analytics table. Technical and legal assessment of this processing remain separate; this description does not assert a legal basis that has not been formally approved.

Voluntary detailed analytics: Optional page, session, menu and partner events remain off until a visitor selects “Allow optional” in Privacy settings. Rejecting, revoking, leaving the choice unset or a missing consent script prevents those optional requests. Consent is stored separately for each website origin and is not used to link identities across TokenOps subdomains. Optional public analytics records are retained for 30 days.

Audit and business records: A concrete claim, wallet authentication, payment, moderation action or support request can create records required for that workflow. Those records are not core reach statistics and follow their own access, audit and retention requirements.

Core and optional analytics are sent only to TokenOps/BEX first-party systems. Optional consent can be changed or withdrawn at any time through the Privacy settings control.

Public Information

Blockchain data is public by nature. Project pages, burn events, trust labels, activity records and submitted public project details may be displayed publicly in BEX when they are part of a public profile or visibility flow.

Third Parties

TokenOps/BEX may interact with wallets, blockchain networks, RPC providers, explorers, market-data providers, hosting providers, email or messaging providers when a feature requires them. Core and optional analytics are not sent to external analytics providers. BEX interface fonts use local system fonts rather than contacting Google Fonts during page load. User-selected external links and concrete wallet or market-data features may contact their displayed provider and are governed by that provider's policies.

Contact

For privacy questions, use the official TokenOps/SafeOneChain contact channel published on the current website.