01 / Local storage
Your history has a home.
It’s your machine.
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.
Conversations
Imported messages and conversation history.
Analysis & suggestions
Signals, evidence excerpts, suggestions, and processing history.
Setup & recap records
Setup inventory, local file mappings, and generated Wrapped cards and summaries.
Conversation and project context stays on your machine for AI analysis. Files you choose to sync and content you submit as delivery evidence are separate cloud records.
02 / Cloud storage
Some features need
a shared place to work.
These records are separate from your imported conversation history.
A shared record of the work
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.
Proof you can come back to
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.
The files you choose to sync
Setup artifact sync stores snapshots of synced files and their relative paths in your cloud account. Each device keeps its own absolute path mapping locally.
Sync sends file content, not just filenames or counts.
Keeping the service working
Sign-in uses remote account and authorization records. Blume also sends aggregate usage counts and product diagnostics such as usage events, app version, platform, timings, and sanitized error details.
Diagnostics are designed to exclude conversation content and credentials.
03 / Local AI analysis
Your context stays
with you.
Analysis stays on your machine
Blume does not send conversation or project context to the cloud for AI analysis.
Your imported conversations, local analysis records, suggestions, and processing history remain on your device. Cloud delivery records, uploaded evidence, and synced files follow the separate boundaries described above.
04 / Your choices
What changes
when you change a setting.
Remove setup sync
Removes the mapping on that device. Deleting the cloud item is a separate action.
Delete local Blume data
Does not delete cloud delivery records or uploaded evidence.
Feature availability can vary by app version. The desktop stores its account session and GitHub token locally using operating-system encryption; connected services still keep their own remote authorization records.
Keep readingBlume’s privacy approach