Cloud Sync versus Drive Backups

Cloud Sync and Drive Backups both involve remote storage, but they solve different problems.

Cloud Sync is the active workspace

Cloud Sync makes eligible Proset recordings, conversions, and retained context available across devices. It is part of how the app's working data stays coordinated; it is not an extra folder of exported files.

Thought Threads depend on this cloud-backed workspace because their sources, context, run history, and results must remain available as one evolving record.

Drive Backups are external copies

Drive Backups copy eligible audio, transcript, and completed artifact files into a connected Google Drive, OneDrive, Dropbox, or WebDAV account. Those copies live outside the active Proset workspace.

Disconnecting a backup provider stops future copies but does not remove files already stored there. Similarly, changing working data in Proset does not turn an earlier final artifact into an editable live document.

Why Drive Backups require Cloud Sync

Backup automation needs the signed-in, cloud-backed state that identifies eligible recordings and completed outputs. Cloud Sync provides that coordinated source; Drive Backups add external copies of it.

Use Cloud Sync for continuity between devices. Use Drive Backups when you also want files in storage you control outside Proset.