Privacy.

Wanigan collects nothing about you: the website sets no cookies and runs no analytics, and the app has no account, no cloud and no telemetry. This page says exactly what does leave your computer, and when.

This website

It sets no cookies, runs no analytics, has no forms and loads nothing from anyone else’s servers. Its Content-Security-Policy holds it to that.

It is served by Cloudflare, which, like any host, sees each request (your address, the page asked for, your browser’s name) in its ordinary logs.

Videos load only when you press play.

The app

Wanigan runs on your computer, and its data stays in its own folder there. It calls GitHub, TypeSafe and, for voice input’s model, Hugging Face itself, each only once you ask, and everything else is the tools you already use, run as you:

Wanigan and Phone

Update checks use GitHub’s public releases; Jev uses TypeSafe when enabled or testing its connection. Jev card reads send card fields, the project name and up to five similar cards’ keys, titles and statuses. Those requests read no files or transcripts, though entered fields may contain code.

Phone is off until enabled. Paired devices read boards, Needs you and selected terminal output, normally over your Tailscale network; Can act permits sessions and typing. Separately enabled notifications send device-encrypted text through the browser’s push service. Protect an acting phone like your terminal.

Voice input downloads its speech model from Hugging Face once, when you ask, each file checked against its SHA-256. After that it works offline: speech becomes text on this computer, and the audio never leaves it.

Your agents

Claude Code, Codex and Gemini CLI run as you, using configured services; gh sends pull requests to GitHub. Local models route Claude Code or Codex to LM Studio or Ollama on this Mac. Wanigan queries both for models and uses LM Studio for requested downloads. Agents and tools can still make other network connections.

Desktop actions start sessions, AI review, Draft and Talk to Wanigan. Can act permits Phone sessions and input too. Account and usage checks use Claude Code’s and Codex’s own CLIs.

Your data

SQLite, attachments and card worktrees stay in ~/Library/Application Support/Wanigan 2/. Local storage does not stop the connections above.

Routine launches keep runtime configuration outside projects. Chosen MCP settings, skill copies, setup commands and Git actions can change files. Git registers card worktrees.

Check it yourself

Wanigan’s window and its core both run as Wanigan 2. While you work, in Terminal:

# Wanigan's open internet connections, right now
lsof -nP -i | grep -i '^wanigan'

# Bytes in and out for each Wanigan process
nettop -P -L 1 | grep -i wanigan

GitHub receives normal connection metadata, but no account, installation identifier or usage data. Daily checks require your choice; Wanigan sends no analytics or crash reports. For all processes, use a firewall such as LuLu or Little Snitch: agent CLIs, gh, local runtimes and Tailscale have their own names.

Your sites

The live view shows your local sites. Opening a hosted environment (Dev, Test, Live), or comparing with one, sends requests to that site only when you do, read-only, in a private session that shares no cookies with your local site.

The site helper is written into a local site only when you install it, after showing what it writes and runs, and is removed on your click.

Questions

Ask in a GitHub issue, or, for anything private, through the security policy.

Updated 10 October 2026.