Privacy notice

This notice applies to the website, commercial discussions, onboarding and configured Building Bots services. The precise data-fiduciary/controller and processor role will be stated for each managed, hybrid or customer-hosted engagement.

Contact and business details; enquiry and requirements content; authorised-user and account details; approved business knowledge and source documents; configured conversation and workflow content; approvals and audit events; connection metadata; support records; billing records; and technical or security logs. Sensitive, clinical, biometric, children’s or regulated data is not accepted by default merely because a field permits entry.

To respond to enquiries, prepare a custom quotation, configure and provide selected services, retrieve approved business knowledge, coordinate specialist tasks, record approvals, support users, secure the service, prevent misuse and meet applicable obligations. Data is not authorised for unrelated marketing or model training merely because it enters a workflow.

A configured workflow may send only necessary, authorised context to a selected provider or connected platform after the required connection, permission and disclosure steps. Customer credentials remain customer-owned. Catalogue entries—including social channels, Apify, WooCommerce and planned agents—are not represented as active until implemented and tested.

Conversation text does not automatically become approved business knowledge or permission to act. Publishing, commercial acceptance, spending, partner activation, commerce changes and similar consequential actions follow the configured human approval boundary.

Each category should be kept only for a documented operational, contractual, security or legal need. Cancellation is not automatic deletion. A deletion workflow must separately cover live data, files, derived indexes, integrations and eventual backup expiry. Per-client isolation, least privilege, provenance and audit controls are intended, but this notice does not claim certification, zero risk or zero provider retention.

Requests for access, correction, deletion, withdrawal or grievance may be sent to support.buildingbots@gmail.com. Identity and authority will be verified before records are disclosed or changed. Applicable rights depend on the law and context.

Production processor list, locations and transfer terms; product-by-product data map; legal basis/authorised ground; retention and backup schedule; privacy request workflow; age restrictions; incident notice process; and final controller/processor allocation.