This article explains where to find Crisp security and SOC 2 compliance information.

Security reviews often require official and up-to-date documentation. Use this article as a pointer to Crisp’s security resources and Developer Hub compliance pages rather than copying static compliance claims into your own records.

Where to find compliance information

Crisp keeps security and compliance information available through official public resources. For audits, procurement reviews, or vendor questionnaires, use those resources as the source of truth so your documentation stays current.

Useful resources include:

• Crisp security documentation → technical and organizational security information
• Developer Hub security practices → engineering and platform security references
• Crisp team → additional documents or vendor-review answers when your organization needs them

Good practice for vendor reviews

Do not copy static compliance details from an old help article into an audit file. Instead, link to the latest official Crisp resources and request any required supporting documentation from Crisp when needed.

Updated on: 03/05/2026