Privacy and data protection

• Crisp EU GDPR compliance status

  Learn how Crisp handles GDPR compliance, data processing, privacy rights, and related security practices. The European Union’s General Data Protection Regulation (GDPR) is a regulation that aims at harmonising EU Member State’s data privacy laws. This article describes the GDPR compliance status of Crisp. **If your company needs toPopular

• Where do I find my GDPR Data Processing Agreement (DPA)?

  **Companies using Crisp and handling European user data (ie. people living in the European Union) may need to sign a Data Processing Agreement (also called DPA), as part of GDPR requirements. Under the European GDPR regulation, Crisp is the Customer’s data processor. From the moment your account is created, Crisp processes the personal data from your end-users as described and agreed in our data processing agreement. This article explains where to find your DPA and how you can obtain a signed coPopular

• How to be legally compliant to your customers with Crisp?

  Use this checklist to configure Crisp in a privacy-conscious way when you support customers under GDPR and ePrivacy requirements. When your team uses Crisp, you may process personal data such as names, emails, IP addresses, conversation content, files, custom data, and customer context. Crisp provides legal resources and product controls to support compliance, while your company remains responsible for deciding what data to collect, what legal basis applies, who can access it, and how long itFew readers

• Does use Hugo use conversational data

  This article explains whether Hugo uses your Crisp conversations as training data and what conversational context it can access. Hugo can use the context of the current conversation to answer properly, but it is not trained on all previous conversations from your inbox. This distinction matters for privacy, security, and the quality of the answers Hugo provides. Does Hugo train on my inbox conversations? No. Hugo is not trained on all conversations from your CrispFew readers

• Crisp Cookie Policy

  Learn what is the Crisp Cookie Policy. The website, Crisp.chat**, does not collect personal identifiable cookies when you visit us. We do collect anonymous information, such as, for example, how often website visitors engaged with our website.** Crisp collects only the necessary and functionality cookies related to its software app and chatbox in order to make those products available to the users. **By default, Crisp does not collect any tracking cookies. Not via its own websiPopular

• Magic Browse feature compliance with GDPR

  Learn how Magic Browse works and how Crisp helps you keep co-browsing privacy-friendly. Magic Browse lets your team guide customers through your website by viewing the page they are currently browsing. It is passive by design, scoped to your website, and includes privacy controls for sensitive information and user consent. Magic Browse is available on the Crisp Essentials and Plus plans. How Magic Browse works Magic Browse renders the HTML and CSS of your websitFew readers

Crisp platform security

• How Crisp manages security on its services

  Learn where to review Crisp security practices and the main resources related to platform security. Crisp takes account, workspace, infrastructure, and visitor data security seriously. The most detailed and current technical security information is maintained in Crisp's Security Practices documentation. Review Crisp security practices For the detailed security documentation, read Security Practices in theFew readers

• How to enable Two Factor Authentication (2FA)

  Learn how to enable Two-Factor Authentication for your Crisp account and enforce it for your workspace. Two-Factor Authentication adds a second verification step when signing in to Crisp. It is optional by default, but strongly recommended for every operator because it helps protect your workspace even if a password is compromised. This guide uses Google Authenticator as an example, but other apps that generate time-based one-time passwords can also be used. ${color}[#0080dd](WhatFew readers

• How to Configure Chatbox Security and Anti-Bot Protection

  This article explains how to configure domain security and anti-bot protection for the Crisp chatbox. Crisp includes security mechanisms to prevent your website chat widget from being used on unauthorized domains and to protect chat sessions from automated traffic, fake visitors, spam, and message floods. Most anti-bot protection works automatically. From the Chatbox Security settings, you can also control which domains are allowed to use your chatbox and tFew readers

Compliance and certifications

• Crisp SOC 2 compliance

  "Information security is a reason for concern for all organizations, including those that outsource key business operation to third-party vendors (e.g., SaaS, cloud-computing providers). Rightfully so, since mishandled data—especially by application and network security providers—can leave companies vulnerable to attacks, such as data theft, extortion and malware installation. At Crisp we consider security very seriously, everything has been detailed over [this article](https://docs.crisp.chat/Few readers

• Crisp ISO 27001 compliance

  "Information security is a reason for concern for all organizations, including those that outsource key business operation to third-party vendors (e.g., SaaS, cloud-computing providers). Rightfully so, since mishandled data—especially by application and network security providers—can leave companies vulnerable to attacks, such as data theft, extortion and malware installation. At Crisp we consider security very seriously, everything has been detailed over [this article](https://docs.crisp.chat/Few readers

• Crisp RGAA 4.1.2 compliance

  Learn about the Crisp Chatbox's accessibility compliance, audit results, and how to report an accessibility issue. The Crisp chat widget is fully compliant with RGAA 4.1.2, according to the accessibility statement established on 30 June 2026. This article summarizes the audit results and the scope of that statement. Accessibility compliance status The accessibility statement reports: Standard assessed → RGAA 4.1.Few readers