Skip to content
SphereHarness SphereHarness
  • Features
  • Pricing
  • Help
  • Blog
  • Community
  • Contact sales
Sign in Start free trial
Features Pricing Help Blog Community Contact sales
Sign in Start free trial

SphereHarness – End User Licence Agreement

Last updated: 26 October 2026 (agreement version 2026-10-26). PLM CAD Utilities AS ("we", "us", "the Licensor"). "You" means the person who installs or uses the software and, where that person acts for an organisation, that organisation as well. By installing or using SphereHarness you agree to this Agreement. If you do not agree, do not install the software.

1. What this software does

SphereHarness is an assistant that plugs into SOLIDWORKS, Autodesk Inventor, Siemens NX, Solid Edge and AutoCAD, together with a desktop agent that runs on your computer and the online services we operate for your account, your licence, software updates, help and support. It accepts instructions in ordinary language and carries them out by calling the CAD system's own programming interfaces. It can create and modify geometry, drawings, assemblies and files, run simulations, generate documents, and read and write data in connected PDM or PLM systems. It can also record, store and replay macros, generate design variations, run skills and other saved sequences, execute approved scripts and code, connect to systems you direct it to, and – where you enable it – carry out a sequence of operations under a single approval or without asking you again for each step.

In this Agreement "the software" means all of those parts together, and an "operation" means any action the software performs in your CAD session, on your files, or against a system it is connected to.

Where the work happens. The AI model that interprets your instructions is one you choose (section 8): a provider with which you or your organisation hold an account, or a model or agent you run yourself; or, only if you choose the "SphereHarness server" option in the desktop agent, the optional server AI service described in section 7c. Unless you choose that option, we do not run AI models for you on our servers, and your instructions, the AI's answers and the operations carried out in your CAD session pass between your computer, your CAD system and the AI you chose; they do not pass through our servers, except the messages you choose to send through a messaging relay (section 7a), which we pass on without storing them. Connections to your other systems (sections 10 and 11) are stored on your organisation's own server or on your computer, and are made directly from your computer. Our servers handle your account, your licence (section 3), software updates, help, the support requests and feedback you choose to send us, and the community forum, the content catalogue and the marketplace when you use them (section 13a). The server AI service in section 7c is optional and is the only service in which we arrange an AI model for you. If we offer other hosted services in future, separate terms will apply to them, and we will ask you to accept those terms before you use them.

2. Licence granted to you

We grant you a non-exclusive, non-transferable, revocable licence to install and use the software on the number of seats covered by your subscription, for your own internal engineering work, for as long as that subscription is paid and current. A seat is named-user: it is assigned to one identified individual, and it may not be shared, passed round a team, or used by more than one person. A trial licence is for evaluation only. We may change how the software works between releases, provided we do not materially reduce the functionality your paid subscription covers during the term you have paid for.

3. Licence control: one user, one computer

A seat may be in use on one computer at a time, and only with the CAD products your subscription covers. So that the seat limit can be enforced, and so that a seat is released promptly when you stop working:

  • While you are signed in on the computer that holds your seat, the software holds a short-lived licence lease, signed by our licence server and issued for that computer, and renews it automatically about once a minute. Each lease lasts a few minutes. The CAD add-ins hold and renew their own lease, so they keep working while you are signed in on that computer even when the desktop agent is not running. A lease is issued only to a user who has accepted the current version of this Agreement. The software and the add-ins refuse to carry out an operation without a valid, current lease issued for the computer they are running on and for the CAD product concerned.
  • Signing out releases the seat, and the software and the add-ins on that computer stop within a few minutes at most.
  • Closing the desktop agent releases the seat, so that it can be claimed on another computer. While you remain signed in, the seat is claimed again automatically the next time you carry out an operation on that computer, provided no other computer holds it at that moment.
  • If a lease is not renewed – for example because your computer has lost contact with our licence server or is asleep – it runs out within a few minutes, and operations are refused until a new lease is issued. A seat that is not renewed for about five minutes is released.
  • While a seat is held on one computer, a request to claim it on another is refused, and the refusal names the computer that holds it. You may then choose "Use here instead": the seat moves to the new computer at once, and the other computer is told that the licence is now in use elsewhere and stops within a few minutes. A borrowed seat cannot be moved in this way.

Offline borrowing. Where an administrator of your organisation has enabled it, you may borrow your seat for a period no longer than the maximum your administrator has set, so that you can work on one computer without contact with our licence server. A borrowed seat is reserved for that computer until you return it or the period ends, and during that time it cannot be claimed on, or moved to, any other computer. Signing out returns it; closing the desktop agent does not. Borrowing is available only for seats held through an organisation.

Because a seat can be released while you are working – if your network drops, if your computer sleeps, if you sign out, or if the seat is moved to another computer – an operation in progress may be interrupted and may not complete. Save your work regularly, and do not leave a long sequence running unsupervised on data you cannot afford to lose. To the fullest extent permitted by law we are not liable for work that is lost, left half-finished or left in an inconsistent state when a licence is released, suspended or lost, whatever the cause.

We keep a record of licence sessions and seat events: the user, an irreversible hash of a machine identifier, the computer name, when the session started, when it last renewed, when it was released and why, any borrowing period, and each time a seat was borrowed, returned or moved, with the computers involved. If you use the server AI service (section 7c), we also keep irreversible hashes of hardware identifiers of your computer, for the purpose and the period that section 7c and the Privacy Policy describe. The software also keeps its most recent lease on your computer, together with the latest time it has seen, so that it can detect a clock that has been set back. We use those records to enforce the seat limit, to support you, to detect abuse and to verify compliance with this Agreement (section 4). The Privacy Policy says how long we keep them.

4. What you may not do

You may not:

  • resell, sublicense, rent, lend, time-share or otherwise make the software available to anyone else, or share your seat, your account or your sign-in credentials, except under a written reseller agreement with us;
  • reverse engineer, decompile or disassemble the software, or attempt to extract its source code, its prompts or any model weights, except to the extent that right cannot lawfully be excluded and then only after you have asked us for the information you need;
  • remove, disable, obscure or work around any licensing, authentication, token-verification, approval, audit or security mechanism; forge, alter, extend, re-use or replay a licence token or an action token; tamper with your computer's clock, its machine identifier or its network in order to defeat the seat rules; or run the software against a licence server other than ours;
  • use, load, start or call any component of the software – including its add-ins, libraries, executables and services, its local interfaces (such as named pipes, local network ports, COM and other automation interfaces, and programming interfaces) and its internal functions – other than through the user interfaces and documented features we supply for that purpose, and in particular to carry out operations without a valid licence;
  • modify, patch, adapt, translate or repackage the software or any of its files, or create a derivative work of it;
  • remove, bypass or defeat any code protection, obfuscation, encryption, code signature or integrity check in the software;
  • use a debugger, instrumentation, code-injection or hooking tool, memory editor or similar tool to change how the software behaves, or to extract content the software protects, such as its prompts, keys, tokens or licence data;
  • create, obtain, distribute or use a key generator, patch, crack, licence-server emulator or any other tool or method intended to give access to the software without a valid licence;
  • use scripts, automation or any other method to imitate a licensed session or a response from our licence server, or to let more people or computers use the software than your seats allow;
  • use the software, or its output, to build or train a competing product;
  • use the software to do anything unlawful, to infringe anyone's rights, or in breach of the terms of an AI provider, a CAD vendor or any other third party whose service or system the software reaches on your instruction.

Nothing in this section restricts a right that the law gives you and that cannot be excluded by agreement – such as the right to observe, study and test how the software functions while you are using it as licensed, or to decompile it to the extent strictly necessary for interoperability under the conditions the law sets.

Use of the software without a valid licence, an attempt to circumvent licence control, and sharing a seat or credentials are each a material breach that we may act on immediately under section 17.

Remedies for unlicensed use. If the software is used without a valid licence – by more people or on more computers than your seats allow, with a CAD product or after a date your subscription does not cover, or by any of the means listed above – then, in addition to our other rights: (a) you will pay us, on our invoice, our list price current at the date of the invoice for a subscription covering each seat and each subscription period of that use, less anything you have already paid us for the same use; (b) we may suspend or terminate your access immediately under section 17; and (c) where the law allows, you will reimburse our reasonable costs of establishing and enforcing our rights, including reasonable legal costs. The payment under (a) is compensation for the use actually made, not a penalty. It does not limit any other right or remedy the law gives us for loss we can show, and it does not apply to a consumer where mandatory law says that it may not.

Verification. We may verify that the software is used in line with this Agreement using the licence records described in section 3. We may also ask you, by written notice and not more than once in any twelve months unless those records indicate unlicensed use, to confirm in writing within thirty days, signed by a person authorised to act for you, the people and computers using the software and that the use is covered by your licence. We will use what you provide only to verify compliance and to invoice under the previous paragraph, and we will keep it confidential.

Organisation responsibility. Where the software is licensed to an organisation, or used by a person acting for one, that organisation must make sure that everyone to whom it gives access – its employees, contractors and anyone else using its seats – complies with this Agreement, and it is responsible to us for their use of the software as for its own. It must remove a seat from a person who should no longer have one, and tell us without undue delay if it becomes aware of use of the software that is not covered by its licence.

5. ARTIFICIAL INTELLIGENCE – UNCERTAINTY AND UNEXPECTED OUTPUT

Please read this section carefully. It describes a limitation that is inherent to the technology and cannot be engineered away.

SphereHarness is built on large language models, supplied by third parties or chosen and run by you. These models are probabilistic, not deterministic. They predict likely responses rather than following fixed rules. They do not understand your design, your standards or your intent; they produce text and tool calls that are usually plausible and are sometimes wrong. That has consequences you must plan for:

  • The same instruction can produce different results on different runs, including a different sequence of CAD operations or different numeric values.
  • Output can be confidently wrong. The software may state that an operation succeeded, report a dimension, mass, stress or cost figure, or describe a model, and be mistaken.
  • It may misinterpret your instruction, act on the wrong geometry, or take an action you did not intend – including creating, changing, moving, overwriting or deleting features, bodies, configurations, drawings, macros, files or vault data. Such an action may not be reversible.
  • It may do less than you asked, stop part-way through a sequence, leave a model or a document in an inconsistent state, or report a step as done when it was not.
  • Content the software reads on your instruction – a CAD file, a drawing, a PDF, an image, a spreadsheet, a database row, a message or a web page – can contain text written to be read as an instruction. A model may follow it. This is known as prompt injection, and it means you should treat any file or web content of unknown origin as untrusted.
  • Simulation, cost, manufacturability and tolerance results are approximations produced by automated setup. Mesh density, boundary conditions, material data and load direction are chosen automatically unless you specify them, and each of those choices changes the answer.
  • Behaviour can change when a model provider updates or retires a model, when you or your organisation select a different model, when you supply your own provider key, or when you point the software at a model you host yourself. We do not control, and cannot test, every model you may choose.
  • The software is not an engineering, safety, structural, regulatory or certification tool. Nothing it produces is a certification, an approval, a sign-off, a compliance statement or a professional engineering opinion.

Accordingly: you remain the engineer of record. Every output and every action of this software is a draft for your review, never an approved result. You must independently verify all geometry, dimensions, tolerances, drawings, bills of material, simulation results, manufacturing data and released documents – by your own qualified people, using your own process – before relying on them, manufacturing from them, quoting from them or issuing them to anyone else. Keep backups and version control of your CAD data and use your PDM system's revision history, so that an unwanted change can be undone. Do not use the software as the sole basis for a decision affecting safety, structural integrity, regulatory compliance or significant cost.

The software is not certified for any safety-critical application and must not be used as the sole basis for one. That includes, without limitation, medical devices, aerospace airworthiness, nuclear, automotive and rail safety systems, pressure equipment, lifting equipment, machinery safety functions, and anything else where a failure can injure someone – unless a qualified person independently verifies the result by means that do not depend on this software.

6. Actions taken by the assistant are your actions

The software acts in your CAD session, under your account, with your privileges, at your direction. Every operation it performs is your operation and your responsibility. That includes, without limitation, an operation that:

  • you approved when the software asked you;
  • ran without a fresh prompt because you chose to allow that operation for the session, enabled unattended mode, or otherwise told the software not to ask again;
  • formed part of a macro, skill, variation set, design study or other saved sequence that you, or someone in your organisation, recorded, wrote, edited, published, imported, shared or ran – a macro executes exactly as written, deterministically, without AI review;
  • executed code, a script or a command, on your machine or elsewhere;
  • created, renamed, moved, overwrote or deleted a file, a body, a feature, a configuration, a drawing or a document;
  • checked out, checked in, revised, released or otherwise changed data in a PDM or PLM system, or in any other connected system.

You are responsible for deciding what to approve, for how widely you grant a standing approval, for supervising unattended work, and for the consequences of everything that runs. Grant a standing or unattended approval only over data you have backed up and can afford to lose.

To the fullest extent permitted by law, we are not liable for the behaviour of an AI model; for hallucinated, incomplete or incorrect output; for prompt injection through content the software was directed to read; for an operation carried out in your session, whether or not it was the operation you intended; or for the consequences of any of these, including lost, corrupted, overwritten or deleted CAD data, lost production or downtime, rework, scrap, warranty, recall or field-service cost, or any other downstream loss.

7. Your data and AI providers

To answer your instructions, the software sends the content of your requests, and the CAD context relevant to them, from your computer directly to the AI model you have chosen (section 8): a provider with which you or your organisation hold an account, or a model or agent you run yourself. Unless you choose the server AI service, which section 7c describes, that content does not pass through our servers, except the messages you choose to send through a messaging relay, which section 7a describes; we do not store your prompts, the AI's answers, your CAD data or the operations carried out on it. Providers are independent third parties under their own terms and privacy practices. Usage figures the software shows you, such as token counts and estimated cost, are worked out and kept on your computer (for the server AI service, section 7c also applies); an estimated cost is produced from published provider rates and is not an invoice.

Our servers receive what is needed to run your account, your licence (section 3) and software updates, what the server AI service needs if you choose it (section 7c), and the content of any support request or feedback you choose to send us, including files you attach to it (section 7b says who may read and answer a support request), and what you post or submit to the community forum or the marketplace (section 13a). What we collect, why, and how long we keep it is described in our Privacy Policy at https://sphereharness.io/privacy, which forms part of this Agreement and lists the sub-processors we use. Do not send export-controlled, classified or personal data to an AI provider, or attach it to a support request, unless you are permitted to disclose it to that recipient.

7a. Messaging relays: Microsoft Teams, Microsoft Copilot and WhatsApp

You may choose to reach the software on your computer from Microsoft Teams, through the SphereHarness Teams app, from a Microsoft Copilot agent, through the SphereHarness address you add to that agent, or from WhatsApp, through your own Twilio number set to deliver its incoming messages to an address we give you. Where you do, our servers relay those messages: each message or request is passed to the desktop agent on your computer or, for an organisation's WhatsApp number, to your organisation's own SphereHarness server, and for Teams and Copilot the answer or result is passed back. We do not store the content of relayed messages. The same holds for a Copilot request and its result. No message, request, answer, result, picture or file is written to our database, our disks or our logs. A message or request is held in memory only while it is being delivered and answered, and a picture or file in an answer is held in memory for no more than one hour so that Teams or Twilio can fetch it. We keep only what is needed to route your messages: the link between your Teams account and your SphereHarness account, your sign-in for a Copilot connection (which you can revoke), or the address we gave you for your Twilio number, and records of when such a link, sign-in or address was made, confirmed, revoked or removed.

Teams. We link a Teams account to a SphereHarness account by matching the sign-in name that Microsoft gives for the sender of a message with the verified e-mail address of exactly one SphereHarness account, and a message runs on a computer only after the link has been confirmed on that computer. The SphereHarness Teams app is added to Teams by your organisation's Teams administrator, or by you where your organisation allows it. Your use of Teams, and what Microsoft does with your messages, are governed by your or your organisation's agreement with Microsoft.

Copilot. You connect a Microsoft Copilot agent by adding the SphereHarness address to it and signing in once with your SphereHarness account; we check that sign-in and your licence on every request, and a request runs on a computer only after you have allowed that Copilot connection on that computer. Copilot may look up, measure and report, and make simple builds; it cannot delete, close, save under a new name, export, suppress or rename, and a step that changes your work still needs your approval on your computer. The AI that reads your question is Microsoft Copilot, and what Microsoft does with your conversation is governed by your or your organisation's agreement with Microsoft. You can revoke a Copilot connection at any time in the desktop agent.

WhatsApp. Your Twilio account, number and auth token remain yours. We never receive the auth token: your computer, or your organisation's server, checks each message's signature and sends the answer to Twilio directly. When neither is connected, our server answers the message with one fixed sentence saying that your computer, or your organisation's server, is not connected; Twilio sends that sentence from your number and may charge your account for it as for any message. Your use of Twilio and WhatsApp is governed by your agreements with them.

Telegram. Telegram messages do not pass through our servers: your own bot talks to your computer or to your organisation's server.

A relayed message is an instruction from you, carried out on your computer with the AI you chose, exactly as if you had typed it there; sections 6 and 8 apply to it. A Copilot request is an instruction from you through Microsoft Copilot, carried out on your computer by the software; section 6 applies to it. Anyone who can reach the SphereHarness Teams app, your Copilot agent or your Twilio number can send it a message: decide who may, and remember that an answer in a Teams channel or group chat can be read by the other members of that chat. We may suspend a relay that is misused or that puts our service, another customer or a third party at risk.

7b. Support requests and the AI support agent

A support request you send us may be read, and answered, by an AI agent operated by PLM CAD Utilities AS. A reply to your request may therefore come from the AI agent or from a person. Every reply written by the AI agent says so, and says how to reach a person. You can ask for a reply from a person at any time by writing "human" in your request or in a later message; from then on the AI agent does not answer that request.

Before the text of your request is given to the AI provider, we remove personal data from it: your name, e-mail addresses, phone numbers, licence keys and account identifiers. The AI provider receives that text and the public help pages, and nothing else: not your account details, not your attachments, not your licence or CAD data. The AI provider for this purpose is Anthropic, which acts as our sub-processor and is listed in the Privacy Policy. The AI agent only answers the request: it does not change your account or licence, and it does not close your request. A request about your account, your licence, a charge or a fault in the software is passed to a person.

Free text can contain more than we can recognise and remove. Do not write personal data about other people, or export-controlled or confidential data, in a support request. An answer from the AI agent is general guidance based on our published help; section 5 applies to it as to any AI output, and you should check it before you rely on it.

7c. The optional server AI service and its token allowance

It is optional. If it is offered to your account, the desktop agent lists "SphereHarness server" among the ways to choose the AI (section 8 lists the others). It is never used unless you choose it. If you do not choose it, nothing in this section applies to you, and none of your instructions, CAD context or answers pass through our servers because of it.

What passes through our servers. If you choose it, the content of your requests, the CAD context relevant to them, the results of the tools the AI calls and the AI's answers pass through our servers to the AI provider we use for this service, which acts as our sub-processor. The provider may change from time to time; contact support to find out which AI provider is currently used. The provider may process data outside the European Economic Area, and support tells you the current provider and the safeguards that apply. The operations the AI carries out in your CAD session are relayed through our server to the add-in on your computer. We do not store the content of those requests, answers or operations: they are held in memory only while a request is being answered. We do keep usage records: when a request was made, the model used, the numbers of input, cached and output tokens, the weighted token charge, your token balance and its history, and the hashed hardware identifiers described below. The provider's own terms and privacy practices apply to what it receives. Do not send export-controlled, classified or personal data through this service unless you are permitted to disclose it to that provider (section 7).

Tokens are a usage credit, not money. Tokens measure how much of the server AI service you may use and have used. They are not money, a deposit, electronic money or a stored balance of value; they cannot be exchanged for cash, paid out or transferred to another person, and they earn no interest. Tokens, whether given or bought and whether used or not, are not refunded, in money or otherwise, except where mandatory law gives you a right to a refund.

Weighted tokens. A request is not charged by plain token count. Input tokens, cached input tokens and output tokens use your allowance at different weights, which also depend on the model used. Your account page shows the current weights. We may change the weights, the models offered and the size of any allowance at any time; a change applies to requests made after it takes effect.

The free allowance. The size of the free allowance is shown on the pricing page at https://sphereharness.io/pricing while the server AI service is offered. We may give the free allowance of tokens when you start a trial and, for a paid subscription, once for each billing period. A free allowance given for a billing period does not carry over: free tokens not used by the end of the period expire and are replaced by the next period's allowance. The free allowance is also limited per computer: the free tokens that can be used on one computer, across all accounts that sign in on it, are capped (the cap can be set differently for an organisation), so using several accounts on one computer does not give more free tokens. Tokens that you buy belong to your account and are not limited by that per-computer cap. To apply the cap, the desktop agent sends irreversible hashes of hardware identifiers of your computer (the system UUID, the motherboard serial number and the serial number of the system disk) when you use the server AI service; the identifiers themselves never leave your computer, we store only the hashes, and we keep them for twelve months. Tampering with these identifiers, or with the software that sends them, in order to obtain more free tokens is a breach of section 4.

Buying tokens. You can buy more tokens from your account page. Prices are shown when you order; you pay by invoice, and the tokens are added to your account after we receive payment.

When tokens run out. A request that has started is completed even if it uses your last tokens. The next request is refused until you have tokens that can be used, and the software tells you why. A request that fails before it completes is not charged. You can choose another AI at any time (section 8). We may suspend or withdraw the server AI service, or a model in it, at any time, for example when our provider changes or ends its service; sections 14 and 15 apply to it as to the rest of the software.

8. Providers and models you bring yourself

The software works with an AI service or model that you choose. Apart from the optional server AI service in section 7c, we do not supply one, and this section describes the ones you bring yourself. That covers:

  • your own provider key (bring-your-own-key), or a key your organisation supplies;
  • a model you host or run yourself, on your own computer or on your own network;
  • a coding-agent or local-agent backend – for example a locally installed agent command-line tool, model runtime or development-environment agent that the software starts, or talks to, on your machine.

Where you do that, you, or your organisation, are that provider's customer – we are not. Your use of that service is governed by your agreement with that provider, and the following are solely your responsibility:

  • complying with that provider's terms of service, acceptable-use policy, model licence, and any age, territory, export-control or sanctions restriction it imposes;
  • everything you send to it and everything it sends back, including whether you are entitled to disclose that content to it;
  • its rate limits, quotas, fees, taxes and overage – those charges are billed to your account, and we neither pay nor refund them;
  • how that provider handles, stores, retains, logs, reviews or trains on the content you send it, which is a matter between you and it;
  • keeping the key, the model files and any local agent secure, and removing them when you no longer want them used.

We do not control, operate, monitor, audit or warrant any such service. We do not promise that it will be available, accurate, secure, private, lawful where you are, or compatible with the software, and we are not liable if it is not, if it changes, if it is withdrawn, if the provider suspends or terminates your account, or if you are charged more than you expected. Content is sent to it on your instruction: the software is the means, and you are the sender. A local agent or a locally run model executes on your computer, under your operating-system account, with your privileges – section 9 applies to it.

Coding agents run headless. Where you choose a coding agent as the backend, the software starts a coding agent that you have installed on your computer and signed in to yourself – for example Claude Code, Codex CLI, Gemini CLI or another agent that speaks the Agent Client Protocol – and runs it headless, that is, in the background without a window of its own, as the model behind the software's chat, with the software's CAD tools made available to it. The agent runs on your computer, under your operating-system account and under your own account with that agent's vendor. Where a small connector program is needed to talk to the agent, it is fetched on your computer from the public package registry through which its authors publish it, under its own licence. You are responsible for your own agreement with that vendor, and for making sure that it allows you to use the agent in this way: started and driven by another program, with the plan, subscription, sign-in or API key you use, and by the people who send it instructions, including through a messaging channel you connect. Some vendors allow a personal subscription to be used only by its holder, only in their own applications, or only interactively, and require an API key for use from other software; where that is so, you must use a sign-in method your vendor permits. We are not a party to your agreement with the vendor, we do not supply, resell or pay for the agent or its usage, and we do not receive your sign-in credentials for it.

This feature depends on the vendors. Running a coding agent in this way is possible only because its vendor currently supports headless and programmatic use, the Agent Client Protocol and the other interfaces involved, and the sign-in methods you use, and it is offered purely on that basis. A vendor may change its terms, its plans, its software, its interfaces or its support for this kind of use at any time. If it does, running that agent through the software may stop working, may work only in part or only with an API key, or may be limited or discontinued by us, for that agent or for all of them; if a vendor no longer supports or permits this use, we will discontinue it for that vendor. To the fullest extent permitted by law, that is not a defect in the software or a breach of this Agreement, it does not entitle you to a refund or a price reduction, and our commitment in section 2 not to reduce functionality during a paid term does not apply to it. The other ways of choosing a model described in this section are not affected.

Where data sent to a coding agent goes. What you type in the chat, the CAD context the software gives the agent and the results of the tools the agent calls go from the software to the agent on your computer, and from there to that agent's vendor, or to the model service you configured in it, under that vendor's terms and privacy practices. As section 7 says, that content does not pass through our servers; a message you send through a messaging relay (section 7a) passes through them only on its way to your computer, and is not stored.

Coding agents connected to the software's local interface. You may also connect a coding agent that you run yourself to the software's local interface on your computer, so that the agent can use the software's tools, including its control of the desktop (section 9). That interface works only while the computer is signed in to SphereHarness with a valid licence (section 3). What such an agent does through the interface is done on your instruction and is your action under section 6, and this section applies to that agent as it does to a coding agent you choose as the backend.

Whichever service or model you choose, section 5 applies: the model is still probabilistic, and its output is still yours to verify.

9. Script, macro and code execution; administrator-level operation

The software can execute code, scripts, macros and commands on your machine when you, or an administrator acting for your organisation, approve that execution – or when you have chosen a mode that gives that approval in advance. Approved code runs with your operating-system privileges and is not sandboxed; human approval is the security control. The same applies to a macro you or a colleague recorded or wrote, to a script an AI model produced, to a skill that names a macro, and to a local agent or model runtime the software starts on your behalf. You and your organisation are responsible for reviewing what you approve, for understanding how much a standing or unattended approval will cover, and for the effects of running it. Destructive operations require explicit consent before they run, unless you have chosen a mode that gives that consent in advance. Do not approve code from a source you do not trust. To the fullest extent permitted by law, we are not liable for the effects of code, scripts, macros or commands that you or your organisation chose to approve, or chose to allow in advance.

Administrator-level (elevated) operation. By default the software controls the desktop and starts programs with the rights of the Windows user who is signed in. Operation with administrator rights ("elevated operation") is off by default. Only a Windows administrator of the computer, or your organisation's IT policy, can allow it, either for a limited time of up to 24 hours or until it is withdrawn. The setting is stored for that computer and is not part of a settings export or import. An administrator can withdraw it at any time.

Accounts without administrator rights. On a Windows account without administrator rights, administrator-level operation is not available.

What elevated operation allows. While elevated operation is allowed, an action requested by you, by the AI acting on your instruction, or by another coding agent connected through the software's local interface (section 8) can act with administrator rights on that computer. It can operate the windows of programs that run as administrator, and it can start a program as administrator, but only after you confirm that on the approval card. You, and the administrator who allowed elevated operation, are responsible for deciding whether to allow it, for whom and for how long, and for the consequences of the actions performed with those rights, including installing or changing software and changing system settings. Section 6 applies to those actions as to any other.

Local record of elevated actions. The software records the actions it performs with administrator rights in an audit log on that computer. The log does not contain the text that was typed. It stays on your computer and is not sent to us.

To the fullest extent permitted by law, we are not liable for the effects of an action performed with administrator rights while an administrator allowed elevated operation, including a change to the software, data, settings or security of that computer or of a network it is connected to.

10. Connections to networks, databases and local listeners

Connection capabilities. The software can, at your direction and subject to the controls below, establish outbound network connections (including HTTP and HTTPS, raw TCP, UDP, WebSocket and named-pipe connections), connect to database systems, and open local network listeners on your machine, in order to send and receive data on your behalf.

Where connections are kept. Connections to your organisation's systems, and the credentials they use, are defined by an administrator of your organisation and stored on your organisation's own server or, for a single user, on your computer – not on our servers. The software makes each connection directly from your computer to the system concerned; the data exchanged does not pass through our servers.

Administrator control. Each category of connection is governed by an organisation-level setting. Except for outbound HTTP and HTTPS requests, these capabilities are disabled by default and take effect only after an administrator of your organisation enables them. Database writes require, in addition, that an administrator has registered the specific database connection and explicitly marked it as writable, and that your organisation's settings allow database writes.

Your consent. Where a capability is enabled, the software asks for your approval for each new connection target before connecting, and asks for explicit confirmation before each database write. Approvals are recorded for the session; approvals for internal or private network targets are never remembered beyond the session.

Your responsibility. You are responsible for the systems you authorise the software to reach, for the credentials you supply, for the correctness and the consequences of the statements the software is directed to execute against those systems (including data modification), and for making sure that such access complies with your own policies and with your agreements with third parties. To the fullest extent permitted by law we are not liable for loss, corruption or disclosure of data arising from a connection or a database operation that your administrator enabled and your user approved.

No warranty of destination. The software transmits and receives data as directed. It does not verify the identity, the trustworthiness or the security posture of the systems you direct it to connect to.

11. Credential handling

Connections to external systems run on the end-user's workstation. Organisation credentials – or short-lived tokens derived from them – are therefore released to, and used on, the workstation that makes the call. Each release is encrypted for that one call (an ECIES envelope, carried over TLS when the connection store is on a server), expires shortly afterwards, and is cleared from memory after use. Stored credentials are encrypted at rest on your organisation's server or on your computer, and are not sent to us. However, a static shared credential is, by design, accessible on the workstation that uses it. By registering such a credential, your organisation's administrator accepts that residual exposure. To the fullest extent permitted by law, we are not liable for credential compromise arising from a workstation or a server that your organisation authorised or operates.

A credential you supply ad hoc within a session is held in volatile memory for that session only and is not written to disk by the software. A key or credential you hold for an AI provider of your own is covered by section 8.

12. CAD systems and other third-party software

The software works with products licensed to you by their own vendors: SOLIDWORKS (Dassault Systemes), Inventor and AutoCAD (Autodesk), NX and Solid Edge (Siemens), their PDM and PLM systems, and other software – office applications, browsers, databases, operating-system tools – that you may ask the assistant to drive.

No affiliation. We are not affiliated with, endorsed by, sponsored by, certified by or authorised by Dassault Systemes, Autodesk, Siemens or any other vendor, and this Agreement grants you no rights in their products. Product names and trademarks are the property of their respective owners and are used only to identify the products the software works with.

Their licences are yours to hold and to observe. You must hold a valid, current licence for every product the software touches, and you must comply with that vendor's licence terms and with its programming-interface, API, automation and add-in terms. Those terms may restrict things we cannot restrict for you – for example limits on automated, unattended or scripted use; on running more than one session or instance; on network, borrowed or token-based licensing; on what a student, educational, academic, hobbyist, trial or viewer edition may be used for; on the use of cloud or connected services; and on moving data between products. Using the software does not extend, waive or substitute for any of that. Deciding whether a particular use is permitted under your vendor licences is your responsibility, not ours.

Compatibility. Vendors change their products and their programming interfaces. A vendor update, a new release, a service pack, a policy change or a licensing change may break a feature of the software, slow it down, or stop it working. We will make reasonable efforts to keep up, but we do not warrant compatibility with any particular version, and we are not liable for the consequences of a vendor's change, for a vendor's decision to restrict, audit, suspend or terminate your licence, or for any claim a vendor makes against you.

The same applies to PDM and PLM systems, to ERP, CRM and database systems, to office suites and browsers, and to any other system you ask the assistant to operate: you must be entitled to use it in that way, and to let the software use it on your behalf.

13. Organisation content: macros, skills, templates and knowledge

The software lets an organisation publish content to its users – global macros, skills, templates, prompts, design rules, indexed documents and other knowledge. That content belongs to the organisation that publishes it, not to us, and it is published by the users that organisation itself authorises, through the roles that organisation administers.

A macro runs exactly as written, deterministically, without AI review and with no model in the loop. Publishing one to an organisation makes it runnable by that organisation's users, on their data, with their privileges. The publishing organisation is responsible for what it distributes: for reviewing and testing it, for the operations it performs, for keeping it correct as CAD versions and data change, and for withdrawing it when it should no longer be used. Where you publish such content, you confirm that you have the right to publish it and that it does not infringe anyone's rights and contains nothing unlawful, nothing confidential to a third party and nothing export-controlled.

We store and deliver that content as a service to your organisation. We do not review it, we do not warrant it, and we are not a party to what your organisation chooses to run. A user who runs it is subject to sections 6 and 9 in the ordinary way.

13a. Community content: the forum, the content catalogue and the marketplace

We operate a public community forum, a content catalogue of knowledge articles and skills, and a marketplace in which users may publish knowledge articles and skills for other users. You need an account to post, to submit or to install; anyone may read the forum and the marketplace listings. The community rules at https://sphereharness.io/community-rules apply to everything you post or submit, and the contributor terms at https://sphereharness.io/marketplace-terms apply to everything you submit to the marketplace. Both form part of this Agreement.

What you post is stored and becomes public. Unlike a relayed message (section 7a), a forum post, a report and a marketplace submission are stored on our servers. Each topic, each reply and each version of a marketplace package is reviewed by us before it is published; once published, anyone may read it, with or without an account. We may refuse, hide, lock or remove any post, mute or ban an account from the community, and block or withdraw any marketplace package, at our discretion and with or without notice, including when it breaks the community rules or the contributor terms, when we receive a notice that it infringes someone's rights, or when it puts users, our service or a third party at risk. The Privacy Policy describes what we keep, for how long, and the choice you have about your posts when your account is deleted.

The licence you give us. You keep ownership of what you post or submit. You grant us a worldwide, non-exclusive, royalty-free licence to host, store, copy, scan, review, display, format, sign and distribute it through our website, the content catalogue and the software, for as long as it is published, and to keep copies afterwards as far as we need them for our records, to handle reports and legal notices, and to meet our legal obligations. A forum post you chose to keep when your account was deleted stays published under that licence, shown without your name.

The licence you give other users. When you submit a marketplace package you choose the licence under which everyone who installs it may use it: Creative Commons Attribution 4.0 International, Creative Commons CC0 1.0 Universal or the MIT License. Withdrawing your package stops new installations; it does not withdraw the licence from anyone who has already received a version.

What you confirm. When you post or submit anything, you confirm that you have the right to do so and to grant the licences in this section; that it does not infringe anyone's rights or break an agreement you are bound by; and that it contains no personal data of other people, no passwords, keys or other credentials, nothing confidential to a third party, nothing export-controlled or subject to sanctions, and nothing designed to make the software or an AI model act against the person using it.

Content you install. Content in the catalogue is published by us for everyone, by a reseller for its own customers only, or by another user through the marketplace, and the software shows which. Each published version is signed by our servers, and the software refuses a package whose signature does not match. The signature shows only that the package comes from our catalogue unchanged; it does not show that the content is correct, safe or fit for your purpose. Knowledge articles and skills are text that the AI reads: they can change what the AI proposes and does, and section 5 applies to them as to any other content the software reads. Installing content does not run it, and every operation remains subject to the approvals described in sections 6 and 9. We review marketplace content before we list it, but that review is not a warranty; content from a reseller is the reseller's responsibility. To the fullest extent permitted by law, we give no warranty for content published by a reseller or by another user, and we are not liable for it or for the consequences of using it. When a package you installed is withdrawn or blocked, the software tells you and offers to remove it; we do not delete or disable your copy remotely.

Reports and notices. You may report a post or a package that you believe breaks the community rules. If you believe that content infringes your rights, send a notice through https://sphereharness.io/legal/takedown; we may block the content while we consider it, and we will pass the notice to the person who published it, who may answer it.

14. No warranty

THE SOFTWARE IS PROVIDED "AS IS" AND "AS AVAILABLE", WITHOUT WARRANTY OF ANY KIND.

To the fullest extent permitted by law we disclaim all warranties, express, implied or statutory, including merchantability, fitness for a particular purpose, non-infringement, quiet enjoyment, and any warranty that the software or its output will be accurate, complete, current, reproducible, fit for your purpose, error-free, secure, uninterrupted or available. We do not warrant that the software is suitable for any particular design, material, process, standard, code or jurisdiction, and we give no warranty in respect of any third-party model, provider, CAD system or connected system. No advice or information, whether given by us, by our support, by the documentation or by the assistant itself, creates a warranty.

15. Limitation of liability

NOTHING IN THIS AGREEMENT EXCLUDES OR LIMITS LIABILITY THAT CANNOT BE EXCLUDED OR LIMITED UNDER MANDATORY LAW – including liability for death or personal injury caused by negligence, for fraud or fraudulent misrepresentation, and under any consumer protection law that applies to you. Subject to that:

TO THE FULLEST EXTENT PERMITTED BY LAW, WE ARE NOT LIABLE FOR INDIRECT, INCIDENTAL, SPECIAL, PUNITIVE OR CONSEQUENTIAL LOSS, nor for lost profits, lost revenue, lost production, downtime, lost or corrupted CAD data, scrap, rework, re-manufacture, warranty, recall or field-service cost, delay, lost opportunity, loss of goodwill, or the cost of correcting a defective design – in each case however caused, and whether or not we had been told that such loss was possible.

Our total aggregate liability arising out of or relating to the software and this Agreement, whether in contract, tort (including negligence), statute or otherwise, is limited to the fees you paid us for the software in the twelve months before the event giving rise to the claim. Where you paid us nothing for it – a trial, a free tier, or a licence supplied to you by someone else – our liability is limited to re-supplying the software to you.

Consumers retain their statutory rights, which this Agreement does not affect.

16. Your indemnity

You will defend and indemnify us against any claim, demand, proceeding, fine, loss, damage, cost or reasonable legal expense brought against us by a third party and arising out of:

  • your use of the software, or an operation carried out in your session or under your account, including anything the assistant did at your direction;
  • your breach of this Agreement or of any law that applies to you;
  • your breach of the terms of an AI provider, a CAD or other software vendor, or any other third party whose service or system the software reached on your instruction;
  • content you submitted, published, distributed or asked the software to process – including organisation content under section 13, community content under section 13a, and content that is unlawful, infringing, confidential to another person, export-controlled or subject to sanctions;
  • a design, drawing, document, simulation result or manufactured part produced with the help of the software, including a claim that it is defective, unsafe, non-compliant or infringing.

We will tell you promptly about any such claim, will not settle it without your agreement (which you will not unreasonably withhold), and will give you reasonable cooperation at your expense. This section does not apply to a consumer where mandatory law says that it may not.

17. Term, termination and survival

This Agreement runs while your licence is active. Either party may terminate it if the other materially breaches and does not remedy the breach within thirty days of written notice. We may suspend or terminate your access immediately, without that notice period, if you circumvent or attempt to circumvent licence control, share a seat or your credentials, use the software unlawfully, or do anything that puts our service, another customer or a third party at risk; where the breach can be remedied we will normally warn you first. On termination you must stop using the software and remove it from every computer. Sections 3 (as to records), 4 (as to remedies and verification), 5, 6, 8, 9, 10, 11, 12, 13, 13a (as to the licences granted and to content already published), 14, 15, 16, 19 and this section survive termination.

18. Changes to this Agreement

We may change this Agreement when the software changes or when the law requires it. The current version, with the date on which it was last updated, is published at https://sphereharness.io/eula and is shown by the installer. When we make a material change the software will ask you to accept the new version, and will not carry out operations for you until you do; accepting it, or continuing to use the software after that, means you accept it. If you do not accept it you must stop using the software; and where you have paid for a term that has not expired and you reject a material change that disadvantages you, you may end your subscription for that term and we will refund the unused part.

19. Governing law

This Agreement is governed by the laws of Norway, and the courts of Norway have exclusive jurisdiction over any dispute arising out of or relating to it, whether in contract, tort (including negligence), statute or otherwise – without prejudice to any mandatory consumer protections available to you where you live.

20. Contact

PLM CAD Utilities AS – https://sphereharness.io – support@plmcadutilities.com

This Agreement: https://sphereharness.io/eula – Privacy Policy: https://sphereharness.io/privacy

SphereHarness SphereHarness

An AI assistant for Inventor, NX, Solid Edge and AutoCAD.

Product

  • Features
  • Pricing
  • Privacy and data flow
  • Choosing an AI for CAD
  • Blog
  • Help
  • Downloads
  • Community forum
  • Marketplace

Get started

  • Start free trial
  • Getting started
  • Install the add-in
  • The desktop agent

By CAD system

  • AI for Autodesk Inventor
  • AI for Siemens NX
  • AI for Solid Edge
  • AI for Autodesk AutoCAD

Company

  • Contact sales
  • Become a reseller
  • support@sphereharness.io

Portals

  • Organization portal
  • Reseller portal
  • Admin portal

© 2026 PLM CAD UTILITIES AS

Licence · Privacy · What goes where · Community rules