Skip to content
CodeMorph

Legal

Data use

Exactly which data CodeMorph touches, where it goes, and who can see it, in one place.

Last updated 11 October 2026

Beta draft, pending legal review. This document describes how CodeMorph works today in plain language. It will be reviewed by counsel before general availability.

This page summarizes how data moves when you use CodeMorph. The privacy policy and security page have the details.

The desktop app

DataWhere it goesWho can see it
Your source codeRead on your machine to scan, plan, review and verifyYou
Dependency graphA local SQLite database on your machineYou
Typecheck, test and build outputRuns and stays on your machineYou
Conversion and Ask requestsSent directly to the model provider you configureYou and your provider, under your agreement with them
Your API keyEncrypted in the editor's secret storage on your machineYou
Usage analytics and crash reportsNot collected. Telemetry is disabledNobody
Extension browsing and installsSent to Open VSX when you use the Extensions viewOpen VSX

CodeMorph has no server that receives your code. We don't train models on your code, and we can't, because we never have it.

Model providers

When you use conversion or Ask, the relevant code and context are sent to your provider, such as Anthropic, using your key. How long they keep it and whether it's used for training are set by your agreement with them. Check your provider's data terms, and use their business or zero-retention options if you need them.

This website

DataWhyKept by
Email from waitlist or newsletter formsTo send what you signed up forResend, on our behalf
Name, email and message from contact formsTo reply to youResend and our inbox
Aggregated page viewsTo see which pages are usefulVercel Web Analytics, without cookies
Standard request logsTo serve and protect the siteVercel

We don't sell data, and every email we send includes a way to unsubscribe.

Questions or deletion requests: support@codemorph.codes.