Jev data handling and customization
Two sentences from the models page matter more than most vendor slogans:
- Jev is not trained on customer requests or responses.
- Jev is not fine-tuned or LoRA-adapted with customer data. The same weights serve every account.
You specialize behavior through the request: put proprietary material in state, encode domain rules in instructions and criteria, and compose answers in code. The AutoResearch cookbook is the documented path if you want a downstream classical model on top of Jev’s probabilities.
Zero data retention
TypeSafe points to its Legal index for the Data Processing Agreement, Privacy Policy, and zero data retention (ZDR) for enterprise customers. We will not invent which plan includes ZDR or how it is enabled on the first-party API.
Vercel’s AI Gateway changelog describes Zero Data Retention and No Training as per-request Gateway options when you call typesafe-ai/jev through the Gateway. That is a Vercel product surface, not a substitute for TypeSafe’s own legal terms.
Read docs.typesafe.ai/legal and your contract. This page is a map, not a DPA.
Sources
Public TypeSafe or adjacent documentation only. No private claims.