Privacy
Temporary by default, local when you choose.
Sparse Halo is designed so the default experience does not depend on a permanent conversation archive. Chatbot and Cabinet sessions stay temporary in the browser unless you explicitly choose to save them locally.
Privacy Model
The default product experience is not built around permanent history.
That is the main idea to understand. Sparse Halo does not assume every conversation should become a durable archive tied to your account. Instead, Chatbot and Cabinet are designed to be useful in the moment first, with durable history only appearing when you choose a local save path.
Default
Temporary sessions in the browser
Optional
Local-only saves on your own device
Not Claimed
That external model providers never process requests
In practice
Open a Session
Chatbot and Cabinet each start as temporary working sessions, not as permanent history views.
Start Fresh
A new session clears the active workspace in that mode rather than building a default long-term archive.
Save Only If You Want
If you choose to preserve something, that history lives locally on your device rather than as a default account-level record.
Default Session Behavior
Chatbot and Cabinet both keep enough context to make the current thread useful, but they are not meant to behave like a permanent cloud history product by default.
Starting a new session clears the active working thread in that mode. The emphasis is on giving you a useful workspace now, not on assuming that every interaction should be retained indefinitely.
Local Saves Are Optional
If you want to keep a session, Sparse Halo lets you opt into local saving on your own device. On supported browsers, that uses a linked folder, where Sparse Halo stores `.sparsehalo.zip` files in `chatbot/` and `cabinet/` subfolders. ZIP import lets you reopen those saved archives later.
That keeps saved history under user control and separate from the default temporary flow, rather than turning every conversation into an automatic account-backed archive.
What This Page Does And Does Not Claim
This page describes how Sparse Halo handles session history and local storage inside the product itself.
It does not claim that AI providers or infrastructure outside Sparse Halo never process requests to generate replies. The promise here is narrower and more specific: Sparse Halo is temporary by default and only keeps durable history when you explicitly choose a local save path.
Design Principle
Privacy here is not a slogan layered on top of default retention. It is part of the product shape itself.