Privacy Policy

Scope of this policy

Flova is the operating layer for connected products. This policy explains what data Flova handles and why when you use an account, organization, device, API, Console, Studio, or related service.

Account and organization information

To create accounts and manage access, we process information such as your name, email, optional phone number, verification status, sign-in sessions, and sign-in method. Flova also stores organization details, members, roles, invitations, settings, plans, and service usage.

• Session information may include expiration time, IP address, and browser or device details.
• Organization roles and permissions determine which product areas and data each member can access.

Connected-product data

When you build a connected product with Flova, we process data such as Device Typedefinitions, datastreams, hardware mappings, device IDs and names, connection status, firmware versions and configuration, telemetry values, events, and command status.

• Reported device data is used to display dashboards, answer queries, and run product logic.
• Dashboard, API, and automation commands are sent to authorized devices, and delivery results or errors are recorded.

How we use data

Flova uses this data to provide and secure the service, authenticate users, enforce permissions, run automation, store and display telemetry, answer FlovaQL queries, provide support, calculate usage, and improve performance. Data is handled within the relevant organization and its permissions.

Studio, API, and FlovaQL

In Studio, layouts and bindings connect product experiences to real data and commands. Organization applications use the organization API at /api/v1; third-party apps use/api/user-app. Each route is controlled by its credentials and permissions.FlovaQL reads catalog and telemetry data, subject to workspace permissions.

FlovaAI

If you use FlovaAI, your prompt and permitted workspace context, such as device types, datastreams, historical data, or dashboards, are processed to generate a response. AI output is assistance, not a substitute for your judgment. Review and approve sensitive changes before applying them. Usage history is recorded to manage organization credits and consumption.

Sharing and access

Organization members may view or act on that organization’s data according to their roles and permissions. Flova makes data available to authorized staff and necessary infrastructure providers to operate and secure the service, provide support, and deliver selected features. Third-party connections receive data only within the permissions and settings you grant.

Retention and deletion

Access to telemetry history depends on the organization’s plan and the policy for that feature, and may change when the plan changes. Operational data such as security records, billing, sessions, or events needed to run the service may be kept separately from telemetry history. Contact us with your account and organization details to request data access or deletion; we review requests based on the data type and operational requirements.

Security and access responsibilities

Flova uses authentication, roles, organization permissions, request limits, and security event logs to protect the service. You are responsible for protecting passwords, tokens, device credentials, API keys, and activation links. Report suspected access promptly.

Requests and changes

Email hello@flova-cloud.xyz with questions about account or organization data, or to request access or deletion. We may update this policy as the product or operational requirements change. The effective date of the current version appears above.