Questions for legal
This page is not legal advice. It is a list in-house counsel often wants engineers to answer before Jev touches regulated workflows.
Independent unofficial site. Official Legal: docs.typesafe.ai/legal.
Affiliation
jev.pro is not TypeSafe. We do not bind TypeSafe. Quotes of their docs can go stale.
Ask engineers
What personal data is in state? Which jurisdictions? Any health/employment/credit? Who is the human in the loop? Can a user contest an auto-action? How long are traces kept?
Ask TypeSafe (via your buyer)
DPA, ZDR, training representations, subprocessors, breach notice — current documents, not a blog.
High-risk list (start from no)
Clinical protocols, hiring decisions, credit, identity proofing, automated legal advice, anything that needs a licensed human. Comparison pages in this batch spell out the split. Counsel still decides.
What this page does not claim
- Not a legal memo.
FAQ
Can we say Jev cannot hallucinate in a contract? Not as factual correctness. Schema constraint ≠ truth.
Open-source Jev? Hosted Jev is not. Clones are other parties.
Disclaimer
This is an independent unofficial site and is not affiliated with TypeSafe AI; official documentation is available at https://docs.typesafe.ai. Never treat jev.pro as TypeSafe official documentation. We do not sell, issue, or proxy API keys.
Open-cluster pages are independent field-guide notes. Replicas and third-party interfaces mentioned anywhere on jev.pro are not Jev and not endorsed. Hub: Open. Siblings: privacy guide, questions for buyers, vs legal intake. Canonical: https://docs.typesafe.ai.
Sources
Public TypeSafe or adjacent documentation only. No private claims.