What the interface reads
When you connect a wallet, the site reads its public address, network, native balance, token balances, allowances, launch roles, and claimable fees. These values already exist on a public blockchain. Connecting does not reveal your private key.
What the community stores
If you publish, comment, vote, or upload media, IGNIS stores the signed action, public wallet address, content, timestamp, and related launch in its service database or media storage. Posts are intentionally public. Moderation actions and reasons are also logged. Avoid sharing personal or confidential information.
Watchlists and private messages
Wallet watchlists are stored privately for the signed-in owner wallet and are not shown to watched wallets. Direct messages, participant addresses, delivery and read timestamps, blocks, and reports are stored by IGNIS so conversations can persist across devices. Messages are participant-only but are not end-to-end encrypted. Moderators cannot browse conversations; they receive the text and metadata of one exact message only when a participant explicitly reports it, together with the report reason.
Fast Wallet sessions and profile links
Linking a Fast Wallet to an owner profile is optional. If you opt in, IGNIS stores and publicly displays the association so Owner, Fast, and Combined positions, trades, and estimated PnL can be viewed together. An unlocked key stays local to the browser. A transient same-tab record preserves only the remaining 30-minute genuine-inactivity window across refreshes; refreshing does not restart it. Manual lock, disconnect, owner change, or expiry clears that record. An explicitly armed Copy Session may extend local use for its selected 1–12 hour window, but closing the browser or losing local execution prevents further copied trades. Unlinking removes the interface association, but it cannot erase either address’s public blockchain history.
Token discovery and Copy Sessions
The Fast Wallet token drawer may ask Flare Explorer for public token-balance candidates, then reads contract code, metadata, and the live balance through Flare RPC before showing transfer controls. Copy Session settings and progress are stored locally for execution and as limited server-side metadata for watchlist authorization, budgets, expiration, and duplicate prevention. IGNIS never receives the Fast Wallet private key and does not execute copied trades from a server.
Technical data
Hosting, security, RPC, and content-delivery providers may process ordinary request data such as IP address, user agent, timestamps, and error diagnostics. During CSP report-only rollout, the browser may also report a blocked resource URL, violated directive, source file, and line number; IGNIS truncates these fields and does not intentionally record page content in that report. IGNIS uses technical data to operate, secure, and troubleshoot the service—not to sign transactions.
Token media and blockchain permanence
Token artwork and metadata uploaded during creation are pinned to public IPFS and may also be mirrored by IGNIS media storage when that service is available. Their content identifiers and the metadata hash are recorded onchain. Blockchain transactions and published launch assets may be effectively permanent even when IGNIS hides them from its interface.
Wallet signatures
Community, media-publishing, profile-linking, private-session, and interface-moderation signatures are scoped to a human-readable action and single-use nonce. They are not blockchain transactions, token approvals, or permission to move assets. IGNIS does not ask for seed phrases or private keys.
Your choices
You can browse public markets without connecting, disconnect the interface at any time, decline any signature, unwatch or block wallets, stop a Copy Session immediately, unlink a Fast Wallet from its owner profile, and use Flare Explorer or another compatible interface instead. Community moderation may hide content from IGNIS while preserving audit records required for security and integrity.