Privacy story

Your data stays on your machine.

A plain-language explanation of where your data goes — and doesn't go — when you run TeamLaboration.

Data flow

~/.claude/projects/ (read-only)

Your existing Claude Code session files. TeamLaboration reads them; it never writes to them.

local daemon

A small background process running on your machine.

local SQLite database

Stores processed summaries (not raw logs). Lives at ~/Library/Application Support/TeamLaboration (mac) or %APPDATA%\TeamLaboration (Windows).

localhost:7842 dashboard

The web UI. Only reachable from your machine. No external network exposure.

api.anthropic.com

The only outbound call. TeamLaboration sends individual conversation content to Anthropic's API using your own API key so the LLM can write a summary. Nothing else leaves the machine.

What's stored

Processed summaries — structured 1–3 sentence descriptions per session.
Weekly rollups — once you generate them.
Configuration — output paths, polling interval, week boundaries.

What's not stored

· Raw Claude Code conversation logs (read on demand, not copied)
· Your API key in plain text (kept in OS credential store)
· Telemetry, usage analytics, error reports

API key handling

Your Anthropic key is stored in your operating system's credential vault — Windows Credential Manager or macOS Keychain — via the standard keyring library. It is:

· Never written to a config file
· Never transmitted to a TeamLaboration server (there is no TeamLaboration server)
· Only sent to api.anthropic.com when summarizing

No telemetry