Security
Security starts with the wallet boundary.
FolioFlux is built around wallet-first crypto portfolio workflows. This page explains how wallet access, imports, portfolio data, and support paths are handled before users import transaction history or open portfolio analytics.
Security basics
No private keys
FolioFlux never requires a seed phrase or private key to review portfolio records.
Support path
Contact FolioFluxWallet secrets remain outside the app.
Signatures prove ownership without custody.
Imports and analytics stay tied to user intent.
Private keys stay outside FolioFlux
FolioFlux explains wallet-based access without asking users to paste seed phrases, private keys, or exchange passwords into the product.
Wallet signatures are explicit
A wallet signature proves account ownership while keeping the requested action clear before users continue.
Portfolio data is operational
Wallet imports, CSV history, and analytics are treated as sensitive portfolio records that need clear access and support paths.
Controls
Wallet safety stays clear before onboarding.
Wallet proof without custody
Wallet-based access proves ownership without giving FolioFlux custody over private keys or signing authority.
Import clarity
Wallet, CSV, and transaction imports show which records feed portfolio analytics.
Clear support path
Security, privacy, account access, and data questions can be handled through public support links before sensitive details are shared.
Telemetry scope
Usage and device signals are used for product health, reliability, and abuse monitoring, with the scope explained in the privacy policy.
Related trust links
Security support