Semantic Cache
Semantic caching is disabled for the first launch. Founding does not include semantic caching. The exact-request cache is a separate in-memory optimization for eligible identical requests; its eligibility depends on request shape and provider cache directives. Do not rely on a cache hit for correctness or assume every request is cached.
There is no customer Settings → Caching control. These docs do not promise a cache-hit response header.
If semantic caching is explicitly enabled in a future deployment, eligible Growth+ requests send prompts to OpenAI for embeddings, retain hashes and unencrypted embeddings, and store encrypted responses per customer with enforced retention. There is no separate customer opt-out. This is distinct from ordinary routing, which does not persist prompt plaintext.
See privacy and security and response headers.