What bank-linked apps can learn through Plaid

The connection can carry more than a balance

Plaid's End User Privacy Policy says collection depends on the product, connected app and available information. Listed categories include account identifiers, balances, transactions, account-owner details and, for some services, loans, investments or payroll information. Transaction fields can include amount, date, payee, location and description. This is not a claim that every app receives every category. Plaid: financial data, uses and retention

The policy describes service delivery, fraud prevention, insights and development of new services, including AI systems, among uses. It separately directs readers to the connected app's own policy and to Plaid CRA's policy for that company's reporting services. One notice does not define every recipient's practices. Plaid: financial data, uses and retention

A dashboard can show categories and access times

Plaid's Portal help describes viewing connections, shared data types, disconnection and financial-data deletion, with exceptions. The data-type guide says an app's Data shared view can expand a category to show more detail and the date and time of its last access. Review that scope rather than treating a connection as only a bank-name label. Plaid: what Portal shows and controls · Plaid: data categories and last-access information

The visible list is not necessarily complete

Plaid says matched connections use a phone number or email to identify connections it believes belong to the Portal user. Those matches are not necessarily comprehensive. Verification, a financial institution's records and the original connection method can affect what appears. Plaid: matched connections and completeness

Its coverage help lists connections that Portal may not display, including manual account-number or microdeposit connections, unsupported institutions, some beta products and Plaid Check Consumer Report connections. It also says a bank's own portal may offer access management. An absent row is not proof that no financial-data relationship exists. Plaid: connections not displayed in Portal

Stopping new sharing does not recall earlier copies

Plaid's disconnection help says the action stops future data sharing through that connection. The app may retain data already collected, and features depending on financial data may stop working. Deleting the app's existing copy requires attention to the app itself. Plaid: stopping future app data sharing

The financial-account deletion help adds another limit: deleting financial data through Portal does not remove third-party copies or payment authorization. Data access and permission to make payments must be reviewed separately. Plaid: financial-data deletion and payment-authorization limits

Retention has stated exceptions

Plaid's policy describes deletion after a developer removes a connection, subject to exceptions such as another active connection, requested services, legal duties, fraud prevention or other specified needs. It does not supply one universal deadline for every record. Plaid: financial data, uses and retention

The privacy-request help says some newer, faster product experiences cannot be fully managed in Portal. It offers a privacy-request route and expressly says some information may remain where law permits or requires it. A completed request is not proof that every copy held elsewhere disappeared. Plaid: privacy requests and retention exceptions