Files is about where your data lives: the portfolio is one local SQLite file, and everything on this page moves, copies, or swaps that file. Nothing here touches the network.
Because switching files replaces what every page is showing, anything on this page that opens a different portfolio asks about unsaved edits first: Open…, Copy to…, Restore, loading or resetting a sample, Back to my portfolio, and Start fresh. Save keeps those edits in the portfolio you are leaving, Discard throws them away, and Stay cancels the switch and changes nothing. That includes the confirmation you were in: a typed phrase for Restore or Start fresh, or a sample's reset, is still there to try again, and nothing on the page claims a switch happened or failed. A confirmation does not follow you to another page: if you open the confirmation for Restore, deleting a backup, a sample's reset or Start fresh and then go to a different page, it closes, and you ask again when you come back. While a switch is running the app declines to save anything, and says so where you asked: your edit stays on screen, and you can save it once the new portfolio is open.
If a price update is running when you switch, the button reads Finishing the price update… for a moment: the batch already downloading is saved into the portfolio you are leaving, and the update stops there. Nothing it downloaded is written into the portfolio you open, and the update reports that it stopped because the portfolio was switched, which is neither a failure nor a finished update. Run Update Prices again in the portfolio now open. If a switch fails, every page re-reads the portfolio that is still open.
These data-custody tools remain available after a commercial trial ends. Read-only means the app stops portfolio and planning edits; it never takes away the ability to export, back up, restore, relocate, inspect or erase your own local data.
The database file
Open… switches to another portfolio file; its chooser starts in the folder of the portfolio you have open (the app's data folder while a sample is open, and Downloads only when no portfolio is open). Copy to… copies the current one to a new location (a synced folder, an external drive) and switches to the copy; the original file stays where it was, as it was. The path shown is the file every other page reads and writes.
The file you open or copy to becomes your portfolio: the app remembers it, so Back to my portfolio after exploring a sample, and Start fresh, both go to that file rather than the app's default one. Opening a sample never changes which file is yours. While a sample is open, Copy to… is unavailable and says so: it copies the portfolio that is open, which would be the sample's data. Choose Back to my portfolio first.
Open… opens only a RangefinderInvest portfolio. It checks the file first, without changing it, and refuses in words a file that is empty, is not a database, or is another program's database. Such a file is left exactly as it was, and the portfolio you had open stays open. Copy to… onto a file that already exists replaces it whole: the copy is written beside it first and swapped in only when complete, and any leftover journal files of the old file are removed, so the copy always opens as your portfolio. If the copy cannot be written (a full disk, for example), the file there and your portfolio are both left as they were. Both actions use only the file you chose in their own window.
When your portfolio is not found
If the file the app remembers is not there (you renamed its folder, a sync service took it offline, or a drive is not connected), the app does not make a new one in its place. It opens no portfolio, makes no changes, and says Your portfolio at … was not found, with two choices:
- Locate it… opens the file where it is now, and it becomes your portfolio.
- Use the default portfolio stops looking for the missing file and opens the default portfolio in the app's own folder (a demo portfolio if you have never used it). The missing file is not deleted. If it comes back, Open… can bring it back.
If the drive just needs to be connected, connect it and reopen the app: nothing was changed while it was missing. The same notice appears here if your portfolio goes missing while a sample is open. Back to my portfolio and Start fresh then refuse rather than create a new file at that location.
While no portfolio is open, the rest of the app waits, and that includes Restore: a backup is always restored into the portfolio that is open. Choose Locate it… or Use the default portfolio first, then restore from the Backups list below.
If a switch fails and the portfolio you had open cannot be reopened either, the app says so and asks you to reopen it. Until then it saves nothing.
Backups
Back up now snapshots the database; auto-backup takes one at each
launch and prunes beyond your keep-count (a whole number, 1 or more; anything
else is refused and nothing is pruned). If the app opened with your portfolio
not found, it waits and backs up the portfolio you then open (Locate it… or
Use the default portfolio) instead. A sample opened in the meantime is not
backed up in its place. Both the pruning and the list are
per database: the keep-count applies to the active database's own
backups, and snapshots of other databases you have opened, such as a sample or a
renamed portfolio, are never rotated out by it. They appear under Other
databases, grouped by source, where they can be deleted individually
(nothing there is removed automatically). Restore replaces your current
data with the chosen snapshot. It asks you to type RESTORE plus the
backup's file name first (a backup saved by a newer version of the app is
refused before anything changes, and the list dates each backup by the time in
its own file name), and it saves a backup of the current database
to this list before swapping, so the state you just replaced stays
recoverable. The app reloads immediately so every page reflects the
restored file. Backups live alongside the database on your own disk.
If the automatic backup at launch fails (a full disk, a folder the app may not write to), the app tells you: a warning with the reason appears at the top of the Backups list, and a notice with an Open Backups button shows at the top of the window. Until a backup succeeds, recent changes are not in one; fix the cause and press Back up now. The warning and the notice clear as soon as a backup succeeds, whether from Back up now or at a later launch.
If a restore fails, the app puts your current database back and says so. If putting it back fails too, nothing is thrown away: the database as it was before the restore is filed into this list, and the error names that entry, so restoring it gets your data back. If even that cannot be done, the error gives the copy's location on disk instead.
When the list is empty, its recovery state offers Back up now directly; you do not have to infer the next action from an empty list.
Creating, listing, deleting and restoring backups, along with changing their automatic-backup/keep-count settings, are explicit post-trial recovery rights. Restore writes the recovered database by design; that does not open a side door for editing its contents.
File → Back Up Now lands here and runs the same backup as the button (watch for the Saved badge); Open Data Folder on the same menu reveals the database file in Finder or Explorer without coming here first. Back up now in the ⌘K palette takes the same route from whatever page you are on.
Sample portfolios
The four universal life-stage households are working copies. Load one, change it while the trial or a license permits editing, and reset it to pristine whenever you like. After expiry you may still load, read and reset a sample, but portfolio edits inside the copy remain read-only. Your own portfolio file is never touched while a sample is active, and Back to my portfolio returns exactly where you left off: to the portfolio file you last opened or copied to, or the app's default file if you never chose one. The ⌘K palette carries the same round trip: Load sample: … for each household, and Back to my portfolio whenever one is open.
A sample runs on its own calendar: price freshness, the retirement plan's first year and other "as of today" readings use the sample's newest close rather than today's date, so a household whose prices end months ago reads as it did on that day. Dates you enter are still checked against today. When you update a sample's prices, its calendar moves to the newest close.
A sample you have opened before keeps the working copy you left, so it keeps the data of the version that made it. Reset brings it up to the current build's sample (and discards your changes to that copy).
A working copy that an earlier version left empty (a copy that was interrupted) is copied fresh from the bundled sample when you load it, rather than opening as a blank portfolio.
Early career demonstrates contributions and a self-directed stock slice; Mid career compares brokerage implementations and retirement ages; Near retirement compares Roth-conversion choices; In retirement demonstrates withdrawals and a 15-rung Treasury ladder. A separate specialty sample for a Federal employee with TSP accounts appears below those universal choices. Its Traditional and Roth TSP accounts use periodic statement snapshots and the same target/reference models. It is an editable planning example, not a TSP connection, FERS calculator, or source of pro-rata/conversion instructions.
Start fresh
Clears your portfolio and re-runs the guided setup. It's deliberately hard to trigger: a typed confirmation is required, and a timestamped backup of your current data is written first, so even a fresh start is reversible from the Backups list above. This confirmed whole-portfolio erase remains available after expiry as the privacy-deletion exception; ordinary account, transaction, ticker and model deletion remains blocked.