Legal

Data Processing Agreement

Effective [EFFECTIVE DATE] · Last updated

This Data Processing Agreement ("DPA") is between the business that uses Chatlian ("customer", the controller) and [COMPANY NAME], [STREET AND NUMBER], [POSTCODE] [CITY], [COUNTRY] ("Chatlian", the processor). It is part of the Terms of Service and applies whenever Chatlian processes personal data on the customer's behalf. It takes effect when the customer accepts the Terms of Service. [IF CUSTOMERS NEED A SIGNED COPY: HOW TO REQUEST ONE.]

1. Subject matter and duration

Chatlian processes personal data to provide the Chatlian service to the customer: hosting chatbots, answering the customer's website visitors with AI, storing conversations and leads, and the related dashboard features. The processing lasts as long as the Terms of Service. Annex 1 describes the processing in detail.

2. Instructions

Chatlian processes the personal data only on the customer's documented instructions. The Terms of Service, this DPA and the customer's settings and actions in the dashboard (for example the chatbot's model, lead extraction settings and deletions of conversations, leads and workspaces) are those instructions. Chatlian tells the customer if it believes an instruction breaks data protection law. If the law requires Chatlian to process data otherwise, it tells the customer first, unless the law forbids that.

3. Confidentiality

Chatlian ensures that everyone it authorises to process the personal data is bound to confidentiality.

4. Security

Chatlian takes the technical and organisational measures described in Annex 2 (Art. 32 GDPR) and may update them, as long as the level of protection does not drop.

5. Sub-processors

  • The customer gives general authorisation for Chatlian to use sub-processors. The current ones are on the list of sub-processors.
  • Chatlian updates that list and informs the customer [NUMBER] days before it adds or replaces a sub-processor. The customer can object for a reasonable data protection reason within that time. If the parties cannot resolve the objection, the customer may end the affected service.
  • Chatlian imposes data protection obligations on each sub-processor that are equivalent to this DPA, and remains responsible for them.
  • Some sub-processors are outside the EU/EEA. Chatlian makes such transfers only with a safeguard under Chapter V GDPR: [TRANSFER SAFEGUARDS, FOR EXAMPLE THE EU-US DATA PRIVACY FRAMEWORK OR STANDARD CONTRACTUAL CLAUSES].

6. Assistance

  • Data subject requests. Chatlian helps the customer answer requests from visitors to access, correct, delete, restrict or port their data. The customer can view and delete conversations and leads in the dashboard. Chatlian forwards requests it receives directly to the customer.
  • Other obligations. Chatlian helps the customer, as far as it can, with security, breach notifications, data protection impact assessments and consultations with authorities (Art. 32 to 36 GDPR).

7. Personal data breaches

Chatlian notifies the customer without undue delay, and within [NUMBER] hours, after it becomes aware of a personal data breach affecting the customer's data, with the information the customer needs to meet its own obligations.

8. Deletion and return

When the Terms of Service end, Chatlian deletes the customer's personal data within [NUMBER] days, unless the law requires it to keep the data. Before that, the customer can export its leads from the dashboard. Deleting a workspace in the dashboard deletes its chatbots, conversations and leads.

9. Information and audits

Chatlian makes available the information needed to show that it meets this DPA, and allows and contributes to audits by the customer or an auditor it appoints, with reasonable notice and at most once a year unless there is a breach or an authority requires it. [AUDIT COSTS AND PROCEDURE.]

10. Liability and precedence

Liability follows the Terms of Service and Art. 82 GDPR. If this DPA and the Terms of Service conflict about data protection, this DPA prevails. This DPA is governed by [GOVERNING LAW, FOR EXAMPLE "THE LAWS OF THE FEDERAL REPUBLIC OF GERMANY"].

Annex 1: Details of the processing

  • Categories of data subjects: visitors of the customer's websites who use the chat widget; the customer's staff who reply to visitors; people named in the knowledge the customer adds.
  • Types of personal data: chat messages and their times; the website hostname where the chat took place; widget session identifiers; AI analysis of each visitor message (sentiment, whether it shares contact details, whether the visitor asks for a person); lead details the visitor shares (such as name, email, phone number, company, job title, interests and custom details the customer defines); IP addresses in short-lived rate-limit counters; personal data contained in knowledge sources.
  • Special categories: none intended. The customer must not use chatbots to collect special categories of personal data without a legal basis and safeguards.
  • Nature and purpose: storing and displaying conversations and leads; sending conversations, instructions and knowledge passages to the AI provider the customer chose to generate replies, analyse messages and extract lead details; creating embeddings of knowledge and visitor questions to search the knowledge; human handoff to the customer's staff; usage counting; abuse prevention.
  • Retention: data is kept until the customer deletes it (or deletes its workspace) in the dashboard, on request, or at the end of the agreement (section 8). [RETENTION SETTINGS, ONCE AVAILABLE IN THE DASHBOARD.]

Annex 2: Technical and organisational measures

  • Access control: dashboard access only with an account; passwords stored as hashes; optional two-factor login with an authenticator app; rate limits on sign-in and other account actions; bot protection on sign-in, sign-up, password and account forms.
  • Separation of customers: every workspace's data is tied to that workspace, and each read and write checks that the signed-in user is a member with a role that allows it.
  • Roles: owners, admins and members have different permissions (for example, only owners and admins can delete conversations and leads).
  • Widget sessions: visitors get a session token issued by the server, stored by Chatlian only as a hash, sent only in request headers (never in URLs), and expired after 30 minutes without activity; new sessions are accepted only from the websites the customer allows.
  • Abuse protection: limits on new chat sessions per IP address, messages per session and messages per chatbot per day; bot protection on widget messages.
  • Transport and hosting: the service runs on the infrastructure of the hosting and database sub-processors. [ENCRYPTION IN TRANSIT AND AT REST AS PROVIDED BY THE HOSTING AND DATABASE PROVIDERS.]
  • Organisational measures: [STAFF ACCESS POLICY, CONFIDENTIALITY UNDERTAKINGS, INCIDENT RESPONSE, BACKUPS AND RECOVERY.]

Annex 3: Sub-processors

See the list of sub-processors.