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.
For Android subscriptions, Google Play purchase identifiers, subscription state, expiry, region, and acknowledgement status used to verify access. FlowMotive does not store full payment-card details.

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.
Private documents use protected storage and access-checked download links where enabled.
Sensitive service credentials are handled through protected deployment settings.
Google Play purchase tokens are encrypted at rest; webhook records use one-way token hashes rather than raw purchase tokens.