Your conversation history stays local
Blume reads supported coding agents’ session files and imports their conversations into a local database. That database is not uploaded as a cloud archive of your chats.
Imported messages, signals, evidence excerpts, suggestions, and processing history remain on your device. Your setup inventory, local file mappings, and generated Wrapped cards and summaries also stay local.
AI analysis stays on your machine
Blume does not send conversation or project context to the cloud for AI analysis. Your imported conversations and local analysis records remain on your device.
Files you choose to sync and content you submit to Deliveries are separate cloud records. Local analysis does not mean that every Blume feature stores its data only on your machine.
Deliveries keeps a shared cloud record
Project settings, plans, tasks, progress updates, reviews, and test results sent to Deliveries live in Blume’s hosted workspace ledger. Text, code, or paths included in an update become part of that cloud record.
Uploaded screenshots and test artifacts are stored in the cloud. Tests can run on your machine and still upload their results and evidence. Hosted tests run in a cloud sandbox against a reachable target.
Your imported conversation database stays local. Content submitted as a delivery update or evidence is stored separately in the cloud.
Setup sync includes file contents
Setup artifact sync stores snapshots of the files you choose to sync, along with their relative paths, in your cloud account. Sync sends file content, not just filenames or counts.
Each device keeps its own absolute path mapping locally. Removing a sync mapping on one device does not delete the cloud item; deleting that item is a separate action.
Accounts and connected services
The desktop stores its account session and GitHub token locally using operating-system encryption. Sign-in also uses remote account and authorization records, and connected services keep their own remote authorization records.
Aggregate usage and product diagnostics
Blume sends aggregate usage counts and product diagnostics, such as usage events, app version, platform, timings, and sanitized error details, to help operate and improve the service.
Diagnostics are designed to exclude conversation content and credentials. These diagnostics are separate from the delivery updates, evidence, and synced files described above.
Know what your choices change
You can:
- Choose which setup files to sync
- Remove a setup sync mapping on a device
- Delete local Blume data
- Remove connected accounts
- Remove Blume from your system
Deleting local Blume data does not delete cloud delivery records or uploaded evidence. Removing setup sync removes the mapping on that device; deleting the cloud item is a separate action. Feature availability can vary by app version.
For a feature-by-feature guide, read What stays local and what goes to the cloud.