Privacy note

Only the details needed to build the workflow.

The starter setup uses business information, inquiry examples, and contact details to prepare intake structures and reply drafts.

Last updated: 9 June 2026 Data minimization No private keys or passwords requested

Information collected

  • Business name, website, niche, and public contact channels.
  • Current lead sources such as WhatsApp, email, forms, or social DMs.
  • Example customer questions or anonymized inquiry patterns.
  • Payment confirmation status from approved payment rails.
  • Messages you send to the operator by email, Telegram, WhatsApp, or form.

Information not requested

  • Passwords, OTPs, or account recovery codes.
  • Private keys, seed phrases, or wallet access.
  • Raw payment card details.
  • Sensitive customer data that is not needed for workflow design.

How data is used

Data is used to understand the lead flow, prepare qualification questions, draft response patterns, and support delivery.

Service providers

The workflow may use Google Forms/Sheets, email, Telegram, WhatsApp, Polar, YooKassa, and other tools needed for payment, intake, and communication.

Retention

Project data is kept only as long as needed for delivery, support, record keeping, and improvement of the service.

Client controls

  • Ask for correction of inaccurate project details.
  • Ask to remove nonessential examples or notes after delivery.
  • Share anonymized inquiry examples instead of real customer identities.