OfficialJev Guides & Articles
Data Processing Addendum
TypeSafe's data processing addendum, last updated 24 April 2026. For customer personal data, the customer is the controller and TypeSafe is the processor.
- Format
- Docs
- Published by
- TypeSafe AI
- Last verified
- Oct 2026
Works forJev for Verification
Used inJev for Legal & Compliance
Highlights
- Last updated 24 April 2026.
- It forms part of the agreement between the customer and TypeSafe.
- The customer is the controller and business. TypeSafe is the processor and service provider.
Watch out
Capitalized terms that this page does not define come from the main agreement.
Questions about this entry
Short answers drawn from the linked project or page.
For customer personal data, the customer is the controller and business, and TypeSafe is the processor and service provider. It forms part of the agreement and was last updated 24 April 2026.
Capitalized terms that the DPA does not define come from the main agreement, per the caveat.
Reasonable advance notice before a new subprocessor gets access to customer personal data. A customer may object within 15 days of that notice on reasonable privacy or security grounds, and the parties then work in good faith to address the objection.
It will notify the customer without undue delay and in any case within 72 hours after becoming aware of any accidental or unauthorized access to, or disclosure or use of, customer personal data.
No. It says TypeSafe will not sell or share customer personal data under the CCPA, will not retain or use it beyond the documented instructions, and will not combine it with third-party personal data except as permitted by law.
The DPA controls to the extent of any inconsistency or conflict with the other terms of the agreement, stated in its conflicts in interpretation section.
Schedule I sets out the subject matter, nature and purpose of the processing, the types of customer personal data, and the categories of applicable data subjects.
More Jev resources like this
TypeSafe's privacy policy, last updated 19 November 2025. It covers the website, the playground, and APIs that link to the policy.
Jev Guides & ArticlesDocs#official#legal#privacy
Official
TypeSafe's website terms, last updated 19 September 2026. They cover typesafe.ai. A separate agreement covers the products and services.
Jev Guides & ArticlesDocs#official#legal
Official
TypeSafe AI, Inc.'s master customer agreement, last updated 23 September 2026. It is the contract for services named in an order.
Jev Guides & ArticlesDocs#official#legal
Official
Rules for using TypeSafe services, last updated 23 September 2026. They ban illegal content, rights violations, and phishing or spoofing.
Jev Guides & ArticlesDocs#official#legal
Official
The hub for TypeSafe's legal and policy documents, plus the data commitments attached to the API.
Jev Guides & ArticlesDocs#official#docs#privacy
Official
The index of TypeSafe's worked examples, from parallel questions and reranking to guardrails, date extraction, and self-consistency, each with datasets and measured results.
Jev Guides & ArticlesDocs#official#docs#cookbook
Official
From the Jev guides
Original write-ups on what this entry is for.
The typed-answer shape removes a category of data risk, not all of it. Zero data retention per surface, the legal set to read, and the controls that remain yours to run.
Jev Guides & Articles#privacy#compliance#legal
Read article
TypeSafe serves Jev from one API. A second tier of independent sites wraps it with their own keys, credits, and playgrounds. How to read the disclaimers before you paste a key.
Jev Guides & Articles#ecosystem#trust#hosting
Read article
The first ten days produced three receptions that rarely meet: a Product Hunt launch, a 620-point Hacker News thread, and a r/LocalLLaMA that doubted the framing. Reading them together.
Jev Guides & Articles#launch#community#reception
Read article
From the Jev community
Posts from builders shipping with Jev right now.