Privacy and Data

Privacy and Data

There is no account, no API key and no telemetry, and there is nowhere for a conversation to go. This page is the specific version of that claim: exactly what reaches the network, exactly where everything is kept, and how to take it all away again.

What never leaves the machine

Your conversations, the files you attach, the documents you index, the embeddings built from them, your settings, and the log file. None of these are sent anywhere, because Draggy has nowhere to send them. The model answering you is a process on your own computer, reached over 127.0.0.1.

There is no analytics, no crash reporting and no usage counter. Not "anonymised" or "opt-out": absent.

What does reach the network

Everything below is something you or the model asked for.

What	When	Where it goes
Model downloads	You pick a model, or the first launch does	Ollama's registry
Web search	The model searches, in Auto or On	The provider set in Settings → Tools
Reading a page	The model reads a URL, or you open one in the browser	That site
Site icons	A search returns results	Each result's own site
Filter lists	The ad blocker refreshes	GitHub, EasyList, OISD
Speech models	First use of voice mode or dictation	Hugging Face
Update check	Launch, then every six hours	GitHub releases
Extensions	Only ones you switch on	npm to install, then that service

Two of those are worth expanding.

Site icons come from the sites themselves. A search result's icon is fetched from that result's own origin, not from a third-party favicon service, so no one company gets handed the list of everything you searched for.

A search is a search. Whichever provider you pick sees the query, exactly as it would if you typed it into that engine yourself. If that matters to you, point Draggy at your own SearXNG instance in Settings → Tools, and it sees nothing.

Turning the network off entirely

Set web search to Off, leave every extension switched off, and Draggy will not open a connection except to check for updates, which you can turn off in Settings → Updates. With a model already downloaded, it works with the network cable out.

Where everything is kept

One folder, Electron's user data folder for the app:

System	Path
Windows	%APPDATA%\Draggy
macOS	~/Library/Application Support/Draggy
Linux	~/.config/Draggy

Inside it:

Name	Holds
draggy.db	Conversations, settings and extension credentials
library.db	The document index and its embeddings
created_files/	Everything the assistant wrote, and exported conversations
code_runs/	One scratch directory per code execution
model-cache/	The speech models
mcp-servers/	Extensions you switched on, installed with npm

Models themselves belong to Ollama and live wherever Ollama keeps them, which is why removing Draggy does not cost you a 5 GB download.

Backing up, moving and resetting

To back up or move to another machine, copy the whole folder while Draggy is closed. It is a SQLite database and some directories, with nothing keyed to the machine.

To reset, delete the folder. The next launch starts as a first launch, and your models are untouched.

To clear just the conversations, use Settings → Data, which also shows how much you have stored and opens the log file. Deleting is immediate and there is no copy anywhere else.

Uninstalling

Uninstall the app the way your system does it: Add or Remove Programs on Windows, drag Draggy.app to the bin on macOS, sudo dpkg -r draggy or delete the AppImage on Linux.

That leaves the data folder above, deliberately, so reinstalling gets your conversations back. Delete it yourself if you want it gone. Ollama and your models are a separate program and are not touched either way.

What an extension changes

Switching one on runs somebody else's program on your machine and gives the model a way to reach whatever that program talks to. That is the whole point of them, and it is also the one place the promises on this page stop being Draggy's to make. Nothing is on by default, install scripts are refused, and credentials you enter are kept in draggy.db rather than passed around. See Extensions.