Back to App

Privacy Policy

Effective Date: May 23, 2026

1. Information We Collect

EverWealth is a minimalist personal financial tracking application. We only process data necessary to provide and optimize your ledger utilities:

  • Account Credentials: When you register, we securely store your email address and authentication identifiers via our infrastructure backend (Supabase).
  • Ledger Entries: We store transaction records you manually log or ingest via enabled API webhook pipelines (e.g., amount, category, item descriptions, and timestamps).
  • Integration Metadata: If you configure custom messaging webhooks, we securely map unique third-party profile identifiers (such as Telegram or messaging channel chat IDs) to connect your text inputs to your secure account row.

2. How We Use Data

Your financial ledger information is treated as strictly confidential. We use this data solely to:

  • Render your personal financial dashboards and calculate expense metrics.
  • Process incoming webhook text data payloads into your private account database.
  • Maintain application security and prevent unauthorized infrastructure access.

3. Data Storage and Retention

  • Isolation: Your transaction entries are tied explicitly to your unique account identifier using row-level security protocols.
  • Retention: We retain your data only for as long as your account remains active. You retain absolute control over your records and can permanently delete your entries or account profile at any time directly through the application interface.

4. Third-Party Services

EverWealth connects to trusted infrastructure providers to serve your application files and host your database:

  • Database & Hosting Providers: Our relational backend databases and edge serverless networks are managed securely via Supabase and Vercel.
  • External Messaging Gateways: If you interact with the system via third-party messaging utilities, those text data payloads transit through their respective systems (e.g., Telegram Bot API or Meta Cloud Graph API) before reaching our ingestion endpoints.