Signing up for a budgeting app creates a four-way data-sharing arrangement. The user, the app, a financial-data aggregator and the bank all receive the email address entered at signup, and the bank link moves transaction data through the aggregator. Giving each budgeting app its own alias isolates that signup and, if the app's list is sold or breached, the alias itself points to the source.
The signup data flow#
The address supplied at signup identifies the account, carries recovery messages, and receives receipts, breach notices and marketing. YNAB's terms place registration details under the company's privacy policy and record the user's authorisation for the company to reach data held by the relevant third-party provider, including personal identity information and transaction records. The address therefore lives in at least three places: the app, the aggregator and the bank's record of the authorised connection.
YNAB charges $109 per year or $14.99 per month, and a 34-day free trial requires no card on direct signup.
Financial data aggregators#
A budgeting app generally does not talk to a bank directly; an aggregator stands in the middle, pulls balances and transactions, and passes them on to the app. Plaid's homepage states that it connects 12,000 financial institutions in 20 countries and that 1 in 2 banked adults in the US use Plaid. For US and Canadian accounts YNAB names Plaid and MX as its providers, and for UK accounts Plaid Financial Ltd., an FCA-authorised payment institution with Firm Reference Number 804718. Finicity, Yodlee and Salt Edge do the same job for other apps.
Under this model the app never holds bank credentials: a token and the data it permits go to the app, the connection stays with the aggregator, and the account stays with the bank. Because each party's privacy policy governs only its own copy, the signup address falls under three policies rather than one. A documentation review of YNAB, Monarch, PocketSmith and Lunch Money, read on 29 October 2026, found read-only bank connections described by both YNAB and Monarch, and both companies stating that they do not sell financial data, with a note that advertising-related sharing may count as a sale or share under some state privacy laws.
OAuth and screen scraping#
Two methods connect an app to a bank. With OAuth the user signs in on the bank's own website or app, approves the connection, and the bank issues a secure token to the aggregator. The credentials never pass through the aggregator at all. Without OAuth the credentials go in through the aggregator's interface, encrypted in transit and in storage, for the aggregator to set up the connection. In older connections that is screen scraping, where software signs in with the stored credentials and reads the data off the page.
Bank login credentials belong with the bank, not with an app that screen-scrapes. A bank-authorised API connection keeps the credentials at the bank and hands the aggregator a token instead. Where a bank offers OAuth through the aggregator, no credential storage is involved at all.
On 22 October 2024 the US Consumer Financial Protection Bureau finalised its Personal Financial Data Rights rule under Section 1033 of the Dodd-Frank Act. Banks, credit unions and card issuers must make covered data available to authorised third parties through standardised APIs. The rule requires API access. Covered data runs to at least 24 months of transactions plus basic account-verification information such as name, address, email address and phone number. The rule was challenged in court within hours of finalisation; on 29 October 2025 a federal court in Kentucky enjoined enforcement while the Bureau reconsiders it. The Financial Data Exchange, recognised by the CFPB as a standard-setting body in January 2025, reports 114 million active US and Canadian customer connections on its standard.
Email aliases for budgeting apps#
AliasFleet supplies email aliases that forward to a destination inbox of the user's choosing. One alias per budgeting app gives the app and the aggregator an address that exists for that signup alone: a permanent forwarding address under the user's control, pausable or deletable at any time, with 10 active aliases on the free tier.
No bank credentials sit in the alias, no bank connection runs through it, and the aggregator still receives the same bank data. What changes is the address held by the app and the aggregator. If the alias turns up in a breach or begins collecting spam, the address itself identifies the source. The primary inbox remains unexposed. The bank keeps a permanent real dedicated address used only for financial accounts, because recovery, statements and fraud alerts depend on it. That separation is the subject of the guide on whether to use a separate email for banking; the alias belongs to the app, not the bank. Setup is covered in the guide on how to set up an email alias. The wider case for an alias instead of a primary address is covered in the guide on whether it is safe to give an email address to apps.
The Money Forward disclosure of 2026#
Money Forward, maker of the household-budget app Money Forward ME, disclosed on 1 May 2026 that GitHub authentication credentials used in software development had leaked and a third party had used them to copy repositories. Its first report listed 370 Business Card records, cardholder name and the last four digits of the card number, as possibly leaked, and stated that no leak from the production database had been confirmed. Bank-account linkage was suspended for a time as a precaution.
Connections began to return on 12 May 2026 and had been restored with every financial institution by 5 June. The final scope arrived on 23 June 2026: personal data of up to 62,901 people may have leaked. Most of the records were internal management numbers that cannot identify anyone on their own; alongside them were 1,807 employee email addresses and 24 customer email addresses. No intrusion into the production database was confirmed, and no secondary harm from misuse was confirmed either. The 62,901 figure comes from the company's 23 June 2026 report, published in Japanese and tracked in full by the English incident record cited below.
The data came from a development repository, not from the production system holding household-budget data. The Money Forward incident record tracks the full breakdown, the company's first report is the primary source for the disclosure dates, and an analysis of the incident records the suspension and staged resumption.
The Plaid settlement of 2022#
Plaid agreed in January 2022 to pay $58 million to consumers. The payment went to consumers who had a bank account linked to any of its approximately 5,000 client apps. The class action alleged that Plaid collected "more financial data than was needed" and took bank login credentials through its Plaid Link interface, "which had the look and feel of the user's own bank account login screen". The class period ran from 1 January 2013 to 19 November 2021. Plaid denied wrongdoing, but it still had to change some of its business practices.
The class action alleged the aggregator used by many budgeting apps had gathered more data than the apps needed and had shown users a login screen that looked like their bank's. Plaid's homepage now states that a user connecting through Plaid controls who has access to their financial data. YNAB's terms show the same structure today: the user gives YNAB a limited power of attorney to fetch account information as the user's agent, with the retrieval running through Plaid or MX. The Engadget report on the settlement records the terms, and the YNAB terms were last modified on 9 April 2026.
Data held by each party#
| Party | What it holds | Source |
|---|---|---|
| The budgeting app | The signup email address, the budget, and copies of imported transactions | YNAB terms |
| The aggregator | The bank connection, the token or stored credentials, transaction data, and identity information passed from the bank | Plaid, YNAB terms |
| The bank | The account, the transaction history, and the record of the authorised connection | CFPB Section 1033 advisory |
| The regulator | The Section 1033 rule, finalised in 2024 and enjoined in 2025, with no current enforcement | Section 1033 technical guide |
Only the email address appears in every row, identifying the account at the app, the identity data at the aggregator and the verification data at the bank. The alias is therefore attached to the address, not to the bank connection, which the token or the stored credentials govern.
Account closure and connection revocation#
Closing the budgeting app account leaves the aggregator connection in place: a separate authorisation between the aggregator and the bank, ended only by disconnecting the account inside the app, inside the bank's own connected-apps settings, or both. YNAB retains account data for a period after expiry unless the user deletes it. Deleting the alias stops mail to that address, but data already held by the app or the aggregator remains.
An app can also shut down while a user still has data inside it: Intuit closed Mint, which had 3.6 million active users in 2021, and moved users to Credit Karma. Mint stayed available until 23 March 2024, and Credit Karma's support page states that the new experience "does not offer the ability to set monthly and category budgets". The transfer option closed on 3 May 2024. An address handed to a budgeting app can therefore outlive the app, which is one more reason to give each app its own alias, deletable when the app closes, so the primary inbox never travels into the migration.
While the app is linked the alias stays live, so account recovery and breach notices keep arriving. Once the app account and the bank connection are confirmed closed, the alias can be deleted. The address can then be checked at Have I Been Pwned, which lists the breaches an address appears in and the data each one exposed. The same check is described in the guide on how to check if an email was leaked. Other financial apps follow the same pattern: the guides on protecting an email for a money transfer app and protecting an email for a stock trading app use one alias per app.
Limits of email aliases#
An alias narrows the exposure of the email address and does nothing else. It does not cut what the aggregator collects from the bank, it does not anonymise transaction data, and it does not stop the app sharing data under its own policy.
No public figure gives the share of bank connections that still run on stored credentials rather than OAuth, so the article gives no percentage. The open banking guide reports that most modern connections use OAuth, with smaller banks and credit unions the most likely to lack it. The Plaid bank sync explanation draws the same line. Major banks send users to their own login pages, while smaller institutions take credentials through the aggregator's encrypted interface. The method only becomes visible at the moment of linking, when the sign-in screen turns out to belong to the bank or to the aggregator.
