Privacy Policy

BudgetDash is operated by Alexander Baltazar Almeida, an individual, not a company. If you have questions about this policy or your data, contact on LinkedIn.

To provide the app, BudgetDash stores:

• Account info: your email address, display name, and password (hashed using industry-standard methods — see "How your data is secured" below).
• Financial data you enter: budgets, categories, transactions (amount, currency, date, and any comment or payee you add), recurring transaction rules, and split rules for shared expenses.
• Accounts and net worth data: any accounts you add on the Assets page (name, type, currency, and whether it's an asset or liability) and the balance snapshots you record for them over time. Balances are whatever you enter manually or import — we don't connect to your bank.
• Shared budget data: if you join or create a shared budget, other members can see your display name, email, the transactions you add to that shared budget, and any accounts you choose to link to it.
• Settings: locale, timezone, and default currency preferences.
• Imported data: if you use CSV import (for transactions or for account balance history), the contents of the file you upload are processed and stored the same as manually entered data.
• Technical/log data: our hosting providers (Vercel and Supabase) automatically log things like IP address, browser type, and request timestamps for security, debugging, and reliability — the same way most web infrastructure does. We don't use this for tracking or advertising.

We use only essential cookies and local storage needed to keep you signed in. We don't use tracking or advertising cookies.

We don't collect data for advertising, and we don't sell data to anyone.

We don't sell or rent your data. We share it only with the infrastructure providers that run the app:

• Supabase: database, authentication, and file storage.
• Vercel: hosting for the web application.

If we add another provider (e.g. an email service for notifications), we'll list it here and update the date at the top of this page.

Within the app, row-level security rules restrict every query so that you can only see budgets you own or have been invited to, plus the members and transactions on those shared budgets. Other users can never query your private (non-shared) budgets.

As the operator of BudgetDash, I also administer the underlying database and technically have the ability to access stored data directly. I don't use that access to browse individual accounts or transactions. I only access specific account data when:

• You've asked for help debugging an issue with your account,
• It's necessary to investigate a bug or security issue, or
• I'm legally compelled to (e.g. a valid legal request) — if that ever happens and I'm not prohibited from saying so, I'll try to notify the affected user first.

BudgetDash is built on Supabase, which encrypts data in transit (TLS) and at rest. Authentication (including passwords and optional multi-factor authentication) is handled by Supabase Auth — passwords are hashed using industry-standard methods and are never visible to me as the operator.

The iOS app also offers an optional Face ID app-lock. This is a local device feature only — it doesn't send any biometric data to us or to Supabase.

If we ever experience a security incident that affects your data, we'll notify affected users without undue delay.

You can delete your data at any time from Settings:

• Reset data permanently deletes every budget you own (including shared ones) along with their categories and transactions, plus all of your accounts and balance history on the Assets page, while keeping your account active.
• Delete account permanently deletes your profile, the budgets you own, and all associated data.

Both actions remove the data from active systems immediately and cannot be undone. We're currently on Supabase's free tier, which doesn't take scheduled backups, so there's no separate backup copy of your data lingering after deletion. If we move to a plan with backups in the future, we'll update this section with how long deleted data may persist there.

Shared budgets: if you own a shared budget, deleting it (via Reset data or Delete account) also deletes it — and all of its transactions and any accounts you shared to it — for every other member, with no separate warning sent to them today. If you're a member (not owner) of a shared budget and delete your account, the budget and your past transactions on it stay intact for the remaining members; only your own profile, any budgets you personally own, and any accounts you own (including ones you'd shared to that budget) are removed. There's currently no self-serve way to leave a shared budget without deleting your account — ask the budget owner to remove you, or contact us.

You can export your transactions and accounts (with balance history) as CSV files yourself at any time from Settings. For anything else — including account deletion help — reach out on LinkedIn.

You must be at least 16 years old to create a BudgetDash account.

BudgetDash is operated from Switzerland by an individual, not a registered company, and is intended to comply with the general principles of the Swiss Federal Act on Data Protection (FADP). If you're located in the EU/EEA, UK, or California, other laws (e.g. GDPR, UK GDPR, CCPA) may also apply to your use of the app — we haven't done a separate formal legal review against those specific frameworks, so treat this policy as a good-faith commitment rather than a certified compliance statement. If you have specific regulatory concerns, contact us and we'll do our best to address them.

BudgetDash is an early-stage, actively developed app. If this policy changes in a way that affects how your data is handled, we'll update the date at the top of this page.