We respect your privacy. This policy explains what information we collect when you use the Dokugen CLI tool and how we use it.
We are open source. You can verify exactly what we send.
Data is transmitted securely over HTTPS.
We never sell your data to third parties.
When you use Dokugen CLI, specifically when running commands like generate, we collect the following technical information:
| Data Point | Purpose |
|---|---|
| username | Your verified GitHub username, used to authenticate requests and prevent spam. |
| Your primary verified GitHub email, when available, used for unique user identification. | |
| GitHub access token | Stored locally with restricted file permissions and sent over HTTPS to authenticate API requests. The server validates it with GitHub and does not store the token. |
| os_platform | To understand our user base (Windows vs Mac vs Linux). |
| cli_version | To track adoption of new versions. |
Dokugen operates local-first. While scanning repositories to build diagrams and system overviews, the CLI enforces strict filters to protect sensitive information. Dokugen never reads, indexes, or transmits any of the following:
.env, .env.local, .env.development, .env.production, etc.package-lock.json, pnpm-lock.yaml, yarn.lock, bun.lockbtsconfig.json, *.log, npm-debug.log, etc.node_modules, .git, build, dist, and .next are skipped entirely.We use Supabase, a secure backend-as-a-service platform, to store usage metrics. The database is secured with Row Level Security (RLS) policies and is only accessible by the Dokugen administration team. Your GitHub access token is not stored in this database or displayed on the leaderboard.
If you have any questions about this Privacy Policy, please contact us via our GitHub issue tracker.