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. Author edits, edited timestamps, deletion state and the choice to show a token-holding indicator are recorded to provide those controls. Hiding the indicator does not hide public wallet balances. 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. The encrypted vault and temporary unlocked session remain in a separate browser signer origin; the public IGNIS page retains only the public owner/account link and cannot read the migrated vault or session key back. 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.
Referrals and cashback
Opening a referral link can store its code and visit time in a first-party cookie for up to 30 days so the invitation can be shown when you return in that browser. Confirmation stores the owner-wallet address, inviter, signed authorization, confirmation time and applicable cashback window. The confirmed relationship persists across devices and does not depend on keeping that cookie.
IGNIS uses confirmed curve trades, linked-wallet identity, launch roles and fee amounts to check eligibility and calculate referral commission and cashback. Records include source WFLR or FXRP fees, recorded FXRP conversion observations, pending and published allocations, and claim transactions. Linked-wallet eligibility history is retained so unlinking or relinking cannot reset a referral or welcome window. Referral links identify an inviter and may display their public profile name; published claim transactions are public on Flare.
Technical data
Hosting, security, RPC, and content-delivery providers may process ordinary request data such as IP address, user agent, timestamps, and error diagnostics. IGNIS enforces a Content Security Policy; when a browser reports a policy violation, the report may include 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. Technical data is used to operate, secure, and troubleshoot the service—not to sign transactions.
To estimate how many visitors are online, a visible browser may send a small presence signal every 30 seconds. A random identifier shared across tabs is stored in that browser and rotates after 24 hours. The presence table stores only its hash and latest signal time, without wallet addresses, page URLs, balances, or raw IP addresses. Administrators see an aggregate count for the last 90 seconds. Records older than 10 minutes are pruned in bounded batches during later presence requests and dashboard reads. This signal is skipped when Global Privacy Control or Do Not Track is enabled, or browser storage is unavailable.
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
Interface-agreement, community, media-publishing, profile-linking, referral-confirmation, 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.
Interface agreement records
When an owner wallet accepts the IGNIS interface agreement, IGNIS stores the public owner-wallet address, terms and privacy versions, Flare chain ID, single-use nonce, signature, and acceptance timestamp. This prevents repeat prompts for the same accepted version and provides a record of the wallet-signed choice. A linked Fast Wallet inherits the owner wallet’s acceptance; IGNIS does not create a second acceptance record for the Fast Wallet. The agreement record does not store a raw IP address.
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. You can decline an invitation or clear an unconfirmed referral cookie; clearing browser data does not remove an already confirmed inviter or published onchain claim. Community moderation may hide content from IGNIS while preserving audit records required for security and integrity.