Source
Security / trust page — found from the homepage — Crisp
Checked for Crisp on 30 Sep 2026
- Page
- https://docs.crisp.chat/guides/others/security-practices/
- Checked
- 30 Sep 2026, 13:19 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:60d5aecd9681beeee3f752fd837dc318b45350bd4201942fbc717bcc3bad2335
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Messaging region Report an error
“Messaging servers are hosted in 🇳🇱 The Netherlands”
-
Plugin region Report an error
“Plugin servers are hosted in 🇩🇪 Germany”
-
Access control Report an error
“All customer data is on a need-to-know access. Employees that can access customer data via our internal system have different security levels and visibility.”
-
Resilience Report an error
“Our architecture is replicated in micro-services, ensuring service continuity in case of hardware failure”
-
Replicated databases Report an error
“We have different layers of databases which are all replicated around the world”
-
Monitoring Report an error
“Our system runs an automated monitoring system allowing us to be aware of issues before those affects our customers.”
-
Vulnerability disclosure Report an error
“If you find any security hole in the Crisp REST API (or any other system), you are more than welcome to report it directly to security@crisp.chat.”
-
Data location no office servers Report an error
“We do not keep any servers or security keys stored in our offices.”
-
No local customer data Report an error
“No Crisp employee is allowed to store customer data on their machines.”
16 facts read from this page are not shown because they could not be confirmed on the page as captured.