Search here or press/
Search
Web
Open QZAR and use an enabled email-code, Google or Telegram sign-in method. Privy verifies supported browser sign-in methods; QZAR then creates its own application session. Telegram Mini App access can use Telegram launch verification. Link another method only through the account settings flow.
The web interface includes wallet creation/import/export and withdrawals, spot trades, supported order and copy-trading controls, portfolio data, watchlists and presets. Availability depends on the interface and configuration; Telegram wallet groups and PIN instructions should not be assumed to match Web controls.
Public profiles, account search, points and tournament leaderboards can reveal profile fields and trading statistics. Searching a public wallet address may connect it to a QZAR profile. Read an event's eligibility, scoring, prize and payout rules before joining a tournament.
The installed PWA caches application assets and can deliver trade/order push notifications when enabled. It needs connectivity for trading. Notifications may reveal a token or trading action on a lock screen; manage permissions and previews in your browser/device settings. Removing the PWA or signing out does not stop active orders.
The current public portfolio API can show the supported wallets linked to an account, their balances, positions and trade history without viewer sign-in. A lookup of one linked wallet can reveal the account and its other wallets. Do not assume account wallets are unlinkable or that editing a profile makes its portfolio private.
Privy Wallet infrastructure
QZAR uses Privy to create and import trading wallets and request transaction signatures. QZAR keeps the public address and Privy wallet identifier; its server authorisation can request signatures and private-key exports. This lets enabled orders run while you are offline. Protect your login and use a dedicated trading wallet with a limited balance.
The Telegram bot requires the wallet PIN before revealing a private key. Sensitive web actions require an authenticator code when enabled; otherwise they require fresh sign-in verification. These are different controls; neither rotates an exposed key nor requires a new approval for each active automated order.
Exporting a key, signing out, ending sessions or removing a wallet from a list does not cancel orders or prove that Privy signing access has been revoked. Cancel active instructions separately. For help with account closure or provider-side access, contact @qzar_support on Telegram or open a support ticket in Discord.