Legal

End User License Agreement

The baseline user terms for accessing Archibot Console, ArchibotChat, shared-hosted workspaces, managed AI routing, documentation, and related services.

Customer adminsCustomer membersPlatform operators

Last updated June 18, 2026

Last updated: June 18, 2026

This End User License Agreement governs access to Archibot Console, ArchibotChat, Archibot shared-hosted workspaces, managed AI routing, documentation, and related services provided by ISM Services, Inc.

By accessing or using Archibot, you agree to this agreement. If you use Archibot for an organization, you represent that you are authorized to use Archibot for that organization and to follow the organization’s Archibot agreement, policies, and admin instructions.

Scope and Definitions

In this agreement:

• “Archibot” means Archibot Console, ArchibotChat, shared-hosted workspaces, managed AI routing, documentation, and related services provided by ISM.
• “Customer” means the organization, team, or other party that obtained access to Archibot from ISM.
• “Customer Content” means source code, repositories, files, databases, backups, prompts, responses, logs, artifacts, configuration, and other content submitted to or used with Archibot.

Relationship to Customer Agreements

Archibot is usually provided under a customer agreement, order form, statement of work, quote, or support arrangement with ISM.

If a signed customer agreement conflicts with this End User License Agreement, the signed customer agreement controls for that customer. Customer admins may also set additional workspace, SSO, billing, repository, security, and acceptable-use rules for their users.

Service Tiers and Operating Modes

Archibot may be offered in service tiers or deployment shapes such as shared-hosted, dedicated-tenant, dedicated-release, or dedicated-cluster arrangements. The applicable customer agreement determines the approved tier, hostnames, workload placement, support profile, and whether any vendor-managed services are included.

Shared-hosted access is acceptable only with customer-scoped isolation and without unrestricted visibility into unrelated customers. Dedicated tiers may provide stronger separation, branding, or operational boundaries when the customer agreement requires them.

Hosting Model and Infrastructure Responsibilities

Archibot may be delivered in ISM-hosted shared or dedicated environments, or in customer-hosted environments where ISM provides approved vendor-managed services. The applicable customer agreement determines the approved hosting model, primary region, public ingress or hostname, and whether dedicated infrastructure, customer-hosted deployment, or regional commitments are included.

Unless a signed customer agreement says otherwise, ISM does not promise customer-dedicated hosting, a specific cloud provider or region, local data residency, custom backup schedules, disaster-recovery objectives, or direct cluster or cloud administration access.

If the customer provides or controls the hosting environment, cloud account, network, or connected infrastructure, the customer is responsible for having authority to use it, following provider terms, approving changes, and paying third-party infrastructure costs unless a signed customer agreement assigns those responsibilities differently.

Regional Availability and International Customers

Archibot is intended for business and organizational use. Availability may vary by country or customer profile, and ISM may decline, limit, or delay service where legal, sanctions, export-control, tax, privacy-transfer, payment, language, support, or operational requirements make a deal unsuitable for the standard service model.

International provisioning may require business verification, additional contract terms, payment verification, transfer safeguards, or country-specific approvals before service begins.

License and Access

Subject to this agreement and the applicable customer agreement, ISM grants you a limited, non-exclusive, non-transferable, revocable right to access and use Archibot for authorized business purposes.

You may use Archibot only for the customer account, tenant, workspace, repository, chat, API key, artifact, and support workflows you are authorized to access.

Customer Admin Authority

Customer admins may manage memberships, tenant scope, workspace access, billing readiness, support contacts, connected providers, and other customer-specific configuration.

You agree that ISM may rely on reasonable instructions from the Customer and its authorized customer admins for account setup, support handling, access scope, billing routing, and workspace administration unless law or a signed agreement requires otherwise.

In shared-hosted arrangements, customer-admin authority is limited to that customer’s approved scope and does not include unrestricted administration of a shared host tenant, cluster, or another customer’s records.

Authorized Users

You are responsible for activity through your account, tokens, connected providers, and workspaces.

You must:

• Keep login credentials, invite links, tokens, API keys, SSH keys, and provider credentials confidential.
• Use only accounts and customer scopes assigned to you.
• Follow your organization’s policies and customer-admin instructions.
• Report suspected compromise, mistaken access, exposed secrets, billing issues, or workspace abuse promptly.

You may not share accounts, bypass SSO, impersonate another user, or use another customer’s data, workspace, billing account, repository, artifact, or provider credentials.

Customer Content

As between you and ISM, you or your organization retain ownership of Customer Content. You grant ISM the rights needed to host, process, transmit, copy, display, troubleshoot, secure, and support Customer Content for Archibot services and related customer support.

Do not upload or submit content that you are not authorized to use.

Onboarding, Approval, and Provisioning

Archibot onboarding may include qualification, requirements survey, operator review, quote generation, approval, provisioning, validation, and handoff steps. ISM is not required to provision customer resources immediately after an intake form or survey submission.

Provisioning, upgrades, higher-isolation tiers, public exposure, premium sizing, unusual retention, and certain integrations may require commercial approval, security review, billing verification, or explicit operator approval before access is activated.

ISM Services and Intellectual Property

Archibot, the service software, documentation, branding, and other ISM-provided materials are owned by ISM or its licensors and are protected by law.

Except for the limited access rights granted in this agreement and any signed customer agreement, no license or ownership right is transferred to you. You may not remove proprietary notices or present Archibot as your own hosted service.

AI and Provider Services

Archibot may route requests to managed AI providers, customer-provided AI providers, or customer-selected development tools.

AI outputs can be inaccurate, incomplete, unsafe, or unsuitable for your use case. You are responsible for reviewing AI output before relying on it, committing it, deploying it, or sending it to customers or third parties.

Do not submit secrets, private keys, passwords, regulated personal information, customer-confidential data, or third-party confidential data to AI tools unless your organization has approved that use and the configured provider terms allow it.

ISM does not sell Customer Content or use ArchibotChat prompts, responses, uploads, artifacts, or transcripts to train general-purpose AI models. AI providers may process prompts and responses to provide the requested feature, subject to provider configuration, provider terms, and the customer agreement.

Customer-selected third-party providers may process requests under their own terms, privacy policies, security practices, and data-handling commitments.

Sensitive Data and Regulated Use

Unless a signed customer agreement and the configured customer workflow expressly allow it, do not use Archibot for:

• Payment card data, bank-account credentials, or other regulated payment information.
• Health, biometric, student, export-controlled, or other specially regulated data.
• Secrets, private keys, production database credentials, or one-time access links that are not required for the approved workflow.
• Data that you are prohibited from sharing with ISM, a workspace provider, an identity provider, or a configured AI provider.

Hosted ArchibotChat is a commercial SaaS product unless a signed customer agreement says otherwise. Do not submit data through public ArchibotChat, commercial Archibot-hosted tenants, API keys, uploads, account exports, support requests, or activity evidence unless your organization has approved that data for the configured commercial processing path. Customers with special security, regulatory, data-residency, or deployment requirements should request the enterprise security packet before use.

Artifacts and Persistent Environments

Archibot may provide customer-scoped artifact catalogs, S3-compatible storage paths, database seeds, WAR artifacts, ArchibotChat uploaded or generated artifacts, and persistent environments for shared dev, test, stage, demo, training, or integration use.

Persistent environments are customer-owned shared runtimes, not personal entitlements to a specific user’s workspace lifecycle, unless a signed customer agreement says otherwise. Artifact access, environment actions, retention, exposure mode, backup policy, and allowed users or groups may be limited by the customer’s service plan, approvals, and technical controls.

Public ingress, premium sizing, dedicated placement, unusual retention, custom artifact access, or destructive rebuild, reseed, snapshot, restore, clone, or delete actions may require explicit approval or additional terms.

Acceptable Use

You may not use Archibot to:

• Violate law, sanctions, export controls, privacy rights, intellectual-property rights, or contractual obligations.
• Access, scan, attack, disrupt, overload, or bypass security for systems you are not authorized to use.
• Exfiltrate, expose, sell, share, or misuse secrets, credentials, personal information, customer data, or proprietary information.
• Upload malware, credential stealers, exploit kits, destructive code, or intentionally harmful artifacts.
• Mine cryptocurrency or run unrelated high-consumption workloads.
• Interfere with other customers, shared infrastructure, billing systems, monitoring, or support workflows.
• Reverse engineer, copy, resell, sublicense, or provide Archibot as a competing service except where law expressly permits.

Workspace and Repository Responsibilities

You are responsible for code, commands, packages, repositories, databases, backups, and external services you use in a workspace.

Workspaces may have prepaid balances, runtime limits, storage limits, node-pool limits, artifact boundaries, and customer-specific policies. ISM or customer admins may stop, update, delete, suspend, or restrict workspaces to protect security, availability, billing integrity, or shared infrastructure.

Billing and Prepaid Balances

Catalog, prepaid balance, metered usage, invoice, ACH, bank-transfer, trial, and operator-approved billing workflows are governed by the customer agreement and the visible billing state in Console.

Prepaid balances and included shared chat credit allowances are accounting entries for workspace runtime, managed AI access, ArchibotChat, and API-key use. They are not cash accounts, bank accounts, stored-value cards, or general-purpose credits unless a customer agreement says otherwise.

ArchibotChat Starter and Team plans may include a monthly allowance of shared chat credits. One shared chat credit covers a single user-submitted prompt that asks Archibot to respond. An API-key request that is accepted for response processing draws from the same shared chat credit balance. Streaming chunks, internal retries, tool traces, and citations belong to the associated request unless the visible plan terms say otherwise.

Credits expire one year after grant unless the applicable signed customer agreement says otherwise. Failed preflight checks that are blocked before model-side work begins should not debit shared chat credits. Refunds, credits for failed requests, overages, plan changes, and disputed charges are handled under the applicable customer agreement, checkout terms, and support review.

Workspace creation, ArchibotChat prompts, and API-key calls may be blocked until required billing review, checkout, workspace-time balance, managed-AI balance, shared chat credit balance, product gate, and operator approval conditions are satisfied.

Provisioning and continued service may also depend on qualification, quote approval, billing verification, service-plan limits, and operator approval for higher-risk or higher-cost configurations.

You are responsible for taxes, duties, levies, bank fees, currency-conversion costs, and similar governmental or financial charges associated with your purchase or use of Archibot, except for taxes based on ISM’s net income, unless a signed customer agreement says otherwise.

Third-Party Services

Archibot may integrate with third-party services such as identity providers, Coder, Stripe, Git providers, cloud infrastructure providers, email services, observability tools, support tools, and AI providers.

Third-party services are governed by their own terms and policies. ISM is not responsible for third-party services outside ISM’s control, but ISM may use them to provide Archibot under the customer agreement.

Preview and Experimental Features

Archibot may include preview, beta, or experimental features. Those features may change, be limited, be withdrawn, or be unsupported at any time unless a signed customer agreement says otherwise.

Preview and experimental features may have additional usage limits, support limitations, or data-handling constraints.

Support Boundaries and Vendor-Managed Services

Standard support covers the Archibot platform, approved onboarding path, routine service operation, and approved integrations identified in the customer agreement. Standard support does not make ISM the customer’s general product-engineering, application-development, or custom-operations team inside the customer’s own environment.

If the customer purchases or receives vendor-managed onboarding, automation, or support, those services are limited to approved runbooks, approvals, and service-plan boundaries. Anything outside that approved scope may require a separate statement of work, change order, or commercial approval.

Feedback

If you submit ideas, requests, feedback, bug reports, or suggestions, ISM may use them without restriction or obligation to you, as long as ISM does not disclose Customer Content or confidential information except as permitted by the customer agreement.

Do not include secrets, payment credentials, raw invite links, provider keys, private customer data, or regulated data in feedback.

Confidentiality and Security

You must protect confidential information you access through Archibot. You must not disclose another customer’s information, ISM non-public operational information, credentials, provider keys, or security-sensitive details without authorization.

ISM may investigate suspected misuse, security incidents, billing fraud, policy violations, unauthorized access, or service abuse.

Suspension and Restrictions

ISM may suspend, restrict, throttle, or remove access to Archibot, workspaces, integrations, or related services if:

• Required billing, trial, or commercial approval is missing or revoked.
• Use threatens security, availability, reliability, or shared infrastructure.
• A user or customer violates this agreement, a customer agreement, provider terms, or law.
• Access appears compromised, fraudulent, abusive, or unauthorized.
• Material overages or high-cost actions proceed without required approval.
• Suspension is needed to comply with legal, payment-provider, or security obligations.

When practical, ISM will work with customer admins to resolve the issue.

Termination

Your right to use Archibot ends when your account is disabled, the customer agreement ends, your organization removes your access, or ISM terminates access under this agreement.

After termination, ISM may retain or delete data according to the customer agreement, retention requirements, support needs, security obligations, and applicable law.

Sections that by their nature should survive termination, including customer-content rights granted for support and operations already performed, confidentiality, disclaimers, liability limits, and payment obligations, will continue to apply.

Offboarding and Export

Unless a signed customer agreement says otherwise, offboarding may include export of approved customer artifacts, ArchibotChat account records, conversation metadata, and configuration metadata, access revocation, retention of audit and billing records for a defined period, and scheduled deletion of runtime resources after the applicable retention window.

Export scope, timing, format, and any post-termination access window are governed by the customer agreement, security requirements, retention duties, and technical feasibility.

Disclaimers

Archibot is provided “as is” and “as available” except as expressly stated in a signed customer agreement.

ISM does not promise that Archibot will be uninterrupted, error-free, secure against all threats, or compatible with every repository, provider, template, database, browser, extension, AI model, or workspace configuration.

AI output, diagnostics, generated code, documentation, support guidance, and operational recommendations require human review before production use.

Limitation of Liability

To the maximum extent permitted by law and except as stated in a signed customer agreement, ISM will not be liable for indirect, incidental, special, consequential, exemplary, or punitive damages, or for lost profits, lost revenue, lost data, lost goodwill, or business interruption.

Any monetary liability is limited by the applicable customer agreement. If no customer agreement applies, liability is limited to the amount paid for the affected Archibot service during the three months before the event giving rise to the claim.

Some jurisdictions do not allow certain exclusions or limitations, so parts of this section may not apply.

Updates

ISM may update this agreement as products, providers, security requirements, commercial terms, or legal requirements change. The “Last updated” date shows when this page was last changed.

Continued use after an update means you accept the updated agreement, unless a signed customer agreement says a different amendment process applies.

Contact

For questions about this agreement, contact your customer admin or the support contact listed in your Archibot agreement or Console.

Related guides

• Privacy Policy for how ISM handles personal data and Customer Content.
• ArchibotChat approved data use for the sensitive-data and commercial-processing boundaries in practice.
• ArchibotChat billing and credits for how shared chat credits are granted and consumed.
• Usage and billing for prepaid balances and metered workspace usage in Console.
• Access roles for customer-admin authority and member scope.