Clip.A.Canvas Privacy Policy

Local Processing

Clip.A.Canvas renders HTML, CSS, JavaScript, SVG, and canvas animations on your own machine using Chromium and FFmpeg. The desktop app, TUI, and local MCP server do not upload your code snippets or rendered MP4 files to Clip.A.Canvas servers.

Data Collection

Clip.A.Canvas does not collect analytics, account data, telemetry, source snippets, rendered videos, or file paths through the local application, TUI, or MCP server.

Files

Rendered MP4 files are saved only to locations selected by the user or returned through the local MCP client. The `render_video_to_file` MCP tool writes to the output path supplied by the user.

Third Parties

Clip.A.Canvas uses local Python dependencies, Playwright Chromium, and FFmpeg or imageio-ffmpeg for rendering and encoding. If a user-provided HTML snippet loads remote images, fonts, scripts, or network resources, Chromium may request those resources from the referenced third-party hosts.

Security

Users should render code they trust. Clip.A.Canvas executes supplied browser code inside Chromium during rendering. The local MCP server does not intentionally provide host command execution tools.

Contact

Report issues at github.com/mechreaper007x/ClipACanvas/issues.