Data & Safety
Back up and restore the local browser database. Use backup files you control for portability and cloud protection.
Private browsing warning
Private or incognito browsing may delete Finvue data when the private session closes. Use a normal browser profile for ongoing use and save a full Finvue backup before closing this window. Finvue cannot reliably detect whether the current browser window is private.
Finvue data belongs to the active browser profile and site origin. Another browser profile has separate data, and app.finvue.me and localhost are separate origins. Private sessions may use temporary or less durable browser storage.
A full Finvue JSON backup is the recovery format. A transaction CSV is not a complete backup and cannot restore the full database.
Checking backup history
Reading full-backup history from this browser profile...
Local data status
A local, read-only summary of the Finvue database owned by this browser profile and site origin.
Support-safe troubleshooting
Start with non-financial metadata that helps explain the problem without sharing your Finvue dataset or authentication secrets.
What to share first
- The Finvue build identifier: open /api/health and provide its
commitvalue. - The affected page or route, browser and version, operating system or device type, and whether you use the browser or an installed PWA.
- The approximate time, a visible sanitized error code or message, and brief reproduction steps without financial values.
- Whether refresh or restart reproduces the problem, and whether it also occurs in an isolated profile using synthetic data.
Data Health: start with the summary
When relevant, use Data Health Copy summary. It is intentionally limited to high-level diagnostic counts and issue types.
Do not send detailed Data Health JSON or CSV exports for ordinary troubleshooting unless a separately reviewed process specifically requires them. Detailed exports may contain account names, descriptions, amounts, dates, taxonomy, and record identifiers.
Keep financial artifacts private
Full Finvue backups are for user-controlled recovery, not ordinary support diagnostics. Do not send full backups, transaction exports, bank or card statements, raw import spreadsheets, or detailed Data Health exports for ordinary troubleshooting; they can contain financial records.
Screenshots can reveal balances, transactions, counterparties, card references, loans, or notes. Redact or obscure financial information before sharing a screenshot; if that is impractical, describe the issue instead.
Never share credentials or browser data
Do not send passwords, API keys, PINs, CVV/CVC or other security codes, full card numbers or PANs, authentication tokens, cookies, or session credentials.
Ordinary troubleshooting should not require IndexedDB or localStorage dumps, browser profile folders, raw DevTools payloads, or HAR/network captures that may contain financial information. Start with the non-financial metadata above.
Browser storage protection
A browser-local view of storage durability and approximate origin-wide capacity. This is separate from Finvue record counts.
Browser compatibility
Current desktop Chrome or Edge is recommended; core support and enhanced browser capabilities are separate questions.
Use a current supported desktop Chrome or Edge release for the best Finvue capability fit. Core Finvue is expected to work in current Firefox and desktop Safari releases supported by the app framework, but project-level validation and browser-specific features may differ. JavaScript and IndexedDB must be available.
Linked-file backup requires browser File System Access support; manual full-backup export and restore remain the fallback. PWA browser-native technical installability has been validated on tested desktop Chrome/Edge versions. The automated QA did not execute the OS-level install workflow. Apple/WebKit documents Home Screen behavior, but Finvue has not been smoke-tested on a real Safari, iPhone, or iPad runtime in this QA environment. Finvue does not promise full offline operation.
Finvue opened from the Home Screen uses a separate web-app storage context. Existing Safari IndexedDB data is not automatically copied or migrated. If Home Screen Finvue starts empty, that does not by itself mean the Safari data was deleted.
- In Safari, export a current full Finvue JSON backup.
- Add and open Finvue from the Home Screen.
- Import that backup inside Home Screen Finvue.
- Verify the restored state and Data Health.
- Only then consider clearing the old Safari site data.
This is a manual move, not automatic migration, shared storage, or sync. Keep the backup until the destination has been verified.
Linked backup file
Choose a backup file in a local folder or in a synced folder such as OneDrive, Google Drive, Dropbox, or iCloud Drive. Finvue writes only to the selected file. If that folder is synced, your cloud-drive app handles the cloud backup.
Direct cloud-provider sync
Future optional provider connection for encrypted backup and restore.
AI privacy
Real AI review and column mapping are optional, explicitly triggered, and scoped.
Accounts, transactions, cards, loans, schedules, reports, and backups stay in this browser during normal use. Finvue does not automatically upload them to a hosted financial database.
When you explicitly use a real AI review or column-mapping action, selected import rows or sample cells and required account, taxonomy, and counterparty context are sent through Finvue's server API to the configured OpenAI or Gemini provider. Do not use a real AI action if you do not want that selected context transmitted.
A provider key saved in local-key mode is stored in this browser, but each real AI request sends that key to Finvue's server route so it can call the selected provider. Finvue application code does not persist the key on the server.
Restore test workflow
Prove a backup is usable in an isolated browser profile before relying on it for recovery.
- Export a full backup and keep the original file unchanged.
- Open Finvue in a separate disposable browser profile.
- Import the backup here and confirm the replacement warning.
- Compare table counts and representative records, then refresh.
- Check Data Health for material relationship or reporting errors.
app.finvue.me and localhost are separate browser origins, and separate browser profiles have separate IndexedDB data. Restore affects only the active profile and origin. It replaces that local Finvue database; it does not merge records. Export the active data first whenever it may be needed later.
Manual full backup
Universal fallback. Download or replace this profile and origin's Finvue data from a full JSON backup.