Cloud and Local Storage
Bringing a Trove to your Device
FTWeb keeps a cloud copy of a synced Trove and a working copy in the browser on each device you use. Before you can edit a cloud Trove on a new device, select Bring Local beside it on the Troves page. This downloads the latest available copy to that device. Edits are made on the local copy and synchronized with the cloud when you are online.
What “local” means
“Local” means saved in the browser’s storage on this device. It does not mean that the Trove has been downloaded as a normal file, nor does it mean it is automatically backed up. Each browser and device has its own local copy. Bringing a Trove local on one device does not bring it local on another.
New user Troves are encrypted by default. For encrypted user Troves, item content is encrypted before it is saved to the cloud and remains encrypted in browser storage. When you unlock the Trove, the app decrypts content on your device for use; readable content is held in memory while you work. Public sample Troves are different: they are intentionally available for people to view and are not encrypted.
Why work from a local copy?
Keeping the working copy on your device lets the app open and edit content without waiting for each field to travel to a server. The app also needs locally available, decrypted content to search and filter items, sort results, show full item details, and support offline work. The cloud stores encrypted content for encrypted Troves.
Local storage can be cleared
Browser storage is useful, but it is not a guaranteed archive. A browser or device may remove it to free space, when you clear browsing data, or when using private/incognito browsing. Browser policies differ. Safari and other WebKit-based browsers can be more likely to clear site data after periods without interaction; storage may also be affected by privacy protections. Other browsers can remove best-effort site data when device storage is under pressure. Visiting a site regularly lowers some risks but does not make browser storage a dependable backup. See the browser documentation for storage eviction rules and WebKit storage policy.
Trove Settings shows a Persistence State. If it says At Risk, the browser has not granted persistent storage for this site. Even a Persistent status is not a substitute for another copy of important information.
Take care of local-only Troves
A local-only Trove has no synced cloud copy. If browser data is removed, its content may be lost. We recommend enabling cloud sync. Also export important item data regularly and keep the exported ZIP somewhere separate from the browser and device. Local-only Troves do not have cloud backups. A sample brought local is a temporary sandbox copy and may expire automatically; it is not a permanent personal archive.
Everyday precautions
- On each device, use Bring Local before opening a cloud Trove there. Let the download finish before working.
- Reconnect periodically so completed edits can synchronize. When working on more than one device, bring the Trove local and sync on each device to receive the latest changes.
- For important local-only content, enable cloud sync if appropriate, or export copies regularly and store them in a safe separate location.
- Avoid private/incognito windows for work you need to keep, and take care before clearing browser data or uninstalling/resetting a browser.