Arc logo Arc

Terms

Terms and Conditions

These terms are a simple public summary of how Arc is offered and used. Arc is typically sold and deployed through enterprise agreements, so customer-specific order forms, security schedules, and data terms may add more detail.

Last updated March 10, 2026.

Scope

By accessing Arc’s website or using Arc software, you agree to these terms. If your company signs a separate agreement with Arc, that signed agreement controls where it conflicts with this page.

Using Arc

  • You may use Arc only for lawful purposes and only in systems, apps, and environments you are authorized to access.
  • You must not misuse Arc to bypass permissions, interfere with security controls, or process data you do not have authority to handle.
  • Access credentials and admin tools must be protected and used only by authorized personnel.
  • End users should be able to see that Arc is present and what permissions or features it has been given.

Deployment and feature control

  • Each customer receives a separate Arc deployment boundary with customer-scoped admin controls.
  • Arc can run with a customer-hosted backend or in a customer-controlled environment, including on-prem or firewall-contained licensing models.
  • Features such as screenshots, voice, analytics, login, and onboarding flows are product controls, not hidden behavior, and can be enabled, restricted, or left out.
  • Arc only appears in the apps and environments a customer has approved for the deployment.

Security, updates, and enterprise rollout

  • Arc ships as signed desktop software with controlled updates, allowing customers to approve, stage, or pin releases.
  • Arc is designed to fit a standard enterprise rollout with managed configuration, approved app mappings, and centrally governed settings.
  • If a customer wants behavior changed or stopped, Arc can be controlled centrally by pausing the deployment, disabling a feature, or tightening policy.
  • Arc sits beside the customer’s core product rather than being embedded into it, which helps keep the assistant layer separate from the customer’s primary application.

Data and privacy

Your use of Arc is also governed by the Privacy Policy.

  • Arc is designed to work with minimal data collection and does not need broad behavioral tracking to be useful.
  • Conversation history, support records, and audit logs may be retained as part of a customer’s deployment and support model.
  • Arc’s policy is to prefer zero-data-retention or no-training AI processing modes where available and configured.
  • Customer-specific retention, deletion, and handling rules may be applied at the customer level.

Ownership, availability, and limits

  • Arc retains ownership of its software, website, and related materials. Customers retain ownership of their own data and materials.
  • Arc may suspend or limit access if necessary for security, abuse prevention, legal compliance, or to protect customers and the service.
  • Unless a signed agreement says otherwise, Arc is provided on an as-available basis and uninterrupted operation is not guaranteed.
  • Service levels, commercial terms, and specific commitments are typically defined in enterprise agreements rather than this public summary.