Privacy & Data Protection Policy

Monsave ("Service", "we", "us", "our") is a Personal Finance Management (PFM) software tool designed to help individuals and families track, plan, and analyze their financial health. Monsave is not a bank, payment processor, credit institution, or custodian of client funds. We do not hold client cash balances or initiate fund transfers.

We process data in line with the principles of the GDPR and the Law of Ukraine "On Personal Data Protection". For any question about your data, contact the operator of the Monsave service at support@monsave.com.

Monsave strictly adheres to the principle of data minimization: we only process information strictly necessary to provide finance management features and secure user accounts.

• Account Profile Data: Email address, nickname, interface language, and time zone preference.
• Finance Workspace Data: Virtual account titles (e.g., "Cash Wallet", "Savings Account"), account balances, base currency (UAH, USD, EUR, etc.), budget limits, and accounting period cycles.
• Transaction Records: Dates, amounts, income, expense, and transfer records, user tags, transaction categories, and custom notes.
• Account Sharing Data: Registered emails of invited family/partner accounts and assigned permission levels (View vs. Edit).
• Security & Device Metadata: IP addresses of active sessions, browser/device user-agent strings, and security logs of recent authentication events.
• Visit source and first steps: with your analytics consent, the source, medium and campaign of your visit, the landing page and the referring site. Regardless of analytics consent, the scenario you chose at signup and the type and time of your first value action in the app (for example, a first transaction). No balances or amounts are included.
• Saved calculations: the bond, quantity and price you choose to save from a calculator. They are stored only after your click, are not sent to analytics and are deleted with your account.
• Category suggestions: to suggest a category for a tag, Monsave compares its name, the merchant types (MCC) of your transactions and the tags you have already sorted. A model computes this on Monsave servers without sending anything to third-party services; the model is not trained on your data, and your suggestions are built only from your own tags. Suggestions you dismiss are stored so they are not offered again.

Who receives data: Google (Analytics after your consent, Google sign-in if you use it, receipt recognition in the Telegram bot), Microsoft (Microsoft sign-in if you use it), Telegram (if you use the bot) and Monobank (if you connect it). Google and other providers may process data outside your country or the EEA. hCaptcha checks the signup, password reset and confirmation email forms for bots.

Connecting Monobank is optional and initiated by you:

• Read-only use: Monsave reads accounts and statements and does not call the bank's payment functions.
• Restricted Credentials: Bank integration identifiers are stored in the database and are reachable only through controlled server-side functions.
• Disconnecting: you can disconnect Monobank in the settings at any time, and Monsave removes the stored connection identifiers. To cancel the permission on the bank's side, use the bank's own tools or contact the bank.

Monsave offers public interactive financial calculators (bonds, compound interest, FIRE 4% rule, car ownership, FOP taxes, rent vs. buy, etc.):

• Client-Side Processing: Calculations run locally in your browser using JavaScript.
• Amounts are not stored: the incomes, savings and rates you enter in the public tools are not saved on our servers. Page visits may be counted by analytics if you allowed it.

In accordance with Art. 6 GDPR, our processing grounds include:

• Contract Performance (Art. 6(1)(b) GDPR): Delivering personal finance tracking, budget alerts, and ledger history.
• Legitimate Interests (Art. 6(1)(f) GDPR): Protecting accounts against brute-force attacks and ensuring infrastructure stability.
• Explicit Consent (Art. 6(1)(a) GDPR): Voluntary activation of bank API sync or Telegram bot notifications.
• Analytics and marketing consent (Art. 6(1)(a) GDPR): Google Analytics, marketing signals to Google and visit-source attribution. You can withdraw consent at any time.
• Legitimate interest (Art. 6(1)(f) GDPR): recording the signup scenario and first value action to direct you to the right page and understand whether the product is useful.

Monsave uses necessary and functional cookies to run the service. Analytics cookies are set only after your consent:

Google Analytics 4 loads only after you allow analytics, and only on public pages and the sign-in and registration pages. It is not used inside your account. Page addresses are sent without query parameters, except campaign tags. Balances, amounts and transactions are not sent. The separate marketing option allows Google to measure and personalize advertising.

With your analytics consent, the visit source is linked to your account at registration or when you connect the Telegram bot. A link to the bot may contain a random key that stores the page and campaign; it gives no access to your account.

We apply a defense-in-depth security approach:

• TLS Transport Encryption: All data in transit is protected by HTTPS with HTTP Strict Transport Security (HSTS).
• Procedural Database Layer: the application works with data through PostgreSQL functions with SECURITY DEFINER rights, which limits direct access to tables.
• Salted Password Hashing: User passwords are encrypted using PBKDF2 with cryptographically unique salts. We cannot view your password.
• Workspace Isolation: your data is available to you after authentication and to the people you have given access through Sharing Center.

You retain full control over your financial history:

• Data Portability: Contact us to request a copy of your transactions, accounts and tags.
• Account deletion: you can delete your profile, which removes its transactions, accounts and categories. Technical logs and backups may be kept for longer, as described below.
• Operational backups: data may remain in backups for some time after deletion so that the service can recover from failures.
• Visit source and first steps: stored until your account is deleted and removed with it. Telegram keys are valid for 30 days and are then purged during routine cleanup. Withdrawing consent stops further collection and removes the cookies; to erase data already linked to your account, contact us.

Under GDPR and international privacy legislation, you have the right to:

• Access, correct, or update your personal records;
• Request complete erasure of your financial ledger and account;
• Revoke banking integration and notification consents at will;
• Lodge a complaint with your jurisdiction's Data Protection Authority.
• To lodge a complaint with a data protection authority.
• To withdraw analytics or marketing consent at any time in the cookie settings, without affecting earlier processing.