Help & Documentation

Your data is stored locally (IndexedDB + an OPFS backup) and is durable for normal use, but there are a few ways it can go away. A periodic manual backup costs seconds and is the only fully independent snapshot.

• Browser storage gets cleared — Safari's tracking-prevention, manual 'Clear site data', Chrome quota eviction.
• Hardware fails, is lost, or is stolen.
• You migrate to a new machine and didn't sign into Cloud Sync there.
• Accidental large delete (a project, a whole category, a category rename gone wrong).
• A risky import or template change you might want to roll back.

One click, one file. The download is a .zip bundle containing a JSON of every project, contact, rental house, template, device, and preference in your local store, plus any images. If zipping is unavailable it falls back to a plain .json file.

• Filenames carry a timestamp — handy when you keep more than one.
• Contains EVERYTHING in the local store. There's no per-category 'export only projects' or 'only templates' option.
• The file is a .zip — unzip it to read the JSON inside if you ever need to inspect a backup outside the app.
• This screen doesn't produce CSV or PDF — those exports live elsewhere in the app (per-project).

1. Open Settings → Backup & Data.
2. Scroll to the 'Backup' section.
3. Click 'Download full backup' — a .zip file is generated and saved by the browser.
4. Park it somewhere safe (cloud drive, external disk, second computer).

Import takes a .zip bundle (or a plain .json) you previously downloaded and MERGES it into your current data. Existing entities are kept; new entities from the backup are added. Nothing is overwritten silently.

1. Settings → Backup & Data → 'Import full backup' in the Backup section.
2. Pick the file from disk.
3. Confirm. The merge runs; a toast reports success or per-entity issues.

Your install takes periodic snapshots to OPFS as you work — full and per-project. The 'Device auto-backup history' panel lists them and lets you restore any single snapshot.

• Device backups include both full snapshots and per-project snapshots. Restoring a per-project snapshot is ADDITIVE — it adds a restored copy to your dashboard and leaves your current data unchanged (so it can create a duplicate). Restoring a full snapshot from the list merges into your current data instead.
• Daily snapshots are retained for ~90 days. The per-project rolling window is configurable separately (see 'Auto Backup settings' below).
• The list is read from local storage (OPFS / IndexedDB) and works fully offline.

1. Settings → Backup & Data. In the 'Device auto-backup history' section, click 'Browse device backups' to open the list. (The separate 'Restore from device backup' button does NOT open a list — it immediately restores your most recent on-device backup, replacing all current data, so use it only when that's exactly what you want.)
2. The list loads — each row shows source (full / per-project), project ID for project snapshots, and a timestamp.
3. Select a row and click 'Restore'. The snapshot is loaded back into local data.
4. Use 'Refresh' if you've just made a change you want to see appear in the list.

Cloud safety backups are created automatically when the sync engine detects a conflict. They are NOT a continuous cloud snapshot of every save — they exist so a conflict can always be undone.

• Cloud backups are produced when the Conflict Resolver fires — your local copy, the remote copy, and the common base are each preserved.
• Filename pattern: backup_conflict_{type}_{entityId}_{local|remote|base}_{timestamp}.json(.gz).
• Restoring writes the chosen variant into local data; sync will then push it back to the cloud as the new canonical version.
• Listing and downloading require online connectivity; the panel disables itself when offline.

1. Settings → Backup & Data → 'Cloud backups' section. The section requires an online connection.
2. Click 'Load cloud backups' to fetch the list from your account.
3. Each row shows: type (project / template / contact / device / etc.), truncated entity ID, source (local / remote / base), and timestamp.
4. Per-row controls: 'Download' fetches a copy to disk, 'Restore' applies the variant locally.

The 'Auto Backups' section controls whether device auto-backups surface in the project dashboard, and how long the per-project rolling window keeps snapshots. Device auto-backups always run — there is no on/off for the mechanism itself.

• 'Show auto backups' toggle — when on, recent auto-backups appear in the project dashboard for quick restore.
• 'Auto backup retention (hours)' — numeric input. Accepts 1 to 168 (1 hour to 7 days). Controls the per-project rolling window only.
• Daily snapshots are kept for ~90 days regardless of the retention value above — that's a separate retention class.

Factory Reset clears ALL local data on this browser and returns you to a blank install. Use it only when you intend to re-import from a backup, when local state is corrupted, or when you want a true clean slate.

1. Settings → Backup & Data → scroll to the 'Factory Reset' section.
2. Read the warning. There is no in-app undo.
3. Confirm twice: 'Continue', then type RESET and click 'Confirm'.
4. A full backup is downloaded automatically before anything is erased — save it when the browser asks where to put it.
5. Confirm then reads 'Resetting…' and everything in the dialog is disabled. This takes a few seconds; leave it alone — the app reloads itself when the reset is done.
6. After the reset: the app is empty. Sign back into Cloud Sync (if you use it) to pull cloud data, or import a manual backup.

The same tab hosts maintenance actions that are not backups but are adjacent. Each shows a confirmation dialog before it runs.

• Clear Orphaned Items — removes items that aren't referenced by any project.
• Clear Old Auto-Backups — drops auto-backups older than the retention window.
• Clear Cache — clears the app cache. You may have to sign back in afterwards.
• Verify Data Integrity — runs read-side checks against the local store and reports any inconsistencies.
• Reset Sync — clears the sync state without touching data. Useful if sync is stuck.