Keep Local Browser Expense Records Safe
On this page8 sections
- Browser storage eviction matrix across platforms
- Practical habits that protect local browser records
- Comparing 19-Column CSV, Full JSON, and Full ZIP backups
- What a Full JSON Backup restores and what stays local
- How do Merge and Replace work inside Restore Backup?
- How do you move local records to a new phone or laptop?
- Honest boundaries and photo storage tradeoffs
- Long-term audit archives for tax and reimbursement claims
Keeping expenses locally in your browser eliminates server breaches, bank credentials, and monthly accounts. In exchange, your browser operating system controls storage eviction rules, making durable installation habits and regular local backups essential for long-term reliability.
Key takeaways
- Pin as a home-screen app: Adding Receipt Scanner via Add to Home Screen or Install app prevents iOS Safari’s 7-day idle cleanup on browser tabs.
- Match export format to task: Use
19-Column CSVfor spreadsheets, Full device backup (.json) for lightweight ledger restores, and Full backup with photos (.zip) for device moves.- Understand Restore Backup modes: Merge combines records safely by ID, while Replace this device swaps the entire workspace inside an atomic IndexedDB transaction.
- Verify before wiping devices: Spot-check restored book totals and receipt photos on new hardware before clearing your old phone or browser profile.
Browser storage eviction matrix across platforms
Modern browser engines follow distinct persistence rules documented in Apple’s WebKit storage policy updates and the MDN StorageManager.persist() spec. Knowing where eviction happens prevents silent data loss before an audit or reimbursement deadline.
| Browser scenario | Default storage status | What deletes expenses | Reliable protection habit |
|---|---|---|---|
| iOS Safari regular tab | Best-effort (7-day idle cap) | Not visiting for ~7 days wipes script-writable storage | Use Share -> Add to Home Screen |
| Android Chrome / Desktop | Best-effort unless engaged or installed | Severe device low-disk pressure | Click Install app and confirm persistence |
| Firefox Desktop / Mobile | Prompts user explicitly on durable request | Clearing site data or low disk if denied | Approve persistence prompt and export JSON |
| Incognito / Private Window | Ephemeral in-memory or blocked | Closing the private tab wipes everything immediately | Scan normal sessions for real bookkeeping |
When storage remains best-effort on low-capacity phones, operating systems clean older website caches automatically without showing a warning dialog. If you chose a private expense tracker without bank sync specifically to keep records under your control, upgrading storage durability protects months of logged receipts.
Practical habits that protect local browser records
Installing the app via Chromium’s install banner or Safari’s Add to Home Screen (walked through step-by-step in our complete user guide) signals intentional user retention across mobile Safari and Chrome. Watch for any storage notice inside My expenses, and keep persistent storage enabled outside restricted Private windows.
Export a Full device backup (.json) monthly—or a .zip backup with photos before OS updates, browser resets, or device swaps. Storing encrypted copies on external drives or personal cloud storage keeps your records portable without granting remote services live database access.
Comparing 19-Column CSV, Full JSON, and Full ZIP backups
Each export option inside My expenses under Export serves a distinct purpose depending on whether you need an accountant spreadsheet, a fast ledger snapshot, or a complete device migration package with every stored receipt photo:
| Backup / Export Format | Typical File Size | Photo Inclusion | Relational Budget & Split Fidelity | Primary Restore Target |
|---|---|---|---|---|
19-Column CSV (expenses-*.csv) |
Tiny (10 KB–200 KB) | Excluded (text rows and itemCount only) |
Flattens splits to text; omits budgets, settlements, and line items | Excel, Sheets, or Import (rows only) |
Full JSON Backup (billsnap-backup-*.json) |
Compact (50 KB–2 MB; 25 MB max) | Excluded from file (keeps existing same-device photos on ID match) | 100% fidelity for Books, Expenses, line items, BookBudgets, CategoryBudgets, and splits | Settings -> Restore… on any browser |
Full ZIP Backup with Photos (billsnap-backup-*.zip) |
Larger (5 MB–200 MB; 250 MB max) | Yes (photos/ folder + photoManifest image blobs) |
100% fidelity across all ledger tables, budgets, splits, settlements, and linked images | Export -> Full backup with photos onto new devices |
What a Full JSON Backup restores and what stays local
A Full JSON Backup exports the structured state of your browser workspace rather than one flat table. It captures every custom Book configuration, BookBudget and CategoryBudget cap, line-item array, participant roster, expense split, and recorded settlement.
For group travel or shared apartment logs described in splitting bills and group expenses offline, JSON and ZIP restores rebuild everyone’s historical settle-up math in seconds. Photo binaries stay excluded from .json backups so routine monthly snapshots remain under a few hundred kilobytes instead of ballooning to hundreds of megabytes.
How do Merge and Replace work inside Restore Backup?
Inside My expenses under Settings, Restore… opens Restore backup with two modes: Merge upserts records by ID while preserving unrelated existing entries, whereas Replace this device swaps all ledger tables, budgets, and splits inside one atomic IndexedDB transaction.
When to pick Merge vs. Replace this device
Pick Merge (the default) when combining scans from two devices or recovering accidentally deleted rows without losing newer receipts logged on your current browser. For existing expense IDs already saved locally, Merge retains their stored local photos when restoring a .json snapshot.
Pick Replace this device when migrating onto a clean browser or reverting to an exact earlier snapshot. After you confirm the warning dialog, it clears existing expenses, books, budgets, participants, splits, and settlements, keeps local photos whose expense IDs match the backup (or unpacks photos from a .zip), and purges orphaned image blobs.
Pre-flight validation and atomic rollback on corrupted files
Corrupted downloads never leave your browser half-wiped. Before modifying storage, the parser verifies file size limits (25 MB for .json, 250 MB for .zip), ZIP headers, presence of backup.json, valid schema version, and non-empty records, displaying a preview count summary before you confirm.
Once confirmed, all clear and bulk-write steps run inside a single IndexedDB read-write transaction. If a browser quota error or unexpected write failure interrupts the restore mid-way, IndexedDB automatically rolls back the entire transaction so your prior workspace stays intact.
How do you move local records to a new phone or laptop?
Moving to a new iPhone, Android phone, or laptop relies on exporting a self-contained .zip photo archive rather than remote accounts. Completing the transfer in four ordered steps preserves your books, split balances, budgets, and linked receipt photos cleanly.
- Export a photo-inclusive ZIP from the old device: Open My expenses -> Export and tap Full backup with photos (
billsnap-backup-YYYY-MM-DD.zip). If your multi-year library exceeds the250 MBrestore limit, also save a compact.jsonbackup alongside annual Report / PDF packets. - Transfer the archive privately: Send the
.zipfile to your new iPhone, Android device, or laptop over AirDrop, USB cable, or an encrypted personal drive. - Install the web app on the new device first: Open Receipt Scanner in a normal (non-private) Safari or Chrome tab, install it via Add to Home Screen or Install app for durable origin storage, and launch the installed app.
- Restore and spot-check before wiping old hardware: Open My expenses -> Settings -> Restore…, pick your
.zipfile, choose Replace this device on a blank phone (or Merge to combine books), and verify category totals and opened receipt photos before resetting the old phone.
Honest boundaries and photo storage tradeoffs
Be clear-eyed about zero-server software: there is zero multi-device synchronization between phone and laptop, no password-reset team, and zero remote disaster recovery if you wipe browser storage without exporting files first. Verify how everything remains isolated on How Privacy Works.
Receipt photos consume far more disk quota than text ledger rows. A heavy year of high-resolution bills can reach hundreds of megabytes, raising OS cleanup pressure on older phones. You can uncheck "Keep the photo with this record" during non-tax everyday scans while retaining photos on reimbursable or tax-critical bills.
Long-term audit archives for tax and reimbursement claims
Before resetting a browser profile or retiring an old phone, pair your backup archive with a clean 19-column spreadsheet dump and PDF receipt packet—see scanning receipts to Excel and CSV for column details. Receipt Scanner organizes local files only and does not provide tax or accounting advice.
Always verify OCR-extracted dates, merchant names, tax numbers, and totals directly against original paper receipts or supplier PDFs, keeping federal preservation expectations such as IRS recordkeeping guidance in mind.