ChatGPT wants your bank account. I built a company because of this.

On 15 May 2026, OpenAI wired ChatGPT into your bank. Not a screenshot you paste — a live connection, brokered by Plaid, reaching more than 12,000 financial institutions. It opened to Pro subscribers and reached everyone on Plus a few weeks later.

I started this company because somewhere along the way it became normal that using software means handing over a record of your life. I did not expect the destination to arrive this quickly, or for the last private thing — the ledger, the one document that describes a household honestly — to be the next thing asked for.

The launch came with a set of reassurances. They are all technically accurate. They also answer questions almost nobody was asking.

“It never sees your password”

True. The connection runs through Plaid over OAuth, and your credentials are handled by your bank. Fine.

But nobody lies awake worrying that a chatbot might learn their banking password. They worry about the thing the password protects. What the arrangement produces is a durable token that grants standing access to your balances and transactions — which is the object of concern, obtained without ever needing the password at all. The reassurance is real and it is beside the point.

“It is read-only”

Also true. It cannot move money, make a payment, or change your accounts.

Reading is the entire harm. Nobody was afraid it would spend their money. The fear is that a complete, structured, continuously updated account of where you go, who you pay, what you are treating, where you worship and what you are struggling with should exist on somebody else’s infrastructure. “Read-only” describes exactly the capability people object to, offered as though it were a limitation.

“Zero retention by default”

This is the one that gets quoted most, and it is the weakest thing in the pile — because a default is a setting, not a wall.

Defaults are revisited in product meetings. They get changed when a new capability needs history to function, and a finance assistant genuinely works better with memory, so the pressure to keep more will be real and it will be well-intentioned. Nothing in the architecture stands in the way. The data is already on their servers; what happens next is governed by a document that can be edited and shipped with a version number.

A promise survives right up until the moment somebody has a good reason to revise it. A design that never receives the data has nothing to revise.

You did not add one company. You added two.

Before: you and your bank. After: you, your bank, Plaid, and OpenAI.

Plaid is easy to miss because it appears for fifteen seconds during setup, but it does not leave when the window closes. It holds the token. It sits in the path from then on, with its own retention schedule, its own subcontractors, its own breach exposure, and its own obligations when a court asks it for something. You have taken on a relationship with a business you never went looking for, on the subject of your money.

And this is the change that actually matters: a screenshot is a snapshot. A linked account is a feed. It keeps working. It updates while you sleep. A consent given once, in a hurry, on a Tuesday, applies indefinitely to information that only becomes more revealing as it piles up.

The pile is the risk

Twelve thousand institutions, against a user base in the hundreds of millions. Whatever fraction connect an account, the result is one of the largest concentrations of household financial detail ever assembled in one place.

That is a risk created by the aggregation itself, and it does not depend on anyone being careless or ill-intentioned. A pile like that is a target in a way that a million separate piles are not, and it only has to fail once. Security is a rate, not a state.

It is the same reason I do not run servers at all. The safest data is the data nobody ever gathered up.

And it still is not accountable

A licensed fiduciary owes you a legal duty, carries insurance, and can be reported to a regulator. A chat assistant with a dashboard owes you nothing, however good the dashboard looks — and now it answers with your real balances in view, which makes it sound far more authoritative than it has any basis to be.

There is another way to do this

Ask an AI how amortisation works, what an expense ratio costs you over thirty years, or what to ask an advisor. Those are questions about how money works, and not one of them needs your account data. Ask about the concept; never hand over the ledger.

For the ledger itself, here is exactly where it lives with Thrive: on your device. If you use a Mac and an iPhone, it syncs between them through your own private iCloud — your Apple account, not mine. I never receive it, because there is nowhere for it to arrive.

Getting your spending in takes one of two forms. You export a statement from your bank and open it, or you let Thrive read the transaction alerts your bank already emails you. No bank login, no aggregator, no token, and no account to create with me. It is less convenient than a live feed. That is the trade, stated plainly, and for this particular category of information I think it is the right one.

What unsettles me is not that the technology exists. It is how quietly this is happening. The most revealing document a household owns is being handed over willingly, a few taps at a time, by people who were never really told what they were agreeing to — and who will not find out what it cost until long after the choice stops being theirs.

Sources: OpenAI’s announcement and TechCrunch’s coverage. The mechanics described are as announced in May 2026; check the current terms yourself before connecting anything.

I am not a licensed financial advisor and none of the above is personalised financial advice. I build a competing product, which you should weigh accordingly. For decisions about your own situation, speak to someone who is accountable to you.

Hear what comes next

I write when there's something worth sending — what's new in the app, and what I'm learning about handling money well. No tracking pixel, unsubscribe in one click.

Email address Subscribe

Thrive is built by Beacon Digital Solutions LLC in Jupiter, Florida. Questions or corrections: support@beacondigitalsolutionsllc.com