Version 1.0

Data Processing Agreement

This Data Processing Agreement ("DPA") is entered into between:

SRI Group BV, a private limited company under Belgian law, with its registered office at Korte Gasthuisstraat 18 bus 301, 2000 Antwerpen, Belgium, enterprise number 1037.052.239, RPR Antwerpen, division Antwerpen, which provides the ChatterLab service ("ChatterLab", "we", "us"); and

the business that accepts this DPA as set out in section 17 ("Customer", "you").

Each a "Party", together the "Parties".

1. Definitions

1.1 Capitalised terms used but not defined in this DPA have the meaning given to them in the Agreement or, failing that, in the GDPR.

1.2 In this DPA:

  • "Agreement" means the agreement between the Parties for the use of the Service, consisting of the ChatterLab Terms of Service published at chatterlab.ai/legal/terms, the plan the Customer has chosen, and this DPA.
  • "Customer Personal Data" means any Personal Data processed by ChatterLab on behalf of the Customer in providing the Service, as described in Annex I.
  • "Data Protection Laws" means all laws on the protection of personal data that apply to the processing of Customer Personal Data under the Agreement, including the GDPR, the Belgian Act of 30 July 2018 on the protection of natural persons with regard to the processing of personal data, the UK GDPR and the UK Data Protection Act 2018 where they apply, and the Swiss Federal Act on Data Protection where it applies.
  • "GDPR" means Regulation (EU) 2016/679.
  • "UK GDPR" means the GDPR as it forms part of the law of the United Kingdom.
  • "Personal Data", "Processing", "Controller", "Processor", "Data Subject", "Supervisory Authority" and "Personal Data Breach" have the meanings given in the GDPR, and their equivalents under other Data Protection Laws.
  • "Service" means the ChatterLab platform and everything provided through it: the dashboard, the chat widget, the channels, the API, the MCP server, reports, client dashboards and related features, as described in its documentation at chatterlab.ai/docs ("Documentation").
  • "Workspace" means the Customer's account in the Service, and "Owner" the person recorded in the Service as its owner.
  • "Users" means the persons the Customer allows to use its Workspace, including members it invites, and anyone using its API keys or the AI assistants it connects to the Service.
  • "Visitor" means a natural person who uses an agent of the Customer, for example by chatting in the widget, writing to an agent's e-mail address, leaving contact details or opening a ticket.
  • "Sub-processor" means a third party engaged by ChatterLab that processes Customer Personal Data on ChatterLab's behalf.
  • "SCCs" means the standard contractual clauses for the transfer of personal data to third countries adopted by the European Commission in Implementing Decision (EU) 2021/914 of 4 June 2021, as amended or replaced.
  • "UK Addendum" means the International Data Transfer Addendum to the EU Commission Standard Contractual Clauses issued by the UK Information Commissioner under section 119A of the UK Data Protection Act 2018, version B1.0, in force from 21 March 2022, as amended or replaced.
  • "Restricted Transfer" means a transfer of Personal Data that, under Data Protection Laws, requires appropriate safeguards because the recipient is in a country not recognised as providing an adequate level of protection.

2. Scope and roles

2.1 Roles. For Customer Personal Data, the Customer is the Controller and ChatterLab is a Processor. Where the Customer itself acts as a Processor on behalf of a third party, such as an agency running an agent for its own client, ChatterLab is a sub-processor of the Customer, and the Customer warrants that its instructions, including the engagement of ChatterLab and of the Sub-processors listed in Annex III, have been authorised by the relevant Controller. The Customer is ChatterLab's sole point of contact, is responsible for all communication with that Controller, and shall pass on to it without delay the information ChatterLab gives under sections 5 and 7.

2.2 ChatterLab's own processing. ChatterLab processes Personal Data as an independent Controller, and not under this DPA, for: the Customer's account and the accounts of its Users, including their sign-in; billing, payment and tax records; usage metering; the security of ChatterLab's systems as a whole, including the detection of attacks across customers and the request logs of its hosting provider; compliance with legal obligations; and statistics that do not identify any Data Subject. That processing is described in ChatterLab's privacy notice. ChatterLab does not use Customer Personal Data to train artificial intelligence models, and does not sell it.

2.3 Business use only. The Customer confirms that it enters into the Agreement in the course of its trade, business, craft or profession, and not as a consumer.

2.4 Precedence. In case of conflict on the processing of Personal Data, the SCCs and the UK Addendum (where they apply) prevail over this DPA, and this DPA prevails over the other parts of the Agreement. In all other respects, the Agreement prevails.

3. The Customer's instructions and responsibilities

3.1 Instructions. ChatterLab processes Customer Personal Data only on the Customer's documented instructions, including with regard to transfers of Customer Personal Data to a third country or an international organisation. The Customer instructs ChatterLab to process Customer Personal Data:

(a) to provide the Service in accordance with the Agreement, including the transfers set out in section 6 and Annex III;

(b) as initiated by the Customer and its Users through the Service, including the configuration of agents, sources, channels, integrations, API keys and connected assistants;

(c) to provide support the Customer or its Users request, and to investigate incidents and abuse;

(d) to review answers of agents, and the questions and passages they rest on, where needed to find and correct faults in the Service, with access limited to ChatterLab's administrators; and

(e) as further instructed in writing by the Customer and accepted by ChatterLab.

These instructions are complete at the time of acceptance of this DPA. Further instructions must be consistent with the Agreement and with the functionality of the Service; ChatterLab may refuse an instruction that would require a change to the Service, or carry it out at its then-current rates.

3.2 Unlawful instructions. ChatterLab shall immediately inform the Customer if, in its opinion, an instruction infringes Data Protection Laws, and may suspend the processing concerned until the Customer confirms or amends the instruction. ChatterLab is not obliged to perform a comprehensive legal examination of the Customer's instructions.

3.3 Processing required by law. ChatterLab may process Customer Personal Data where required to do so by Union or Member State law to which it is subject. In that case, ChatterLab shall inform the Customer of that legal requirement before processing, unless that law prohibits such information on important grounds of public interest.

3.4 The Customer's responsibilities. The Customer is responsible for:

(a) the lawfulness of the processing of Customer Personal Data, including having a valid legal basis for it and for the Customer's instructions;

(b) informing Visitors and other Data Subjects, including through its own privacy notice, that its agent is operated with ChatterLab and how their data is processed, and providing any notice required by Article 50 of Regulation (EU) 2024/1689 (the "AI Act") that is not displayed by the Service;

(c) obtaining any consent required, including for cookies or similar technologies on its own website and for any feature of the Service that the Service makes conditional on consent;

(d) the content of its sources, its instructions to its agents and its configuration of the Service, including the choice of model, channels, integrations and the deletion of conversations;

(e) not configuring the Service to request special categories of Personal Data, data relating to criminal convictions and offences, or data of children, unless it has ensured that such processing is lawful, and warning Visitors in its notices not to share such data where its use case makes this likely;

(f) declaring truthfully the use case of each agent, and not using the Service for a use that is high-risk under the AI Act unless the Customer's plan expressly allows it; and

(g) the security of its Workspace, devices, API keys, report links and connected assistants, and the acts of its Users.

3.5 Third parties chosen by the Customer. Where the Customer connects the Service to a third-party service of its choice, including webhooks, helpdesks, scheduling tools, automation platforms, e-mail addresses, messaging accounts, API clients or AI assistants, ChatterLab transfers Customer Personal Data to that third party on the Customer's instruction. Such third parties are not Sub-processors of ChatterLab. The Customer is responsible for its relationship with them and for any data protection agreement with them, and ChatterLab is not responsible for their processing.

4. ChatterLab's obligations

4.1 Confidentiality. ChatterLab ensures that the persons it authorises to process Customer Personal Data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality, and access Customer Personal Data only to the extent necessary for the purposes set out in section 3.1.

4.2 Security. ChatterLab shall take all measures required pursuant to Article 32 of the GDPR. At the date of this DPA these include the measures described in Annex II, which the Customer, taking into account the state of the art, the costs of implementation and the nature, scope, context and purposes of the processing, agrees provide a level of security appropriate to the risk. ChatterLab may change the measures from time to time, provided that the overall level of protection is not materially reduced.

4.3 Data Subject requests. The Service provides the Customer with means, described in the Documentation and depending on its plan, to read, export and delete conversations, contact details, tickets and files, through the dashboard and, on plans that include it, the API. Taking into account the nature of the processing, ChatterLab shall assist the Customer by these means in fulfilling its obligation to respond to requests from Data Subjects. If ChatterLab receives a request directly from a Data Subject that relates to Customer Personal Data, it shall, where it can identify the Customer, refer the Data Subject to the Customer and shall not respond to the request itself, unless required by law. Assistance beyond the means provided by the Service is given at the Customer's cost, at ChatterLab's then-current rates, of which ChatterLab shall inform the Customer before incurring it.

4.4 Other assistance. Taking into account the nature of the processing and the information available to it, ChatterLab shall assist the Customer in ensuring compliance with Articles 32 to 36 of the GDPR, primarily by making available this DPA, its Annexes and the Documentation. Assistance beyond this is given at the Customer's cost, at ChatterLab's then-current rates, of which ChatterLab shall inform the Customer before incurring it.

5. Sub-processors

5.1 General authorisation. The Customer gives ChatterLab a general written authorisation to engage Sub-processors. The Sub-processors engaged at the date of this DPA are listed in Annex III, and the current list is published at chatterlab.ai/legal/subprocessors.

5.2 Changes. ChatterLab shall inform the Customer of any intended addition or replacement of a Sub-processor at least ten (10) days before that Sub-processor processes Customer Personal Data, by e-mail to the Owner and by updating the published list. The Customer may object to the change on reasonable grounds relating to the protection of Personal Data, by written notice to ChatterLab within those ten (10) days. ChatterLab shall answer the objection before the change takes effect, proposing a reasonable alternative or confirming the change. If the objection is not resolved, the Customer may, as its sole and exclusive remedy, terminate the Agreement by written notice with effect no later than the date the change takes effect for it, and ChatterLab shall refund the subscription fees prepaid for the period after termination. If the Customer does not object in time, it is deemed to have accepted the change.

5.3 Optional features. Where a Sub-processor processes Customer Personal Data only for a feature, channel, integration or model that the Customer chooses to enable or select, ChatterLab names the Sub-processor in the published list and in the Documentation of that feature before it processes Customer Personal Data, and the Customer authorises it by enabling or selecting the feature after it is named. Section 5.2 does not apply to it. The Customer may withdraw this authorisation at any time by disabling the feature.

5.4 Urgent replacement. Where a Sub-processor must be replaced urgently for reasons beyond ChatterLab's reasonable control, such as a security incident, the cessation of its service or a change of law, ChatterLab may replace it with shorter notice, informing the Customer before the replacement takes effect where possible and otherwise without delay. Section 5.2 applies to the Customer's right to object, the notice period running from the date the Customer is informed.

5.5 Obligations of Sub-processors. ChatterLab shall impose on each Sub-processor, by contract, in substance the same data protection obligations as set out in this DPA, in particular sufficient guarantees to implement appropriate technical and organisational measures, to the extent relevant to the services it provides. ChatterLab remains fully liable to the Customer for the performance of a Sub-processor's obligations as for its own, as provided by Article 28(4) of the GDPR, subject to section 11.1. On request, ChatterLab shall provide the Customer with a copy or summary of the data protection terms of a Sub-processor, to the extent it may share them.

6. International transfers

6.1 Location. ChatterLab hosts the application, its database and its file storage in the European Economic Area. Customer Personal Data is processed, including stored, outside the European Economic Area only by the Sub-processors and for the purposes indicated in Annex III.

6.2 Transfers to Sub-processors. Where a transfer of Customer Personal Data to a Sub-processor is a Restricted Transfer, ChatterLab ensures that it is made on the basis of an adequacy decision, including the EU-U.S. Data Privacy Framework where the Sub-processor is certified under it, or of the SCCs as incorporated in the Sub-processor's data processing terms, or other appropriate safeguards under Article 46 of the GDPR, together with such supplementary measures as are required. Annex III states the safeguard each Sub-processor provides.

6.3 Transfers to the Customer. Where the Customer is established in a country outside the European Economic Area that is not recognised as providing an adequate level of protection, and ChatterLab transfers Customer Personal Data to the Customer, the SCCs, module four (processor to controller), are incorporated into this DPA by reference and apply between ChatterLab as data exporter and the Customer as data importer, completed as follows: Customer Personal Data includes data ChatterLab collects in the European Economic Area on the Customer's behalf; clause 7 (docking clause) does not apply; clause 11(a), the optional language, does not apply; in clause 17 the Parties choose the law of Belgium; in clause 18 the Parties choose the courts of Belgium; Annex I of the SCCs is completed with the information in Annex I of this DPA.

6.4 United Kingdom. Where the UK GDPR applies to the processing of Customer Personal Data:

(a) references in this DPA to the GDPR, to Union or Member State law and to a Supervisory Authority are read as references to the UK GDPR, to the law of the United Kingdom and to the UK Information Commissioner;

(b) ChatterLab ensures that any transfer of such data to a Sub-processor, and any onward transfer by a Sub-processor, to a country the United Kingdom does not recognise as adequate is made under the UK Addendum, the UK International Data Transfer Agreement, the UK Extension to the EU-U.S. Data Privacy Framework where the recipient is certified under it, or another safeguard recognised under the UK GDPR; and

(c) where a transfer to the Customer under section 6.3 is a Restricted Transfer under the UK GDPR, the UK Addendum is incorporated into this DPA and applies to the SCCs of section 6.3: in Table 1 the start date is the date this DPA takes effect and the Parties are those at the head of this DPA and in Annex I; in Table 2 the Approved EU SCCs are those of section 6.3; in Table 3 the Appendix Information is set out in Annexes I, II and III; and in Table 4 neither Party may end the UK Addendum as set out in its Section 19.

The transfer of Customer Personal Data from the United Kingdom to ChatterLab in the European Economic Area is not a Restricted Transfer under the UK GDPR, the European Economic Area being recognised as adequate by the United Kingdom.

6.5 Switzerland. Where the Swiss Federal Act on Data Protection applies: (a) references to the GDPR are read as references to that Act, and references to a Supervisory Authority as references to the Federal Data Protection and Information Commissioner; and (b) ChatterLab ensures that any disclosure of such data by it or a Sub-processor to a country Switzerland does not recognise as adequate is made under the Swiss-U.S. Data Privacy Framework where the recipient is certified under it, or under the SCCs with the adaptations the Commissioner requires, including that the term "Member State" in their clause 18(c) does not prevent Data Subjects in Switzerland from bringing claims where they habitually reside.

6.6 Change of transfer mechanism. If a transfer mechanism relied on in this section 6 is invalidated, amended or replaced, or does not fit the Customer's situation, ChatterLab may rely on an alternative mechanism permitted by Data Protection Laws, and the Customer shall co-operate in putting it in place.

7. Personal Data Breaches

7.1 Notification. ChatterLab shall notify the Customer without undue delay after becoming aware of a Personal Data Breach affecting Customer Personal Data, by e-mail to the Owner.

7.2 Information. The notification shall describe, to the extent then known to ChatterLab, the nature of the Personal Data Breach, the categories and approximate number of Data Subjects and records concerned, the likely consequences, the measures taken or proposed to address it, and a contact point where more information can be obtained. Where it is not possible to provide this information at the same time, it may be provided in phases without undue further delay.

7.3 Measures and assistance. ChatterLab shall take reasonable measures to contain the Personal Data Breach and mitigate its possible adverse effects, and shall provide the Customer with reasonable assistance, taking into account the nature of the processing and the information available to it, to enable the Customer to meet its own obligations to notify the Supervisory Authority and Data Subjects. Notifying the Supervisory Authority and Data Subjects is the responsibility of the Customer as Controller.

7.4 No admission. A notification or response under this section 7 is not an acknowledgement by ChatterLab of any fault or liability.

7.5 Incidents caused by the Customer. Where a Personal Data Breach results from an act or omission of the Customer, its Users, its API keys, its connected assistants or the third parties it has chosen under section 3.5, such as the disclosure of a report link or an API key, ChatterLab shall still notify the Customer under section 7.1, and its assistance under section 7.3 is given at the Customer's cost.

8. Information and audits

8.1 Information. ChatterLab shall make available to the Customer, on written request, the information necessary to demonstrate compliance with this DPA and Article 28 of the GDPR. The Parties agree that this obligation is primarily fulfilled by this DPA and its Annexes, the Documentation, written answers to reasonable questionnaires, and the certifications, reports or data protection terms of Sub-processors that ChatterLab is permitted to share. Questionnaires are answered no more than once in any twelve-month period, except following a Personal Data Breach, a change of Sub-processor or a request of a Supervisory Authority.

8.2 Audits. Where the Customer reasonably considers that the information under section 8.1 is not sufficient to demonstrate compliance, where a Supervisory Authority requires it, or following a Personal Data Breach at ChatterLab affecting Customer Personal Data, ChatterLab shall allow for and contribute to audits, including inspections, by the Customer or an auditor it mandates, subject to the following conditions:

(a) the Customer gives at least thirty (30) days' written notice, describing the scope of the audit;

(b) the audit is carried out no more than once in any twelve-month period, unless a Supervisory Authority requires otherwise, during ChatterLab's normal business hours, without unreasonable disruption to its business, and remotely unless an on-site visit is strictly necessary;

(c) the audit is carried out by the Customer or by an independent auditor that is not a competitor of ChatterLab and is bound by obligations of confidentiality reasonably acceptable to ChatterLab;

(d) the audit does not extend to the data of other customers, to information subject to legal privilege or third-party confidentiality, or to the premises or systems of Sub-processors, whose compliance is demonstrated by the information under section 8.1;

(e) the Customer provides ChatterLab with a copy of the audit report free of charge, and treats it as confidential; and

(f) the Customer bears its own costs and reimburses ChatterLab's reasonable costs, including the time of its personnel at its then-current rates, unless the audit reveals a material breach of this DPA by ChatterLab.

9. Deletion and return

9.1 During the Agreement. The Customer can export and delete Customer Personal Data through the Service, as described in section 4.3. Customer Personal Data is retained as described in Annex I until it is deleted by the Customer, by the Service under its retention periods, or under section 9.2.

9.2 On termination. Within thirty (30) days after the termination of the Agreement, or after the Customer's written request to close its Workspace, ChatterLab shall delete the Customer Personal Data in its live systems, except as provided in section 9.4 or where Union or Member State law requires its storage, and shall confirm the deletion in writing on request. Before that deletion the Customer may export Customer Personal Data with the export functions of the Service. Where it no longer has access to them, ChatterLab shall, on a request received within that period, give it access to them again for the time needed to export.

9.3 Backups and copies. Deleted data remains in the backups of ChatterLab's database host until they are overwritten in the ordinary course, currently within fourteen (14) days, and is used only to restore the Service. Copies held by Sub-processors are deleted under the retention periods of their own terms.

9.4 Records kept after termination. All Customer Personal Data, the audit log of Annex I included, is deleted under section 9.2. The Customer is responsible for exporting, before termination, any record of the use of its agents it must keep, including under the AI Act. Records ChatterLab keeps as an independent Controller under section 2.2 are governed by its privacy notice.

10. Costs

Except where this DPA expressly provides otherwise, each Party bears its own costs of performing this DPA.

11. Liability

11.1 One cap for the whole relationship. The total aggregate liability of ChatterLab arising out of or in connection with this DPA and the Agreement, whether in contract, tort (including negligence), breach of statutory duty or otherwise, and including liability for its Sub-processors, shall not exceed the total amount of fees actually paid by the Customer to ChatterLab under the Agreement in the twelve (12) months preceding the event giving rise to the claim, or one hundred euros (EUR 100), whichever is higher. Claims under this DPA and under the other parts of the Agreement count together towards this single limit.

11.2 Excluded losses. ChatterLab shall not be liable for: (a) indirect or consequential loss; (b) loss of profit, revenue, turnover, business, contracts, goodwill or anticipated savings; (c) business interruption; (d) loss or corruption of data, except the reasonable cost of restoring it from the most recent available backup; or (e) loss arising from the Customer's instructions, configuration, content or the third parties it has chosen under section 3.5. Each of these exclusions is separate from the others. Points (a) to (d) do not apply to amounts recoverable under the last sentence of section 11.4, nor to the Customer's reasonable and documented costs of notifying a Supervisory Authority and Data Subjects of a Personal Data Breach caused by ChatterLab's breach of this DPA.

11.3 Answers of AI models. ChatterLab does not warrant that the answers of the Customer's agents, which are generated by AI models and not reviewed by ChatterLab, are accurate, complete or suitable for any purpose, and is not liable for decisions taken on the basis of them. This section does not limit ChatterLab's liability for its breach of this DPA, such as an answer that discloses data of another customer.

11.4 What is not limited. Nothing in this DPA or the Agreement limits or excludes liability for fraud, intent or gross negligence of ChatterLab or of its employees and agents, for death or personal injury, or any liability that cannot be limited or excluded under applicable law. The rights of Data Subjects under Article 82 of the GDPR against either Party are not affected by this section 11. As between the Parties, a Party that has paid compensation to a Data Subject may claim back from the other Party only the part of that compensation corresponding to the other Party's share of responsibility for the damage, and such a claim against ChatterLab is subject to section 11.1.

11.5 Fines. Administrative fines imposed on a Party by a Supervisory Authority are borne by that Party. To the extent permitted by law, a fine imposed on the Customer may be claimed from ChatterLab only to the extent it is directly caused by ChatterLab's breach of this DPA, and subject to section 11.1.

11.6 The Customer's responsibility. To the extent permitted by law, the Customer shall indemnify ChatterLab against claims of third parties, including Data Subjects and the Controller referred to in section 2.1, and against fines, damages and reasonable costs, including legal fees, to the extent they result from the Customer's breach of Data Protection Laws or of this DPA, from an instruction of the Customer that infringes Data Protection Laws, or from the content of its sources, and not to the extent they result from ChatterLab's breach of this DPA or of Data Protection Laws. ChatterLab shall notify the Customer promptly of any such claim, shall not settle it without the Customer's consent, which may not be unreasonably withheld, and shall allow the Customer to take part in its defence.

11.7 Time limit. Any claim by a Party against the other arising out of or in connection with this DPA must be brought within one (1) year after the claiming Party became aware, or should reasonably have become aware, of the facts giving rise to it.

11.8 Mitigation. Each Party shall take reasonable steps to mitigate any loss for which it claims against the other.

12. Term

This DPA applies for as long as ChatterLab processes Customer Personal Data on behalf of the Customer, and terminates automatically once ChatterLab no longer does so. Sections 9, 11, 15 and 16 survive its termination.

13. Changes to this DPA

13.1 ChatterLab may amend this DPA where reasonably necessary: to comply with Data Protection Laws or the decision of a Supervisory Authority or court; to reflect a change of transfer mechanism; to reflect changes in Sub-processors under section 5; or to reflect changes in the Service that do not materially reduce the protection of Customer Personal Data.

13.2 ChatterLab shall publish the amended DPA and inform the Owner at least thirty (30) days before an amendment that is not required by law takes effect. If the amendment materially and adversely affects the Customer, the Customer may terminate the Agreement by written notice before it takes effect, and ChatterLab shall refund the subscription fees prepaid for the period after termination. ChatterLab may ask the Customer to accept the amended DPA as set out in section 17; otherwise continued use of the Service after the amendment takes effect constitutes acceptance of it.

14. Notices

Notices under this DPA are given in writing, by e-mail. Notices to ChatterLab are sent to management@sri-group.eu. Notices to the Customer are sent to the e-mail address of the Owner, which the Customer shall keep current.

15. Governing law and jurisdiction

15.1 This DPA is governed by the laws of Belgium, without regard to its conflict of law rules, except where the SCCs or the UK Addendum provide otherwise for the matters they govern.

15.2 The courts of Antwerp, division Antwerp, have exclusive jurisdiction over any dispute arising out of or in connection with this DPA, except where the SCCs or the UK Addendum provide otherwise. This does not affect the right of a Data Subject to bring proceedings before the courts that Data Protection Laws make available to them.

16. Miscellaneous

16.1 Severability. If any provision of this DPA, or part of one, is held invalid or unenforceable, the remainder of this DPA remains in force, and the Parties shall replace the invalid or unenforceable provision with a valid and enforceable one that comes as close as possible to its intent.

16.2 Entire agreement. This DPA, with the Agreement, is the entire agreement of the Parties on the processing of Customer Personal Data, and supersedes any prior data processing terms between them. Terms proposed by the Customer, including in a purchase order or a data processing agreement of its own, do not apply unless ChatterLab has accepted them in a document signed by its authorised representative.

16.3 Language. This DPA is drawn up in English. A translation is for information only; the English text prevails.

16.4 No third-party rights. Except as provided by the SCCs and the UK Addendum, this DPA does not confer rights on any third party.

17. Acceptance and effective date

17.1 The Customer accepts this DPA, together with the Terms of Service, by pressing the button or ticking the box that refers to them when creating a Workspace or when asked to accept them on signing in, after being shown links to both texts; or by signing it. This DPA takes effect on the date of acceptance. Acceptance by a person on behalf of the Customer is a confirmation that the person is authorised to bind the Customer.

17.2 For a Customer whose Workspace existed before 1 January 2027, ChatterLab's obligations in sections 3 to 10 and the Annexes apply from that date or from the Customer's acceptance, whichever is earlier; the other provisions apply from the Customer's acceptance, which is given by accepting under section 17.1 or by continuing to use the Service after 1 January 2027 having been informed of this DPA by e-mail to the Owner at least thirty (30) days before.


Annex I. Description of the processing

1. Parties

  • Data exporter (Controller, or Processor under section 2.1): the Customer, as identified in its Workspace. Contact: the Owner.
  • Data importer (Processor): SRI Group BV, as identified at the head of this DPA. Contact: management@sri-group.eu.

2. Categories of Data Subjects

  • Visitors of the Customer's websites and channels who use its agents.
  • Persons who write to an agent's e-mail address or reply to a ticket.
  • Persons whose details the Customer's own website passes to the Service when signing in its Visitors.
  • Persons mentioned in the sources the Customer adds to its agents, such as web pages, documents and texts.
  • The Customer's clients, for an agent run on their behalf.

3. Categories of Personal Data

  • Messages Visitors send and the answers given, with the time, the sources used, quality measurements and the address of the page each question was asked on, with numbers and codes in it masked where the agent does not know the page.
  • A random identifier created in the Visitor's browser for the duration of the visit.
  • Ratings Visitors give to answers.
  • Contact details Visitors leave in the contact form, if the Customer has enabled it: the fields the Customer has chosen (such as name, e-mail address, telephone number, company), their consent to marketing where asked, the wording shown to them and the page.
  • Tickets, if the Customer has enabled them: the Visitor's e-mail address, name if given, question, the e-mails exchanged and the notes of the Customer's team.
  • E-mails to an agent, if the Customer has enabled e-mail as a channel: the sender's address, the subject and the new text of the message, and the answer sent.
  • Files Visitors send, if the Customer has enabled it, and the text read from them, including by text recognition for scanned documents.
  • For signed-in Visitors: the reference, name, e-mail address and context the Customer's website includes in the visitor token.
  • For an agent run for a client: the client's name and the address its reports are sent to.
  • Personal Data contained in the Customer's sources.
  • A keyed fingerprint of the Visitor's IP address, used for rate limiting.

4. Special categories of Personal Data

None intended. Visitors may nevertheless volunteer such data in free text or files. The safeguards are those of Annex II and the retention periods of section 7 below; the Customer's responsibilities are set out in section 3.4(e).

5. Nature and purposes of the processing

Hosting and storage; reading the Customer's websites and documents (crawling, text extraction and text recognition); dividing sources into passages and converting them and Visitors' questions into search vectors; searching the passages; generating answers with AI language models and checking answers against the passages; storing conversations; producing analytics, reports and dashboards for the Customer and, where the Customer chooses, for its clients; sending notifications, reports, ticket e-mails and, where enabled, answers by e-mail; preventing abuse and enforcing rate limits; support, the investigation of incidents and the correction of faults under section 3.1; and transferring data to third parties chosen by the Customer under section 3.5.

6. Frequency and duration

Continuous, for the duration of the Agreement and the period of section 9.

7. Retention

  • Conversations and sources: until deleted by the Customer, or with the agent.
  • Files Visitors send, and their text: 30 days; the file name stays with the conversation.
  • Files a Visitor attached but never sent: 2 hours.
  • Source files the Customer began to upload and never completed: 1 hour.
  • Contact details from the contact form: 3 years, or until deleted with the lead, its conversation or the agent.
  • Tickets: 2 years after being solved, or until deleted; a ticket that is never solved, until deleted.
  • Deliveries to the Customer's webhooks: 7 days.
  • Rate-limit fingerprints: 24 hours.
  • The audit log of the agents' actions and of changes, which records events and not the content of conversations: 2 years, or until the Workspace is closed.
  • Backups and copies: as set out in section 9.3.

Annex II. Technical and organisational measures

Location and infrastructure

  • The application runs in Frankfurt, Germany. The database is hosted in Frankfurt (AWS eu-central-1). Files are stored in a storage bucket restricted to the European Union jurisdiction.
  • Data in transit is encrypted with TLS. Data at rest is encrypted by the hosting providers.
  • Daily snapshots of the database are kept for 14 days, and point-in-time recovery is possible for 7 days.

Separation and access

  • Every record belongs to one Workspace, and the application reads and writes it only within that Workspace. An agent answers only from its own sources.
  • Users sign in through a dedicated authentication provider; ChatterLab does not see or store their passwords. Workspaces have roles (owner, admin, member) that limit what each User may do.
  • API keys are shown once and stored only as a cryptographic hash. Each key has one scope, can be restricted to one agent, and is rate limited. Connected AI assistants authenticate with tokens that are checked on every request.
  • Links to client dashboards are random tokens of 192 bits, can be replaced at any time, are kept out of search engines and do not pass on their address to other sites.
  • Secrets held for the Customer's helpdesks, webhooks and messaging accounts are encrypted with AES-256-GCM.
  • Access to production systems, including from administrators' own workstations, is limited to ChatterLab's administrators. The administrative console of the platform shows Workspace metadata, not the content of conversations.

Records

  • An audit log records changes to agents and settings, with the person, key or assistant that made them, and the actions of agents, for 2 years.

The AI components

  • Requests to the AI language models that write and check answers are sent through OpenRouter's European endpoint, and the account refuses any other route; a model that cannot be run in Europe is refused rather than sent elsewhere. Logging of prompts and answers at OpenRouter is switched off. For some models the provider may keep prompts and answers for a limited period to prevent abuse, and not for training; at the date of this DPA this applies to models served by Google. Converting text into search vectors is done by OpenAI in the United States, as set out in Annex III.
  • Customer Personal Data is not used to train AI models, by ChatterLab or, under their terms with ChatterLab, by its Sub-processors.
  • Agents do not call other systems of their own accord. They produce text, and buttons configured by the Customer that a Visitor may choose to open. Where the Customer has enabled e-mail as a channel, the answer is sent by e-mail to the sender. The chat displays text only, and shows the real destination of links.
  • Measures against prompt injection are applied to questions and to passages, including the removal of hidden text from crawled pages, and attempts are recorded in the audit log.

Visitors and their files

  • The widget sets no cookies and stores nothing in the Visitor's browser before the Visitor uses the chat, except where the Customer's website passes the Visitor's consent.
  • ChatterLab's database does not store Visitors' IP addresses; rate limiting uses a fingerprint made with a key that changes daily. The hosting provider's request logs, kept for about a day, include them.
  • Files sent by Visitors are recognised by their content. Images are redrawn by the widget before they are sent, and the server removes their embedded metadata, such as location. The files themselves are shown only to signed-in members of the Workspace; the text read from them is also available to the Customer's API keys and connected assistants.
  • The crawler fetches only public addresses on standard ports and refuses private and internal network addresses.

Abuse and availability

  • Rate limits per Visitor, per agent and per key, and spending limits per answer and per month.

Organisation

  • Persons with access to Customer Personal Data are bound by confidentiality.
  • Sub-processors are selected for their security and data protection commitments and bound by the agreements described in section 5.
  • Personal Data Breaches are handled under section 7.

Annex III. Sub-processors

At the date of this DPA. The current list is published at chatterlab.ai/legal/subprocessors.

Sub-processorPurposeLocation of processingTransfer safeguard
Vercel Inc. (United States)Hosting of the applicationThe application runs in Frankfurt, Germany; requests pass through Vercel's global network, and Vercel names the United States as its primary locationEU-U.S. Data Privacy Framework, its UK Extension and the Swiss-U.S. framework, and SCCs under its data processing addendum
Databricks, Inc. (United States), for Neon, on Amazon Web ServicesDatabaseFrankfurt, Germany (AWS eu-central-1)EU-U.S. Data Privacy Framework, its UK Extension and the Swiss-U.S. framework, and SCCs under its data processing addendum
Cloudflare, Inc. (United States)Storage of files (R2)Files stored in the European Union jurisdictionEU-U.S. Data Privacy Framework, its UK Extension and the Swiss-U.S. framework, and SCCs under its data processing addendum
OpenRouter, Inc. (United States)Routing of requests to AI language models: answers, the check of answers, the rewording of follow-up questionsPrompts and answers in Europe (EEA, United Kingdom, Switzerland) under its EU-only processing addendum; account, billing and operational records may be held in the United StatesSCCs under its data processing addendum
The providers to which OpenRouter routes the model chosen for an agent, as set by ChatterLab: at this date Microsoft (Azure), Amazon Web Services (Bedrock), Google (Vertex AI), Mistral AI and InceptronRunning the AI language modelEuropeUnder OpenRouter's agreements with them
Cortecs GmbH (Austria), using Mistral AIText recognition of scanned files sent by Visitors, where the Customer has enabled filesEuropean UnionNot applicable
OpenAI Ireland Ltd, with OpenAI OpCo, LLC (United States)Converting passages and questions into search vectorsUnited StatesSCCs under its data processing addendum
Plus Five Five, Inc. (Resend, United States)Sending reports, notifications, ticket e-mails and e-mail answers, and receiving repliesMail is sent from the European Union (Ireland); messages, metadata and logs are stored in the United StatesEU-U.S. Data Privacy Framework and its UK Extension, and SCCs under its data processing addendum

Clerk, Inc. provides the sign-in of the Customer's Users, which ChatterLab processes as Controller under section 2.2 of the DPA; it does not process Customer Personal Data. Stripe processes payment data for ChatterLab's billing under section 2.2 and does not process Customer Personal Data.