Privacy Policy
Clear rules for how FolioFlux handles identity, portfolio data, and telemetry.
This policy explains what the product needs to operate, where the limits are, and how wallet-first access changes the trust model.
Last updated
March 22, 2026
Wallet boundary
FolioFlux uses wallet-based sign-in. We never ask for your private keys, and every signature stays in your wallet app.
Authentication begins with address ownership.
FolioFlux does not ask for private keys.
Data-handling scope stays visible before onboarding.
What we collect
Data collection is scoped to product operation, not broad surveillance.
FolioFlux needs enough information to authenticate users, process imports, render account data, and keep the service stable. That scope should remain legible in public.
Account and access data
Information tied to wallet-based access, profile setup, and support conversations so the service can recognize your account and keep it secure.
Portfolio and transaction data
Imported wallets, transaction history, balances, performance context, and tax-related records used to power portfolio, analytics, and reporting workflows.
Usage and device signals
Basic logs, browser details, device context, and interaction patterns that help monitor service health, reliability, and abuse.
Your controls
Product controls should be understandable without legal translation.
Ask about the personal data associated with your account.
Request corrections when account details are inaccurate.
Request deletion or export where the product and applicable law allow it.
Manage communication preferences and use public contact channels for privacy questions.
How data is used
Data should have named jobs: function, security, and iteration.
The policy is stronger when it names the actual work the data performs instead of hiding behind generic language.
Operate the product
Run wallet authentication, keep imports connected to the right account, and render the portfolio, analytics, and tax surfaces you ask to use.
Protect accounts and infrastructure
Detect abuse, respond to support requests, and investigate issues that could affect account access, data quality, or product integrity.
Improve workflows
Understand where onboarding, imports, and reporting flows break down so the product can become clearer and more reliable over time.
Sharing and disclosure
Disclosure stays narrow and named.
Service providers
We may use infrastructure, analytics, or support vendors that help run the service, subject to the controls and contracts in place for those tools.
Legal and safety requirements
We may disclose information when required by law or when reasonably necessary to protect users, the service, or FolioFlux itself.
Business changes
If FolioFlux is involved in a merger, acquisition, or asset transfer, relevant data may move with the business subject to applicable law.
Linked trust pages
Privacy is stronger when the rest of the trust model stays nearby.
Policy pages should connect cleanly to contact paths and product-scope language so people can question what the app does before they rely on it.
Need a human answer
Use the public contact path when policy language still leaves questions open.
The trust model is incomplete unless the product gives people a public way to question it.