This operational summary explains the information used for demo enquiries and the data categories a configured ChatFlow workspace may process.
Last updated 29 July 2026The demo form submits work email, name, business name, selected business type, workflow notes, optional phone number, source page, referrer, and available campaign parameters to a same-origin server route. A hidden anti-spam field, request rate limits, validation, and an idempotency key protect the intake path.
Enquiry information is used to review the requested workflow, respond to the organisation, prepare a tailored demonstration, understand acquisition context, secure the service, and manage the resulting sales conversation. Submitting the form creates a lead record; it does not book a calendar event or create a paid product account.
A configured workspace can include tenant-scoped customer records, conversations, messages, services, schedules, bookings, invoices, payment status, product and order records, notifications, role assignments, and audit evidence. The exact information depends on enabled capabilities, connected providers, and the applicable agreement.
ChatFlow can connect to external services such as WhatsApp and configured payment providers. Those providers process information under their own terms and the customer’s configuration. The applicable privacy documentation should identify the providers used for your deployment.
Demo-request records include a retention-review field, and the product uses tenant, role, validation, redaction, webhook, idempotency, and audit controls across sensitive paths. Retention follows the approved policy, applicable agreement, and legal requirements.
People may contact ChatFlow about access, correction, deletion, objection, restriction, portability, or consent withdrawal where applicable. Requests may require identity verification and remain subject to the applicable agreement and law.
Questions about this notice? Contact the ChatFlow team.