Privacy Policy

When you deploy a token, we may store deployment metadata such as token name, symbol, chain, contract address, transaction hash, selected package, fee amount, feature settings, deployment timestamp, and approximate country from hosting headers.

If contract verification is attempted, we may store verification status, explorer name, explorer GUID, explorer response messages, compiler metadata, constructor arguments, source template identifiers, and verification timestamps.

Wallet connection is handled by wallet providers and wallet connection libraries. We do not ask for or store your seed phrase, private key, or wallet password.

Deployment metadata is used to provide support, monitor reliability, detect abuse, improve product behavior, and prepare contract verification workflows.

If Telegram notifications are enabled, a short deployment summary may be sent to our internal notification chat.

Contact form submissions are used to respond to support requests and may be marked internally as new, replied, or archived.

EasyTokenCreator may use Vercel for hosting, Supabase for database storage, Telegram for internal notifications, wallet providers for wallet connection, RPC providers for network calls, and block explorers for contract and transaction links.

These providers process data under their own policies and infrastructure controls.

Blockchains are public networks. Contract addresses, transaction hashes, wallet addresses, token metadata, and contract source verification may be publicly visible forever.

We use necessary browser storage for wallet connection, security, and remembering your cookie preference.

Optional analytics storage is disabled unless you accept it from the cookie banner or save it in preferences.

We do not store seed phrases, private keys, wallet passwords, complete payment card data, or custody of your crypto assets.

We do not control your deployed token contract after deployment unless the contract owner is explicitly set to an address we control, which the normal EasyTokenCreator flow does not do.

We do not guarantee that deleting internal support records removes public blockchain data, explorer pages, cached search results, or third-party logs.

Deployment logs may be retained for operational, support, fraud-prevention, and compliance reasons.

We use reasonable technical safeguards, but no internet service or blockchain workflow can be guaranteed to be error-free or perfectly secure.

Admin access is restricted, but operational staff or service providers may process limited data when needed to maintain the service or investigate abuse.

We may update this policy as the product, integrations, or legal requirements change.

If you need help with a deployment record, include the transaction hash and contract address so we can identify the relevant log.