1. Data captured in the product
ChatRobot stores workspace accounts, memberships, agent settings, widget configuration, conversations, routed action records, knowledge content, billing state, API keys, and audit logs needed to operate the service.
Privacy and data handling
How ChatRobot handles workspace, visitor, and billing data.
This page explains what ChatRobot stores, why it is stored, which processors are involved, and what operators control before a workspace goes live.
Workspace isolation
Audit records
Processor visibility
6 min
from website URL to first agent
4 routes
email, webhook, HubSpot, Zendesk
1 script
to launch the widget on a live site
Knowledge pages
42 indexed
Ready routes
3 configured
Credit mode
Starter / Venice
Widget conversation
Business accounts can use invoice billing and get priority support.
Please have sales follow up.
Routed action: Lead Capture -> CRM Webhook
Latest handoff
Lead captured
Ops Director at Northline Parts
Source used
Billing FAQ + Pricing article
Delivery
Webhook accepted in 241 ms
2. Visitor conversation data
Widget conversations can include visitor messages, origin metadata, optional lead capture details, and routed follow-up payloads. Teams should only publish the widget where they are prepared to receive and retain that traffic.
3. Uploaded and crawled knowledge
Website crawl output, manual articles, FAQs, and uploaded TXT, MD, or PDF files are converted into searchable Knowledge records so the workspace agent can answer from published material.
4. Processors and providers
The current product can use Venice or a workspace BYO OpenAI-compatible provider for AI responses, Stripe for billing, and operator-configured mail or connector endpoints for routed follow-up.
5. Operator controls
Workspace status, allowed widget origins, connector delivery proofs, audit history, and launch readiness checks exist so operators can control whether a workspace is safe for public traffic.
6. Privacy contact and requests
Privacy questions and deletion requests should be sent to [email protected] so the operator can verify workspace ownership before processing them.
7. Retention and deletion
Teams should define their own retention policy before launch. ChatRobot should only be used in production after legal, privacy, and storage configuration are reviewed against the actual deployment environment.
Ready