C
CONXA
Browse docs
Docs home

Product docs

Platform OverviewClaude Automation With CONXABuild StudioConxa CloudRuntime And MCP Execution

Trust and security

Security

Legal

Privacy PolicyTerms And ConditionsCookie PolicyAcceptable Use PolicyData Processing

Billing

Billing And Refund Policy

Support

Support
Page sections
Authorized use onlyProhibited activityCustomer responsibilityEnforcementReport abuse

Legal

Acceptable Use Policy

Rules for safe, lawful, and authorized use of CONXA workflow recording, packaging, installers, runtime, and cloud services.

Updated June 11, 20267 min read

Summary

  • Use CONXA only for workflows and systems you are authorized to operate.
  • Do not publish packages or installers containing credentials, malware, or intentionally harmful automation.
  • Do not bypass plan, security, workspace, or target-application controls.

Authorized use only

You may use CONXA only for workflows, websites, products, accounts, and data that you are authorized to access and automate. Authorization must come from your organization, the target system owner, your customer agreement, or applicable law.

Prohibited activity

  • Credential theft, phishing, session hijacking, account takeover, spam, scraping where prohibited, or unauthorized account creation.
  • Packaging passwords, API keys, browser storageState files, session cookies, malware, droppers, or intentionally harmful scripts.
  • Automating regulated, high-risk, or safety-critical workflows without required human review, approvals, records, and legal authority.
  • Bypassing rate limits, plan limits, security checks, workspace isolation, target-application restrictions, or payment controls.
  • Using CONXA to harass, surveil, discriminate, defraud, impersonate, or violate privacy rights.
  • Testing vulnerabilities or running load tests against CONXA without written authorization.

Customer responsibility

Customers are responsible for reviewing compiled workflows before distribution, confirming that installers go only to authorized users, and ensuring that end users understand what a skill will do before execution.

Customers must maintain appropriate access controls in the target application. CONXA cannot determine whether a particular end user should be allowed to perform a business action inside the customer product.

Enforcement

CONXA may investigate suspected misuse and may suspend accounts, revoke hosted installers, restrict package sync, remove content, contact workspace admins, or terminate service where misuse creates legal, security, operational, or reputational risk.

Report abuse

Report suspected abuse to noreplay@conxa.in. Include the workspace, plugin slug, installer URL, timestamps, and a concise description of the concern.

Related docs

Terms And Conditions

Terms for using CONXA websites, dashboard, Build Studio, cloud APIs, package hosting, installers, and runtime services.

Security

Security boundaries, local execution guarantees, auth handling, token storage, and practical operational limits.

Support

How to contact CONXA for product help, billing questions, security reports, privacy requests, and enterprise procurement.