← ~/agent $ cd ..

Privacy Policy

Effective 2026-07-30 · TokenDam
TL;DR — Your traces and prompts never leave your browser — TokenDam analyzes them entirely on your device, and we never receive, store, or log the content you paste. There is no account system. The only thing we measure is anonymous, content-free usage: cookieless page analytics and a counter that an analysis ran — a number, never what you analyzed.

What we don't collect

TokenDam's analysis runs 100% client-side (in your browser) or locally (the CLI on your machine). Specifically, we do not collect, transmit, store, or log:

What we do measure (anonymously)

So we can tell whether TokenDam is actually useful, we collect two aggregate, content-free signals. Neither can see your trace, your prompts, or your results, and neither builds a profile of you:

That is the entire extent of it, and only in the web app — the tokendam CLI still makes no network calls at all. The guarantee at the top holds without exception: the content you analyze never leaves your browser.

The only third parties involved

To be precise and honest, loading the web page itself involves two ordinary web requests that — like visiting any website — reveal your IP address to the host, but never see your trace content:

That's the complete list. There is no backend that your trace data is sent to — because there isn't one. The tokendam CLI makes no network calls at all when analyzing.

Where your data goes when you use it

When you click "copy fix prompt" or "copy audit," the text is placed on your clipboard. If you then paste it into another tool (e.g. your own coding agent, a PR, an issue), that tool's own privacy terms apply — that action is yours, not ours.

Children

TokenDam is a developer tool and is not directed at children under 13.

Changes

If this policy changes, the effective date above will change. Because we keep no contact information, material changes will be reflected here and in the project's changelog.

Contact

Questions: hello@avantia2a.com.

# This policy covers the free, client-side web app and CLI. Any future opt-in feature that processes your data at runtime (e.g. a proxy) will be governed by a separate, clearly-consented data-processing agreement.