Privacy
Clear handling for workspace data.
This summary explains the practical data handling FlowMotive is built around. It is intended to support onboarding and trust discussions, not replace tailored legal advice.
What we collect
- Workspace setup details such as business name, contact details, workflow mode, plan interest, and onboarding notes.
- Operational records entered into a workspace, including clients, jobs, invoices, notes, messages, uploaded files, and support history.
- Account and security details needed for login, tenant membership, role access, billing, audit, and support workflows.
How we use it
- To provide the workspace, support day-to-day workflow, and keep tenant data scoped to the right business.
- To respond to support requests, onboarding requests, subscription questions, and operational incidents.
- To maintain activity history, security controls, billing status, and service reliability.
How we protect it
- Access is separated by workspace membership, user role, and permission checks.
- CareFlow documents use private storage and short-lived signed links after access checks.
- Sensitive service credentials are handled through protected deployment settings.
Australian privacy postureFlowMotive is designed around reasonable access control, auditability, tenant separation, and support-safe handling of personal information. Production customers should still confirm their own privacy notices, consent wording, retention rules, and regulated-sector obligations.