Privacy Policy & Zero-Upload Execution Guarantee
LLMEOL is engineered as a static, read-only developer workbench under CodeAP Studio. Configuration snippets pasted into the auditor never leave your browser.
1. 100% Client-Side Model Config Auditing
When you paste a .env file, litellm_config.yaml router manifest, or source code snippet into the Model Config & .env EOL Auditor, parsing and model-ID matching execute entirely in JavaScript within your local browser memory against the preloaded public EOL catalog. LLMEOL does not transmit, log, or store pasted text, environment variable names, or secret values on any backend server.
2. Theme Preferences, Analytics & Local Reset
When you explicitly override your operating system's light or dark color scheme, LLMEOL stores codeap_color_scheme in localStorage and sets a first-party codeap_theme cookie scoped to .codeap.com so your visual preference stays synchronized across CodeAP Studio, DevToken, ToMarkdown, and LLMEOL. Anonymous UI interaction counters via Google Tag Manager never include pasted configuration content.
Do RSS, Atom, JSON Feed, iCal, or API requests require authentication?
No. All machine-readable endpoints (/api/v1/eol.json, /api/v1/upcoming.json, and /feeds/*) are static public files served over HTTPS without API keys, cookies, or user tracking.
Are exported CSV, JSON, or Markdown migration reports saved on a server?
No. Every CSV table export, JSON snapshot download, and Markdown checklist copy is generated locally via browser Blob URLs and the Clipboard API inside your current tab, leaving zero server-side audit trails or retained files.