Data handling
How teemd handles launch-user data.
Updated August 28, 2026
teemd processes account data, workspace metadata, onboarding choices, provider-key metadata, build prompts, diffs, usage records, billing state, and support messages.
Build-scoped diffs can be stored so the review gate, audit trail, and dispatch records stay coherent.
Prompt context may transit teemd's dispatch proxy and the model provider selected for the build.
Engine vendors are subprocessors only when you choose or authorize that routing path.
Provider keys are stored encrypted and are used only for user-authorized model calls.
teemd does not publish provider keys, prompt text, diffs, or secret-like values in public status or download surfaces.
Billing, audit, usage, and security records are retained long enough to operate the product, investigate abuse, satisfy accounting needs, and support customer recovery.
A failed payment does not delete workspace data by itself.