Questo documento è disponibile solo in inglese.
Documenti
Data Processing Agreement (Article 28 GDPR)
Version 2, in force from its publication at chattopus.com/data-processing-agreement.
Parties
Between
the customer identified in the Chattopus account or in the order form (the “Customer”),
and
ERBA INTERACTIVE, with its registered office at Via Cantonale 62, 6983 Magliaso, Svizzera (the “Provider”),
together, the “Parties”.
Recitals
A. The Provider provides the Chattopus service: a support chat to be installed on websites which, according to the Customer's plan and settings, answers visitors with an artificial intelligence system on the basis of the knowledge base provided by the Customer, through the artificial intelligence provider chosen and contracted by the Customer (Article 8.9), or with automatic replies drawn from the Customer's frequently asked questions, or with the Customer's people only; it allows visitors to ask at any time for a person to step in and allows the Customer's operators to reply from a dashboard (the “Service”), under the conditions of the Terms of Service published at chattopus.com/terms (the “Terms”).
B. To provide the Service, the Provider processes personal data on behalf of the Customer.
C. With this agreement (the “DPA”) the Parties govern that processing under Article 28(3) and (4) of Regulation (EU) 2016/679.
The recitals and the annexes form an integral part of the DPA.
1. Definitions
1.1 “GDPR”: Regulation (EU) 2016/679. “Italian Privacy Code”: Legislative Decree 196/2003, as amended by Legislative Decree 101/2018. “Applicable Law”: the GDPR, the Italian Privacy Code, the measures of the Italian Data Protection Authority (Garante per la protezione dei dati personali) and any other Union or national law on the protection of personal data that applies to the processing.
1.2 The terms “personal data”, “processing”, “controller”, “processor”, “data subject”, “personal data breach” and “special categories of data” have the meaning given to them in Articles 4 and 9 of the GDPR.
1.3 “Customer Data”: the personal data processed by the Provider on behalf of the Customer in providing the Service, described in Annex 1.
1.4 “sub-processor”: any other processor engaged by the Provider to carry out specific processing activities on Customer Data.
1.5 “Visitor”: the natural person who uses the chat installed on the Customer's website.
1.6 “Operator”: the natural person authorised by the Customer to access the Service's dashboard, with one of the roles provided for (Owner, Admin, Agent).
1.7 “End Client”: if the Customer is a web agency, the party on whose behalf the agency manages one or more websites through the Service.
2. Roles of the Parties
2.1 For Customer Data, the Customer acts as controller and the Provider as processor.
2.2 If the Customer is a web agency that uses the Service on behalf of End Clients:
- a) each End Client is a controller, the Customer is a processor and the Provider is a sub-processor under Article 28(4) GDPR;
- b) the Customer declares and warrants that it has received from each End Client written authorisation to engage the Provider and its sub-processors;
- c) the instructions given by the Customer are deemed to be consistent with the End Client's instructions, and the Customer is liable for them;
- d) the Agency and Reseller Addendum also applies, and prevails over this DPA on the matters that it governs, without reducing the protections for data subjects.
2.3 The Provider processes as an independent controller, and not under this DPA, the data needed to manage the contractual relationship: the Customer's registration and invoicing data, the access and security data of the Operators' accounts, tax and accounting obligations, prevention of abuse of the platform. For this processing the Provider provides its own privacy notice.
2.4 The Provider does not process Customer Data for its own purposes, does not sell them, does not disclose them to third parties for marketing purposes and does not use them to train or improve artificial intelligence models, whether its own or third parties'. The Provider may use technical usage data that do not include the content of the conversations (number of replies and of conversations, tokens consumed, estimated costs, technical errors) to apply the artificial intelligence limits that the Customer turns on, to show the Customer its usage, and for the security and sizing of the Service.
3. Subject matter and duration
3.1 The subject matter, nature and purpose of the processing, the types of personal data and the categories of data subjects are described in Annex 1.
3.2 The processing lasts as long as the Terms and, after they end, for the time needed to return and erase Customer Data in accordance with Article 13.
4. Documented instructions
4.1 The Provider processes Customer Data only on documented instructions from the Customer, including with regard to transfers of data to a third country or an international organisation, unless required to do so by Union or national law to which the Provider is subject. In such a case, the Provider informs the Customer of that legal requirement before the processing, unless that law prohibits such information on important grounds of public interest.
4.2 The following constitute documented instructions from the Customer:
- a) this DPA and the Terms;
- b) the settings configured by the Customer in the dashboard, including: sites and authorised domains, knowledge base content, the artificial intelligence provider connected with its key, artificial intelligence on or off for each site and its optional limits (replies per conversation, conversations a day), automatic replies, welcome messages, language, texts, hours, retention period, the email notice to Visitors of the Operators' replies (on unless the Customer turns it off), the secret key with which the Customer's website signs the data of its registered customers: by creating that key, the Customer instructs the Provider to receive and verify those data (Article 5.6);
- c) the operations carried out by the Customer and its Operators through the dashboard, including replies to Visitors, notes on Visitors, edits and deletions of replies, exports and erasures;
- d) further written instructions sent to assistance@chattopus.com and accepted by the Provider, provided that they are compatible with the operation of the Service.
4.3 The Provider immediately informs the Customer if, in its opinion, an instruction infringes Applicable Law. In that case it may suspend the execution of that instruction until the Customer confirms it in writing or changes it.
5. Obligations of the Customer
5.1 The Customer warrants that the processing of Customer Data is based on an appropriate legal basis and that the Visitors receive the information required by Articles 13 and 14 GDPR. The Provider makes available a template privacy notice, the Visitor Privacy Notice Template, which the Customer adapts and publishes under its own responsibility, entering its address in the site's settings so that the widget shows it to the Visitors. The notice also names the artificial intelligence provider chosen by the Customer (Article 8.9).
5.2 The Customer does not enter in the knowledge base, nor do its Operators enter in the notes on Visitors, personal data that are not needed for the purpose of support and, in no case, special categories of data (Article 9 GDPR) or data relating to criminal convictions and offences (Article 10 GDPR). The Customer does not use the Service to ask Visitors for such data.
5.3 The Customer does not use the Service on websites or services aimed mainly at children under 14, nor for the purposes prohibited by the Terms.
5.4 The Customer chooses a retention period appropriate to its purposes, assigns the Operators the minimum role necessary, keeps the credentials confidential and protects the devices from which the Operators access the dashboard.
5.5 The Customer is responsible for the lawfulness of the instructions given to the Provider.
5.6 If the Customer has its website tell the chat which people have signed in to it (registered customers), the Customer decides which of the data provided for (customer ID, email and name) the website sends, sends only those needed for support, informs the people concerned and keeps safe the secret key with which the website signs them (Terms, Article 12.8).
6. Confidentiality and authorised personnel
6.1 The Provider allows access to Customer Data only to the persons who need it to provide, maintain and protect the Service or to provide the support requested by the Customer. These persons are authorised and instructed under Article 29 GDPR and Article 2-quaterdecies of the Italian Privacy Code and are bound to confidentiality by a contractual undertaking or by a legal obligation.
6.2 The Provider's staff do not read the content of the conversations, unless: a) the Customer asks for it in order to receive support; b) it is necessary to investigate a security incident or an abuse of the Service; c) it is required by law or by an order of an authority.
7. Security of processing
7.1 The Provider adopts the technical and organisational measures described in Annex 2, appropriate to the risk under Article 32 GDPR, and keeps them up to date. The Provider may change them provided that the overall level of protection is not reduced.
7.2 The Customer acknowledges that part of the security depends on its own configuration and behaviour: the roles assigned, the authorised domains, the retention period, the strength and confidentiality of the Operators' passwords, the security of the Operators' devices.
8. Sub-processors
8.1 General authorisation. The Customer gives the Provider general written authorisation to engage sub-processors. The sub-processors in use at the date of acceptance of this DPA are listed in Annex 3 and on the Sub-processors page (chattopus.com/sub-processors), and are deemed authorised.
8.2 Notice of changes. The Provider informs the Customer of any addition or replacement of sub-processors at least 30 days before the new sub-processor begins to process Customer Data. The notice is given by email to the users with the Owner role of the organisation and by updating the Sub-processors page (chattopus.com/sub-processors), and states the identity of the sub-processor, the activity carried out, the place of processing and, where applicable, the tool for transfers to third countries.
8.3 Objection. Within 15 days of the notice, the Customer may object on reasonable grounds relating to data protection, by writing to assistance@chattopus.com. The Parties seek a solution in good faith. If no solution is found before the new sub-processor begins to process Customer Data, the Customer may withdraw from the Terms without penalty, with effect from the date stated in its notice of withdrawal, and is entitled to a refund of the part of the fee already paid that relates to the period after the withdrawal. If no objection is made within the time limit, the change is deemed accepted.
8.4 Urgent replacements. If the replacement is necessary for urgent reasons of security or of continuity of the Service, for example because a sub-processor suddenly stops its service, the Provider may proceed with shorter notice, informing the Customer as soon as possible. The rights under Article 8.3 remain unaffected.
8.5 Obligations of sub-processors. The Provider imposes on each sub-processor, by contract or other legal act, data protection obligations substantially equivalent to those of this DPA, in particular sufficient guarantees as to the adoption of appropriate technical and organisational measures.
8.6 Liability. If a sub-processor fails to fulfil its data protection obligations, the Provider remains fully liable to the Customer for the performance of those obligations (Article 28(4) GDPR).
8.7 Chain with agencies. If the Customer is an agency, it passes on to the End Clients without delay the notices provided for by Article 8.2 and forwards their objections, if any, to the Provider, in accordance with the Agency and Reseller Addendum.
8.8 No emails about conversations to Operators. The Service notifies the Operators of conversations only in the dashboard and with push notifications on the devices on which they have turned them on, which contain no Visitor data (Annex 2): it does not send the conversations, or notices about them, by email, either to Users or to other addresses. The only emails with data from a conversation are those to the Visitor who asked for them (Annex 1, purpose c-bis).
8.9 Artificial intelligence provider chosen by the Customer. The provider of artificial intelligence models whose key the Customer connects in the dashboard for a site (Anthropic for Claude, OpenAI for ChatGPT, Google for Gemini, xAI for Grok, Mistral AI, DeepSeek, Groq, OpenRouter or another service compatible with the OpenAI APIs) is chosen and contracted by the Customer and is not a sub-processor of the Provider: the Provider does not choose it, has no contract with it for the Service and is not liable for it under Article 8.6. By connecting the key, the Customer instructs the Provider to transmit to that provider, for each artificial intelligence reply, the data described in Annex 1, which that provider processes under the contract between it and the Customer. The Customer:
- a) checks that the contract with that provider offers sufficient guarantees under Article 28 GDPR (or, if that provider processes the data for its own purposes, assesses the legal basis of that disclosure) and, for processing outside the EEA, a transfer tool under Chapter V GDPR;
- b) sets up its own account with that provider consistently with its own purposes (for example data retention and use for training models);
- c) names that provider in the privacy notice for the Visitors of the sites that use it and, if the Customer is an agency, in the list of its own sub-processors communicated to the End Clients.
The Provider transmits to that provider only the data in Annex 1, over encrypted connections, and only to the public addresses of the provider specified by the Customer; it stores the key encrypted and uses it only for the Service. The Customer can stop the transmission at any time, site by site, by deleting the keys connected to a site or by turning off the site's artificial intelligence: in that case the chat of that site replies with automatic replies, if active, and with the Customer's people, and no data of that site are transmitted to artificial intelligence providers.
8.10 The Provider's artificial intelligence. The replies to Visitors are generated only with the artificial intelligence provider chosen by the Customer (Article 8.9): the Provider does not offer an artificial intelligence of its own to reply to Visitors. The Provider's dashboard Help feature (an automatic assistant), which helps Users to use the Service, does not receive Customer Data relating to Visitors: it receives the Users' questions, essential information about the account and a summary of how the sites are set up (no visitor data), for which the Provider acts in accordance with Article 2.3.
9. Transfers outside the European Economic Area
9.1 The Provider does not transfer Customer Data outside the European Economic Area (EEA), nor allows a sub-processor to do so, except in compliance with Chapter V GDPR: on the basis of an adequacy decision (including the EU-US Data Privacy Framework, Commission Implementing Decision (EU) 2023/1795, for certified recipients), of the standard contractual clauses approved by Commission Implementing Decision (EU) 2021/914 or of another appropriate safeguard. Each transfer is shown on the Sub-processors page (chattopus.com/sub-processors) with the related tool.
9.2 The Customer acknowledges that some sub-processors belong to groups based outside the EEA, for example in the United States, and may be subject to laws of third countries that allow authorities to request access to data stored or processed in the EEA (for example the US CLOUD Act). To reduce this risk the Provider:
- a) chooses, where available, options for storing and processing data in the EEA;
- b) documents the assessment of the risk of transfers and of access by authorities of third countries;
- c) if it receives directly a request for access to Customer Data from a public authority, informs the Customer (unless prohibited by law), challenges the requests that it considers unlawful and discloses only the data strictly necessary.
10. Data subject requests
10.1 Taking into account the nature of the processing, the Provider assists the Customer by appropriate technical and organisational measures in responding to requests for the exercise of data subjects' rights (Articles 15-22 GDPR). In particular, the dashboard makes the following available to the users with the Owner role:
- a) a complete export, in JSON format, of sites, knowledge base sources, conversations, with the Visitor's data that accompany them (the IP address while it is kept, estimated country, browser time zone and language, device, pages viewed, referring website, browser code, registered customer data, read mark) and the Operators' notes, messages, contacts and unanswered questions, the latter with their context and the link to the conversation that they come from, of saved replies, of the images uploaded for the chat's look (including the photos of Operators) and of the Operators' profiles in the chat; the assistant's replies are marked in it as generated by artificial intelligence; artificial intelligence keys and secret keys for registered customers are never exported (rights of access and to data portability);
- b) the erasure of a Visitor's conversations, messages, contacts and unanswered questions, by entering their email address, telephone number or conversation identifier (right to erasure). The email address is searched as a complete address, without distinguishing between upper and lower case, also among the addresses that the Customer's website has given for its registered customers; the telephone number is searched by its digits, ignoring spaces, hyphens, brackets and the +39 prefix. The other conversations of the same Visitor on the same site, recognised by their browser code or by the registered customer that the website has identified, are erased too, with their messages and contacts and the Operators' notes written in them, as are the unanswered questions whose text contains the email address or the number given;
- c) the consultation of the conversations and contacts collected, with CSV export of the contacts on the plans that include it.
The features in letters a) and b) operate on the Customer's whole organisation, including all the conversations of its sites that match the criteria given. If the Customer is an agency, the Agency and Reseller Addendum also applies (Article 5.5).
10.2 If the Provider receives a request directly from a data subject, it does not respond to it on the merits, unless required by law, and forwards it to the Customer without undue delay and in any case within 5 working days.
10.3 If the Customer cannot respond to a request with the dashboard's features, the Provider provides reasonable assistance on written request to assistance@chattopus.com.
11. Personal data breaches
11.1 The Provider notifies the Customer of any personal data breach concerning Customer Data without undue delay after becoming aware of it and in any case within 48 hours, by email to the users with the Owner role and to any privacy contacts given in Annex 4.
11.2 The notification contains, to the extent available, the information in Article 33(3) GDPR: the nature of the breach, the categories and approximate number of data subjects and of records concerned, a contact point, the likely consequences, the measures taken or proposed. Information that is not available at once is provided in phases without further undue delay.
11.3 The Provider takes reasonable measures without delay to contain the breach and mitigate its effects, and cooperates with the Customer in the notifications to the supervisory authority (Article 33 GDPR) and the communications to data subjects (Article 34 GDPR), which remain the controller's responsibility.
11.4 The notification of a breach does not constitute an acknowledgement of liability by the Provider.
12. Data protection impact assessment and prior consultation
The Provider makes available to the Customer the information reasonably necessary for the data protection impact assessment (Article 35 GDPR) and for any prior consultation of the supervisory authority (Article 36 GDPR): a description of the Service, the measures in Annex 2, the list of sub-processors and the places of processing.
13. Retention, return and erasure
13.1 During the contract. Conversations and their messages are erased automatically when their last activity is older than the site's retention period, which depends on the plan: 15 days, not adjustable, on the Low plan; 90 days by default, adjustable by the Customer from 30 to 365, on the Mid plan; 365 days by default, adjustable from 30 to 730, on the High plan; on the Custom plan, as agreed, up to 730 days. The period in force is the one shown for the site in the dashboard; if the Customer moves to a plan with a shorter period, the older data are erased at the next automatic clean-up. The unanswered questions drawn from the conversations are erased with them. The contacts left by Visitors follow the same period, calculated from when they were left. The data that accompany a conversation (Annex 1, points 3, 5, 11, 12 and 13) and the Operators' notes written in it are erased with the conversation. The Visitor's full IP address (Annex 1, point 10) is erased automatically 30 days after the last activity of the conversation, or earlier, together with the conversation. The Customer may also erase specific data at any time with the features in Article 10.1. Deleting a site entails the erasure of that site's conversations, messages, notes, contacts, knowledge base, unanswered questions, saved replies and secret key for registered customers.
13.2 At the end of the plan and when the Terms end. If the Customer deletes a site or the whole organisation from the dashboard, the Provider erases the related data on the Customer's instruction, at once and without the period described below (Terms, Article 18.4). When the organisation is left without a plan (subscription closed, end of the Terms), the chat stops working and for 30 days the Customer can export Customer Data with the export feature, which constitutes the means of returning the data; during this period the data are neither used nor erased by the automatic retention, except for the Visitors' full IP addresses, which are erased in any case 30 days after the last activity of the conversation (Article 13.1) and may therefore no longer be in the export. The Provider informs the Owners by email at least 7 days before the erasure; if the notice cannot be delivered to any Owner, the erasure is postponed by 7 days. Once 30 days have passed without a plan, the Provider automatically erases the organisation with all Customer Data from the systems in use (Terms, Article 11.4). The same applies, 30 days after registration, to an organisation that has never had a plan. Backup copies are overwritten according to the rotation cycle within 14 days and, until then, remain protected and are not used. Retention obligations provided for by law are unaffected. On written request, the Provider confirms the erasure in writing.
14. Information and audits
14.1 The Provider makes available to the Customer the information necessary to demonstrate compliance with the obligations of Article 28 GDPR: this DPA, the up-to-date Annex 2, the list of sub-processors and, if available, the certifications or audit reports of the sub-processors that they allow to be shared.
14.2 The Customer may send reasonable written questionnaires, no more than once a year except in the event of a personal data breach or of a request from a supervisory authority.
14.3 If the information provided is not sufficient, the Customer may carry out an inspection, directly or through an independent auditor who is bound to confidentiality and is not a competitor of the Provider, with at least 30 days' written notice, during working hours, without access to other customers' data and without compromising the security of the Service, no more than once a year. The costs of the inspection are borne by the Customer, unless a material breach of this DPA by the Provider emerges. The powers of the supervisory authorities are unaffected.
14.4 The Provider keeps the record of the categories of processing activities carried out on behalf of controllers (Article 30(2) GDPR). The dashboard also makes available to the Customer's Admins a log of the main actions taken by the users of the organisation.
15. Liability
15.1 Towards data subjects, each Party is liable in accordance with Article 82 GDPR.
15.2 Between the Parties, the limitations of liability provided for by the Terms apply, except in the event of wilful misconduct or gross negligence.
16. Duration, precedence and changes
16.1 This DPA forms an integral part of the Terms, takes effect from their acceptance and remains in force until Customer Data are erased in accordance with Article 13.
16.2 In the event of conflict between this DPA and the Terms on matters of personal data protection, this DPA prevails.
16.3 The Provider may change this DPA to bring it into line with Applicable Law or with measures of the authorities. Any other change that reduces the Customer's protections is notified with at least 30 days' notice; within that period the Customer may withdraw from the Terms without penalty.
17. Governing law and jurisdiction
This DPA is governed by Italian law. The courts of the place where the Provider has its registered office have exclusive jurisdiction over any dispute between the Parties, without prejudice to the rights of data subjects and to the powers of the supervisory authorities.
The Provider's contact for data protection: assistance@chattopus.com.
Annex 1 — Description of the processing
| Item | Description |
|---|---|
| Subject matter | Provision of the Chattopus Service to the Customer, in accordance with the Terms. |
| Nature | Collection through the chat widget; recording and storage; organisation by site and by conversation; search in the Customer's knowledge base; comparison of the messages with the Customer's frequently asked questions and quick-reply buttons for the automatic replies; transmission to the artificial intelligence provider chosen by the Customer for the site (Article 8.9), to generate the replies; communication to the Operators through the dashboard; push notifications to the Operators without Visitor data (no emails to the Operators about conversations, Article 8.8); sending the Operators' replies to the Visitor by email when the Visitor is no longer on the website, if they have left their address in the chat to receive them and the Customer has not turned this feature off; estimation of the Visitor's country from their browser's time zone and recognition of the device from the User-Agent, on the Provider's servers and without external services; recording of the pages of the website viewed while the Visitor's browser keeps the conversation; linking of the conversations of the same Visitor on the same site; verification of the signature of the registered customers' data sent by the Customer's website; notes written by the Operators; export; erasure. |
| Purposes | a) answering the Visitors' questions automatically using the Customer's knowledge base, with artificial intelligence or with automatic replies; b) passing the conversation or the messages to the Operators when the Visitor asks for it, the assistant cannot answer or the site replies with people only, and notifying them; c) passing to the Operators the requests for a person, also outside hours, without the Visitor having to leave contact details, and notifying them; recording the contact details that the Visitor asks the assistant to use to contact them again, and notifying the Operators of them; c-bis) letting the Visitor find the Operators' replies when they come back to the website and, if they have left their email address in the chat to receive them (the “Your contact details” form or the offer after a request), notifying them by email with the reply and a link to resume the conversation (at most one email every 3 hours per conversation; never for the assistant's replies), only on a site for which the Customer has entered in the settings the email address to which the Visitor can reply (“Email for your customers’ replies”): the email is sent from an address of the Service with the name of the Customer's business as the sender's name and gives that address for replies, which reach the Customer directly and do not pass through the Service; showing the Operators whether the Visitor is still on the website; d) providing the Customer with management tools: conversations, contacts, unanswered questions, ratings of the replies, report; e) counting the artificial intelligence replies, per conversation and per day, and the related tokens, to apply the limits that the Customer turns on for each site and to show the Customer its usage, without using their content; f) protecting the Service from abuse, with traffic limits; g) showing the Operators, in the Visitor card, who the Visitor is, the estimated country, the IP address, the device, the pages viewed and the Visitor's previous conversations on the same site, recognising the registered customers of the Customer's website and keeping the Operators' notes; h) showing the Operators whether the Visitor has seen their replies and whether the Visitor is typing, and showing the Visitor when an Operator is typing; h-bis) on the Mid, High and Custom plans, unless the Customer turns it off for a site, showing the Operators the text that the Visitor is typing before sending it, only while the conversation is waiting for a person or is followed by the Operators, so that they can prepare the reply (typing preview). |
| Categories of data subjects | Visitors to the Customer's website, including the registered customers identified by the Customer's website; persons whose data appear in the content that the Customer enters in the knowledge base (for example the staff named on the pages of the website); the Customer's Operators, limited to the name, role and image (photo, icon or initials, if the Customer sets them) shown to Visitors in the chat, to the assignment of conversations and to the notes that they write, of which they are the authors; persons named in the Operators' notes; persons portrayed in the images that the Customer uploads for the chat's look. |
| Frequency | Continuous, for the whole term of the Terms. |
| Duration and retention | See Article 13: conversations and contacts erased after the site's retention period, which depends on the plan (Low 15 days; Mid 90 days, from 30 to 365; High 365 days, from 30 to 730; Custom up to 730), with the data that accompany the conversations and the Operators' notes; the Visitor's full IP address erased 30 days after the last activity of the conversation; organisation erased after 30 days without a plan. |
| Recipients | Operators authorised by the Customer; the sub-processors in Annex 3; the artificial intelligence provider chosen by the Customer, on the Customer's instruction (Article 8.9); the Visitor themselves, at the address they left in the chat to receive them (the Operators' replies). |
Types of personal data
- Messages: text written by the Visitor (at most 1,000 characters per message), replies generated by the artificial intelligence system and the Operators' replies, with date and time; any rating of a reply (helpful / not helpful). An Operator's reply may quote another message of the conversation: it copies at most 120 characters of it, which are removed if the quoted message is deleted. Operators may edit their own replies (not in closed conversations) and delete them within 15 minutes of sending them (Owners and Admins may delete, within the same time, the other Operators' replies too): the time of the edit is kept, and the text of a deleted reply is removed from the database (not from the backup copies already made, nor from the emails or exports already sent). The widget updates its copy of the conversation (point 6) when it checks for replies, until the conversation is closed: the copy of a conversation that is already closed keeps the earlier text until it expires. The Visitor's and the assistant's messages are not edited or deleted one by one.
- Contact details provided voluntarily by the Visitor: email address and, if the Visitor gives them, name, any note or interest, the consent given and its proof. The Service does not ask for the telephone number. For the email address left in the chat's forms, the proof is the text of the box shown to the Visitor (“I agree to have the team's replies to this chat emailed to me.”, in the language in which the chat shows it); for the address that the Visitor writes in the conversation and that the assistant records when the Visitor states that they want to be contacted again, it is the Visitor's message containing the words with which they stated it, as reported by the assistant, or, if those words cannot be found in the Visitor's messages, their last message (at most 300 characters). The assistant records only an email address that appears in full in a message of the Visitor, never a telephone number. A telephone number can appear in the data only if the Visitor writes it of their own accord in a message (it remains in the text of the conversation) or in a contact recorded before November 2026.
- Page context: origin and path of the page from which the Visitor writes, without query parameters or fragments, and the page title. In addition, for the Operators: the page from which the conversation started; the domain of the website from which the Visitor arrived, if it is another website (without path or parameters); the pages of the website opened while the Visitor's browser keeps the conversation, also on later visits (until the copy in point 6 expires: 30 days from the last use of the chat or from the last reply of the Operators that reached the chat, never beyond the site's retention period), at most the last 20, each with path, title and time, recorded when the widget checks with the Service whether there are replies.
- Preferences: language.
- Technical data: conversation identifier; signed session token, valid for 31 days, renewed when the Visitor's widget uses it at least one day after it was issued; when the Visitor's widget was last in contact with the Service, whether at that moment it was checking for replies continuously or with a single check on opening a page, and the last message it received (to show the Operators whether the Visitor is on the website and not to send by email a reply that the Visitor has already seen); the time of the last email sent to the Visitor for a reply; the codes of the links to resume the conversation sent by email, stored only as a fingerprint (SHA-256 hash), valid for 7 days and for one use only, erased the day after their use or expiry; a fingerprint (hash) of the IP address, used to limit abuse; the moment when the disclosure on the use of artificial intelligence was shown to the Visitor; the last reply of the Operators that the widget showed to the Visitor with the chat open and the page visible (read mark: the Operators see one tick for a reply sent and two for a reply seen; the Visitor sees no ticks); the signal that the Visitor is typing, only while the conversation is waiting for a person or is followed by the Operators, and the signal that an Operator is typing a reply, in a conversation that is not closed (the other Operators see it and, only in the two cases above, the Visitor), never the text, kept for a few seconds in the Service's memory and never saved; with the typing preview (purpose h-bis), the text that the Visitor is typing, before they send it (at most the last 500 characters, sent by the widget at most every 3 seconds and only when they change), kept for at most 30 seconds in the Service's memory and deleted when the Visitor sends the message or empties the box, never saved or transmitted to the artificial intelligence provider; the widget tells the Visitor so with a line under the typing box (“The team sees your text as you type.”, in the language in which the chat shows it).
- Data stored in the Visitor's browser: the widget saves in the local storage of the Visitor's browser the token and a copy of the recent messages of the conversation and, after the first use of the chat, the browser code (point 12), to resume the conversation when the Visitor changes page or comes back to the website and to let them find the Operators' replies that arrived while they were away (when a page opens with a saved conversation, the widget asks the Service whether there are new replies: once, or for as long as the page stays open if the conversation is followed by a person). The Provider does not access this copy. If the Visitor opens the link in the email that notifies them of a reply, the copy is saved in the same way on the chat page hosted by the Provider. When the website shows a teaser bubble next to the chat button, the widget remembers in the session storage whether the Visitor has closed it and, if the bubble is to be seen only once, in the local storage that the Visitor has already seen it.
- Knowledge base content provided by the Customer (questions and answers, texts, pages of the website acquired automatically), to the extent that it contains personal data.
- Unanswered questions: the text of the questions that the assistant could not answer, with their context, linked to the conversation that they come from. When the Customer answers a question from the dashboard, it reviews its text, proposed in the Visitor's words and editable (for example to remove names or order numbers): that text becomes a frequently asked question of the knowledge base, and the resolved question keeps only that text, without the context.
- Images uploaded by the Customer for the chat's look (logo, backgrounds, stickers, the team's faces), to the extent that they contain personal data. They are public by nature, shown to Visitors and reachable by anyone who knows their address; the Customer chooses them and is responsible for them (Terms, Article 12.7).
- Full IP address of the Visitor: taken when the conversation starts and again when the Visitor writes from another address; stored with the conversation and shown to the Operators in the Visitor card; erased automatically 30 days after the last activity of the conversation, or earlier with the conversation; never written in the technical logs. Backup copies contain it for as long as they are kept (Annex 2, Part B, point 3).
- Country, language and device: country estimated from the time zone of the Visitor's browser, on the Provider's servers and without geolocation databases (only the country, never the city or region; the estimate may be wrong); time zone and language of the browser; browser with its major version, operating system and type of device (phone, tablet or computer), derived from the browser's User-Agent, which is not stored, and, to tell an iPad from a Mac computer, from the widget's indication that the screen is a touch screen.
- Visitor's browser code: a random code that the Service assigns when the Visitor uses the chat for the first time (a message, a request for a person or the email left in the chat) and that the widget keeps with the conversation (point 6) and sends back when the Visitor starts another conversation on the same site; it links the conversations of the same Visitor on that site. Before the chat is used, it is not created, saved or sent.
- Registered customer data: only if the Customer's website sends them signed with the site's secret key (HMAC-SHA256, signature valid for 48 hours): the customer ID on the website, the email address and the name of the person who has signed in to it, and the moment when the signature was verified. Data without a signature or with a wrong signature are ignored. The widget reads them only when the Visitor writes a message, asks for a person or leaves their email address.
- Operators' notes: free text (at most 2,000 characters) that the Operators write about a Visitor, with the author and the dates of creation and editing; kept with the conversation in which they are written and shown to the Operators with all the conversations of the same Visitor on the same site; never shown to the Visitor. Each Operator edits and deletes their own notes; Owners and Admins all of them.
Special categories of data. Not provided for. The Service is not designed to process special categories of data or data relating to criminal convictions. Since messages are free text, the Visitor might enter such data spontaneously; the Customer handles them as controller and can erase them with the features in Article 10.1. The Operators' notes are also free text: the Customer does not enter such data in them (Article 5.2).
Data transmitted to the artificial intelligence provider (the one chosen by the Customer for the site, Article 8.9), only for the replies generated by artificial intelligence: automatic replies and conversations handled by people involve no transmission. System instructions; extracts from the knowledge base relevant to the question; the history of the conversation; the context of the page from which the Visitor writes (path and title). The IP address and its fingerprint, the session token, the data in points 10-14, the other pages viewed and the referring website (point 3), the quotations of messages (point 1) and the read marks (point 5) are not transmitted. The history includes the most recent messages of the conversation, including those left unanswered. The name and email address left in the chat's forms are not transmitted; any note added to a request for a person is saved as a message of the Visitor and, if the conversation goes back to the assistant, is part of the history, as are the contact details that the Visitor writes in messages. The search in the knowledge base is carried out on the Provider's servers with a text index, without using external text analysis services.
Annex 2 — Technical and organisational measures
A. Measures in the Service
Described according to the product specifications.
- Encryption in transit. The widget, the dashboard and the interfaces of the Service can be reached via HTTPS (TLS). The connections to the artificial intelligence provider (the one chosen by the Customer or the sub-processor) and to the payment provider use HTTPS. Sending emails requires TLS (implicit or via STARTTLS). Push notifications are encrypted according to the Web Push standard and contain no Visitor data.
- Authentication of Operators.
- Passwords stored only as scrypt hashes (parameters N=16384, r=8, p=1; random 16-byte salt; 64-byte key), with constant-time verification.
- Password rules: at least 10 characters, at most 200, the most common passwords refused.
- A limit of 5 failed sign-in attempts every 15 minutes per IP address and per email address.
- One-time password reset and invitation links, with an expiry, stored only as hashes.
- Session cookie HttpOnly, SameSite=Lax and Secure over HTTPS, stored on the server only as a SHA-256 hash, expiring 30 days after its last use; changing the password closes all the other sessions, cancels the reset links not yet used and turns off push notifications on the other devices; resetting the password does the same on all devices.
- A limit of 5 failed verifications of the current password every 15 minutes per user (password change, account deletion) and of 3 reset emails an hour per address.
- Role-based access control.
- “Agent” role: conversations, contacts, viewing the unanswered questions, own account.
- “Admin” role: in addition, sites, knowledge base, team, reports, action log.
- “Owner” role: in addition, billing, export, erasure of data and deletion of the organisation.
- The connection to the artificial intelligence provider of each site is managed by Admins and Owners; only the Owner can delete it.
- Every user sees all the sites of their organisation, according to their role: the Service does not allow a user to be restricted to some of the sites.
- Every request to the dashboard is checked against the organisation indicated and the user's membership of that organisation; the search in the knowledge base is filtered by site.
- The Visitor card, IP address included, and the notes can be seen by anyone who can open the conversation, Agents included; the previous conversations and the notes that it shows are only those of the same site. Every user edits and deletes their own notes, Admins and Owners all of them.
- The secret key for the registered customers of a site can be seen and managed only by Admins and Owners.
- Protection of the widget's public interface.
- When the Customer has given the authorised domains for the site, the widget replies only to those domains. Until it gives any, the widget accepts any HTTPS origin and records the first one that uses it, to detect the installation: for this reason the Customer gives the authorised domains as soon as it installs the widget.
- Each conversation is protected by a signed token (HMAC-SHA256) bound to the site and the conversation, expiring after 31 days and renewed as described in Annex 1, point 5.
- Traffic limits: creation of sessions per IP address, messages per conversation and per IP address, only one reply generated at a time per conversation; maximum message length of 1,000 characters.
- Data minimisation.
- Of the page visited, only the origin and path are transmitted and stored, never query parameters or fragments; the same applies to the pages viewed during the conversation. Of the referring website, only the domain is stored.
- The widget does not set cookies. In the Visitor's browser it stores only the token, a copy of the recent messages and, after the first use of the chat, the browser code, with an expiry (Annex 1, point 6), as well as the memory of the teaser bubble already seen or closed.
- Before the Visitor uses the chat (a message, a request for a person or the email left in the chat), the browser code does not exist and the widget does not send the data for the Visitor card (browser time zone and language, pages, referring website); the registered customer's data are read only when the Visitor writes a message, asks for a person or leaves their email address.
- The User-Agent is read only to derive the browser, the operating system and the type of device from it, and is not stored; the country is estimated from the browser's time zone on the Provider's servers, without geolocation databases or external services.
- The “is typing” signal is kept for a few seconds in the Service's memory and is never saved. The text that the Visitor is typing is not sent before they send it, except for the typing preview of the Mid, High and Custom plans (Annex 1, purpose h-bis), which the Customer can turn off for each site: only while the conversation is waiting for a person or is followed by the Operators, with a line in the widget that tells the Visitor so; it is kept for at most 30 seconds in the Service's memory only, never saved, never put in the logs, exports or emails or sent to the artificial intelligence provider, and shown only to the Operators who can see that conversation.
- Push notifications to the Operators contain no Visitor data.
- Conversations are not sent by email to the Operators or to other addresses: the Operators see them in the dashboard and are notified of them only with push notifications. Every email of the Service has a single recipient, who does not see the addresses of others.
- The email to the Visitor with an Operator's reply is sent only to the address that the Visitor left in the chat's forms to receive it (never to an address given to the assistant), at most one every 3 hours per conversation, and is not sent if in the meantime the Visitor's widget has received the reply. The link that it contains carries a random one-time code, valid for 7 days and stored only as a hash, never the conversation's token; the code is in the part of the address that the browser does not send to the server, and the page removes it from the address as soon as it opens.
- Only the data needed to generate the reply are transmitted to the artificial intelligence provider (Annex 1), and nothing when the chat replies with automatic replies or with people.
- The Provider's dashboard Help feature does not receive the Visitors' conversations or keys: it receives essential information about the account and a summary of how the sites are set up (no visitor data); strings that look like keys or passwords written by Users are masked before being sent to the model and in support requests.
- Protection against malicious content.
- The Visitors' texts, page titles, knowledge base content and settings are treated as untrusted and shown as text, without being interpreted as code, in the widget and in the dashboard.
- The page context is passed to the model as content of the user's message and not as a system instruction.
- The automatic acquisition of pages for the knowledge base respects the robots.txt file and refuses addresses of internal or reserved networks (SSRF protection).
- The Customer's custom styles (CSS) are cleaned on the server of instructions that load or run other code and apply only inside the chat; the chat page hosted by the Provider does not run scripts inserted in the page.
- Images uploaded for the chat are accepted only in PNG, JPEG or WebP format, recognised from the content of the file and not from its name (never SVG), with a size and number limit per site; they are stored only with what is needed to show them, without metadata (for example EXIF data with the place where a photo was taken), and served with headers that prevent their use as a page or as code.
- The Customer's artificial intelligence keys. They are stored encrypted (AES-256-GCM, with a key derived from the server's secret and bound to the individual connection); they never appear in the dashboard's responses (only the last four characters are shown), in logs, in the action log, in exports or in emails; the providers' error messages are shown to the Customer's Admins without anything that resembles a key.
- Secret key for registered customers. It is stored encrypted in the same way (AES-256-GCM, with a key derived from the server's secret and bound to the individual site); it is shown only to Admins and Owners, on the site's Install page; it does not appear in exports, in logs or in the action log, which records only that it was created, changed or deleted. The signatures of the registered customers' data are verified with a constant-time comparison and are valid for 48 hours; a change of the key immediately invalidates the signatures made with the previous key. If the server's secret changes, the key can no longer be read and the Customer creates a new one.
- Addresses of compatible providers. The address of a compatible provider given by the Customer is accepted only over HTTPS, without credentials, and only if it corresponds to public addresses; the check is repeated before every request, the connection is made only to the address checked, and redirects are not followed (SSRF protection).
- Protection of the dashboard against cross-site request forgery (CSRF). Requests that change data and have a body must have it in JSON format; deletion requests without a body must state their origin (the Origin header, which browsers always send). When the Origin header is present, it must match the public address of the Service.
- Logs. For each request, the application log records only the method, the path pattern (without identifiers, tokens, site keys or search texts), the response code and the duration. It does not record IP addresses, headers or request bodies; server errors are recorded without the content of the request; credentials are never recorded. The users' relevant actions are recorded in a log that the Customer's Admins can consult.
- Retention and erasure. Retention period per site according to the plan (Low 15 days; Mid 90 days, from 30 to 365; High 365 days, from 30 to 730; Custom up to 730), with automatic erasure of conversations and contacts; automatic erasure of the Visitors' full IP address 30 days after the last activity of the conversation, checked every 6 hours, also for organisations without a plan; automatic erasure of the whole organisation after 30 days without a plan, preceded by a notice to the Owners; targeted erasure by email address, telephone number or conversation, extended to the other conversations of the same Visitor on the same site; the text of a reply deleted by an Operator is removed from the database; erased data are overwritten in the database file and do not remain readable in its free space; complete export in JSON; cascading erasure of the data of a deleted site and of a deleted organisation, including the Users' membership of the team and the action log. Notice emails waiting to be sent (at most about an hour and a half, in the event of new attempts) are erased together with the conversation or contact to which they refer, so that erased data are no longer sent.
- Files. The files created by the application, including the database, have read and write permissions reserved for the service's user (0600), and the data folders that it creates are accessible only to that user (0700), where the system allows it. The configuration file with the secret keys is reserved for the same user (0600), according to the installation guide.
- Continuity towards Visitors. If artificial intelligence is not available or a limit that the Customer has turned on is reached, the widget continues to work with automatic replies, if active, and as a chat with the Operators and a collection of contacts, so that the Visitors' messages are not lost.
B. Organisational and infrastructure measures
- Infrastructure. Servers at the hosting provider named, with its region, on the Sub-processors page (chattopus.com/sub-processors).
- Encryption of data at rest. The Customer's artificial intelligence keys and the secret keys for registered customers are stored encrypted (Part A, point 6); the other data are protected by the permissions of the files that hold them (Part A, point 10, and point 3 below).
- Backups. A copy of the database is made every night and kept on the server for 14 days, in files and in a folder that only the server's administrator account can read; if copies are also kept with a separate backup storage provider, that provider is named on the Sub-processors page.
- Administrative access to the servers. Administrative access to the servers is reserved for the persons authorised by the Provider (point 7).
- Updates and vulnerabilities. The Provider installs the security updates of the operating system and of Node.js and periodically checks the Service's dependencies.
- Breach management. Personal data breaches are handled in accordance with Article 11.
- Personnel. Authorisation, written instructions and a confidentiality undertaking for anyone who accesses Customer Data (Article 6).
- Security testing. The Service's automated tests include tests of the security measures in Part A.
Annex 3 — Authorised sub-processors
The up-to-date list, with the activities, the data processed, the places of processing and the tools for any transfers, is published on the Sub-processors page (chattopus.com/sub-processors). Changes follow Article 8. At the date on which this DPA comes into force:
| Sub-processor | Activity |
|---|---|
| The hosting provider of the Service | Application server and database of the Service |
| Anthropic | The dashboard's Help, an automatic assistant that receives no Visitor data (Article 8.10) |
| The email sending provider | Sending the Service's emails |
| The backup storage provider, if different from the hosting provider | Storage of the backups |
The names, contracting entities and regions of these sub-processors are given on the Sub-processors page.
The artificial intelligence provider chosen by the Customer does not appear in this list because it is not a sub-processor of the Provider (Article 8.9).
Annex 4 — Contacts and special instructions of the Customer
To be filled in by the Customer, if different from the users with the Owner role.
- The Customer's privacy contact: name, email address, telephone number.
- The Customer's data protection officer, if designated: name, email address.
- Special instructions: any additional documented instructions under Article 4.2, letter d).