DRUID AI

Overview

DRUID AI is a no-code conversational AI platform that enables enterprises to deploy intelligent virtual assistants on customer-facing websites, employee portals, and mobile applications. Unlike simple FAQ chatbots, DRUID AI connects conversational interfaces to backend enterprise systems — ERP, CRM, ITSM, HR platforms — enabling the virtual assistant to perform transactional workflows: submitting insurance claims, checking order status, resetting passwords, scheduling appointments, and processing service requests through natural conversation. The platform is widely deployed in banking, insurance, healthcare, retail, and enterprise IT contexts.

What This Script Does

DRUID AI's scripts embed a conversational virtual assistant on the host website:

Chat widget initialization:

• Loads the DRUID widget script from DRUID's CDN or a self-hosted endpoint, rendering a chat icon (typically in the bottom corner of the page) that expands into a full conversation interface when clicked
• The widget is initialized with a bot ID and tenant configuration that determines which virtual assistant and conversation flows to load

Natural language processing pipeline:

• When a visitor types a message, the widget transmits the message text to DRUID's NLU (Natural Language Understanding) engine via a REST API call
• The NLU engine classifies the intent and extracts named entities (e.g., account number, date, product name) from the message
• The conversation manager determines the next response based on the recognized intent and the current conversation state

Enterprise backend integration:

• For transactional interactions (e.g., "check my order status"), DRUID's backend makes API calls to connected enterprise systems using the credentials and context provided during the conversation
• Results (order details, account information, ticket status) are returned to the conversation and presented to the visitor
• This backend integration is entirely server-side — the visitor's browser never communicates directly with enterprise backend systems

Session and conversation data:

• Sets a session cookie (druid_session_[bot_id], first-party, expires at session end) to maintain conversation context across page navigations within the same visit
• May set a persistent visitor cookie (druid_vid, first-party, 30-day expiry) if the widget is configured to recognize returning visitors and restore conversation history
• Conversation transcripts are stored on DRUID's servers for quality analysis, bot training, and compliance purposes

AI transparency:

• Visitors interacting with DRUID virtual assistants are typically informed they are speaking with an AI assistant through the widget's interface branding

Consent & Compliance

• Category: Functional
• GDPR: Conversation data constitutes personal data processing. DRUID acts as a data processor, with the deploying organization as the data controller. The visitor-initiated nature of chat interactions supports a functional or legitimate interest basis — visitors who click the chat widget are explicitly requesting the service. Session cookies are strictly necessary for the conversation to function. The deploying organization must ensure its privacy notice covers chatbot data processing. A DPA with DRUID is required.
• ePrivacy Directive: The druid_session cookie is strictly necessary for maintaining the conversation state the visitor explicitly initiated. If a persistent visitor identification cookie is configured, this goes beyond session necessity and may require consent.
• Sensitive data in conversation: If the virtual assistant handles sensitive information (health details, financial account numbers, HR matters), additional safeguards and potentially explicit consent for that specific processing are warranted.
• AI transparency: GDPR Article 22 and national AI regulations increasingly require disclosure when decisions are made by automated systems. Visitors should be clearly informed they are interacting with AI.

Should You Block This Without Consent?

No. DRUID AI's virtual assistant serves a functional purpose — providing automated service assistance that visitors actively seek by clicking the chat widget. The session cookies are strictly necessary for the requested conversation service. Blocking would prevent visitors from accessing AI-powered support functionality.