Jev privacy guide
Privacy work is minimization + contract. Jev will happily score whatever text you send. That is not consent.
Unofficial minimization notes — we are not your DPO, not a party to your DPA, and not TypeSafe Legal. TypeSafe models page: not trained on customer requests/responses; ZDR for enterprise customers — vendor statements. Read Legal. Replicas are not Jev and not endorsed.
Independent angle (cover, do not clone)
Win delta (myth-faq): “does Jev train on your data?” lives here as a GEO atom, not a cloned FAQ URL.
Practical minimization
Strip unused CRM fields. Hash or drop identifiers you do not judge. Never send PAN, full ID images, or secrets. Transcribe media yourself if you must judge content.
Doors
Gateway vendors have their own privacy cards. The channel matrix is not a DPA.
What to write in your RoPA (you, not us)
Purpose: language judgment for routing/screening. Recipients: TypeSafe and/or the gateway you chose. Fields: the filtered state you actually send. Retention: your traces. Legal basis: yours.
If a door’s card disagrees with TypeSafe on context length or logging, believe the door for that traffic and document the split.
RoPA fields you actually send
Write the record of processing against the filtered state, not against the warehouse table you could have sent. A useful inventory:
- Purpose — language judgment for routing, screening, or completeness — not “AI” as a blob.
- Data subjects — whose text is in the ticket / lead / passage.
- Categories — only fields that appear in the POST to
https://api.typesafe.ai/v1/systemone(or the gateway). - Recipients — TypeSafe and/or the gateway you chose. Two doors = two recipient lines.
- Retention — your traces (
response.model, probabilities, action, SHA). Ask TypeSafe what they retain; do not take our word. - Legal basis — yours. We will not pick one.
- Transfers — door residency, in writing.
Strip unused CRM fields. Hash or drop identifiers you do not judge. Never send PAN, full ID images, or secrets. Transcribe media yourself if you must judge content — Jev does not take raw image/audio/video as a first-class input in the public loop we cite.
If a door’s card disagrees with TypeSafe on context length or logging, believe the door for that traffic and document the split. The channel matrix is not a DPA. Security controls (injection, keys) live on security; explainer-level handling on data handling.
We are not your DPO
Counsel asks TypeSafe the training / ZDR / subprocessor questions — questions for legal. Engineers bring the field list. jev.pro does not see your production traffic, does not issue keys, and does not countersign.
Schema-safe ≠ a lawful basis. A Noul that stayed in [0,1] is not a DPIA. High-risk uses (clinical, hiring, credit, identity) start from no unless counsel designs a narrow admin hop.
Vendor list price and “not trained on customer requests” stay labeled vendor. Confirm models and Legal on the date you ship.
When not to use this page’s advice
Do not file this URL as your privacy policy. Do not treat jev.pro as a processor. Do not run SemIf/OpenJev under TypeSafe’s representations — different processor, not Jev and not endorsed. Do not send the whole CRM “because ZDR.” Unused state still leaves your network.
What this page does not claim
- Not legal advice.
- Not a GDPR/CCPA completeness claim.
FAQ
Does Jev train on my data? TypeSafe says no on customer requests/responses. Confirm the current Legal text.
Is jev.pro a processor? This site is a public guide. We do not process your production traffic.
Open clones? If you run SemIf/OpenJev, that is a different processor entirely — and not Jev.
Can I put “see jev.pro privacy guide” in the RoPA? No. Write the fields you send. This page is unofficial orientation.
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: what is jev, security guide, data handling. Canonical: https://docs.typesafe.ai.