Privacy

MMHVAULT is designed as a private personal-finance workspace. Authentication identifiers are used to identify the signed-in account and enforce separation between users.

What the application uses

The application may process account configuration, transactions, investments, budgets, goals, recurring items, financial alerts and notification subscriptions that you choose to store in the service.

Authentication data

Authentication is provided through Supabase Auth. Google OAuth credentials are entered on Google's authorization flow, not into MMHVAULT. MMHVAULT no longer offers phone OTP sign-in. Previously linked phone identity data may still be retained by the authentication provider until separately reviewed or removed.

Push notifications

When enabled, the browser creates a Push subscription. Lock-screen Push messages are intentionally limited to short summaries; complete transaction history, email addresses, user IDs and full account balances are not included in Push payloads.

Sensitive credentials

MMHVAULT does not ask for bank PINs, card numbers, crypto recovery phrases or passwords for external financial services.