Privacy Policy & Zero-Retention Governance
Effective 2026-11-11. CodeAP Studio (codeap.com, devtoken.codeap.com, markdown.codeap.com, and eol.codeap.com) requires no user accounts, sells no personal data, and never stores or trains on your documents, prompts, configs, or schemas.
1. Client-Side Browser Workbenches
All parsing, token estimation, config auditing, and schema compilation inside our browser-native tools—including the LLM Cost Ledger, Caching & Batch Calculator, Multi-Vendor LLM EOL Tracker, Model Config EOL Auditor, HTML-to-GFM Compiler, CSV/TSV/JSON Table Builder, RAG Semantic Chunker, MCP Config Generator, llms.txt Generator, and JSON Schema / Zod Converter—run exclusively inside your local browser tab without network transmission. Proprietary prompts, .env / litellm_config.yaml files, and configuration payloads remain strictly in local browser memory.
2. Stateless Document Conversion API & Local Preferences
Binary files uploaded to POST https://markdown.codeap.com/api/v1/conversions (up to 10 MB over TLS 1.3) are extracted into Markdown solely in volatile memory and discarded immediately after the HTTP response completes—never written to databases, object storage, application logs, or model-training corpora. Transient network metadata is inspected strictly to enforce payload size caps and per-IP abuse rate limits.
Browser localStorage stores at most two optional client-side keys: codeap_color_scheme (created only when you override your system light/dark theme) and codeap_telemetry_events (a local ring buffer of UI interaction counters). Aggregate page-view trends are measured via Google Tag Manager (GTM-N64WPS2P) without ever transmitting input text, schema payloads, or uploaded document contents. You can clear all local browser keys at any time below.