Skip to content
CryptoMuz
Docs menu

DocsTrust and safety

Security

How CryptoMuz protects you and your project.

Connected wallets and separate trading wallets

Connecting a wallet, signing in and launching a token do not require sharing that wallet's private key or recovery phrase. Trading-wallet imports accept separate wallet keys and keep encrypted browser entries scoped to your account.

What we store

CryptoMuz stores account and payment records, settings, support messages, poll responses, automation records and usage statistics. The normal trading dashboard reads wallets from encrypted browser storage. See the privacy policy for public data, analytics, retention and privacy requests.

How transactions work

Deployments and manual transactions are prepared for approval in your connected wallet, which shows you the details before signing. Auto-trade instead signs scheduled transactions through the separate trading wallet you unlock in your browser, it does not ask the login wallet to approve each run. Payments are verified against the blockchain on our servers before access is granted.

Contracts

Token contracts use established open-source standards, but CryptoMuz's contracts have not been independently audited. Explorer verification depends on the network and deployment; check its status for your actual contract. Verification makes source available and does not prove security.

Stay safe

  • Bookmark the official site and check the address before connecting a wallet.
  • Rehearse on a testnet before spending real funds.
  • Revoke token approvals you no longer need, for example after a multi-send.
  • Ignore unsolicited direct messages offering help (pretending to be CryptoMuz), support or investment.