Terms And Conditions

These Terms and Conditions govern access to and use of CONXA websites, cloud dashboard, Build Studio, runtime, package hosting, installer distribution, support, and related services.

If your organization has a signed agreement, order form, data processing addendum, or enterprise terms with CONXA, that written agreement controls where it conflicts with these public terms.

Build Studio is licensed to you, not sold. Subject to your plan and to these terms, CONXA grants you a limited, non-exclusive, non-transferable, revocable licence to install and run one copy of Build Studio per licensed machine, on machines you or your organization own or control, and only for the number of installs your plan or order form permits.

The licence is granted for your internal business purpose of recording, compiling, testing, publishing, and distributing your own skill packages and installers. It ends automatically when your subscription ends, when your plan no longer covers the install, or when CONXA terminates access under these terms. On termination you must stop using Build Studio and remove it from your machines.

CONXA and its licensors own all right, title, and interest in Build Studio, the CONXA cloud services, the local runtime, the recorder, the compiler, the element-identity and self-healing recovery logic, the templates shipped inside generated packages, and all related intellectual property. These terms grant you the licence described above and no other rights, express or implied.

The skill packages, installers, and workflow content you create with Build Studio are yours. Subject to your plan capabilities and to the acceptable-use rules in these terms, you may use, bundle, distribute, and sell those packages and installers to your own end customers under your own name and commercial terms.

That freedom covers what you build, never the tool that built it. Distributing a skill package or an installer you produced is permitted; distributing, reselling, white-labeling, or otherwise providing Build Studio itself, in whole or in part, is not.

Generated packages and installers include CONXA runtime components under the licence CONXA grants to your end customers through the installer. You must not modify, repackage, or strip those components, and you must not represent them as your own software.

You retain ownership of workflow recordings, workflow names, step descriptions, screenshots, skill package metadata, package content, support materials, and other content you submit or create through CONXA.

You grant CONXA the rights needed to host, process, transmit, analyze, compile, package, update, support, secure, and operate that content for the service. This includes using authorized service providers and LLM providers for requested build-time features.

You represent that you have the rights and permissions needed to record workflows, automate the target application, publish packages, distribute installers, and process any data involved in those workflows.

CONXA skills execute on the end user machine through a local runtime. You are responsible for ensuring that each end user is authorized to access the target application and perform the workflow being automated.

You are responsible for endpoint security, operating system permissions, target-site account controls, browser session hygiene, and compliance with your own contracts and policies for the software being operated.

Paid plans are subscription services unless an order form says otherwise. Self-serve paid checkout may use Razorpay or another payment provider. Enterprise plans may use custom procurement, invoicing, and written commercial terms.

Plan limits may include seats, machines/devices, Conxa Execute seats, monthly compile credits, and AI Usage Credits pools, along with which capabilities a plan unlocks — internal or external distribution, dashboard and audit-log depth, and bring-your-own-key. CONXA may enforce these limits automatically through the dashboard, Build Studio, backend APIs, or support processes.

Taxes, payment fees, foreign exchange costs, and bank charges may apply depending on the payment method, jurisdiction, and customer setup.

CONXA depends on third-party services such as identity providers, payment processors, hosting platforms, model providers, MCP clients, browsers, operating systems, and target applications. Those services may have their own terms and privacy policies.

CONXA is not responsible for target-application behavior, target-application availability, customer endpoint configuration, MCP client changes, or third-party provider outages outside CONXA control.

CONXA may change, improve, suspend, remove, or limit features as the product evolves. Public docs describe current intended behavior and may be updated over time.

No public docs page creates a service-level agreement, uptime commitment, support response time, security certification, or custom compliance obligation unless that commitment is included in a signed agreement.

To the maximum extent permitted by law, CONXA is provided on an as-is and as-available basis. CONXA does not guarantee that every workflow will compile, recover, execute, or remain compatible with future target-application changes.

To the maximum extent permitted by law, CONXA is not liable for indirect, incidental, special, consequential, exemplary, or punitive damages, or for lost profits, lost revenue, lost data, business interruption, target-application account action, or unauthorized customer-side use.

CONXA may suspend or terminate access if you violate these terms, fail to pay, create security risk, misuse the service, or use the platform in a way that may harm CONXA, users, third parties, or target applications.

You may stop using CONXA at any time. Some records may remain as needed for billing, security, legal, backup, dispute, or compliance purposes.

These public terms are drafted for an India-oriented SaaS service. Unless a signed agreement says otherwise, disputes should first be escalated to CONXA support for good-faith resolution.

The exact governing law, venue, arbitration, tax, and procurement language for enterprise customers should be set in the signed order form or master agreement rather than inferred from public docs.

Questions about these terms can be sent to noreplay@conxa.in.