Privacy Policy, Terms of Service & Trademarks

Privacy-first wallet experience

Flare Wallet is designed around a simple principle: the website should collect as little information as possible, and the desktop wallet experience should keep sensitive wallet material under the user's control. You do not need an account to browse flarewallet.org, read product information, open the legal center or reach the download section.

Public blockchain activity is different from website data. When a wallet address, transaction hash, Smart Account interaction, FXRP minting step or vault allocation is published to a blockchain, that information may be visible through the relevant network, explorer, RPC provider, data connector or protocol interface.

Information we do not ask for

• Recovery phrases, seed phrases, private keys or wallet passwords.
• Full identity documents on this website.
• A Flare Wallet web account just to browse, compare features or download desktop builds.
• Private wallet contents beyond what is already public on the networks you use.

Information you may choose to provide

• Email address and issue details submitted through the support chat.
• Technical context you voluntarily include, such as operating system, app version, asset name, route type or transaction hash.
• Browser-level signals needed to load pages, assets, fonts, video and static files.

Website and support data

This website may process basic request data needed to serve pages and assets. The support chat is a product-facing help flow: it asks for an email address first, then asks for a short description of the question. You should never include recovery phrases, private keys, passwords or full secret backup material in any support message.

Wallet and network context

Product flows described on the site may involve public wallet addresses, token balances, network fees, transaction hashes, dApp requests, Flare Data Connector proof states, Smart Account states, FXRP status and vault activity. Some of this information is public by design once a transaction or protocol action is broadcast.

Local desktop expectations

Desktop wallet settings, action previews, device-level security, app preferences and local wallet state should be handled by the installed application and operating system. The website itself is not a place to enter or restore private wallet credentials.

This website uses localStorage to save a single consent value named flareWalletConsent. It keeps the cookie banner hidden after you select Accept. You can clear it from your browser at any time.

The current site does not need advertising cookies to explain the product. If analytics, performance monitoring or additional support tooling is added later, this page should be updated to describe the provider, purpose and user choices.

Scope and acceptance

By accessing flarewallet.org, downloading a desktop build, using support channels or interacting with the Flare Wallet product experience, you agree to use the product responsibly and in compliance with applicable laws. If you do not agree with these terms, you should not use the website or product.

Nature of the product

Flare Wallet is presented as a desktop wallet interface for familiar wallet actions, Xaman-style review flows, FLR control, FXRP visibility, FAssets routes, Smart Account execution, vault status and XRPFi activity. Product features, labels, supported assets, supported networks, downloads and integrations may change over time.

User responsibilities

You are responsible for securing your device, verifying wallet addresses, reviewing assets and amounts, checking fees and understanding the route before confirming any action. Blockchain transactions can be irreversible, and Flare Wallet cannot guarantee that a transaction, swap, mint, redemption, delegation, staking action, vote or vault route can be reversed after confirmation.

Acceptable use

You may not use the website, support channel or desktop product to commit fraud, evade sanctions, attack infrastructure, misrepresent affiliation, distribute malware, imitate Flare Wallet branding, interfere with other users or use the product in a way that violates applicable law or protocol rules.

No financial, legal or tax advice

Product copy, balances, market views, vault previews, route explanations and educational material are provided for product understanding only. They are not investment, tax, accounting or legal advice. You remain responsible for your own decisions and outcomes.

The product story centers on user-controlled wallets. Flare Wallet presents a familiar Xaman-style signing and review pattern on desktop, while Flare-side execution is represented through Smart Accounts, FAssets, FDC and related Flare infrastructure.

• Keep recovery material offline and away from websites, chats, screenshots and cloud documents.
• Review every action preview before confirming: asset, amount, address, route, network, fee and expected result.
• Use support for product questions, not for sharing secrets. Support should only need issue context, public transaction IDs or operating-system details.

Protocol and route risk

FXRP, FAssets, Smart Accounts, vault allocation, minting, redemption and Flare execution routes may depend on blockchain networks, data providers, collateral systems, smart contracts, vault strategies, liquidity and third-party interfaces. Availability, fees, timing, collateral health and final results may change.

Oracle, proof and bridge-style risk

Data verification and proof-aware activity can make routes more understandable, but they do not remove all technical risk. Oracle data, proof systems, network congestion, protocol bugs, validator behavior and cross-chain assumptions may affect outcomes.

No yield guarantee

Vault previews, XRPFi examples or position views should not be read as guaranteed returns. Any displayed rate, projection, health factor or vault status can change and should be reviewed before action.

Flare Wallet may reference or connect to independent networks, wallets, dApps, RPC endpoints, data providers, oracle systems, FAssets components, vault protocols, onramps, swaps, bridges, explorers or support tooling. Those services are operated by their own providers and may have their own terms, privacy policies, fees, eligibility rules and regional limitations.

When you choose a partner-powered action, the relevant provider may process public wallet data, transaction details, routing details, device information, compliance checks or support context needed to complete that action.

Flare Wallet marks

Flare Wallet, flarewallet.org, the Flare Wallet logo, product interface, copy, layout, visual identity and related product names are used for this desktop wallet product experience. You may not copy, imitate or modify these brand elements in a way that could confuse users or suggest affiliation.

Third-party marks and ecosystem references

Xaman, Flare, Flare Network, XRP Ledger, XRPL, XRP, FXRP, FAssets, FTSO, FDC and other product, protocol, company or token names mentioned on this site are trademarks, service marks, logos or identifiers of their respective owners. References are used to describe ecosystem compatibility, product concepts, integration flows and user-facing wallet functionality.

No implied endorsement

Use of third-party names does not imply endorsement, sponsorship, partnership or official approval unless explicitly stated. Any external logos or ecosystem labels should remain visually clear, unmodified where practical and limited to factual identification.

For product questions, use the support chat on the main Flare Wallet website. The support flow may ask for an email address, operating system, app version, asset name, route type or public transaction hash. It should never ask for recovery phrases, private keys or wallet passwords.

Legal, privacy or trademark requests can be routed through the same support entry point and should include enough context to identify the page, product claim, brand usage or data request being discussed.

This page may be updated to reflect new desktop builds, product flows, supported platforms, support tooling, Flare ecosystem references, legal requirements or brand guidelines.