Privacy Policy

1. Introduction

MintValt ("we," "our," or "us") is committed to protecting your privacy. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you visit our website and use our financial-management application (the "Service").

1.1 Who we are

MintValt is made and run by Omvion Ltd, a company registered in England and Wales (company number 17536209), with its registered office at Office 482, Unit 5, 399-405 Oxford Street, Mayfair, London W1C 2BU, United Kingdom. Omvion Ltd is the controller of your personal data, which means it decides how your data is used and is responsible for protecting it. Wherever this policy says "we", it means Omvion Ltd.

For anything about your data, email privacy@mintvalt.com or write to us at our registered office.

Core privacy principle: We do not and will never store your bank credentials, ask for bank login information, or request access to your bank accounts. You maintain complete control over your financial data at all times.

2. Information We Collect

2.1 Information you provide directly

• Account information: your name, email address and account preferences. Not your password. Sign-in is handled by Firebase Authentication, so a password you type goes to Google and never reaches us. We do not receive it, hash it, or store it in any form.
• Financial data: the bank statements you choose to upload, the transactions and account balances they contain or that you enter yourself, and the budgets, goals and categories you set. A statement you upload is read by AI to pull the transactions out of it, and section 4 sets out exactly what that sends and to whom.
• Receipt data: receipt images you choose to scan. The image is sent to our AI provider, read, and discarded in the same request. We never write it to disk or to a database, so there is no receipt image for us to keep, lose, or hand over.
• Profile information: currency preferences, notification settings, and dashboard customisations.
• Communication: messages, feedback, and correspondence through our chat feature or support channels.
• Waitlist: if you join the waitlist on mintvalt.com before you have an account, we keep your email address, the country you live in, the currencies you choose, whether a friend invited you, and the campaign tag on the link you followed. When your invite comes and you sign up with the same address, your place in line is linked to your new account. If you get one of the first 200 seats, your seat number and your discount are kept with your account, and the discount is set up with our payment provider under a code that does not identify you.
• Invite codes and friend rewards: your account has its own invite code, and we keep the code of the friend whose link you signed up with, if any. To give the month free that three paying friends earn, we keep, for each payment our payment provider reports, its reference and when it was taken and refunded, never the amount or your card, and we ask the provider whether a payment was kept before it counts. Whoever invited you sees how many of their friends signed up and how many are paying, never who they are.

2.2 Information collected automatically

• Marketing-site analytics: pages visited on mintvalt.com, via Google Analytics, and only if you accept the cookie banner. Decline and no analytics script loads at all. This runs on our public marketing pages only. There is no analytics SDK inside the app itself, on the web app or in the mobile apps, and nothing from one is sent to a third party. The app notes which sections you use, described next, but never which budget or account you look at or what you spend on.
• The days you used the app, and which parts of it: the date, which sections you opened that day (budgets or the forecast, say), and whether that was on the website, the iPhone app or the Android app. Each is noted once a day, so we can see how many people use MintValt, which parts they use and whether they come back. Nothing about what was on the screen, how long you stayed or what you tapped, and nothing that identifies your device. It is deleted with your account.
• Device information: browser type, operating system, and IP address.
• Push notification token: if you turn on notifications in a mobile app, we store the token your device gives us so we can send them. It identifies an app installation, not you, and deleting the app or signing out removes it.
• Crash reports: when the app or the website fails, the error and where it happened, with your account ID attached so we can tell "this breaks for one person" from "this breaks for everyone". Off in development builds.
• Cookies: analytics cookies on the marketing site if you accept them, and nothing else. Signing in does not set a cookie: your session is a token your browser or phone holds, so there is no session cookie here for us to describe.
• Logs: request metadata for security and performance monitoring.

2.3 Information we do NOT collect

• Bank login credentials. The password a bank puts on a statement is a different thing, and we keep it only if you ask us to, as section 5 explains.
• Full credit card numbers (payments are processed securely by Creem)
• Biometric data
• Your location. The apps never ask for it, on any platform.
• Your contacts, or your photo library. The receipt scanner opens a picker and receives the one image you choose; nothing else in your library is read, and we never browse it.
• Anything else on your device that you have not handed to a specific feature
• Advertising identifiers. There is no ad SDK in any MintValt app, so there is nothing to build an advertising profile from.
• Information from third-party financial institutions without your explicit upload

3. How We Use Your Information

We use the information we collect to:

• Deliver the service: process your uploads, maintain your account, and provide support.
• Read what you upload: a statement or a receipt is sent to our AI provider to extract the transactions from it, and a payment we have not seen before is sorted into a category the same way. You can correct any of it, and a correction is remembered.
• Answer your questions: when you ask the assistant something, it reads the figures it needs to answer you.
• Work out your figures: budgets, spending breakdowns, projections, observations about your spending and your financial health score are calculated from your own data, on our servers. No model is involved in any of them.
• Communicate: send account notifications, service updates, and respond to inquiries.
• Run the waitlist: email you your place in line and send your invite, and count the friends who join with your link. Nothing else, and the list is never shared or sold.
• Improve the app: understand usage patterns to improve features and experience.
• Keep it secure: detect and prevent unauthorised access or misuse.

3.1 Why we are allowed to

Data protection law only lets us use your data where we have a lawful reason, and each use above rests on one of these (UK GDPR and EU GDPR, Article 6):

• To provide what you signed up for (contract): delivering the service, reading what you upload, answering your questions, working out your figures, running your subscription and sending the emails your account needs.
• Our legitimate interests: keeping MintValt secure, fixing what breaks, and learning which parts of the app are used so we can improve it. We only rely on this where it does not override your interests, and you can object to it at any time.
• Your consent: analytics cookies on the marketing site, push notifications, and the waitlist. You can withdraw it at any time, and doing so does not affect what happened before.
• Legal obligations: keeping payment records, and anything else the law requires us to keep or disclose.

4. Data Sharing & Disclosure

4.1 We share data with

• People you invite: a household lets you share chosen parts of your finances with the people you live with. Only what you pick crosses: an account you share (its balance, and its transactions from the date you shared it onwards), a category you share, and a budget you share. Members also see your name, the address an invitation was sent to, and how much each member has spent on shared accounts. Nothing else moves. Your other accounts, your private transactions, your savings goals and your conversations with the assistant stay yours alone. You keep control of anything you share: only you can rename, delete or unshare it, and unsharing, leaving the household or being removed from it ends the other members' access immediately.
• Creem: our Merchant of Record, which handles checkout, billing and tax (PCI-DSS compliant). Your card details go to Creem and never reach us.
• Firebase (Google): sign-in, crash reporting, and delivering push notifications. Your email address and account identifier reach Firebase; your financial data does not.
• Anthropic: the AI behind the assistant, transaction categorisation, receipt scanning and statement parsing. Worth being specific about, because it is the one that touches your financial data. When a transaction is categorised, its description and merchant name are sent. When you scan a receipt, the image is. When you upload or forward a bank statement, its text is. And when you ask the assistant a question, your question and the transactions, balances, budgets, goals and categories it needs to answer you reach Anthropic too. In every case except the receipt image, your name, email, phone number and account and card numbers are first replaced with placeholders, which we swap back once the answer comes out, and on a statement your address is too. Your name is recognised as it appears on your profile, and your address where the bank prints it at the top of a page, so a nickname or an unusual layout can let them through. Other people named in your transactions, such as someone you paid, are not masked. All of it is sent to get an answer back, none of it is used to train models. Anthropic may hold what it receives for up to 30 days, and longer only if its automated safety checks flag it or the law requires it.
• Resend: carries our email, in both directions. Outbound: sign-up, budget alerts, weekly summaries, billing notices and the waitlist, so your address and the contents of those messages reach Resend. Inbound: if you forward a bank statement to your personal import address, or reply to a support thread, that message reaches us through Resend. Forwarded statements are parsed into transactions; support replies are kept as the conversation thread. Resend itself keeps every email it carries, a forwarded statement and its attachment included, for up to 30 days before deleting it, and we cannot delete it sooner. If you would rather no copy of a statement stays anywhere, upload it in the app instead of forwarding it: uploads never pass through Resend.
• Rollbar: error tracking, on our servers and in your browser. When something fails, the error, where it happened and your account identifier go there, so a failure reaches us rather than only you. Before a report is sent, what was typed into any field, the contents of the request that failed, search terms in web addresses, passwords, tokens, cookies and authorization headers are removed, and your IP address is shortened. The error message itself can still mention a figure, which is why we keep reports to errors and nothing else.
• Google Analytics: on the marketing site only, as described above.
• DigitalOcean: hosts our servers, database and encrypted backups, in Amsterdam, in the Netherlands. Everything you keep in MintValt is stored there.
• Our own staff: a small number of administrators can look up an account to answer a support request or investigate a fault. What the console shows them is your name, email, plan and subscription status, and counts of how many accounts, transactions, budgets and goals you have. It does not show them the transactions themselves.
• Legal authorities: only when required by law or valid legal process.

4.2 We do NOT share

• Your financial data with advertisers
• Your transaction history with marketing companies
• Your data with data brokers for commercial purposes
• Your information without your consent, except as required by law

5. Data Retention

• Active accounts: your data is retained while your account is active.
• Closing your account: you can do it yourself, from Settings on the web or in either mobile app. You do not have to email anyone and wait. Your account is then erased after seven days. The delay exists so that a tap made in anger or by accident can be undone: sign in during that week and cancel, and nothing is lost. After it, your profile, accounts, transactions, budgets, goals, categories, notifications and saved devices are deleted permanently and cannot be recovered.
• What survives that deletion: three things. First, records of payments: what our payment provider sent us, when, and whether it was genuine. These are financial records and we are required to keep them, so they outlive the account they belonged to, and they contain no transaction data, no budgets and no balances. Second, support correspondence: an email thread with us is filed under the address that sent it rather than under your account, so closing the account does not sweep it up. Ask us and we will delete it. Third, a fingerprint of your email address, so the same inbox cannot start a second free trial: a one-way, keyed hash of the address with any +tag and, for Gmail, any dots removed. It cannot be turned back into the address, holds nothing else, and is kept for as long as we offer a free trial.
• Backups: routine backups are rotated on a rolling basis, so a copy of deleted data can persist in a backup for a short period before it ages out.
• Receipt images: never stored in the first place. The image is read and discarded within the request that uploaded it.
• Uploaded statements: never stored either. The file is read in memory and discarded; only the transactions you choose to import are saved.
• Forwarded statements: the transactions read from one wait for you to import or discard them, and are deleted after 24 hours if you do neither. We remind you once before that. When you import or discard one, its transactions are cleared at once, and only its file name and how many transactions it held stay, for 60 days, so you can see what you imported. The email it arrived in is kept separately by Resend, our email provider, for up to 30 days, as section 4 says.
• Locked forwarded statements: a forwarded statement your bank locked with a password cannot be read until you enter that password, so we keep the file, encrypted with our own key, for up to 24 hours while it waits. It is deleted the moment you open or discard it, after five wrong passwords, or when the 24 hours pass, with one reminder before that.
• Saved statement passwords: kept only if you tick Remember when you enter one, so the next statement from that bank opens by itself. Each is encrypted with a key held apart from our database and its backups, is used only on our servers to open your own statements, and is never shown to you, our staff or anyone else again. You can remove one under Settings at any time, and all of them go when you delete your account.
• Duplicate check: for a year we keep the file name and a fingerprint of each statement you forward, so the same one is not imported twice. A fingerprint cannot be turned back into the statement.
• Waitlist: kept until you leave the list, which you can do yourself from your waitlist page at any time, and deleted then. The whole list is deleted once the waitlist has closed and its last invites have gone out. A seat number, the discount and any friend rewards belong to your account, and are kept and deleted with it.
• Legal hold: data may be retained longer where required for legal compliance.

6. Your Data Rights

As a UK company, we are bound by the UK GDPR, and we apply the EU GDPR to people in the European Union. We give everyone the same rights, wherever they live. If the law where you live gives you more, you have those too. You can ask us for the following:

6.1 Your rights

• Access: request a copy of your personal data.
• Rectification: correct inaccurate information.
• Erasure: request deletion of your data.
• Portability: download your transactions and your net worth history as a spreadsheet from your settings, or ask us for a copy of anything else we hold.
• Restriction & objection: limit or object to certain processing.
• Withdraw consent: take back anything you agreed to, such as analytics cookies, push notifications or your place on the waitlist, at any time.

We do not sell your personal data, and using any of these rights never costs you anything or changes the service you get.

To exercise any of these, email us at privacy@mintvalt.com with "Data Request" in the subject line. We will reply within one month.

6.2 Making a complaint

If you are unhappy with how we have handled your data, please tell us first and we will try to put it right. You also have the right to complain to a data protection authority: in the UK, the Information Commissioner's Office (ico.org.uk), in the European Union, the authority in the country where you live, and elsewhere, the data protection authority where you live, if there is one.

7. Security

• Encryption in transit: all connections use TLS 1.2+, served over HTTPS with HSTS.
• Encrypted backups: database backups are encrypted before they leave the server, and stored separately from it.
• Scoped access: every request is scoped to your account, so your data is isolated from other users.
• Protected secrets: API keys and secrets are kept in environment configuration, separate from application code.
• No bank credentials: since we never store bank logins, there's no such credential to breach. Statement passwords you choose to save are encrypted with a separate key that is not stored with the database.

No system is ever 100% secure, but we take protecting your data seriously and will notify affected users promptly if we become aware of a breach that puts their data at risk.

8. International Data Transfers

Your data is stored on our servers in Amsterdam, in the Netherlands. Omvion Ltd is a UK company, and our team works from Sri Lanka, so the people who run MintValt access it from there to provide support and keep the service running. That access stays within our own company, under the limits set out in sections 4 and 7.

The providers named in section 4 operate in other countries, including the United States and the European Union. Each is bound by a data processing agreement with us that incorporates the Standard Contractual Clauses published by the European Commission and, for people in the UK, the UK International Data Transfer Addendum. Those are the safeguards the law provides for transfers to a country without an adequacy decision. Providers may process your data only on our instructions and only to provide the service they are there for.

Accepting our Terms of Service when you create an account is your agreement to the contract, not a substitute for that safeguard. Wherever you are, if you want to know what applies to a particular transfer, ask us at privacy@mintvalt.com and we will tell you.

9. Third-Party Links

Our Service may link to third-party websites and services. We are not responsible for their privacy practices, so we recommend reviewing their policies before sharing information.

10. Children's Privacy

The Service is not intended for anyone under 18, which is the minimum age set out in our Terms of Service. We do not knowingly collect information from children, and will delete it if we become aware of it.

11. Cookies & Tracking

• Sign-in uses no cookie: your session is a token your browser or phone holds and sends with each request. There is nothing to clear from your cookie settings to sign out, and no session cookie exists to be stolen from one.
• Analytics cookies: set by Google Analytics on the public pages of mintvalt.com, and only after you accept them. Nothing is set before you answer, declining costs you nothing because no page here needs them to work, and the app does not set them at all. You can change your answer at any time from Cookie choices at the foot of this page.
• Do Not Track: we do not act on Do Not Track or Global Privacy Control signals. Browsers send them inconsistently and no agreed standard says what honouring them means, so rather than claim a behaviour we have not built, we would rather point at the ones that do work: decline the banner, change your answer later under Cookie choices at the foot of this page, or block the cookies in your browser.

You can change your answer at any time from Cookie choices at the foot of this page, or manage cookies through your browser settings. Nothing on the marketing site depends on them, and the app itself does not use cookies.

12. Changes to This Policy

We may update this Privacy Policy to reflect changes in our practices or applicable laws. We'll note material changes here and update the date above. Continued use of the Service means you accept the updated policy.