Why CSV Import Beats Open Banking for Privacy-Conscious Couples

The Open Banking promise

Open Banking launched in the UK in 2018 with a compelling pitch: connect your bank accounts to third-party apps via secure APIs, and those apps can read your transaction data automatically. No CSV exports, no manual steps. It sounds ideal for a budgeting app.

So why does JoinFunds not use it? And why might CSV import actually be the better choice for couples managing a household budget -- especially if you have accounts in multiple countries?

CSV import vs Open Banking: the head-to-head comparison

Before diving into the details, here is how the two approaches compare on the things that matter most to couples:

For a couple with straightforward UK-only finances and no privacy concerns, Open Banking is fine. For couples who value data control, have international accounts, or want granular privacy between partners, CSV import wins on every metric except initial convenience.

The privacy trade-offs most apps gloss over

Open Banking is undeniably convenient. But convenience comes with trade-offs that are rarely discussed clearly -- and they matter more when two people's financial data is involved.

Persistent access to your account

When you grant Open Banking access, you are giving a third-party company ongoing permission to read your bank transactions. Most connections refresh automatically every 90 days via re-consent, but during that window the provider can pull your data at any time. You are trusting not just the app, but its infrastructure, employees, and any future acquirer of the company.

For couples, this means both partners are trusting the same third party with their individual financial data. If one partner is uncomfortable with this, the whole system breaks down.

Third-party data storage

With Open Banking, your raw transaction data flows from your bank to the app's servers. Once there, it is subject to that company's data retention policies, security practices, and potential breach exposure. Even with strong encryption, your data is now in two places instead of one.

Data aggregation risk

Open Banking providers often aggregate data across thousands of users. This aggregated dataset becomes valuable -- and therefore a target. A breach at an aggregator exposes far more sensitive data than a breach at any individual user level.

Scope creep

Today you consent to read-only transaction access. But Open Banking also supports payment initiation, and the scope of permissions can expand over time. The regulatory framework is evolving, and what you consent to today may look different in two years.

The international gap

For immigrant and expat couples, Open Banking has a fundamental limitation: it only works with UK-regulated banks. If you or your partner maintains accounts in Romania, Poland, Spain, or anywhere else, those accounts are invisible to Open Banking. You get a partial household picture at best. With CSV import, any bank that exports a statement works -- regardless of country or currency. Read more in our guide to managing finances as an immigrant couple.

The CSV alternative

JoinFunds takes a fundamentally different approach. Instead of connecting to your bank via API, you manually export your bank statement as a CSV file and upload it.

This sounds old-fashioned. It is, deliberately.

Your data never leaves your browser

When you upload a CSV to JoinFunds, the file is parsed entirely in your browser using client-side JavaScript. The raw CSV content is never sent to our servers. Only the parsed, structured transaction data (date, description, amount, category) is saved to your encrypted database.

This means:

• No raw bank files on our servers -- we could not leak what we do not store
• No API tokens to steal -- there are no bank credentials or OAuth tokens in our system
• No third-party aggregator -- your data flows directly from your browser to your encrypted database

You control what gets imported

With Open Banking, every transaction is pulled automatically. With CSV import, you choose exactly which date range and which accounts to include. Want to keep a personal credit card out of the household budget? Simply do not import it.

For couples, this is particularly valuable. Each partner decides independently what to share with the household budget. JoinFunds provides three account visibility levels -- Shared, Balance Only, and Private -- giving each person granular control. Our account visibility guide explains how privacy controls work within your household.

No ongoing connection to manage

Open Banking connections break. Banks revoke tokens, APIs change, and re-consent flows interrupt your workflow. With CSV import, there is nothing to maintain. Your bank's online banking portal is the only system involved, and it will always be there.

Works across borders

If you or your partner have accounts outside the UK -- a common situation for expat and immigrant couples -- CSV import is the only approach that works. Export from your Romanian bank, your Spanish bank, or your Revolut multi-currency account, and import them all into one household view with automatic currency conversion.

What we do store (and how we protect it)

Transparency matters. Here is exactly what JoinFunds stores:

• Parsed transaction data -- date, description, amount, currency, category, and account reference
• User account data -- email address and household membership
• Budget and review data -- budget targets, review status, comments, and flags

All data is stored in a Supabase database hosted in the EU (AWS eu-west-2, London region). Data is encrypted at rest and in transit. Row-level security ensures each household can only access its own data.

We are fully compliant with UK GDPR (Data Use and Access Act 2025). You can export all your data as JSON at any time, and you can request complete account deletion from Settings with a 30-day grace period.

The honest trade-off

The trade-off with CSV imports is convenience. You need to log in to your bank, export a file, and upload it. This takes about two minutes per account, typically once a month. For a couple with three accounts each, that is roughly 10 minutes of exports per month.

We believe this is a reasonable trade-off for the privacy, control, and international coverage you gain. And with JoinFunds' auto-detection for 12 UK banks, the import process is as streamlined as a manual approach can be -- your bank format is recognised automatically, columns are mapped, and transactions are categorised using 60+ built-in rules.

Who is this approach right for?

The privacy-first CSV approach is ideal if you:

• Value data sovereignty -- you want to know exactly where your financial data lives
• Distrust third-party connections -- you prefer not to grant ongoing API access to your bank
• Want household-level budgeting -- you and your partner can budget together without a joint account, each importing your own statements
• Have accounts in multiple countries -- expat and immigrant couples need a tool that works beyond UK borders
• Care about security -- fewer connections mean fewer attack surfaces

If real-time transaction syncing is essential to your workflow, Open Banking apps may suit you better. But if you are comfortable with a monthly import rhythm and want maximum privacy, JoinFunds is built for you.

Getting started

Ready to try the privacy-first approach?

1. Export your bank statement as CSV
2. Create your free JoinFunds account
3. Import and categorise your transactions
4. Set up your household budget in under ten minutes

Your financial data stays in your hands. That is the way it should be.