Home / Privacy

Privacy: what DANGO reads, what it keeps, what it never touches

DANGO runs entirely on your computer and uploads nothing. It reads the session logs that Claude Code, Codex, DeepSeek Harness and WorkBuddy already write to your home folder, turns them into numbers (minutes, turns, lines changed, which job, tokens and cost) and keeps those numbers in a local database. Your prompts, the AI’s replies, your code and your file paths are never stored. There is no account, no telemetry and no analytics in the app.

What it reads

Only the logs the agents keep for themselves. Nothing is installed into Claude Code or Codex.

On Windows the same folders are under %USERPROFILE%.

While reading, a prompt is looked at once in memory to tell what it is about (a cat’s health goes to the doctor, a stock question to the financial analyst), and a shell command to tell what kind of step it is (tests, a commit, ffmpeg). Then both are dropped. Only the resulting job, such as doctor, is kept.

What it keeps

A SQLite database at ~/.dango/data.db (Windows: %USERPROFILE%\.dango), readable only by your user account:

• Per turn: start and end time, which agent, how many files were touched, lines added and removed, whether tests ran and passed, whether it committed or merged, how many subagents, minutes per job and what they are worth, tokens per model and what they cost at API prices.
• Per session: start and end time, active minutes, and a 12-character SHA-256 fingerprint of its working folder instead of the folder path.
• Session titles and project folder names, read from the agents’ own logs, so the report window on your Mac can list what you worked on. They stay on your computer and are never put on a share card.

Every other text stored must be a short token (an ID, a hash, a fixed value). The project ships a check, dango privacy-scan, that fails if anything stored looks like a path, code, a prompt or free text.

What it never touches

Share cards

A share card (day, week, month, year or all-time) carries numbers, jobs and your ABTI type. It never carries project names, session titles or code. A card leaves your Mac only when you share it yourself.

Remove everything

On a Mac, quit DANGO from its right-click menu, then in Terminal:

launchctl bootout gui/$(id -u)/com.dango.daemon 2>/dev/null
launchctl bootout gui/$(id -u)/com.dango.widget 2>/dev/null
rm -f ~/Library/LaunchAgents/com.dango.daemon.plist ~/Library/LaunchAgents/com.dango.widget.plist
rm -rf /Applications/Dango.app ~/Applications/Dango.app ~/.dango

On Windows, uninstall Dango from Settings → Apps, then delete %USERPROFILE%\.dango. Your Claude Code and Codex logs are not touched either way.

The website

dangoai.org sets no cookies and runs no analytics. The home page loads its fonts from Google Fonts. We count downloads only from the public download numbers GitHub shows for each release.

Questions

Does DANGO upload my code or conversations?

No. Everything is computed on your computer. Prompts are read once in memory to recognise the topic and then dropped; code, file paths and replies are never stored or sent anywhere.

Does DANGO need an account or an internet connection?

No. It has no account and works offline. The background service has no network code at all.

Can I check this myself?

Yes. The source is on GitHub (github.com/justinz183/dango), the database is a plain SQLite file in ~/.dango, and dango privacy-scan checks that it holds only numbers and short tokens.