Privacy policy

Last updated: 2026-09-30

The CleanLens extension and the cleanlens CLI run entirely on your machine.

#What they do

• Read code files and Git history inside the opened folder / target directory.
• Run external commands locally only: git log, git diff, git cat-file, git rev-parse.
• Keep the last analysis result in VS Code session memory (extension) or write it to standard output (CLI), and keep per-commit results in a local cache on your machine.
• Write the .clean-code-tracker.json config file in the project root — only after you confirm (extension) or never (CLI).

#What they do not do

• Make no network requests. No code, reports, or developer data is sent to any server or service.
• Do not require sign-in or a GitHub token.
• Do not collect telemetry, analytics, or crash reports.
• Do not modify code during analysis.
• Do not access anything outside the opened folder (except the cache file in the local storage directory).

#Contributor emails

Attribution uses the author email already recorded in your Git history and displays it in the dashboard and reports. Use a .mailmap file to merge or mask identities.

#Permissions

The extension does not support Untrusted Workspaces because it runs Git commands against the repository; make sure you trust the project before running an analysis.