Security

Kira manages signing wallets for an authenticated account. Keep only operational balances in managed wallets and keep an independent copy of keys you cannot afford to lose.

Managed wallets

Wallet keys are encrypted at rest and decrypted by the backend only for an authorized operation. A browser never needs to approve every wallet in a coordinated launch, but Kira should not be treated as cold storage.

Key export is deliberate and scoped to the selected account and chain. Support never needs a private key, login credential, browser cookie, or RPC key.

Account access

Wallet actions, project changes, launches, trades, funding, and claims require the authenticated account that owns them. Public chart access is read-only and does not grant any wallet or admin permission.

Use a unique credential, close sessions on shared computers, and report any wallet, project, or transaction you do not recognize.

Private and public routes

Public distribution and relay wallets remain fully visible on-chain. Private Funding removes the direct transfer between the original source and final destination, but exchanges, bridges, timing, amounts, and later wallet reuse can still reveal relationships.

Before confirming

Check the active chain, selected wallets, destination, amount, launchpad, and action. Kira validates what it can before enabling execution, but network inclusion, price movement, token behavior, and third-party availability remain external to Kira.

If something unexpected happens, save the public transaction and the Kira project, job, campaign, or order ID. Contact support without sending credentials or keys.