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 the Crisp Developer Hub.
The security documentation covers topics such as:
- Data privacy → Crisp's approach to protecting customer and end-user data
- Account security → strong authentication and secure access practices
- Infrastructure security → safeguards around server, network, and operational access
- Application security → secure product design and protection against common risks
- Responsible disclosure → how security researchers can report issues to Crisp
Related security resources
Useful companion articles:
- How to enable Two Factor Authentication → add an extra login protection layer to Crisp accounts
- Crisp Chatbox Cookie & IP policy → understand Chatbox cookies, sessions, and IP handling
- Crisp EU GDPR compliance status → review GDPR-related information
- What is Crisp compliance status with SOC2 → understand SOC 2-related security areas
- What is Crisp compliance with ISO 27001 → understand ISO 27001-related security areas
Frequently Asked Questions
Still have questions which were not covered in this article? Here is a collection of the most frequently asked questions on this topic.
Where should I start for a security review?
Start with the Security Practices documentation. It is the best reference for technical security information, then use the related articles above for GDPR, cookies, 2FA, SOC 2, and ISO 27001 topics.
Where can I report a security issue?
Use Crisp's responsible disclosure guidance. The Security Practices documentation explains how to report security concerns and which channel to use.
Updated on: 03/05/2026
Thank you!