Privacy Policy & Subprocessor Schedule
Privacy Policy
1. Zero Model Training Commitment
Stellar Content Inc. (d/b/a LeanLM) never uses customer source code, prompts, tool outputs, or completions to train, fine-tune, or distill machine-learning models, and we route inference strictly to contracted non-training US datacenter GPU endpoints.
2. Two Connection Modes & Exact Repository Data Lifecycle
How source code reaches api.leanlm.ai depends on whether you connect via Direct HTTPS or via the optional ecocoder CLI wrapper:
- Mode 1 — Direct HTTPS (
ANTHROPIC_BASE_URL,OPENAI_BASE_URL, Codexconfig.toml, or HTTP SDKs): No background repository file sync occurs. Only the prompt and tool-result messages constructed by your client travel over TLS 1.3. LeanLM processes prompt and completion bodies in volatile memory to complete the turn and does not write prompt or completion text to persistent LeanLM databases or logs. - Mode 2 — Optional
ecocoderCLI Wrapper (ecocoder claude,ecocoder pi,ecocoder delegate): To compute structural repository context for multi-turn edits, the CLI enumerates tracked and untracked, non-ignored files in your working directory (git ls-files --cached --others --exclude-standard; runecocoder sync-previewto inspect the exact file list locally before any network call). Eligible source and config files (≤1 MiBper file,15 MiBtotal, excluding.env*,*.pem/*.key,.aws/.ssh/.gnupg, and build directories) are staged into a tenant-isolated ephemeral cloud workspace. Staged workspace objects are deleted automatically when the CLI session exits and swept within 24 hours if a client disconnects abnormally. Use Mode 1 (Direct HTTPS) if you do not want workspace file staging.
Important secret-hygiene note: Filename filters cannot detect secrets hardcoded inline inside normal source files (for example, a credential pasted into config.py). Never place live secrets inside tracked or untracked source files.
3. What LeanLM Logs & Retention Windows
LeanLM logs numeric operational metadata so you can audit credit usage and GPU board energy without storing your code:
- Per-turn billing & energy receipts (retained 90 days in Cloudflare Durable Objects; 24-hour session receipt cache):
request_id,tenant_id,principal_id, timestamp, requested model alias,prompt_tokens,cached_tokens,completion_tokens,energy_joules(NVML GPU board energy),billing_micros, HTTP status code, attempt count, and turn latency in milliseconds. - Account & waitlist records (retained until deletion request): Work email address, hashed API key identifier, credit cap/balance, and optional client preference submitted on
leanlm.ai/#intakeorleanlm.ai/results#follow. - Marketing website analytics (
leanlm.aionly): Pageviews, scroll depth, and CTA clicks via PostHog (identified_onlymode). PostHog is never loaded onapi.leanlm.aiinference endpoints.
4. Subprocessors & Data Residency
| Subprocessor | Role & Scope | Region | Data & Retention |
|---|---|---|---|
| Cloudflare, Inc. | Edge TLS routing, gateway compute, encrypted billing ledger, ephemeral CLI workspace staging | US (storage & state) / Global TLS edge | Staged CLI files: purged on session exit (≤24h abnormal-disconnect sweep). Numeric turn receipts: 90 days. |
| Contracted US Datacenter GPU Host (vendor named under NDA / upon request) |
Stateless NVIDIA NVML GPU inference execution for api.leanlm.ai |
United States (US-Central / US-East) | Contracted non-training inference endpoints; LeanLM persists zero prompt/completion logs. Dedicated contractual ZDR addenda require an enterprise deployment agreement. |
| WorkOS, Inc. | Portal authentication & SSO session management on api.leanlm.ai/portal |
United States | Invited reviewer/account email and authentication session metadata; retained until account deletion. |
| Brevo (Sendinblue SAS) | Transactional evaluation-key notifications & opt-in benchmark update emails | US / EU | Submitted email address and form source; deleted upon unsubscribe or email request. |
| PostHog, Inc. | Product analytics on public leanlm.ai web pages only |
United States (us.i.posthog.com) |
Pseudonymous web navigation events (identified_only); zero API prompt or code data. |
5. Your Rights & Data Deletion
You may request access to, export of, or immediate deletion of your email record, API keys, staged workspace objects, and billing metadata at any time by emailing [email protected] (we do not sell or share personal information for cross-context behavioral advertising under CCPA/CPRA). We complete verified deletion requests within 7 business days.