Contact FolioFlux
Public contact is part of the trust surface, not a footer afterthought.
Use this page when you need support, want to question the trust model, or need a direct path to the builder behind the product.
Response boundary
Keep the note specific.
Contact works best when it points to a route, an issue, or a policy question that can be answered directly.
A real public contact path exists before sign-in.
Users should be able to challenge scope and policy in public.
Wallet-based sign-in keeps private keys in your wallet app.
Why reach out
Contact exists to support product accountability, not vague brand outreach.
A wallet-first product still needs a human path for support, public explanation, and trust review.
Support and bug reports
Report broken imports, confusing onboarding states, or data issues that keep you from trusting what you see in-product.
Privacy and trust questions
Ask how wallet sign-in works, what FolioFlux stores, or how the public trust pages map to the product that exists today.
Collaboration or advisory conversations
Reach out if the project direction, blockchain product UX, or potential partnerships are the reason you are here.
Contact paths
Use the route that matches the job.
Founder contact
Best for product questions and professional outreach
Use the public founder profile for direct questions about the product, trust model, or collaboration.
Open LinkedIn
Website contact path
Best for feedback, partnerships, and background context
Use the personal site when you want a broader portfolio view or need a more general contact channel.
Visit website
Trust stays public
Contact, privacy, and terms should reinforce each other.
FolioFlux links public contact with public policy so users have a visible way to question scope, data handling, and wallet-first claims before they commit to the product.
Ready to use the product
Start from onboarding when you want the app to lead the workflow.
The public pages explain the trust model. Onboarding is where FolioFlux turns that promise into a wallet-first path that preserves route intent.