Data & Safety help
How local storage, backups and linked backup files work in Finvue.
Where Finvue data lives
Core Finvue finance data is stored in this browser profile for this site origin. Separate browser profiles, devices and origins such as app.finvue.me and localhost do not automatically share that data.
Clearing browser or site data can remove the local Finvue database. Private or incognito sessions are not suitable for ongoing use.
Full backups
A full Finvue JSON backup is the portable recovery copy of the local finance database. Keep backup files somewhere durable that you control.
Finvue can record that a manual or linked full backup was created, but it cannot verify that the file still exists or that it contains every change made afterward.
Restore replaces the destination browser profile's local Finvue database. It is not a merge.
Browser storage durability
Browsers can expose whether this site's storage is persistent or best-effort. Persistent storage reduces the risk of automatic eviction under storage pressure, but it does not protect against manually clearing browser data and it does not replace a backup.
The request is real, but the browser decides whether to grant it. Chrome and Edge normally make that decision automatically rather than showing a prompt; site engagement and installed-app status can help, but a request can still be denied. Firefox can ask the user directly. A denied request does not mean Finvue storage is broken: the database continues to work in best-effort mode and you can try again later.
Finvue intentionally does not surface storage-quota figures in the main UI. Browser quotas vary by browser, device, available disk space and browser policy, and Finvue's normal record-based finance data is expected to remain modest compared with modern browser storage capacity. Quota becomes materially relevant only if Finvue later stores large files or other binary data locally.
Linked backup file
On browsers that support the File System Access capability, Finvue can keep a selected backup file linked and update it while the app is open.
For most users, the preferred location is a locally synced OneDrive, Google Drive, or Dropbox folder. Finvue writes to the selected local file; the cloud-drive application handles the off-device sync.
Those providers also offer file-version recovery features, with retention depending on the provider and account plan. That can add another recovery layer if the linked Finvue backup is overwritten or corrupted. Cloud sync is still not a substitute for occasionally keeping an independent full backup.
Clearing browser data can remove Finvue's stored permission to that file even when the file itself still exists.
Browser and device notes
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.
Linked-file backup depends on browser File System Access support. Manual full-backup export and restore remain the fallback where that capability is unavailable.
Browser-native technical installability has been validated on tested desktop Chrome/Edge versions. The automated QA did not execute the OS-level install workflow. Finvue has not been smoke-tested on a real Safari, iPhone or iPad runtime in this QA environment, and it does not promise full offline operation.
On iPhone/iPad, Home Screen Finvue can use a separate web-app storage context. Existing Safari IndexedDB data is not automatically copied or migrated. If the Home Screen version starts empty, export a current full Finvue JSON backup in Safari, restore it inside Home Screen Finvue, verify the restored state and Data Health, and only then consider clearing the old Safari site data. This is a manual move, not automatic migration, shared storage or sync.
Verify a backup before relying on it
- Export a full backup and keep the original file unchanged.
- Open Finvue in a separate disposable browser profile.
- Restore the backup and accept the replacement warning.
- Check representative records and refresh the app.
- Run Data Health and confirm there are no material errors.