This Acceptable Use Policy (“Policy”) describes the rules governing the use of software products, cloud services, APIs, websites, applications, integrations, and related services (“Services”) operated by Fluixio Technologies Private Limited (“Fluixio”, “we”, “our”, or “us”).

This Policy applies uniformly to all Fluixio products and Services unless an independent product-specific commercial agreement or framework explicitly overrides these conditions. By accessing, purchasing, or interacting with any level of our Services, you agree to comply in full with this Policy.

Our singular goal is to maintain a secure, highly reliable, and trusted environment for all customers, businesses, and developers. This Policy sets operational boundaries designed to isolate and protect our customers, business channels, third-party platform integrations, core Fluixio cloud infrastructure, and wider internet ecosystem resources from malicious intent, degradation, or systemic abuse.

You may leverage the assigned operational capabilities of the Services strictly under the following criteria:

• Exclusively for lawful and compliant corporate or personal purposes.
• In complete accordance with all applicable regional, national, and international laws or regulations.
• In total alignment with our core Terms of Service and specific published product technical documentation.
• Exclusively within the intended, documented functionalities of the particular Service interface.

You are strictly prohibited from utilizing the Services to engage in, facilitate, or promote any of the following behaviors:

Where Fluixio provides application programming interfaces (APIs) or webhooks, client systems and developer workflows must not:

Note: Fluixio maintains the absolute right to enforce dynamic rate throttling, traffic shaping, and payload size limitations to guarantee underlying multi-tenant node stability.

Many Fluixio ecosystems rely on pipelines exchanging database blocks with third-party networks. Customers hold exclusive liability for ensuring that data orchestration actions performed via Fluixio stay completely compliant with the external terms, acceptable use parameters, and platform agreements enforced by those corresponding providers.

Account handlers must not submit, host, stream, or log properties containing binary code variations designed to exploit network sockets, content infringing proprietary trade secrets, or files explicitly engineered to break multi-tenant workspace containment layers. The individual account owner remains uniquely responsible for validating all content passed through their integration nodes.

Customers must strictly refrain from sharing multi-factor administrative tokens, executing unmapped boundary stress tests, injecting memory overflow payloads, running unauthorized fuzzing scripts, or sniffing telemetry files belonging to other workspaces.

Suspected architecture gaps or code exceptions must be directed exclusively through the guidelines established inside our Responsible Disclosure Policy.

Accounts must not force excessive server calculations or network volumes that impact other multi-tenant workspace pipelines. This includes processing constant high-density API call clusters that bypass threshold layouts, creating loops intended to max out cloud processing configurations, or repeating operations designed to exhaust system capacity.

Users are strictly barred from mirroring Fluixio platform source blocks, white-labeling or reselling active software channels without formal authorization, modifying structural legal or branding notices, reverse engineering code segments to map proprietary algorithms, or spinning up unauthorized lookalike frameworks.

Operators or platform entities spotting a violation of these usage structures are urged to communicate the metrics clearly to our operations desk. Please attach replication data blocks or logs to allow our teams to audit the anomaly effectively.

We alter this Acceptable Use Policy periodically to match changing cloud infrastructures and global compliance standards. Continued platform interaction following a revised update cycle denotes automated acceptance of the modified layout.