Skip to main content
ChatFlow
PricingGuides
Log inStart free trial
Privacy

How information moves through ChatFlow.

This operational summary explains the information used for demo enquiries and the data categories a configured ChatFlow workspace may process.

Last updated 30 August 2026
At a glance

Your signed agreement, approved privacy notice, configured providers, and applicable law determine the complete terms for your organisation.

Public storefront enquiries

The 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.

How enquiry information is used

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.

Product workspace information

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.

Service providers and external channels

ChatFlow can connect to external services such as WhatsApp, configured payment providers, and Google Maps Platform for optional storefront address search, exact delivery pins, browser location, and reverse geocoding. Those providers process information under their own terms and the customer’s configuration. When Google Maps is enabled, Google receives the map and location requests needed to provide that feature and processes them under the Google Privacy Policy. The applicable privacy documentation should identify every provider used for your deployment.

Retention and security

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.

Requests and choices

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.

ChatFlow

AI customer operations, bookings, sales, and commerce for service businesses.

From first enquiry to paid work.

Platform

  • Overview
  • Conversations
  • Bookings
  • Sales, payments & commerce
  • Operations & control

Solutions

  • Overview
  • Beauty & wellness
  • Health & clinics
  • Fitness & education
  • Field services

Guides

  • Guides
  • Pricing
  • Security
  • FAQ

Company

  • Start free trial
  • Book a demo
  • Log in
  • Privacy
  • Terms
  • Cookies
Platform
  • Overview
  • Conversations
  • Bookings
  • Sales, payments & commerce
  • Operations & control
Solutions
  • Overview
  • Beauty & wellness
  • Health & clinics
  • Fitness & education
  • Field services
Guides
  • Guides
  • Pricing
  • Security
  • FAQ
Company
  • Start free trial
  • Book a demo
  • Log in
  • Privacy
  • Terms
  • Cookies
© 2026 ChatFlow
PrivacyTermsCookies
Product and pricing details are subject to the applicable order or agreement.