Crisp Chat AI (crisp.chat)
Script Signature: client.crisp.chat
Crisp Chatbot enables automated support scenarios across web and mobile apps. Deployers must verify initial bot events contain explicit AI notifications. Crisp Chat's automated scenarios are powerful, but they must be designed with transparency in mind. Initial bot triggers must include explicit notifications that the user is interacting with an AI. Failing to do so violates the core principle of informed interaction laid out in the EU AI Act.
Audit Methodology & Findings
Scan Date: 2026-08-01
Methodology: Automated DOM script detection and manual UI verification
Evidence: Observed default script signatures and generated metadata components.
Limitations: Technical diagnostic only. Excludes backend processing and custom enterprise implementations.
Article 50 Regulatory Breakdown
Article 50(1) Chatbots
Natural Person Notification
Partial ComplianceArticle 50(2) Media
C2PA & Watermarking
Non-ApplicableArticle 50(3) Text
Public Copy Disclosure
CompliantIdentified Integration Risks & Vulnerabilities
- ⚠️Crisp bot triggers firing without clear identity disclosure.
- ⚠️Script loading without structured metadata tags.
Recommended Technical Remediation
Set initial Crisp scenario message to declare: "Crisp Bot Notice: You are chatting with an AI assistant."
<!-- Compliant Article 50(1) Disclosure Snippet for Crisp Chat AI --> <div class="ai-disclosure" itemprop="isBasedOn" rel="ai-info"> Notice: This system incorporates automated Crisp Chat AI AI technology per EU Regulation 2024/1689 Article 50. </div>
Test Live Website URL
Scan Webpages for AI Transparency
Automated technical audit for AI chatbots, C2PA synthetic media metadata, and mandatory Article 50 transparency notices.