Four ways in, receipts attached
Four ways in, each with a receipt.
Start with a file or fact you choose: an export, browser-extension capture, statement PDF, or manual entry. GlidePath previews what it read before anything saves, then keeps the source close enough that you can check freshness and changes later. The first fair question is still: if it doesn't connect to my bank, do I have to type everything in by hand?
No. The longer answer is the intake model itself: choose the source, inspect the read, then let the app reuse what it learned.
The one trade we made on purpose
It stays useful because the intake is visible.
GlidePath never logs into your bank. Each import starts when you export, capture, drop a PDF, or type a fact, then the app previews the rows and stores the accepted result on your computer. That visible path is the reason your financial file stays readable, portable, and easy to back up.
So the real question is: with nothing out there fetching your data for you, how do we keep the work small? By automating everything we responsibly can on your machine — and being straight with you about the small part that stays yours.
Two ways your data could travel
An auto-sync loop through another service — or a short receipt trail on your own machine.
Connecting through a bank-login aggregator keeps a standing sync path outside the app. GlidePath starts with a file or fact you bring in, previews it, and keeps the core financial file local by default. The contrast is the receipt trail.
What we do for you, and the part that's yours
The short column is the point.
That column on the right is short because we automated the rest. The part that stays with you is the part that should — the decision to bring something in, and a quick look to make sure it's right.
Four ways in — and they all stay on your machine
Bring in the raw material; GlidePath does the bookkeeping.
Drop an export
Download the CSV (or spreadsheet) your bank, brokerage, or old budgeting app already gives you, and hand it to GlidePath. It detects the format, shows you the rows first, and the one time it sees a layout it doesn't recognize, you map the columns once and it remembers. This works with any bank's export — that's the universal on-ramp.
Let the browser extension catch it
Install the Chrome extension, click "download" on your bank's site the way you always would, and the extension hands that same file straight to your local app — no second step, no separate upload. It works with major bank accounts out of the box, and a few more with a one-time setup; brokerage exports come in through the manual export path instead. The file goes to your app on your computer and nowhere else.
Drop in a statement PDF
A statement lands in a review queue, GlidePath reads what it can, and you confirm before it saves a thing. We read Bank of America card statements precisely today, and pull useful hints from many other statements — always with you in the loop. The reading happens in-process on your machine; the PDF never goes to a server.
Type it in
The floor under everything: add an account, a transaction, a holding, or a goal by hand, any time. Always there when you want it.
And underneath all four: you never enter the same fact twice. Balances, net worth, running totals, spending by category — those are calculated from what you brought in, not things you maintain by hand.
What actually leaves your computer
This is the part most apps gloss over, so here it is plainly.
-
Drop an export, type it in, or read a PDF: nothing leaves. It's parsed and stored right on your machine.
-
Refreshing prices: the only thing that goes out is the ticker symbol of what you hold — say, VTI — to look up today's price. Never how much you own, never your cost basis, never an account name or balance.
-
Asking the built-in helper a question: it sees your question and which page you're on — never your accounts, balances, or transactions — and many questions are answered without anything leaving at all.
Why we think this is the useful deal, not just the private one
Receipts beat promises.
Connecting your bank to an aggregator can feel effortless, but the numbers often arrive without much context. The GlidePath way asks a little more of you — a few minutes when something new comes in — and gives you something back for it: the numbers are yours, in files you can read, with a visible trail from source to saved result.
We'll be honest about the trade the other direction, too: if a few minutes of upkeep is a dealbreaker, an always-on aggregator app may suit you better, and we don't think less of that choice. But if “I can open it, copy it, and see exactly what's there” sounds like the version you want, that's the whole idea.