Where your data lives

• Format: SQLite database (single file)
• Location (macOS): ~/Library/Application Support/HubSpace/hubspace.db
• Location (Windows): %APPDATA%\HubSpace\hubspace.db

The folder is still called HubSpace, which was the app’s working name before it became BooshHUB. The path is correct as written — only the product name changed.

• Self-contained: one file holds all your structured data — clients, projects, tasks, deals, everything. Your actual documents stay in your own filesystem / Drive (the app stores pointers, not copies), and email attachments are never stored in the DB.

What’s kept where (pointers, not copies)

The database holds your structured data; your heavy content stays in your own files:

• Folders & files attached to a record store a path or web/Drive URL — the files themselves stay on your disk / in your Drive. Removing the app leaves them untouched.
• Email attachments are never stored in the DB — fetched from the mail server on demand when opened.
• Email bodies are a prunable cache (removable / auto-pruned by age — Forever / 1 / 3 / 6 / 12 months, applied as soon as you choose it); deliberately logged emails become permanent Activity Log entries (their own copy). Bodies are the bulk of a typical workspace, so a shorter window is the single biggest lever on its size.

Backup

Updated 2026-07-26 (v0.7.7). Three layers, all producing clean single-file SQLite copies you fully own:

• Manual copy — the whole database is one file. Drag hubspace.db to Drive/Dropbox for offsite backup, or copy-and-date it (hubspace-2026-07-26.db). Restore by dropping it back and relaunching.
• Automatic rolling backups (new) — on launch (when the newest is more than ~a day old) a clean snapshot is written to the backups/ folder beside your database, keeping the last 5. Plus Back up now and a Restore list in Settings → Workspace. A snapshot is also taken automatically before enabling sync and before switching back to local.
• Pre-upgrade backup — before any schema upgrade, the database is copied to backups/ first (last 10 kept), so an update can always be rolled back.

Getting data out

Tool	What you can do
In-app CSV export (Settings → Export)	One CSV per entity; custom channels include their custom-field columns. Opens in Sheets/Excel/Numbers
DB Browser for SQLite (free)	Full table view, search, edit — works on Mac/Win/Linux
TablePlus / DBeaver	More polished SQL client

Credentials

Secrets (email app-passwords, OAuth tokens, the workspace auth token) are encrypted at rest with the OS secure store (safeStorage — Keychain / DPAPI / secret service) and are machine-bound: copying the DB elsewhere won’t expose them.

Safe updates

Updating the app never wrecks your data:

• Pre-upgrade backup — when a launch finds an older schema, it copies the DB to …/HubSpace/backups/ before migrating (last 10 kept).
• Atomic migrations — all schema upgrades for a launch run in one transaction: they fully apply (version advances) or roll back cleanly to the prior version. No half-applied state.
• Downgrade guard — an older app refuses to open a DB created by a newer one, rather than mangling it.
• Migrations are forward-only and additive (new tables/columns layered on; existing data preserved).

Portability

Moving to another machine: copy hubspace.db to the same path on the new machine. Full restore, all relationships intact, no re-import needed. (Email/Drive/Calendar credentials are machine-bound by design — re-enter once.)