Clear terms for shared work.

01Agreement

These Terms of Service (“Terms”) are an agreement between you and Agnes Riley, the operator of ThreadOps, concerning the ThreadOps website, hosted application, and related hosted services (the “Service”). By creating an account, joining a workspace, or using the Service, you agree to these Terms and the Privacy Policy.

If you use ThreadOps for an organization, you represent that you are authorized to accept these Terms for that organization. “You” then includes the organization.

02Accounts and workspaces

You must provide accurate account information, keep credentials secure, and promptly notify us of suspected unauthorized use. You are responsible for activity performed through your account unless applicable law provides otherwise.

Workspace owners and administrators manage membership, connected devices, integrations, and shared records. If you invite someone or connect a machine, you are responsible for having the authority and notices needed to do so. Do not connect a device, repository, account, or service you are not authorized to access.

Workspace activity may be shared with other authorized members. Supported actions by members—including Jira assignment and transitions, integration changes, and release approvals or merges—may be attributed to their accounts and preserved with the relevant record. Organizations are responsible for choosing appropriate roles and for their members’ authorized use of connected systems.

03The Service

ThreadOps organizes operational metadata from coding agents, machines, repositories, supported project-management records, selected-channel messages, builds, deployments, and reference links from other connected records. It may link related records into a work graph and allow authorized members to coordinate or request actions. It is an observability and coordination tool, not a substitute for source control, backups, security review, human approval, or professional judgment.

Suggested links, ownership, status, or next steps may be based on automated matching and can be wrong. Review important context in the authoritative provider before relying on a suggestion or taking action.

Task handoff and remote execution

If offered and enabled, task handoff allows an authorized member or workspace policy to send structured instructions and selected context to an approved machine and supported agent runtime. A connected collector does not become a remote worker unless the receiving machine separately enables that capability and its trust settings permit the task.

You authorize an approved worker to execute an accepted task within its configured repository, runtime, and permission mode. Agent execution can read or modify files, create branches or commits, use third-party model capacity, and cause other effects allowed by the receiving account and machine. You are responsible for approved roots, recipients, trust policies, runtime accounts and charges, backups, review of results, and ensuring that dispatched instructions and context may lawfully be shared with the receiving machine and runtime provider.

Dispatch, lease, heartbeat, cancellation, and result delivery can be delayed, interrupted, or duplicated by network or worker failure. Cancellation is not a guarantee that all processes stop immediately or that earlier file, provider, or external effects are reversed. Review the receiving worktree and authoritative systems before retrying or relying on a result.

We may add, modify, or discontinue features. We will use reasonable efforts to avoid materially reducing paid functionality during a current paid term without notice. Preview, beta, or experimental features may change or end at any time.

04Acceptable use

You must not use the Service to:

• break the law or violate another person’s rights;
• access systems, accounts, or data without authorization;
• upload malware or interfere with Service availability;
• bypass security, rate limits, access controls, or plan limits;
• probe or test vulnerabilities without written permission;
• resell access to the hosted Service as a standalone competing service;
• collect sensitive data the Service is not designed to receive; or
• use the hosted Service to build, train, or benchmark a competing product except as permitted in writing.

You may perform ordinary interoperability testing and good-faith security research only within published rules or written authorization.

05Collectors and integrations

You choose whether to install a collector or connect a third-party service. You authorize ThreadOps to access and process the minimum data permitted by the credentials and scopes you provide so the requested connection can work.

If a connected feature supports write actions, an authorized member may direct ThreadOps to send instructions to the provider to assign or unassign Jira work, change Jira workflow state, merge an approved GitHub pull request, or perform another action clearly shown in the Service. You authorize those provider-directed actions when requested through your workspace. ThreadOps may use scheduled synchronization to receive later provider changes.

Third-party services are governed by their own terms and may change or revoke access. We are not responsible for third-party products, their availability, or changes they make. You are responsible for selecting appropriate read and write scopes, confirming member authority, and rotating or revoking credentials when access is no longer needed. Provider permissions still apply; a ThreadOps role does not grant rights in a connected service.

Disconnecting a provider stops future access after processing but does not reverse actions already completed there. Provider events and action results can be delayed, duplicated, incomplete, or rejected. Check the authoritative provider when a result is pending, conflicted, or important.

06Your data

As between you and ThreadOps, you retain ownership of data you submit or direct the Service to process (“Customer Data”). You grant the Service operator a limited, non-exclusive license to host, copy, process, transmit between providers you connect, and display Customer Data only as needed to provide, secure, support, and improve the Service and to meet legal obligations.

You represent that you have the rights and permissions required to provide Customer Data. You are responsible for maintaining independent source-control history and backups. Aggregated or de-identified operational information may be used to understand and improve Service reliability if it cannot reasonably identify you, a workspace, or an individual.

07ThreadOps ownership

The Service, including its hosted software, interface, visual design, documentation, branding, and underlying technology, is owned by the ThreadOps operator or its licensors and is protected by applicable intellectual-property laws. Except for the limited right to use the Service under these Terms, no rights are transferred to you.

Some ThreadOps collectors, plug-ins, or other components may be distributed under a separate software license. That license—not these Terms—governs your right to copy, modify, or distribute those components. These Terms govern access to the hosted Service and do not limit rights expressly granted by a separate software license.

If you provide feedback, you allow us to use it without restriction or compensation, provided we do not publicly identify you as its source without permission.

08Plans and payment

The Service may offer free and paid plans. Current pricing, limits, billing interval, renewal terms, taxes, and cancellation options will be shown before you authorize a charge. We will not charge a payment method without authorization.

A trial may require a payment method and may convert to a paid subscription when the stated trial period ends. Before you confirm, checkout will show the trial length, recurring price, first charge date, and cancellation terms. If paid access ends, we may keep existing workspace history readable while pausing ingestion, syncing, and new setup.

Unless required by law or stated at purchase, fees already paid are non-refundable. We may change future pricing with advance notice appropriate to the plan. Taxes are your responsibility except taxes based on the operator’s income.

09Suspension and termination

You may stop using the Service at any time and may cancel a paid plan through the cancellation method then provided. We may suspend or limit access when reasonably necessary to address a security risk, unlawful use, nonpayment, material breach, or harm to the Service or others.

We may terminate these Terms for material breach or discontinue the Service with reasonable notice when practicable. Provisions that by their nature should survive—such as ownership, disclaimers, liability limits, and payment obligations—continue after termination.

10Disclaimers

To the maximum extent permitted by law, the Service is provided “as is” and “as available.” We disclaim implied warranties of merchantability, fitness for a particular purpose, non-infringement, and uninterrupted or error-free operation.

Agent status, repository state, deployment state, collision warnings, graph links, assignments, workflow state, and integration records can be incomplete, delayed, or inaccurate. Provider actions can fail or remain pending even if ThreadOps received your request. Verify important facts and consequential results in the authoritative system before relying on them.

11Liability

To the maximum extent permitted by law, neither ThreadOps nor its service providers will be liable for indirect, incidental, special, consequential, exemplary, or punitive damages, or for lost profits, revenue, data, goodwill, or business interruption arising from the Service.

To the maximum extent permitted by law, aggregate liability arising from the Service will not exceed the amount you paid for the Service during the 12 months before the event giving rise to the claim. These limits do not apply where applicable law does not permit them.

12General terms

You may not assign these Terms without consent, except as part of a genuine merger, reorganization, or sale of substantially all relevant assets. The Service operator may assign them as part of a business transfer or reorganization.

If a provision is unenforceable, it will be limited to the minimum extent necessary and the rest will remain effective. Failure to enforce a provision is not a waiver. These Terms, the Privacy Policy, and any signed order or service agreement form the agreement about the Service; a signed agreement controls if it expressly conflicts with these Terms.

Any separate written agreement may specify governing law and venue. Otherwise, applicable law determines those questions.

We may update these Terms and will post the revised version with a new effective date. Material changes will receive additional notice when required. For terms questions, contact the operator through the ThreadOps support form.