Reference

Data and privacy

Assistant has no account and no cloud. Everything is stored on your computer.

Where your data is#

Settings → About → Local Data shows the paths. One database file holds your conversations, messages, settings, personas, recipes, memory, automations and sessions. The models folder holds the model files. Logs are next to them.

OSApp data
Linux~/.local/share/cgeosoft.assistant.desktop/
macOS~/Library/Application Support/cgeosoft.assistant.desktop/
Windows%LOCALAPPDATA%\cgeosoft.assistant.desktop\

Back up this folder to keep everything. Copy it to another computer to move.

What leaves your computer#

WhenWhatTo whom
Every hour and at startA request for the model catalogueassistant.cgeosoft.com
At start and every hour, while the update check is onA request for the latest versionassistant.cgeosoft.com
When you download a model or the CUDA buildThe download requestHugging Face, GitHub
When a chat uses a cloud engineThe conversationThat provider
When the model calls a toolThe page address, search words, place name or coin symbolThe site, your SearXNG instance, OpenWeatherMap, Binance
When you report an issueThe e-mail you send, with the log when you attach itSupport, through your e-mail application

Nothing else. With the built-in runner and no cloud engine, a conversation never leaves your computer. Switch the update check off under Settings → About.

The website uses analytics only after you accept the cookie banner. See the terms of use.

Export and import#

  • One conversation: File → Export as Markdown or JSON. The JSON can be imported again.
  • Everything: Settings → General → Data → Export writes one JSON file with your settings, personas, recipes, conversations and memory. Import reads such a file into this install: conversations, personas and recipes come across; memory is collected again from the messages.
  • Delete: Settings → General → Data deletes conversations in bulk. Chat → Delete Conversation removes one, with its memory facts.

Keys and passwords#

The API keys of cloud engines and tools stay in the local database. They are sent only to the service they belong to and never appear in logs. The app-lock PIN is stored as a hash.