Skip to main content

​
Overview

Embedding a contact button or chat widget on your website and automating conversations with Quick.bot is a powerful way to provide real-time support. These features make it easier for customers to reach you and improve their overall experience. ⚠️ Every digital conversation involves processing personal data (e.g., identifiers, names, messages). Under the General Data Protection Regulation (GDPR) and the Law on Information Society Services (LSSI), businesses must inform users and obtain consent before processing such data. Failure to comply can lead to fines and reputational damage. This guide summarizes the legal obligations and best practices for deploying Quick.bot on messaging platforms.

​
GDPR and Data Protection

The GDPR requires a clear legal basis for collecting and using personal data.
  • When a user clicks a chat button and starts a conversation, they provide personal information.
  • You need their explicit consent or another valid legal basis to process it.
Authorities recommend safeguards such as encryption, internal privacy policies, and regular audits to ensure compliance.

​
LSSI and Commercial Communications

  • The LSSI prohibits sending unsolicited marketing messages.
  • To use messaging channels for marketing, you must obtain specific and additional consent from each recipient.

​
EU Artificial Intelligence Act

The EU AI Act (Regulation EU 2024/1689) requires AI providers to publish a summary of the data used to train their models (from 2 August 2025).
Quick.bot relies on third-party AI, and we ensure our providers comply with these transparency obligations.

​
Best Practices for Quick.bot Integrations

​
Displaying the Chat Entry Point

  • Privacy notice: Place a clear notice near the chat button or link to your privacy policy.
  • Explicit consent: Before chat begins, ask users to confirm they accept your privacy policy.
    • If you plan to send promotions, include an additional checkbox: “I agree to receive offers via chat”.
  • Avoid sensitive data: Do not request health, financial, or other sensitive information via messaging platforms.

​
Using Business Accounts & Automated Messages

  • Welcome message: Configure an automatic message that explains data usage.
    Example: “Thank you for contacting us. We will use your data only to respond to your request in accordance with our privacy policy.”
  • No spam: Never send marketing messages without consent.
  • Transparency: Always distinguish service messages from promotional content.

​
Chatbot Transparency & Fairness

  • Inform users that Quick.bot collects data and provide a link to your privacy policy.

​
Cookies & Tracking

Quick.bot may use cookies or tracking pixels.
  • Strictly necessary cookies are allowed without consent.
  • Analytics/marketing cookies require prior consent.

​
Consequences of Non-Compliance

  • Fines: GDPR penalties can reach €20 million or 4% of annual global turnover.
  • Reputation risk: Mishandling personal data erodes user trust and damages your brand.
  • Compliance benefits: Following the law shows professionalism and increases customer confidence.

​
Summary of Recommendations

✅ Provide a visible privacy notice near the chat button.
✅ Obtain explicit consent before processing data.
✅ Add extra consent checkboxes for marketing.
✅ Avoid sensitive data in chat channels.
✅ Configure a transparent welcome message in your chatbot.
By following these steps, you can deploy Quick.bot on messaging platforms responsibly, improving customer support while respecting privacy laws.
⌘I