Browse docs
Legal
Privacy Policy
How CONXA collects, uses, stores, shares, and protects information across the website, dashboard, Build Studio, cloud services, and runtime telemetry.
Summary
- CONXA collects account, workspace, billing, product usage, package, support, and telemetry information needed to provide the service.
- Target-site browser session files are local-only runtime or Build Studio state and are not intended to be uploaded in skill packages.
- CONXA does not sell personal information or use advertising cookies by default.
Scope of this policy
This Privacy Policy explains how CONXA handles information when you visit the website, sign in to the cloud dashboard, use the Build Studio, publish packages, install the runtime, contact support, or use billing features.
If your organization signs a separate agreement, data processing addendum, order form, or enterprise security document with CONXA, that written agreement controls where it conflicts with this public policy.
Information we collect
| Category | Examples | Purpose |
|---|---|---|
| Account and identity information | Name, email, organization, sign-in identifiers, workspace role, and authentication metadata from Clerk or similar providers. | Create accounts, secure dashboard access, manage workspaces, and support account recovery. |
| Workspace and plugin information | Plugin names, slugs, workflow names, package versions, installer metadata, usage meters, and publish status. | Host packages, show dashboard state, enforce plan limits, and deliver updates. |
| Build and compile information | Recorded workflow metadata, step descriptions, selected screenshots, DOM-derived signals, validation settings, and compile logs where submitted for compile-time assistance. | Generate and improve skill packages, troubleshoot build failures, and meter compile usage. |
| Billing information | Plan tier, subscription status, payment provider identifiers, billing period, checkout events, and invoice-related metadata. | Operate subscriptions, process payments, prevent fraud, and maintain tax or accounting records. |
| Telemetry information | Skill identifiers, run status, timestamps, recovery counts, duration, compact errors, runtime version, and package version. | Provide observability, diagnose failures, improve reliability, and measure product health. |
| Support information | Messages, screenshots, logs, attachments, contact details, and diagnostic context that you choose to send. | Respond to support requests and investigate incidents. |
Local-only browser session data
Target-application browser sessions can contain cookies, local storage, and authentication state. CONXA treats this as sensitive local state. It is used by the Build Studio or runtime on the local machine and is not intended to be included in published skill packages.
The runtime stores browser sessions locally and encrypts them at rest where supported. You should not upload auth files, browser profiles, passwords, or raw customer credentials to CONXA support unless a secure support process is agreed first.
How we use information
- Provide, secure, and operate the website, dashboard, Build Studio, cloud APIs, and runtime update services.
- Authenticate users, manage workspace membership, and enforce plan entitlements.
- Compile and repair workflows when you request compile-time AI assistance.
- Host skill packages and installers and deliver updates to installed runtimes.
- Process payments and maintain subscription records.
- Send service messages, security notices, support responses, and operational updates.
- Detect abuse, investigate failures, maintain logs, and improve product reliability.
- Comply with applicable law, accounting duties, dispute resolution, and legal process.
Compile-time LLM processing
CONXA may route compile-time prompts to third-party LLM providers or model infrastructure when you request compilation, semantic repair, selector repair, visual anchor generation, or related Human Edit assistance.
The information sent to an LLM provider depends on the feature. It may include workflow descriptions, selected DOM context, element metadata, validation goals, or selected screenshots. It should not include target-site browser session files or passwords.
Runtime execution of an already compiled skill is separate from compile-time LLM assistance. The cloud does not execute your target workflow merely because a build-time model was used to create the skill package.
Retention
CONXA keeps information for as long as needed to provide the service, maintain business records, comply with legal obligations, resolve disputes, enforce agreements, and protect the service.
Retention may vary by plan and data type. For example, telemetry retention may be shorter on free or starter tiers and longer on enterprise terms. Support records and billing records may be kept longer when needed for accounting, tax, fraud prevention, or legal reasons.
Your privacy rights
Depending on where you live, you may have rights to access, correct, delete, restrict, object to, export, or receive information about personal data processing. You may also have rights related to consent withdrawal, grievance redressal, nomination, or non-discrimination.
To make a request, contact noreplay@conxa.in. We may need to verify your identity and workspace authority before acting on a request. If your employer or customer organization controls the workspace, CONXA may direct your request to that organization where appropriate.
Children
CONXA is a business software platform. It is not directed to children, and users should not create accounts or submit personal information if they are not legally permitted to use business software services in their jurisdiction.
International transfers
CONXA may process information in countries other than your own through hosting, identity, support, payment, and LLM service providers. Where required, transfer safeguards should be addressed through customer agreements, subprocessors, or applicable statutory mechanisms.
Contact
For privacy questions, data requests, or complaints, contact noreplay@conxa.in. Enterprise customers should also use any support channel or contract contact specified in their order form.
Drafting references
These public resources informed the policy structure. They are not a substitute for legal review.
Related docs
Data Processing
Plain-language explanation of customer and CONXA data roles, subprocessors, local-only data, deletion requests, and enterprise DPA expectations.
Cookie Policy
How CONXA uses essential cookies and similar technologies for authentication, checkout, security, and service operation.
Security
Security boundaries, local execution guarantees, auth handling, token storage, and practical operational limits.
Terms And Conditions
Terms for using CONXA websites, dashboard, Build Studio, cloud APIs, package hosting, installers, and runtime services.