Cloud Backupin Your Own Google Drive

Turn it on once and Plexon keeps the backup up to date in the background. What travels is what a transfer bundle carries: your settings, the skills and agents you wrote, personas, connectors with the credentials they use, workflows, dashboards, memory, journal, notes, your cloned voice, and the chats of every project on the machine. Heavy machine-local things stay out on purpose: speech and avatar engines, browser profiles, the avatar recording, and caches.

• Settings, skills, agents, personas, workflows, and dashboards
• Connectors travel with the credentials they use
• Memory, journal, notes, and your cloned voice
• Every project's chats, not just the current one
• Engines, browser profiles, the avatar recording, and caches stay out
• Turning backup on asks for your app PIN once, when you have one set. Background cycles never ask
• While an upload runs, the background jobs pill reads "Backup"

The backup lives in a per-app folder of your own Google Drive that only Plexon can reach. You cannot see it in the Drive interface, which also means you cannot corrupt it by accident. It is your storage: the backup counts against your own Drive quota, and a full Drive pauses backup with a notice in Settings rather than failing over and over.

• Invisible in the Drive interface. Only Plexon can reach it
• Counts against your own Drive storage quota
• A full Drive pauses the backup instead of erroring on every cycle
• Nothing in the backup's file names says what your projects are called or where they live
• Disconnecting inside Plexon asks whether to keep or delete the backup
• Revoking Plexon's access in your Google account settings deletes the folder, backup included. The disconnect dialog says so in plain words

Everything is encrypted on your machine before it uploads, and the staging area on disk only ever holds encrypted files. By default the key travels beside the data, so signing in with Google is all it takes to restore. That default has an honest cost: whoever controls the Google account can read the backup, connector credentials included. If that is not the custody you want, set a backup passphrase and Google holds ciphertext only.

• Encrypted on your machine before anything uploads
• Default: your Google sign-in is enough to restore
• The cost of that default: whoever controls the Google account can read the backup, connector credentials included
• The passphrase is at least 12 characters, with a recovery code shown once when you set it
• With a passphrase set, restore asks for the passphrase or the recovery code, and Google stores ciphertext only

When a laptop dies or gets wiped, install Plexon and click "Restore from Google Drive" on the sign-in screen. The restore runs through the same rails as importing a transfer bundle: you map the old project folders onto local ones, read exactly what goes away, and type the word replace before anything moves. The setup being replaced is kept as a restore point.

• "Restore from Google Drive" sits on the sign-in screen. Settings has a "Browse the backup" view too
• Same mapping screen, same typed confirmation, same restore point as a transfer bundle import
• Nothing is laid down until you type the word replace

Open a folder whose chats are in the backup and they come back. If the folder is empty, they restore on their own, with a note saying so. If the folder already has chats, Plexon asks first, in one sentence. Either way the merge only ever adds; wiping and replacing a machine is the full restore's job, behind its own rails.

• An empty folder restores automatically. A folder with chats of its own gets a one-line offer first
• The merge is additive. It never deletes a chat that is already there
• Projects whose folders no longer exist anywhere are remembered, and "Restore to folder" merges them into a directory you pick

One machine backs up at a time, and moving between machines is part of the flow. Open Plexon on your other laptop and it pulls what the backup has that the laptop lacks: memory, notes, journal entries, and tasks arrive on their own. Files changed on that laptop more recently are kept, and nothing is ever deleted. When the backup holds newer versions of files that also changed there, Plexon asks first, in one sentence. Once the pull settles, that laptop takes the backing-up seat, so the day's work backs up from the day's machine.

• A second machine adopts the existing backup rather than starting a rival one
• Opening your other laptop brings its new memory, notes, journal entries, and tasks over on its own
• Files you changed more recently on this machine always win, and replaced files go to the trash folder first
• Settings has "Pull latest from backup" for doing it by hand
• Chats keep their own additive restore, and deletes never travel between machines