AI Finance Apps: What They Actually Access, and Whether It's Safe

The short answer

An AI finance app connects to your bank through a data aggregator — usually Plaid, MX, Finicity, Akoya or Yodlee — and typically receives your full transaction history, balances, account and routing numbers, and identity details. With the major US banks that now require OAuth, you sign in on your bank's own site and the app never sees your password. With smaller institutions, credential-based connections still exist, and there the aggregator does store your login.

"Read-only" is the most misleading phrase in this category. A read-only connection still discloses your account and routing number. In the US ACH system that is functionally enough to originate a debit — the thing stopping it is legal and contractual, not technical.

And here's the part almost nobody knows. Plaid's own documentation states that deleting an account from Plaid Portal "does not remove data from third-party applications or remove payment authorization." Disconnecting the data does not stop the charges. Those are two separate jobs, and most people only do the first.

The realistic risk isn't the app you chose. We found no publicly reported breach at YNAB, Monarch, Copilot, Rocket Money, Empower, Albert or Dave. Every large loss in 2025–26 happened at an infrastructure company three steps upstream — a partner bank, a lending platform, a credit-data vendor. That's the actual threat model, and it's the one these articles never describe.

What actually happens when you tap "connect your bank"

The two connection types, and why it matters which you get

OAuth. You leave the app, land on your own bank's real sign-in page, authenticate there, and get redirected back. Your bank issues a scoped token. The aggregator never sees your password. Plaid states OAuth is required for its US integrations, and lists Chase, US Bank, Wells Fargo, Bank of America, PNC, Capital One and Charles Schwab among the institutions where it's mandatory.

Credential-based. You type your bank username and password into the app's connection window. The aggregator stores those credentials and replays them to log in on your behalf. Plaid's own privacy policy lists "usernames, passwords, security tokens, and one-time passwords" among the categories it collects.

Why the difference matters practically: an OAuth token can be revoked at your bank, and the app can't restore it without you re-authenticating. A stored credential generally can't be revoked individually — the equivalent action is changing your online banking password, which invalidates it everywhere at once.

How much is OAuth now? Plaid said in September 2024 that "80% of our traffic is now on or committed to APIs." Read the hedge: on or committed to bundles banks that have signed up with banks that have actually migrated. We could not verify a 2026 figure from any primary source, so treat 80% as a dated ceiling rather than today's number.

What the app receives

Per Plaid's published policy, the categories collected include identifiers (name, email, phone, Social Security number, date of birth), financial data (account and routing numbers, balances, full transaction history, credit limits), device data (IP address, hardware, OS, browser), and derived data — inferred location, inferred annual income, account types.

That last category is worth sitting with. Your transaction history isn't just a list of purchases. It reveals where you live, where you work, your commute, your health providers, your religious donations, your relationship status, and roughly what you earn. It is one of the most revealing datasets a person can hand over, and the consent flow takes about eight seconds.

The aggregators are not interchangeable

Akoya is structurally different and it's worth knowing why. Its own documentation states it "does not copy, store, or hold any consumer financial data or login credentials. Data flows directly from the financial institution to the authorized third party." Bank-owned, no retention, revocation handled inside your bank's own app. If an app offers a choice of connection method — most don't — that's the one with the least data sitting in the middle.

(One note on MX: its marketing says credentials "never leave your organization" and it offers a consent dashboard. That describes its tokenized product tier. It isn't a statement that MX has eliminated credential-based aggregation, and we found no independent breakdown, so we're not going to characterize it either way.)

"Read-only" is a category error

Almost every article on this subject reassures you that these connections are read-only. That's true in a narrow technical sense and misleading in the sense you care about.

Plaid's Auth product — the standard one for apps that need to move money — lets a developer "request a user's checking, savings, or cash management account and routing number, making it easy for you to initiate credits or debits via ACH." Plaid's own documentation says so plainly.

Once an app has your account and routing number, the barrier to debiting your account is legal, not technical. NACHA authorization rules and Regulation E error resolution are real protections, and they work — after the fact. They are not the same thing as the app being unable to take money.

Plaid also has products that do move money directly: Transfer handles ACH, Same Day ACH, RTP, FedNow and wires in the US; Payment Initiation operates across Europe.

The useful question isn't "is this read-only?" It's: did I also agree to let this app debit my account, and how do I cancel that separately? Which brings us to the thing worth knowing above everything else on this page.

Disconnecting does not stop the charges

This is the single most actionable finding here, and it's in Plaid's own help documentation.

Disconnecting an app in Plaid Portal: "the app will no longer be able to access your data through Plaid." But — and this is Plaid's own wording — "Disconnecting an app stops future data sharing only. The app may still keep data it has already collected."

Deleting a financial account from Plaid Portal: Plaid will "remove the account data from our systems and stop sharing any new information." And then the critical sentence: "This action does not remove data from third-party applications or remove payment authorization."

Read that again if you've ever tried to stop a subscription by disconnecting it. Revoking data access does not cancel an ACH debit authorization. Someone who disconnects Plaid to stop an app charging them has stopped the data and not the money.

Stopping the data and stopping the money are two separate jobs. To stop debits you cancel the authorization with the app directly, and if that fails, you file a Regulation E unauthorized-transaction or stop-payment claim with your bank.

(A small piece of context that says something: Plaid Portal exists because a court ordered it. Creating "a portal for users to manage app-to-financial-account connections" was part of the injunctive relief in the Cottle settlement — see below. It's a genuinely useful tool and it was not a voluntary product decision.)

How to actually revoke access

Three layers. Any one alone leaves something connected.

Layer 1 — the aggregator

Plaid: sign in at my.plaid.com → Overview → select the app → Manage connections → Disconnect app → choose the institution → confirm. Separately, delete the financial account from the Portal to remove data from Plaid's own systems. If the Portal won't let you, Plaid offers a data-subject request form and a privacy address.

MX and Akoya: no consumer-facing portal of their own. Revocation runs through your bank's or the app's interface.

Finicity and Yodlee: we could not locate any consumer self-service revocation portal. Use Layer 2, or send a written privacy request.

That asymmetry is worth noting. Plaid is the most consumer-accessible of the aggregators, largely because litigation made it so.

Layer 2 — your bank (the durable one)

Most large US banks now have a third-party access page, usually under Security Center, Data sharing and privacy, Third-party access, or Linked apps.

For OAuth connections this is the layer that actually works. Because the token is issued bank-side, revoking it there genuinely kills the connection, and the app can't restore it without you signing in again. For credential-based connections, changing your online banking password is the equivalent move.

Layer 3 — the app, and separately, the authorization

Deleting your account inside the app is the only route to data the app already holds. And as above: none of these layers cancels a payment authorization. Handle that as its own task.

What FDIC insurance does and doesn't cover

This is where people lose actual money, and it has nothing to do with hacking.

The FDIC's own consumer guidance is unambiguous:

"Nonbank companies themselves are never FDIC-insured."

Funds you send to a nonbank aren't protected until that company deposits them in an insured bank and other conditions are met — chiefly that "records must be kept to identify who owns the money and the specific amount that each person owns."

And: "FDIC deposit insurance does not protect against the insolvency or bankruptcy of a nonbank company."

Synapse is the proof

In April 2024, Synapse — a middleware company most of its users had never heard of — collapsed. It sat between roughly 100 fintech apps and their partner banks, and its ledger was the only record of who owned what.

Over 100,000 people lost access to more than $265 million. The bankruptcy trustee, former FDIC Chair Jelena McWilliams, identified a shortfall of $65 million to $95 million between the ledgers and customer claims. The partner banks could not reconstruct ownership.

Yotta, a savings app, had around 85,000 customers and roughly $112 million locked up. Evolve Bank said about $109 million in Yotta customer deposits was unaccounted for. Some customers reportedly recovered cents on the dollar — one widely reported case received $0.75 against $15,000 deposited.

FDIC insurance did nothing, because no bank failed. The recordkeeping failed. Pass-through insurance is only as good as the middleware's ledger, and you cannot audit that ledger.

The practical distinction that matters

An app that reads your bank data has a data-loss risk profile. An app that holds your money through a nonbank chain has a Synapse risk profile. These are completely different, and consumers routinely conflate them.

If an app holds a balance, look for a named partner bank — "Deposits held at [Bank Name], Member FDIC." Verify that institution in the FDIC's BankFind tool. If the marketing says "FDIC insured up to $250,000" without naming a bank, that's the red flag.

What has actually gone wrong

The breaches were upstream, not at the apps

We found no publicly reported data breach at YNAB, Monarch, Copilot, Rocket Money, Empower, Albert or Dave. That's a real finding, and we'd rather report it than manufacture alarm. (No publicly reported breach as of August 2026 is not the same as never breached.)

What did get breached in 2025–26 was infrastructure:

• Figure Technology Solutions — 967,200 accounts, February 2026. Names, phone numbers, addresses, dates of birth. Cause: social engineering, part of a broader voice-phishing campaign against SSO accounts.

• 700Credit — a fintech data-services firm, at least 5.6 million people.

• FinWise — 689,000 users, via a former employee.

• Marquis — a banking-technology vendor, 672,000 in a ransomware attack.

Notice what none of those are: a consumer budgeting app. You chose the app. The breach happened three companies upstream at a vendor whose name you've never seen. That's the threat model, and it's why "is this app trustworthy" is only a third of the question.

Evolve Bank & Trust — the big one

LockBit ransomware, 2024. 7,640,112 individuals, per the Maine Attorney General filing. Intrusion February–May 2024, discovered May 29, data leaked June 26 after Evolve refused to pay. Exposed: full names, Social Security numbers, detailed bank account information, phone numbers, email addresses. No evidence customer funds were accessed.

Because Evolve was a banking-as-a-service provider, downstream fintech customers were exposed — Affirm, Wise and Mercury among them. Their users had no relationship with Evolve.

One detail worth knowing: LockBit initially advertised the theft as a Federal Reserve breach with "33 terabytes of sensitive banking data." That was false — the data was Evolve's — and several outlets ran the Fed claim before it was corrected. Attackers lie about scope, and early breach reporting is often wrong.

Separately, in June 2024 the Federal Reserve issued a cease and desist against Evolve — not about the breach, but finding "unsafe and unsound banking practices" in how it managed its fintech partnerships. A class settlement of roughly $11.8 million was filed in April 2025.

Plaid: what's true, and what's overstated

Cottle v. Plaid — $58 million, final approval July 2022. The allegation was that Plaid "designed login screens in its interface to look like screens used by individual financial institutions, but failed to disclose to users that they were not interfacing with their bank," and over-collected as a result. The class was around 98 million people; individual payouts were roughly $13.50.

Be precise about this one, because most articles aren't. Headlines described it as a settlement "for selling consumer data." Plaid denied ever selling or harvesting data, and the settlement was about deceptive interface design and over-collection, not a proven sale. The injunctive relief — data deletion, collection minimization, new disclosures, and the consumer portal — is arguably the more consequential outcome.

A 2026 incident, reported honestly. Plaid began notifying affected individuals on April 27, 2026, with filings to the Maine Attorney General and New Hampshire Department of Justice in May. The cause was phone-number recycling: when a carrier reassigned a previously used number to a new subscriber, Plaid's system in a small number of cases treated the new holder as the previous owner of an existing connection. Data categories included name, date of birth, address, driver's license number, Social Security number, bank name and account number. Online banking credentials were not compromised. The reported window runs December 25, 2024 to April 22, 2026.

Now the caveats, because they matter. Plaid described the scope only as "a very small number of connections" and published no figure; one report indicates the Maine filing covered roughly four residents. There has been no mainstream press coverage, and the secondary sources are largely plaintiff-side law firm pages. Plaid's own developer changelog shows it added "phone number recycling detection to Link" in January 2025, which sits oddly against a window extending to April 2026 — either the fix was partial or one of the reported dates is off.

We're including it because it's real and it illustrates something systemic — identity tied to a recycled phone number is a genuine failure mode across the industry — not because it's a mass breach. It isn't.

And one claim to kill: we found at least one article referencing a "2024 FTC settlement" involving Rocket Money's parent, then operating as Truebill. We could find no such FTC action. Don't repeat it.

Your legal rights, which are thinner than you'd expect

There is currently no enforceable federal right to your own financial data

The CFPB finalized its Personal Financial Data Rights rule (Section 1033) in October 2024. It would have given you the right to access your data and direct your bank to share it.

A federal judge in the Eastern District of Kentucky preliminarily enjoined it on October 29, 2025, finding the plaintiffs likely to succeed on all four claims including that the rule exceeded the CFPB's authority. The CFPB had by then switched sides and asked the court to set aside its own rule. A revised proposal went to White House review around August 6, 2026.

The rule is enjoined, not vacated — it sits in the Code of Federal Regulations and is unenforceable. What that means for you right now:

• No enforceable federal right to get your data from your bank in a portable format

• No enforceable federal right to direct your bank to share it with an app

• No enforceable federal ban on banks charging for that access

• No enforceable federal limit on what a third party does with it afterwards

Watch the fee question. The revised rule is expected to permit data-access fees rather than ban them. JPMorgan and Plaid signed a paid data-access deal in September 2025. If banks can charge aggregators for your data, that cost lands somewhere — your subscription price, or pressure to monetize the data itself.

GLBA protects the company's obligations, not your rights

The Gramm-Leach-Bliley Act does apply to fintech apps and aggregators — the FTC reads "financial institution" broadly, and a Treasury report classified data aggregators and consumer fintech providers as covered. It requires a written information security program, risk assessment, encryption, MFA, vendor oversight and incident response.

But GLBA gives you disclosure and a narrow opt-out. No access right. No correction right. No deletion right. It's a company-obligation statute, not a consumer-rights statute, and articles conflate the two constantly.

Your state decides whether you have any rights at all

This is the part that genuinely surprises people.

California's exemption is data-level. Only data actually subject to GLBA is exempt, so everything outside that scope — behavioral analytics, device data, marketing profiles, inferences — is fully covered by CCPA/CPRA, with rights to access, delete, correct and opt out.

Virginia, Colorado, Utah, Connecticut and Nevada use an entity-level exemption. The entire GLBA-regulated company is exempt, which means residents get no state privacy rights against it at all.

Same company, same data, opposite outcomes depending on your ZIP code. A Californian can demand deletion of a budgeting app's non-GLBA data. A Virginian generally cannot demand anything.

One protection survives everywhere in California: the private right of action for data breaches, with statutory damages of $100 to $750 per consumer per incident, is not blocked by the GLBA exemption.

Breach notification goes to the regulator, not to you

The FTC's amended Safeguards Rule, effective around May 2024, requires non-bank financial institutions to notify the FTC within 30 days when unencrypted information of 500 or more consumers is acquired without authorization.

It does not create a federal duty to notify you. Consumer notice comes from state breach-notification laws — which is precisely why the Plaid incident above surfaced through Maine and New Hampshire filings rather than a federal announcement.

Useful and almost never mentioned: the FTC maintains a public database of these notices. It's worth a look before you connect anything.

When you delete the app, the data usually stays

There is no general US requirement to delete it. GLBA gives no deletion right. Section 1033 would have addressed retention and is unenforceable. CCPA's deletion right reaches only non-GLBA data, and not in entity-exemption states. Everywhere else it's whatever the privacy policy promises — and privacy policies are unilaterally amendable.

Plaid's stated position is more generous than the law requires: it deletes personal information when a developer removes your connection, except where you have other active connections, or for legal compliance, fraud prevention, or where the data has been aggregated or anonymized.

That last exception swallows a great deal, and it's industry-standard. Aggregated and anonymized data is generally exempt from deletion everywhere.

Mint is the case study. Intuit announced the shutdown in November 2023 and migrated users to Credit Karma — a different product, with a different privacy policy, and a different business model built on financial-product lead generation. Users who did nothing were moved by default.

How to read a privacy policy in five minutes

Find the GLBA notice, not the website policy

GLBA-covered companies must publish a standardized notice with a table headed "Reasons we can share your personal information" and a column asking "Can you limit this sharing?" The format is federally prescribed, which makes it the one document you can compare across companies.

You can opt out of: sharing with non-affiliated third parties for non-exempt purposes — marketing firms, data licensing.

You cannot opt out of: joint marketing agreements between financial institutions, service providers under confidentiality contracts, everyday business purposes, and — the big one — sharing with affiliates, meaning companies under common ownership. If a budgeting app belongs to a large financial group, moving your transaction history to affiliates is generally not something you can block.

Search for these five phrases

The honesty test

YNAB is a good example precisely because it doesn't overclaim. It says it doesn't "under any circumstances 'sell'" your information — and then concedes that its targeted advertising "may be legally classified as 'sales' under state privacy laws," and provides an opt-out. It publishes concrete retention periods: most account data for 24 months after a subscription ends, support conversations up to 3 years, training recordings deleted after 21 days.

A policy that admits an inconvenient edge case and publishes hard numbers is more trustworthy than one that only says "we never sell your data."

Follow the money

If an app is free, shows no ads, and doesn't upsell products, something is paying for it. Subscription-only apps have a structurally cleaner incentive. Free apps monetized through financial-product referrals have every reason to profile your transactions closely.

Six red flags

1. "FDIC insured" with no named partner bank. Legitimate looks like "Deposits held at [Bank], Member FDIC."

2. The app holds your balance rather than reading your data. Different risk category entirely — see Synapse.

3. Free, no ads, no visible revenue. Someone is paying.

4. No published retention periods. Compare against YNAB's specific figures.

5. Cancellation friction. The FTC's action against Cleo centred partly on making cancellation difficult. An app that makes leaving hard has told you how it views your autonomy.

6. No named security contact or published incident history. Companies confident in their security say so specifically.

Frequently asked questions

Are AI finance apps safe to connect to my bank?

The connection itself is reasonably safe at major banks; the risks are elsewhere. With banks that require OAuth — Chase, Wells Fargo, Bank of America, Capital One, US Bank, PNC and Schwab among them — you authenticate on your bank's own site and the app never sees your password. The real risks are that the app receives your full transaction history and account details, that "read-only" access still discloses your account and routing number, and that disconnecting an app does not cancel any payment authorization you also gave it. We found no publicly reported breach at the major budgeting apps; the large 2025–26 breaches all hit infrastructure companies upstream.

What data does a budgeting app actually collect?

Considerably more than most people expect. Plaid's published policy lists identifiers (name, email, phone, Social Security number, date of birth), financial data (account and routing numbers, balances, full transaction history, credit limits), device data (IP address, hardware, browser), and derived data including inferred location and inferred annual income. Transaction history alone reveals where you live and work, your commute, your health providers, your donations and roughly what you earn. It's one of the most revealing datasets you can share, and the consent flow takes seconds.

Is Plaid safe?

Broadly yes, with two things worth knowing. Plaid uses OAuth at major US banks, so it doesn't see your credentials there; at smaller institutions credential-based connections still exist and it does store logins. Plaid settled Cottle v. Plaid for $58 million in 2022 over allegations it designed login screens resembling banks' own and over-collected data — Plaid denied selling data, and the settlement produced the consumer portal at my.plaid.com. In April 2026 Plaid notified a small number of people about a phone-number-recycling flaw; Plaid published no figure and there was no mainstream coverage, so treat it as a narrow incident rather than a mass breach.

How do I disconnect an app from my bank account?

Do three things, because any one alone is incomplete. First, revoke at the aggregator — at my.plaid.com, go to Overview, select the app, then Manage connections and Disconnect. Second, revoke at your bank, usually under Security Center or Third-party access; for OAuth connections this is the layer that genuinely kills access. Third, delete your account in the app itself, since that's the only route to data it already holds. And separately cancel any payment authorization — Plaid states plainly that deleting a connection "does not remove payment authorization."

Are AI finance apps FDIC insured?

The apps themselves never are. The FDIC states directly that "nonbank companies themselves are never FDIC-insured" and that deposit insurance "does not protect against the insolvency or bankruptcy of a nonbank company." Pass-through coverage requires the money to reach an insured bank and for records to accurately identify who owns what. When Synapse collapsed in 2024, over 100,000 people lost access to more than $265 million with a $65–95 million ledger shortfall — and FDIC insurance was irrelevant because no bank failed. Look for a named partner bank and check it in the FDIC's BankFind tool.

Can a budgeting app take money from my account?

Not through data access alone — but the practical protection is legal, not technical. A standard connection discloses your account and routing number, which in the US ACH system is functionally enough to originate a debit. What stops it is NACHA authorization rules and Regulation E, which work after the fact. Many apps also ask you to authorize debits separately at signup, buried in the terms. That authorization survives disconnecting the data connection, so if you're trying to stop charges, cancel it with the app directly and file a Regulation E claim with your bank if that fails.

Do budgeting apps sell my data?

Most say they don't sell personal information, and most do monetize aggregated or de-identified data. Those aren't contradictory — "aggregated," "de-identified" and "anonymized" data generally falls outside legal definitions of a sale, and outside deletion rights. Check the app's GLBA notice, which uses a federally prescribed table format that makes companies comparable. Note that sharing with affiliates — companies under common ownership — is generally not something you can opt out of under GLBA, so ownership matters.

What rights do I have over my financial data?

Fewer than you'd expect, and it depends heavily on your state. There is currently no enforceable federal right to obtain or port your financial data — the CFPB's Section 1033 rule was preliminarily enjoined in October 2025 and is being rewritten. GLBA imposes security obligations on companies but grants you no access, correction or deletion right. California's exemption is data-level, so Californians retain CCPA rights over everything outside GLBA scope. Virginia, Colorado, Utah, Connecticut and Nevada use entity-level exemptions, which means residents get no state privacy rights against a GLBA-covered fintech at all.

The bottom line

The connection is probably fine. The consent is the part to think about. At major banks, OAuth means the app never sees your password. What it does see is your entire financial life, including inferences you never volunteered.

Stopping the data and stopping the money are different jobs. Disconnecting an app does not cancel a payment authorization. That single fact is worth more than everything else on this page.

If an app holds your balance, ask which bank. Synapse cost more than 100,000 people access to $265 million without a single bank failing.

Read the GLBA notice, not the marketing. It's the one document with a federally mandated format, which makes it comparable across companies — and the affiliate row is the one to look at.

And know that your rights depend on your ZIP code, which is an unsatisfying answer and the true one until Section 1033 is resolved.

Vera connects through Plaid, doesn't sell your data, doesn't run ads, and lets you delete your data at any time. We're a data-reading app, not a balance-holding one, so the Synapse risk profile described above doesn't apply to us — but everything on this page about consent, retention and state-by-state rights applies to Vera exactly as it does to everyone else. Our privacy policy is the place to check us against the five phrases above.

This article is for general information and is not legal or financial advice. Regulations, company policies and incident details change — verify current terms with each provider. Where we could not confirm something from a primary source, we say so. Breach and enforcement details reflect public reporting as of August 2026.

Last verified: August 2026.

Sources

Connection mechanics: Plaid legal and privacy · Plaid OAuth docs · Plaid Auth docs · Plaid payments docs · Plaid — disconnecting an app · Plaid — deleting accounts from Portal · Akoya data sharing · MX data access

Incidents: Cottle v. Plaid coverage · Evolve breach — 7.6M · Evolve settlement · Federal Reserve C&D on Evolve · Figure breach · Synapse collapse · Yotta deposits

Regulation: FDIC — banking with third-party apps · CFPB 1033 reconsideration · 1033 injunction coverage · FTC Safeguards breach notification · GLBA and fintech · State GLBA exemptions · YNAB privacy policy