Skip to content

ABOUT THIS SCREEN


Designed For:

Users who want to understand the data-related obligations in their contracts.

 

Purpose:

This screen identifies 7 obligations that may be found in data processing agreements and presents them in a structured format.

Each obligation is broken down into sub-parts, as follows:
1. Responsible Party

2. Obligation Summary (may also include a standardized version of the same, where available)
3. Consequence Summary (may also include a standardized version of the same, where available)
4. Obligation Trigger
5. Trigger Type
6. Obligation Type

 

Limitations, Assumptions, Details:

This screen has been validated on a majority of data processing agreements, and a small subset of other general commercial agreements. Evaluation on a random sample of 30+ contracts achieved ≥85% precision and ≥90% recall across all questions.  

Some questions return detailed summaries; others return yes/no. This screen may only return a single obligation per question. Standardized outputs are generated only when a single obligation or consequence exists. Time references such as “business days” are ignored. See the user guidance for details on each question.


ABOUT THE AUTHOR


Maya Lash

Maya Lash

Maya is a Senior Legal Knowledge Engineer at Agiloft, where she leverages her legal expertise to enhance contract lifecycle management through AI-driven features. Prior to joining Agiloft, she worked at Zuva, where she began her career in Legal Knowledge Engineering, focusing on AI for contracts.

Before transitioning into Legal Tech, Maya practiced as a corporate lawyer, advising startups and high-growth companies on financing, exits, and general corporate matters. During her legal career, she also began exploring ways to integrate AI into legal workflows and is licensed to practice in both Canada and Australia.