1. Scope of this notice
This notice covers the FlashAlliance website and frontend interface. It describes what information may be processed by the client application, connected infrastructure providers, and the public blockchain environment used by the project.
This notice does not override the policies of wallet providers, RPC providers, block explorers, hosting platforms, or third-party services linked from FlashAlliance pages.
2. Information the frontend may process
- Wallet address used for connection, signature prompts, and contract interactions.
- Public blockchain data such as balances, events, transaction hashes, vote status, and contract state.
- Browser-side state such as interface preferences, temporary form values, or local convenience settings.
- Network metadata exposed through wallet or provider connections, including selected chain and RPC context.
FlashAlliance frontend is intended to operate with minimal user account collection. The application does not require a traditional username, password, or custodial account to use onchain features.
3. Public blockchain disclosure
Blockchain transactions are public by design. If you interact with FlashAlliance through a wallet, your wallet address, transactions, event logs, approvals, and other related data may be publicly visible onchain and through third-party indexing services.
FlashAlliance does not claim that public blockchain activity can be treated as private, erased, or meaningfully hidden once confirmed onchain. Users should avoid linking personally identifying information to public wallet activity unless they accept that disclosure risk.
4. Third-party services and infrastructure
When you use the site or dApp, information may also be exposed to third-party infrastructure such as wallet extensions, RPC endpoints, block explorers, asset hosts, analytics-free hosting providers, or repository-linked services. Those providers may process metadata under their own terms and privacy rules.
FlashAlliance does not control third-party policies and cannot guarantee how external services retain, analyze, or log connection data.
5. Local storage and device-side persistence
The frontend may use client-side storage to preserve non-custodial convenience state, such as recently viewed alliance data, UI toggles, copied-address feedback, or form/session continuity. This data is generally stored locally in the browser and is not treated as private if the device itself is shared or compromised.
6. Security limitations
FlashAlliance frontend can reduce custodial handling, but it cannot protect users from wallet compromise, malicious browser extensions, unsafe RPC providers, malware, social engineering, or public chain visibility. Users remain responsible for wallet security and for reviewing all transaction prompts before signing.
7. Retention and deletion
Public blockchain data cannot be deleted by frontend operators. Local browser state can typically be removed by the user through browser storage clearing, wallet disconnection, or device-level cleanup. Third-party providers may keep logs according to their own retention policies.
8. Contact and related references
For privacy, security, or disclosure concerns, use the project contact and reporting routes listed in the repository and documentation. Operational context is also available in Status, Release Readiness, and Risk.