wallet, money, banknotes, euros, in cash. How to revoke finance app data access
Photo by Puurchantal on Pixabay

Guides

Part of Open banking guide: consent, APIs, aggregators, permissions, and data flows

How to revoke finance app data access

Map each connection, revoke finance app data access at the app and bank, request deletion separately, and keep proof of the result.

This is an editorial pen name used by the publication, not a claim of an independently verified personal identity. Original editorial credit: Guides Desk.

What to take away

  • Deleting the app icon leaves the server-side token live, so the connection keeps pulling balances.
  • One app can sit behind an aggregator, and the bank's dashboard will name the aggregator, not the app.
  • Revocation stops future access; deletion covers copies already held. They are two separate requests.
  • Pull the current terms and permission screen before you disconnect, because the app may rewrite them afterward.
  • Verify against the next refresh cycle, then keep the confirmation text, case number and timestamps.

To revoke finance app data access, start with the connection, not the app icon. Removing an app icon is not revocation. A connection can survive on a server-side token, an aggregator, or stored credentials long after the software leaves your phone.

This applies to budgeting tools, portfolio dashboards, tax services, payment apps and lending tools. Anything that reads a financial account has a connection worth mapping.

Names you may encounter include Plaid, Yodlee, Finicity, MX, and Akoya. As a worked example, if your YNAB connection screen identifies Plaid, record YNAB as the app and Plaid as the aggregator; verify the provider in your own settings rather than assuming. Empower, Copilot, and Rocket Money are other finance apps whose connection details you should check individually. If Plaid is named, Plaid Portal is an additional route to view participating apps and manage eligible connections; search Plaid's official site for its consumer portal.

Build a connection inventory

Open a table with one row per app-to-account relationship. Fill what you know and mark the rest unknown.

Connection inventory fields

  • Visible app or service
  • App account email
  • Financial institution
  • Connected account
  • Aggregator, if named
  • Connection method
  • First authorization date

Field / Entry

Visible app or service
App account email
Financial institution
Connected account
Aggregator, if named
Connection method
API, redirected bank login, credentials, file import, unknown
First authorization date
Last successful refresh
Data categories
Payment authority
Yes, no, or unclear

Never put a full password, access token, account number or recovery code in this table. Store it somewhere you control, not in a shared note.

Find both connection views

Inside the app, look under settings for connected accounts, linked institutions, data permissions, integrations or security. Then sign in to the financial institution through an address you typed yourself and look for connected apps, authorized services, shared access or third parties.

Two connection views compared

App view

Where to look
Settings menus
Menu names
Connected accounts
What it names
The app you see
Typical mismatch
Display name
Action
Record name

Bank view

Where to look
Typed bank address
Menu names
Connected apps
What it names
The aggregator
Typical mismatch
Auth entity
Action
Record name

The two lists often disagree. The bank sees the aggregator that authenticates you; you recognize the app that displays the numbers. Record both names rather than treating the mismatch as an error.

Examples of institutions to check include Chase, Capital One, Wells Fargo, Bank of America, and Schwab. On each institution's official site, search settings for terms such as connected apps, third-party access, linked services, or data sharing; Schwab's route is described around third-party app access. Labels and available controls vary, so match the aggregator and account details rather than relying on the app name alone.

Read what you actually authorized

Pull the current terms, permission screen and privacy notice. Then work through the questions below and write the answers next to each connection.

For each connection, note the data categories it can access, whether access is read-only or can initiate actions, how often data is retrieved, the stated purpose, any named third parties, how long authorization lasts, and the steps for revocation and deletion. Record what the screen actually says; do not assume every permission applies to every account.

What you authorized

  • Which accounts are included?
  • Which fields can be read?
  • One-time or ongoing access?
  • How often can it refresh?
  • Can it initiate payments?
  • Can it share data?
  • How long does it retain data?

The 12 CFR 1033.331 revocation provision describes a data provider offering a reasonable method to revoke a third party's access to covered data. It then requires timely revocation and notice to the third party.

Compliance dates for that rule sit under a court stay, so treat the text as a design principle, not a live deadline. It still explains why provider-side control matters next to an app-side button.

The Consumer Financial Protection Bureau (CFPB) issued the Personal Financial Data Rights rule, codified in 12 CFR part 1033. The court stay means the rule's compliance dates are not a dependable timetable for an individual revocation or deletion request.

Identify the connection method

Redirected authentication or API authorization

The app sends you to an institution-controlled sign-in page. The institution returns a token with defined access. You never type your bank password into the app's own form.

Which connection method

Did you type your bank password into the app's own form?

Yes

Credential-based retrieval

No

Redirected authentication or API

Credential-based retrieval

The app or aggregator holds your credentials and signs in as you to collect data. Multifactor prompts, password changes or redesigned pages can interrupt it.

File import

You download a statement or transaction file and upload it. There may be no continuing bank connection, but the imported copy stays with the app.

Unknown

Do not guess. Ask the app and the institution which entity authenticates the user, who stores credentials or tokens, and how future access ends.

Export evidence before you change anything

  • Save the app's connection and permission screens, the institution's connected-app listing, and the relevant terms and privacy notice.
  • Record the app, aggregator, institution, account identifier in redacted form, authorization or connection ID, and the date and time shown for access.
  • Keep support messages, case numbers, revocation confirmations, and any stated deletion or retention response.

Evidence to export first

  • Dated connected-account list
  • Authorization or consent text
  • Named aggregator
  • Accounts and scopes
  • Last refresh time
  • Support case numbers
  • Terms and privacy version

Redact secrets before sharing anything with a third party. Keep the originals in one controlled location.

Revoke inside the app

Use the disconnect, unlink or revoke control. Read the confirmation carefully, because "hide account" may remove a display tile without ending retrieval.

Record after in-app revoke

  • Date and time
  • Account disconnected
  • Control used
  • Confirmation text
  • Connection or case ID
  • Whether app keeps data

If the app only offers account closure, ask support whether closure revokes every connection and what records remain.

Revoke at the financial institution

If the institution runs a connected-app dashboard, remove the matching app or aggregator there as well. That gives you a second control and a second confirmation.

What to give bank support

  • App name
  • Aggregator
  • Accounts
  • Connection ID
  • Authorization date
  • Never a password or token

Where no dashboard exists, contact the institution through a verified support channel. Give the app name, aggregator, accounts, connection ID and authorization date. Ask for the exact action that stops future retrieval or payment initiation. Never send a password or full token to support.

If the issue remains unresolved and concerns a financial product or service within its process, submit a complaint through the CFPB complaint portal. The CFPB Consumer Complaint Database can also be searched for complaints about companies; check that the company and issue fit the CFPB process.

Handle shared credentials

If you handed credentials to the app or aggregator, change the financial-account password after revoking. Use a unique password and review multifactor and recovery settings.

A password change is defensive. It is not a substitute for killing an API token or server-side authorization.

If a breach notice names the app or aggregator, follow the institution's incident instructions and read your statements closely.

Request deletion separately

Send a specific request naming the account and app profile. Include the connected institution. List the categories of imported data. Name any derived profiles, backups or processors in scope. State your requested completion date. Say what confirmation you want back. Note any retention exception the provider claims.

Please revoke [app]'s and [aggregator]'s access to [institution and accounts] and confirm when revocation takes effect. Separately, please delete [listed data categories] associated with my [app profile or account], including applicable copies held by processors. Identify any data you will retain, the reason and retention period, and the response period that applies to this request. Please confirm when the request is complete. This request does not authorize continued access.

Revocation stops future access. Deletion concerns copies already held. A provider may keep records it says are required for legal, fraud, accounting, dispute or security purposes. Ask it to name the category and the retention period instead of promising that every byte vanishes at once.

Other rules may matter, but none creates a universal deletion right for every finance app. The Gramm-Leach-Bliley Act (GLBA) and the FTC's Safeguards Rule may apply to covered financial institutions and impose security duties; they are not a blanket consumer deletion process. The Fair Credit Reporting Act (FCRA) applies in covered consumer-reporting contexts, not automatically to every app that handles financial data. California residents may have rights under the California Consumer Privacy Act (CCPA), as amended by the California Privacy Rights Act (CPRA), and Virginia residents may have rights under the Virginia Consumer Data Protection Act (VCDPA), subject to coverage limits and exemptions. Ask the company which law and response period it says apply to your request.

Test that access stopped

Use the app's stated refresh cycle as a practical check, not as a legal deadline. Ask the app and institution to confirm the date revocation took effect, and ask the app which response period applies to the deletion request. Do not create a real transaction as a test.

A clean check reads: revocation recorded, token or connection disabled, no later successful fetch, app shows disconnected, deletion response tracked.

If a fresh balance or transaction appears, preserve the timestamp and reopen the case with both the app and the institution. It may be a cached display, so ask for the underlying fetch time.

Close the record

Write a short final note covering the entities involved, controls used, confirmations, the last successful access time, the deletion outcome and any unresolved retention.

Review remaining connections quarterly, and again whenever a device, email address or financial account changes.

Common questions

Does deleting the app stop access?

No. The server-side connection lives on the provider's systems, not your phone. Revoke it through the app and the institution wherever both controls exist.

Should I change my bank password?

Change it if you gave credentials to the app or aggregator, or if you suspect exposure. Then revoke the tokens and authorizations directly, because a new password alone may not end an existing token.

Is disconnecting the same as deleting my data?

No. Disconnecting ends future access. Deletion covers copies already collected, so send a separate request and track the response.

How do I prove revocation worked?

Keep the confirmation text, case number and timestamps, then confirm no successful retrieval happens after the recorded revocation time. If one does, escalate to both the app and the institution with the timestamp.

More in Guides

Latest from Sofia A. Turner