Privacy & Security

Bank Connections vs. CSV Imports: What You Share

"Connect your bank" can describe several different technologies. A modern bank-authorized OAuth flow can issue a limited token without showing the budgeting app your password. Older or unsupported connections may use credential-based screen scraping. CSV import avoids an ongoing bank connection altogether. Here is how to tell the difference.

Scope
Review what a connection can reach and how long access lasts

A connection may rely on a bank-issued OAuth token, an aggregator token, or credentials used for screen scraping. Each method exposes different information and permissions.

Any service that receives credentials, tokens, or detailed financial records has a security responsibility. Risk depends on what is stored, how it is protected, and whether access can be limited and revoked.

Budget without handing over your bank login

Free for 30 days. No credit card. No bank connection required.

Start My Free Scan

What "Connect Your Bank" Actually Means

A connection may be direct bank OAuth, a bank-approved API, an aggregator token, or credential-based screen scraping. The sign-in experience matters: a redirect to your bank's own domain is different from entering a bank password directly into a budgeting app or aggregator form.

In credential-based screen scraping, a third party uses stored or relayed credentials to retrieve data from online banking. In OAuth-based access, the bank issues a scoped token instead. Aggregators may support different connection methods for different institutions, so review the consent screen and the provider's current documentation for your specific bank.

Check the actual terms: Banks distinguish between bank-authorized connections and sharing credentials directly with an unapproved third party. Review your institution's current account agreement, connected-app settings, and fraud policy before authorizing access.

Three Levels of Bank Access — and What Each One Can See

Not all "bank connections" are the same. The method the app uses determines what it can access, how long it retains that access, and how much risk you assume. These are the three levels:

Credential Scraping
  • Your full login username
  • Your bank password (stored)
  • All account balances
  • Full transaction history
  • Account and routing numbers
  • Payee details on every transfer
Read-Only OAuth Token
  • Balances (read-only)
  • Recent transaction data
  • Account identifiers
  • No password stored
  • Bank can revoke access
  • Token still held by third party
CSV / Manual Entry
  • Only what you choose to share
  • No bank credentials shared with the budgeting tool
  • No live bank connection
  • You control the data
  • Works where a supported CSV export is available
  • No third-party intermediary

What "Read-Only" Does and Does Not Mean

In a bank-authorized OAuth flow, the budgeting app does not receive your password. The bank issues a scoped token granting the approved access. A token may remain usable until it expires or is revoked, depending on the bank and authorization.

This generally reduces credential risk, but the connection and synced financial data still require protection. A compromise could expose data or tokens depending on the provider's controls, token scope, and the bank's safeguards. Review what accounts and fields you are authorizing and how to revoke access.

The financial-data ecosystem continues moving toward bank-authorized APIs, but implementation and regulatory requirements change over time. Use your bank's current guidance rather than assuming every connection uses the same technology.

Compare the Three Access Methods

The table below summarizes the key differences between the three methods, including what each one requires you to hand over and what can go wrong.

Credential Scraping OAuth Token CSV / Manual
What you hand over Your full bank username and password A bank-issued token (no password) Nothing — you export and upload yourself
Credential exposure risk Higher — bank credentials are handled by a third party Lower — no password is shared, but a scoped token is stored No connection exposure — no bank credentials or tokens are shared with the tool
Bank ToS compliance Check the bank's credential-sharing terms Typically bank-authorized; confirm the consent screen Uses your institution's standard export feature
Fraud protection impact May affect a claim depending on your agreement and facts Governed by the bank's authorization and fraud terms No connection-specific authorization is created
Revocable by you Change the password and revoke access where available Yes — revoke via your bank's connected apps page Not applicable — nothing to revoke

Check Your Current Exposure

Use the checker below to assess how many apps currently have access to your bank accounts, and what type of access each has been granted.

Credential Exposure Self-Check

Check every type of bank access you have currently granted. Your exposure level updates automatically.

Low exposure. You are following good credential hygiene. Consider completing the remaining items if any are not yet addressed.
Moderate exposure. You have some open risk areas. Review connected apps in your bank's security settings and enable two-factor authentication if it is not already on.
High exposure. Multiple risk factors are currently active. Change your bank password, revoke all connected app access via your bank's security settings, enable 2FA, and switch to a budgeting method that does not require credential sharing.

What to Do If You Already Shared Your Credentials

If you have given a budgeting app your banking login username and password at any point, these are the steps to take in order:

1
Change your bank account password immediately

Log into your bank's website directly (not through any app) and change your password. Use a password you have not used anywhere else. A password manager makes this practical.

2
Revoke all third-party app access in your bank's settings

Look under Security, Privacy, Data Sharing, or Linked Accounts in your online banking settings. Revoke every connection you do not actively need, and confirm that it disappears from the bank's authorized-app list.

3
Enable two-factor authentication on your bank account

Multi-factor authentication can block many password-only login attempts. Prefer an authenticator app or security key when your institution offers one, and keep recovery methods current.

4
Switch to a budgeting method that does not require credential sharing

Export a CSV or PDF of your statement from your bank and use a tool that does not require a live bank connection. Review how that tool transmits, stores, and protects the imported data.

Frequently Asked Questions

Is it safe to give a budgeting app my bank login?

Avoid typing bank credentials directly into a budgeting tool unless you understand who receives them, why they are needed, and what your bank permits. Prefer a bank-hosted OAuth consent flow or a CSV/manual workflow. Review your bank's current agreement and the provider's security documentation.

What is screen scraping in banking apps?

Screen scraping is a technique where a third-party application stores your bank login credentials and uses them to log into your bank's website automatically, then reads (or "scrapes") the resulting page content to extract your transaction data. From your bank's perspective, these logins appear as if you are logging in yourself. This is distinct from bank-sanctioned API access, where your bank controls and audits which data is shared.

What is the difference between Plaid and screen scraping?

Aggregators can support different connection methods for different institutions. In a bank-hosted OAuth flow, the bank issues a token and the budgeting app does not receive your password. Other connection flows may work differently. Check the consent screen, your bank's connected-app settings, and the aggregator's current documentation.

Can a budgeting app move money out of my account?

A properly scoped read-only token should not authorize transfers. Credential-based connections are less clear because capabilities depend on the bank's controls, MFA requirements, and the provider's implementation. Never infer permissions from the phrase "bank connection" alone; read the consent screen and verify the connection in your bank settings.

How do I see which apps are connected to my bank account?

Log into your bank's website and look for a section called Connected Apps, Linked Accounts, Third-Party Access, or Data Sharing under Settings, Security, or Privacy. Where supported, review and revoke individual connections there. If your bank does not show this information, contact its customer-service team and ask how to review authorized third-party access.

Are bank connections becoming safer?

Bank-authorized APIs can reduce reliance on credential-based screen scraping and give people clearer consent and revocation controls. Availability differs by institution, and consumer-data rules and legal timelines can change. Check current guidance from your bank and the CFPB when evaluating a connection.

Budget Without Giving Anyone Your Password

Liberty Budget works from data you choose to share. The manual/CSV trial needs no bank connection. Automatic account connections are not currently enabled; Liberty never asks you to type your bank password into Liberty Budget.

Start My Free Scan

Sources: Consumer Financial Protection Bureau, Personal Financial Data Rights Final Rule (Dodd-Frank Section 1033) (2024); American Bankers Association, "Bank Customer Guide to Third-Party Data Sharing" (2022); Plaid, Inc., "How Plaid Handles Your Financial Data" developer documentation (2024); U.S. Office of the Comptroller of the Currency, "Third-Party Relationships: Risk Management Guidance" (2023); National Institute of Standards and Technology (NIST), "Digital Identity Guidelines" SP 800-63B (2022).