---
title: "Apps you install"
description: "What a third-party app is, what installing one lets it see, where your data goes, and how to remove it — keeping your tables and cutting its access straight away."
section: "Integrations"
canonical: "https://banksync.io/docs/integrations/apps"
specs: ["apps"]
operationBindings: [{"capability":"apps","operation":"apps.directory.list"},{"capability":"apps","operation":"apps.listing.get"},{"capability":"apps","operation":"apps.install.approve"},{"capability":"apps","operation":"apps.install.get"},{"capability":"apps","operation":"apps.install.remove"},{"capability":"apps","operation":"apps.install.revoke-all"},{"capability":"apps","operation":"apps.grants.list"},{"capability":"apps","operation":"apps.grants.revoke"},{"capability":"apps","operation":"apps.integrations.list"}]
---

An **app** is somebody else's product that you connect to your BankSync workspace: a tax filing tool, a bookkeeping assistant, a reporting product. You install it once, it reads the bank data you chose to give it, and it can add tables, feeds and dashboards to your workspace. Apps sit alongside your other outbound connections — Google Sheets, Notion, webhooks — on the **Integrations** tab, because they answer the same question: who touches my data?

An app is a guest. Your workspace owns every bank, table and feed before the app arrives and after it leaves.

> **Apps are still being built:** 'You can install an app, it can read the bank data you approved, and the tables and feeds it declared are now created in your workspace when you install it and removed again when you remove it. The parts still landing are the dashboards an app ships, and one step of the removal — see "Cut an app\u2019s access" below. This page marks which is which.'

> **Before you start:** 'You need the Owner or Admin role to install or remove an app, because installing one grants access to bank data. Editors and viewers see installed apps on the Integrations tab but cannot add or remove them. In a client portal, only the parent workspace owner or admin can install.'

## How you get there

Most people never start at BankSync. You are inside the app — say a tax product — you tap its "connect your bank" button, and it sends you to a BankSync page that shows who is asking and for what. That is the [connect link](/docs/apps/connect-link). You sign in or sign up, pick your bank, approve the install, and the app sends you back where you came from.

Only a workspace **Owner** or **Admin** can approve. If you reach the approval screen and cannot complete it, that is why.

## What you are agreeing to

The install screen is derived from what the app declared — the developer cannot write the sentence that describes what they will take. It shows four things.

| On the screen          | What it means                                                                                               |
| ---------------------- | ----------------------------------------------------------------------------------------------------------- |
| **Reads**              | The scopes the app requested — transactions, balances, holdings and so on. It can read nothing else.        |
| **Which banks**        | The accounts you tick during the flow. The app's reads are limited to them at the point the data is served. |
| **Sends**              | What actually leaves BankSync and to whom, if anything. An app that only reads shows nothing here.          |
| **Your email address** | A separate, explicit tick. Leave it unticked and the developer never sees your email address.               |

> **Installing an app is a disclosure:** When an app receives data, that data leaves BankSync and is governed by the app's own privacy policy rather than by BankSync's. The install screen links to that policy and to the app's terms. Read them before you tick the box — this is the same warning you get before sending Australian CDR data to a spreadsheet.

## What the app can and cannot see

An app sees the data you approved, through the same public API any developer uses. Concretely:

- **It can see** — The data types in its scopes, from the accounts you ticked, for the history depth it declared —
  plus anything you later ask it to receive through a feed.
- **It cannot see** — Accounts you did not tick. Data types outside its scopes. Anything in another workspace. Your
  bank login credentials — those never leave the bank's own screens.
- **The developer sees** — Their own identifier for you, how many banks are connected, a health state, when the app last
  used its access — and your email address only if you ticked the box.
- **The developer never sees** — Your workspace id, your workspace name, which bank you connected, or any account identity. A
  count, never a list.

> **Bank consent screens never name the app:** 'When you connect a bank during an app install, the bank and the open-banking provider name BankSync, not the app. That is deliberate: the app is not the party holding the provider relationship, and presenting it as one would misstate who your bank is dealing with.'

## What an app adds to your workspace

An app can contribute two kinds of thing, both of which belong to you:

- **Tables** — datasets it declared, created inside your workspace. They carry the app's badge so you can tell where they came from, and they show up on your Tables tab like any other table.
- **Feeds** — pipelines that move data from the bank you connected into one of those tables, or out to the app. They appear on your feeds list with the same badge, and can carry enrichment steps the app shipped with them.

## Seeing what leaves BankSync, and where

The **Integrations** tab lists every outbound connection your workspace has in one list — destinations, installed apps, connected AI tools such as Claude or ChatGPT, and any private client you minted yourself. Each card carries a kind badge and a plain-language line: what the connection reads, what it sends, to whom, and when it last did so.

Open an app's card for the full picture: what it added here (each item links into its own tab), what it can see, what leaves and where it goes, its verification badge, and the **Remove** button.

> **Verified vs unverified:** 'A verified app has been through BankSync review: its identity, links and declared data usage were checked. An unverified app can still be installed by link, but it is capped at ten active installs, it never appears in the directory, and the install screen warns you and asks you to confirm you trust it.'

## Cut an app's access

The fastest way to stop an app reading your data is **Disconnect**, from your connected apps list. It revokes the app's access straight away: every BankSync server checks the revocation list on every request, so the app's tokens stop working within moments rather than whenever they would otherwise have expired.

Removing the app (below) is the tidier action — it also clears the app out of your workspace — but if what you want is "stop this now", disconnect.

## Remove an app

**Remove an installed app**

1. **Open the Integrations tab** — From your workspace, open Integrations and click the app's card.
2. **Click Remove** — The removal dialog explains what is about to happen and lists what the app created here.
3. **Decide about the app's tables** — Keep my tables is the default. Tick Also delete the app's tables only if you want that
   data gone — the tables hold your financial data, and deleting them cannot be undone.
4. **Confirm** — The app's access is revoked, its feeds stop, its widgets disappear, and the card leaves your
   Integrations list.

What removal does, precisely:

| Thing                            | What happens                                                                                                                                   |
| -------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
| The app's grants                 | Detached from the install, so the app no longer counts as connected here.                                                                      |
| The app's feeds                  | Paused, then deleted. Nothing of the app's keeps running.                                                                                      |
| The app's enrichment steps       | Deleted with the feeds they belonged to.                                                                                                       |
| The app's tables                 | **Kept by default.** They stay in your workspace, keep their data, and stop carrying the app's badge — they are simply your tables now.        |
| Your own rules that watched them | Repaired. A rule of yours that pointed at one of the app's feeds stops pointing at it, and is switched off if that leaves it watching nothing. |
| Your own tables, feeds and banks | Untouched. Removing an app never removes anything the app did not create.                                                                      |
| Your email at the developer      | No longer shown to them.                                                                                                                       |

Choosing **Also delete the app's tables** removes those tables as well, leaving
nothing of the app behind.

> **Removing does not yet cut the tokens on its own:** 'Removing an app clears everything it put in your workspace and detaches its grants, so this surface stops treating it as connected. The last step — expiring the access tokens it already holds — is still being wired up. Until it lands, use Disconnect as well if you want the access cut for certain; Disconnect does cut it immediately.'

> **Per-user connections:** 'AI tools such as Claude connect per person, so one card can represent several members. Each member can revoke their own connection; an owner or admin can revoke everyone at once from the card.'

## Not supported yet

Being explicit about the edges, so nothing surprises you:

- **No delivered events.** An app that asked to be told when you revoke is not notified automatically yet.
- **No advance notice when an app is retired.** There is no deprecation or sunset flow yet: if a developer removes their app, you find out because it stops working. Your tables stay.
- **No per-app changelog.** An app that publishes a new version does not yet show you a history of what changed.
- **No third-party widget code.** Apps ship dashboard and widget *templates*. Code written by a third party does not run in your workspace.
- **No per-app usage meter.** You can see when an app last used its access, not how much it read.

## Related guides

- [The connect link](/docs/apps/connect-link) — the hosted page an app sends you to, and what each part of it does.
- [Managing your integrations](/docs/integrations/managing-integrations) — the destinations that sit in the same list.
- [Connected apps](/docs/workspaces/connected-apps) — the OAuth grants you have given, and revoking one.
- [Building an app](/docs/apps/apps-reference) — if you are the developer rather than the person installing.
- [Roles and permissions](/docs/workspaces/members-and-roles) — who in your workspace can install or remove an app.