Compare LLM API retention and zero-data-retention evidence
LLM API Data Retention Compared — Training Use and ZDR by Provider
No LLM API retention answer is transferable across providers, tiers, endpoints, features, or accounts. Compare the exact service’s documented prompt/output storage, training use, human review, exceptions, and zero-data-retention prerequisites, then mark unknown joins Unavailable. “Not used for training” is not zero retention, and neither is a generic compliance verdict. Verified 2026-09-02.
Verified 2026-09-02 — source
Compare documented prompt and output handling by exact provider service, account, endpoint, feature, and verification date. Qualitative demand: dedicated cross-provider retention and ZDR comparisons were reviewed 2026-09-02; exact US monthly volume is unavailable.
Batch 58 · server-rendered evidence boards · verified 2026-09-02
Intent answer: No LLM API retention answer is transferable across providers, tiers, endpoints, features, or accounts. Compare the exact service’s documented prompt/output storage, training use, human review, exceptions, and zero-data-retention prerequisites, then mark unknown joins Unavailable. “Not used for training” is not zero retention, and neither is a generic compliance verdict. Verified 2026-09-02.
Demand evidence: Qualitative demand: dedicated cross-provider retention and ZDR comparisons were reviewed 2026-09-02; exact US monthly volume is unavailable.
Scope boundary: Compare documented prompt and output handling by exact provider service, account, endpoint, feature, and verification date. Exact provider, seller, serving host, account/tier, endpoint, model/snapshot, region, feature, and evidence identity are required; unresolved joins render Unavailable.
Retention-scope normalizer
Deterministic formula / rule: comparable = provider + seller/host + product + account + endpoint/feature + content class + dated policy; tier mismatch => excluded.
Boundary: Owns cross-provider API policy normalization; All AI Ask’s own notice and provider quality remain elsewhere.
| Frozen scenario / field ID | Exact identity and evidence fields | Result | State |
|---|---|---|---|
batch58-data-retention-m1-r1paid stateless API | route=/compare/llm-api-data-retention; owner=data-retention; provider/seller/host/account/tier/endpoint/model/snapshot/region/feature/request=data-retention; scenario=paid stateless API; provider; seller/host; product; account; endpoint/feature; content class; purpose; duration; training/human-review state; exception; source/effective/verification dates; observed versus documented versus assumed inputs are labeled; artifact/schema/tool/job/result hashes and verification date=2026-09-02 | Unavailable — frozen data-retention fixture requires an exact source, identity, and result receipt | UNTESTED — module 1 rule is reproducible but no production observation is claimed |
batch58-data-retention-m1-r2free/developer tier | route=/compare/llm-api-data-retention; owner=data-retention; provider/seller/host/account/tier/endpoint/model/snapshot/region/feature/request=data-retention; scenario=free/developer tier; provider; seller/host; product; account; endpoint/feature; content class; purpose; duration; training/human-review state; exception; source/effective/verification dates; observed versus documented versus assumed inputs are labeled; artifact/schema/tool/job/result hashes and verification date=2026-09-02 | Unavailable — frozen data-retention fixture requires an exact source, identity, and result receipt | UNTESTED — module 1 rule is reproducible but no production observation is claimed |
batch58-data-retention-m1-r3batch job | route=/compare/llm-api-data-retention; owner=data-retention; provider/seller/host/account/tier/endpoint/model/snapshot/region/feature/request=data-retention; scenario=batch job; provider; seller/host; product; account; endpoint/feature; content class; purpose; duration; training/human-review state; exception; source/effective/verification dates; observed versus documented versus assumed inputs are labeled; artifact/schema/tool/job/result hashes and verification date=2026-09-02 | Unavailable — frozen data-retention fixture requires an exact source, identity, and result receipt | UNTESTED — module 1 rule is reproducible but no production observation is claimed |
batch58-data-retention-m1-r4file/vector-store feature | route=/compare/llm-api-data-retention; owner=data-retention; provider/seller/host/account/tier/endpoint/model/snapshot/region/feature/request=data-retention; scenario=file/vector-store feature; provider; seller/host; product; account; endpoint/feature; content class; purpose; duration; training/human-review state; exception; source/effective/verification dates; observed versus documented versus assumed inputs are labeled; artifact/schema/tool/job/result hashes and verification date=2026-09-02 | Unavailable — frozen data-retention fixture requires an exact source, identity, and result receipt | UNTESTED — module 1 rule is reproducible but no production observation is claimed |
batch58-data-retention-m1-r5user feedback | route=/compare/llm-api-data-retention; owner=data-retention; provider/seller/host/account/tier/endpoint/model/snapshot/region/feature/request=data-retention; scenario=user feedback; provider; seller/host; product; account; endpoint/feature; content class; purpose; duration; training/human-review state; exception; source/effective/verification dates; observed versus documented versus assumed inputs are labeled; artifact/schema/tool/job/result hashes and verification date=2026-09-02 | Unavailable — frozen data-retention fixture requires an exact source, identity, and result receipt | UNTESTED — module 1 rule is reproducible but no production observation is claimed |
batch58-data-retention-m1-r6abuse-flagged request | route=/compare/llm-api-data-retention; owner=data-retention; provider/seller/host/account/tier/endpoint/model/snapshot/region/feature/request=data-retention; scenario=abuse-flagged request; provider; seller/host; product; account; endpoint/feature; content class; purpose; duration; training/human-review state; exception; source/effective/verification dates; observed versus documented versus assumed inputs are labeled; artifact/schema/tool/job/result hashes and verification date=2026-09-02 | Unavailable — frozen data-retention fixture requires an exact source, identity, and result receipt | UNTESTED — module 1 rule is reproducible but no production observation is claimed |
First-party citation: OpenAI API data controls. Verified 2026-09-02; missing or conflicting joins fail closed.
Zero-data-retention eligibility and exception matrix
Deterministic formula / rule: ZDR admitted = approved organization/config ∧ eligible endpoint ∧ excluded features understood ∧ verification method recorded; training status cannot substitute.
Boundary: Owns conditional eligibility evidence; it cannot call a route safe, compliant, private, or universally ZDR.
| Frozen scenario / field ID | Exact identity and evidence fields | Result | State |
|---|---|---|---|
batch58-data-retention-m2-r1self-serve default | route=/compare/llm-api-data-retention; owner=data-retention; provider/seller/host/account/tier/endpoint/model/snapshot/region/feature/request=data-retention; scenario=self-serve default; application/contract/config prerequisite; eligible endpoint; excluded data/features; revocation signal; admitted/conditional/unavailable state; observed versus documented versus assumed inputs are labeled; artifact/schema/tool/job/result hashes and verification date=2026-09-02 | Unavailable — frozen data-retention fixture requires an exact source, identity, and result receipt | UNTESTED — module 2 rule is reproducible but no production observation is claimed |
batch58-data-retention-m2-r2approved organization | route=/compare/llm-api-data-retention; owner=data-retention; provider/seller/host/account/tier/endpoint/model/snapshot/region/feature/request=data-retention; scenario=approved organization; application/contract/config prerequisite; eligible endpoint; excluded data/features; revocation signal; admitted/conditional/unavailable state; observed versus documented versus assumed inputs are labeled; artifact/schema/tool/job/result hashes and verification date=2026-09-02 | Unavailable — frozen data-retention fixture requires an exact source, identity, and result receipt | UNTESTED — module 2 rule is reproducible but no production observation is claimed |
batch58-data-retention-m2-r3endpoint-excluded feature | route=/compare/llm-api-data-retention; owner=data-retention; provider/seller/host/account/tier/endpoint/model/snapshot/region/feature/request=data-retention; scenario=endpoint-excluded feature; application/contract/config prerequisite; eligible endpoint; excluded data/features; revocation signal; admitted/conditional/unavailable state; observed versus documented versus assumed inputs are labeled; artifact/schema/tool/job/result hashes and verification date=2026-09-02 | Unavailable — frozen data-retention fixture requires an exact source, identity, and result receipt | UNTESTED — module 2 rule is reproducible but no production observation is claimed |
batch58-data-retention-m2-r4safety-monitoring exception | route=/compare/llm-api-data-retention; owner=data-retention; provider/seller/host/account/tier/endpoint/model/snapshot/region/feature/request=data-retention; scenario=safety-monitoring exception; application/contract/config prerequisite; eligible endpoint; excluded data/features; revocation signal; admitted/conditional/unavailable state; observed versus documented versus assumed inputs are labeled; artifact/schema/tool/job/result hashes and verification date=2026-09-02 | Unavailable — frozen data-retention fixture requires an exact source, identity, and result receipt | UNTESTED — module 2 rule is reproducible but no production observation is claimed |
batch58-data-retention-m2-r5cloud-hosted equivalent model | route=/compare/llm-api-data-retention; owner=data-retention; provider/seller/host/account/tier/endpoint/model/snapshot/region/feature/request=data-retention; scenario=cloud-hosted equivalent model; application/contract/config prerequisite; eligible endpoint; excluded data/features; revocation signal; admitted/conditional/unavailable state; observed versus documented versus assumed inputs are labeled; artifact/schema/tool/job/result hashes and verification date=2026-09-02 | Unavailable — frozen data-retention fixture requires an exact source, identity, and result receipt | UNTESTED — module 2 rule is reproducible but no production observation is claimed |
batch58-data-retention-m2-r6undocumented provider | route=/compare/llm-api-data-retention; owner=data-retention; provider/seller/host/account/tier/endpoint/model/snapshot/region/feature/request=data-retention; scenario=undocumented provider; application/contract/config prerequisite; eligible endpoint; excluded data/features; revocation signal; admitted/conditional/unavailable state; observed versus documented versus assumed inputs are labeled; artifact/schema/tool/job/result hashes and verification date=2026-09-02 | Unavailable — exact data-retention evidence join is not closed for “undocumented provider” | FAIL CLOSED — manual, probe, or source evidence required |
First-party citation: Anthropic commercial terms and privacy. Verified 2026-09-02; missing or conflicting joins fail closed.
Sensitive-workload evidence router
Deterministic formula / rule: eligible evidence = every declared hard requirement is documented for the exact service/account/feature; any unknown cell routes to review.
Boundary: Owns evidence routing for sensitive workloads, not HIPAA, GDPR, security, confidentiality, or provider-quality conclusions.
| Frozen scenario / field ID | Exact identity and evidence fields | Result | State |
|---|---|---|---|
batch58-data-retention-m3-r1source code | route=/compare/llm-api-data-retention; owner=data-retention; provider/seller/host/account/tier/endpoint/model/snapshot/region/feature/request=data-retention; scenario=source code; hard requirements; candidate service/account; retention/training/residency cells; satisfied/unknown; contract-review flag; safer architecture handoff; observed versus documented versus assumed inputs are labeled; artifact/schema/tool/job/result hashes and verification date=2026-09-02 | Unavailable — frozen data-retention fixture requires an exact source, identity, and result receipt | UNTESTED — module 3 rule is reproducible but no production observation is claimed |
batch58-data-retention-m3-r2customer-support transcript | route=/compare/llm-api-data-retention; owner=data-retention; provider/seller/host/account/tier/endpoint/model/snapshot/region/feature/request=data-retention; scenario=customer-support transcript; hard requirements; candidate service/account; retention/training/residency cells; satisfied/unknown; contract-review flag; safer architecture handoff; observed versus documented versus assumed inputs are labeled; artifact/schema/tool/job/result hashes and verification date=2026-09-02 | Unavailable — frozen data-retention fixture requires an exact source, identity, and result receipt | UNTESTED — module 3 rule is reproducible but no production observation is claimed |
batch58-data-retention-m3-r3health record | route=/compare/llm-api-data-retention; owner=data-retention; provider/seller/host/account/tier/endpoint/model/snapshot/region/feature/request=data-retention; scenario=health record; hard requirements; candidate service/account; retention/training/residency cells; satisfied/unknown; contract-review flag; safer architecture handoff; observed versus documented versus assumed inputs are labeled; artifact/schema/tool/job/result hashes and verification date=2026-09-02 | Unavailable — frozen data-retention fixture requires an exact source, identity, and result receipt | UNTESTED — module 3 rule is reproducible but no production observation is claimed |
batch58-data-retention-m3-r4financial document | route=/compare/llm-api-data-retention; owner=data-retention; provider/seller/host/account/tier/endpoint/model/snapshot/region/feature/request=data-retention; scenario=financial document; hard requirements; candidate service/account; retention/training/residency cells; satisfied/unknown; contract-review flag; safer architecture handoff; observed versus documented versus assumed inputs are labeled; artifact/schema/tool/job/result hashes and verification date=2026-09-02 | Unavailable — frozen data-retention fixture requires an exact source, identity, and result receipt | UNTESTED — module 3 rule is reproducible but no production observation is claimed |
batch58-data-retention-m3-r5public-content generation | route=/compare/llm-api-data-retention; owner=data-retention; provider/seller/host/account/tier/endpoint/model/snapshot/region/feature/request=data-retention; scenario=public-content generation; hard requirements; candidate service/account; retention/training/residency cells; satisfied/unknown; contract-review flag; safer architecture handoff; observed versus documented versus assumed inputs are labeled; artifact/schema/tool/job/result hashes and verification date=2026-09-02 | Unavailable — frozen data-retention fixture requires an exact source, identity, and result receipt | UNTESTED — module 3 rule is reproducible but no production observation is claimed |
batch58-data-retention-m3-r6synthetic evaluation | route=/compare/llm-api-data-retention; owner=data-retention; provider/seller/host/account/tier/endpoint/model/snapshot/region/feature/request=data-retention; scenario=synthetic evaluation; hard requirements; candidate service/account; retention/training/residency cells; satisfied/unknown; contract-review flag; safer architecture handoff; observed versus documented versus assumed inputs are labeled; artifact/schema/tool/job/result hashes and verification date=2026-09-02 | Unavailable — frozen data-retention fixture requires an exact source, identity, and result receipt | UNTESTED — module 3 rule is reproducible but no production observation is claimed |
First-party citation: Google Gemini API additional terms. Verified 2026-09-02; missing or conflicting joins fail closed.
Method and limitations: this board exposes deterministic rules, first-party citations, and dated evidence identities. It does not invent volume, coverage, entitlement, retention, residency, quota, capacity, feature support, quality, price, reliability, or legal conclusions. Run the data-retention evidence flow →