Coflow privacy

Your code stays on your machine

• The analysis reads your project's files (Python, JSON and config files such as docker-compose) on your computer, with your own Python interpreter. It never runs your code.
• The map is drawn inside VS Code. Nothing is uploaded, and no AI service is involved.

No network access, no telemetry

• Coflow makes no network requests: no telemetry, no analytics, no crash reports, no account and no licence check.
• The map's panel blocks every outside connection with a strict Content Security Policy.

What Coflow writes, and only when you ask

• Arrange by hand: the box positions are saved in .vscode/coflow-layout.json in your project (setting coflow.layoutFile; off keeps them in VS Code's workspace storage).
• Record a Run…: runs the script or test you pick, locally, with your interpreter. The recording stays in memory for the replay. What your own program does while it runs is up to your program.
• Export Map as HTML…: writes one HTML file where you choose.
• The Coflow log in the Output panel stays on your computer. You share it only if you copy it into a message.

VS Code, the Marketplace and Open VSX

• Installing and updating Coflow goes through VS Code and the store you use (the Visual Studio Marketplace or Open VSX). They work under their own privacy policies, and their settings (such as VS Code's telemetry setting) apply to them, not to Coflow.

When you contact support

• If you write by email, your message and what you attach (such as a log) are used only to answer you and fix the problem. They are not shared or sold, and you can ask for them to be deleted.

Questions

If this ever changes, this page and the changelog will say so before it ships. Questions about privacy: candidathector@gmail.com.