Skip to main content
CoverFi requires users to accept the current Terms and Privacy notice before opening the authenticated app.

Terms version

The active version is configured with:
The login page stores acceptance locally using the current version. The backend compatibility route confirms the storage boundary but does not persist linked legal records in a product database.

Required user-facing disclaimer

Use this wording consistently:
CoverFi protection is not insurance, not a bank product, not financial advice, and not a guaranteed payout. Payout eligibility depends on smart-contract rules, reserve funding, oracle data, network behavior, and protocol state.

Terms that must be covered

The app terms page should include these user rules before production:
  • Product is beta and may change.
  • User must be legally eligible to use the website, app, wallet flow, and smart contracts.
  • User controls wallet keys and must review every wallet signature.
  • CoverFi is non-custodial and never asks for seed phrases or private keys.
  • Protection is not insurance, not a bank product, not financial advice, and not guaranteed.
  • Payouts depend on contract rules, reserve state, expiry-time oracle data, and network execution.
  • Premiums, service fees, and network fees may be non-refundable after signed acceptance.
  • User is responsible for taxes, reporting, and recordkeeping.
  • Usernames may be rejected, removed, reclaimed, or restricted for impersonation, abuse, rights violations, or misleading use.
  • Payment and receipt tools are records and workflow helpers, not transaction reversal or guarantee tools.
  • AI is only a support and drafting layer; users must verify all AI output.
  • Prohibited uses include fraud, sanctions evasion, illegal activity, market manipulation, phishing, spam, scraping, malware, impersonation, abuse of AI endpoints, upload abuse, and attempts to bypass security controls.
  • CoverFi may rate limit, suspend, remove content, pause contracts, or restrict access for security, compliance, legal, abuse, or reliability reasons.
  • Third-party services such as wallets, analytics/indexer infrastructure, AI providers, price providers, Stellar infrastructure, and hosting providers have their own terms.
  • The service is provided as-is and as-available, subject to legally permitted warranty disclaimers and liability limits.
  • Production terms must define governing law, venue, dispute handling, support/contact address, and jurisdiction-specific consumer/privacy rights after counsel review.

Privacy summary

CoverFi may process:
  • Wallet address.
  • Username.
  • Browser-local profile fields entered by the user.
  • Protection position state.
  • Browser-local payment receipt display data.
  • On-chain receipt hashes and encrypted references.
  • AI chat messages and replies sent to the configured AI provider when the user asks for a reply.
  • Privacy-safe analytics events and aggregate metrics.
  • Operational logs and request IDs.
  • IP-derived security metadata.
  • Browser, device, and network metadata needed for reliability and abuse prevention.
Users should never enter seed phrases, secret keys, private keys, passwords, or highly sensitive personal data into the app or AI chat.

Data use and sharing

CoverFi may use data to:
  • Operate the app and backend.
  • Keep wallet-scoped app state locally in the browser.
  • Resolve usernames through the Soroban username registry.
  • Store encrypted local payment receipt metadata in the browser.
  • Provide AI support and drafts.
  • Prevent abuse and enforce rate limits.
  • Monitor errors, security, and product reliability.
  • Comply with legal obligations.
Data may be processed by service providers such as AI providers, hosting providers, wallet providers, price providers, analytics/indexer infrastructure, and Stellar infrastructure providers.

Official provider references

Use official provider documentation when configuring product and privacy disclosures:

AI disclosure

CoverFi AI is a UX and support layer. It may draft actions for review, but it cannot sign transactions, move funds, or guarantee outcomes. This document is a product/legal readiness draft. It should be reviewed by qualified counsel before production or mainnet launch.