Data Processing Addendum
Status: DRAFT. Written by Claude on 2026-11-11 from how Dave works today. It is not legal advice. Danilo and a lawyer replace this text and fill in every [bracket], then delete this line.
Last updated: [date]
This addendum is part of the Terms of Service between [Dependables legal name], [address] ("Processor") and the business that uses Dave ("Customer"). It applies when Dave processes personal data for the Customer under data protection law such as the GDPR and the UK GDPR.
Roles
The Customer is the controller of the personal data in its Slack workspace and its connected apps. Dependables is the processor and processes that data only on the Customer's documented instructions. The Terms, Dave's settings and the changes the Customer approves are those instructions.
The processing
- Subject: providing Dave, an AI assistant in Slack that reads the Customer's connected apps to answer questions and makes changes only after approval.
- Duration: while the Customer uses Dave, then until deletion as the Privacy Policy says.
- Data subjects: the Customer's staff who use Slack, and people whose data is in the Customer's connected apps, such as its customers and contacts.
- Types of data: names, Slack ids, messages to and from Dave, and whatever the connected apps hold that Dave reads, such as contact names, emails and order details.
- Special categories: none intended. The Customer should not ask Dave to process them.
Processor's commitments
- Process the data only to provide Dave, and tell the Customer if an instruction seems to break data protection law.
- Make sure everyone who handles the data is bound to confidentiality.
- Keep appropriate security measures, including: each account's data kept apart from every other's; encryption in transit; access to production limited to named staff behind single sign-on; error reports that hold ids and never content; changes to the Customer's apps only after an Owner or Approver approves.
- Help the Customer answer requests from data subjects and with data protection impact assessments, as far as Dave's role allows.
- Tell the Customer without undue delay, and within [48] hours, after becoming aware of a personal data breach that affects it.
- At the end, delete the Customer's data as the Privacy Policy says, keeping only the billing records the law requires.
- Give the Customer the information it needs to show compliance, and allow [reasonable audits on [30] days' notice].
Subprocessors
The Customer agrees to these subprocessors: Cloudflare (hosting, storage, queues), Slack (messaging), OpenRouter, Anthropic and OpenAI (AI models), Composio (app connections and their logins), Stripe (payments), WorkOS (web sign-in) and Resend (email). Each is bound by data protection terms no weaker than these. We tell Customers [30] days before adding or replacing one, and a Customer may object for a good reason.
Transfers
Where data leaves the EU, EEA or UK, the [EU Standard Contractual Clauses and the UK Addendum] apply.