Goal
Decide whether the vendor's data terms are good enough to sign, and what to negotiate if they are not.
Inputs
- Vendor and tool: [e.g. cloud helpdesk software]
- Data the tool will hold: [e.g. customer names, emails, order history, chat transcripts]
- Where your customers and staff are: [e.g. India, EU, United States]
- The agreement text: [paste the data processing agreement or the privacy and security sections of the contract]
- Your own commitments to customers: [e.g. data stays in India, deletion within 30 days on request]
Check each point
- Roles: who is the controller and who is the processor, and processing only on your instructions.
- Purpose and data types listed, nothing beyond what the service needs.
- Sub-processors: a published list, notice before changes, a right to object.
- Data location and cross-border transfer terms.
- Security measures described in concrete terms, not only "industry standard".
- Breach notification: a time limit in hours and what the notice includes.
- Help with data subject requests such as access and deletion.
- Deletion or return of data at the end of the contract, with a deadline.
- Audit rights or independent reports offered in their place.
- Liability and how it relates to the main contract's cap.
Output format
- | Point | Present, missing or weak | Clause reference | Risk | What to ask for |
- Questions to send the vendor, numbered.
- A sign-off memo of under 150 words: sign, sign with changes, or do not sign, and why.
Quality rules
- Quote clause numbers, not long passages.
- Mark anything that depends on a specific law as [confirm with counsel]; this is not legal advice.
- Judge only the text pasted; say if key sections seem missing.






