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

Privacy Policy

Last updated 21 November 2026 · PLM CAD Utilities AS

This policy explains what SphereHarness collects, why, where it goes, and how long we keep it. It covers the CAD add-ins for SOLIDWORKS, Autodesk Inventor, Siemens NX, Solid Edge and AutoCAD, the desktop agent that runs on your computer, this website, and the SphereHarness server that handles accounts, licences, downloads and support. It forms part of the End User Licence Agreement you accept when installing the software.

Messaging apps (Microsoft Teams, WhatsApp and Telegram) are covered in section 11: Teams and WhatsApp messages you send that way are relayed through our server and never stored. The community forum and the marketplace are different: what you post or submit there is stored (section 12). Our website forms are checked by Cloudflare Turnstile (section 13). The SphereHarness phone app is covered in section 15. A plain-language table of every data flow is on What goes where.

The short version. Unless you choose the optional SphereHarness server AI (section 3), SphereHarness does not run AI on its servers. Your requests, the CAD context needed to act on them, and the answers go from your computer to the AI provider you choose (your own key, or a coding agent on your computer; with the server AI, our server passes them to our AI provider and does not store them), and CAD operations run between the desktop agent and the add-in on the same computer. We receive your account details, a licence check that includes a machine identifier and your computer’s name, update checks, and the support requests you choose to send us. This applies to the desktop agent and add-ins version 1.3.0 and later; section 5 describes earlier versions. If you choose to use SphereHarness from Microsoft Teams, from a Microsoft Copilot agent or from your own WhatsApp number, those messages and requests are relayed through our server to your computer and are not stored (section 11). If you post in the community forum or submit to the marketplace, we store what you post and, once it is approved, anyone can read it (section 12). We do not sell your data.

1. Who we are

PLM CAD Utilities AS is the data controller for the information described here. Contact us at support@plmcadutilities.com for any privacy question, or to exercise the rights in section 8.

2. What we collect

CategoryExamplesWhy
Account Name, email, organisation, hashed password, licence and seat assignment, reseller relationship, and a device identifier sent when you sign in To create your account, control access, and apply your licence
Licence sessions Your user id, an irreversible hash of a machine identifier, the computer name, when a session started, when it last reported in, when it was released, and the reason it was released (sign-out, agent closed, sleep, Windows session end, or no contact for about five minutes) To enforce the one-user-one-computer seat rule, to free a seat promptly, to support you, and to detect seat sharing and other abuse
Support requests and feedback What you write in a support request, a reply or a feedback message, and the files you attach, such as a diagnostics archive with logs from the software and your CAD system To investigate and answer what you reported
Notifications Replies to your support requests and announcements we or your reseller send you, and whether you have read them To tell you about them in the desktop agent
Records from before 24 September 2026 Until 24 September 2026 we also offered an AI that ran on our servers. For requests that ran on it we hold the instruction, the answer and the instructions given to the model, and usage records (timestamp, model, provider, token counts, estimated cost). A few users also stored an AI provider key with us. See section 6. Collected to provide that service. Nothing is added to them any more.
Server AI usage (only if you choose the SphereHarness server option) When each request was made, the model, the numbers of input, cached and output tokens, the weighted token charge, your token balance and its history (grants, charges, purchases), and your account. Not the content: your instructions, the CAD context, tool results and the AI’s answers pass through our server to our AI provider and are not stored. See section 3. To run the service, to meter the token allowance, to support you and to detect abuse
Hardware identifier hashes (only if you choose the server option) Irreversible hashes of the system UUID, the motherboard serial number and the system-disk serial number of your computer, each hashed on your computer so that we never receive the identifiers themselves; when the computer was first and last seen; and which accounts used free tokens on it To give one free allowance per computer instead of one per account, and to flag one account appearing on many new computers
Token orders If you buy tokens: the pack, the amount, who ordered, the status of the order and when it was paid To invoice and credit your purchase, and for our accounting records
Messaging relay links If you use the SphereHarness Teams app: the link between your Teams account (your Microsoft 365 tenant id and your Microsoft Entra object id) and your SphereHarness account, which of your computers you prefer, and on which computers you confirmed it. If you relay your own WhatsApp number: the relay address we gave you and the account it belongs to. Never the messages themselves. To deliver your messages to your own computer (section 11)
Community posts and reports If you use the community forum: the public name you chose, your topics and replies, the earlier text of a post you edited until the edit is reviewed, the reports you make, and the moderators’ decisions about them. Not your IP address. To publish what you post once it is approved, and to moderate the forum (section 12)
Marketplace submissions If you submit to the marketplace: the package files, what you write about them, the licence you chose, the result of our automatic scan, the review decision, and which version of the contributor terms you accepted To review, publish, sign and distribute your package (section 12)
Catalogue installs and reports Which catalogue packages and versions you installed and when, a record of each download (identifiers only), and the reports you make about a package. A takedown notice holds the details its sender gives us. To tell you about updates and withdrawals, to count installs, to limit abuse, and to handle reports and legal notices
Sign-in and form protection For each wrong password and each sign-up, forgot-password or contact request: an irreversible hash of the e-mail address (never the address itself), your IP address and the time; audit entries of failed sign-ins and locks with the IP address. A fingerprint of each accepted Cloudflare Turnstile check, so that it cannot be used twice. To stop password guessing, spam and automated abuse (section 13)
Optional shared content Macros, skills and automations your organisation chooses to share through our server, and documents you choose to index on our server. Sharing is off unless your organisation switches it on; documents are indexed on your own computer by default. Only to provide them to your organisation

We do not ask for special-category personal data, and you should not submit any. Please also do not submit export-controlled or classified material, or third-party data you are not permitted to disclose to a processor.

3. AI model providers

Carrying out an instruction requires sending it, and the relevant CAD context, to a large language model. Unless you choose the optional SphereHarness server option described below, SphereHarness does not run that model and does not relay the request. The desktop agent on your computer sends it directly to the AI you chose:

  • Your own provider key. You open an account with a provider (for example OpenAI, Anthropic, Google, xAI or DeepSeek, or any compatible service, including one you host) and enter its key in the desktop agent. The key is stored encrypted for your Windows account on your computer and is not sent to us.
  • A coding agent on your computer. You point the software at an agent you installed and signed in to yourself, such as Claude Code, Codex or Gemini CLI. It runs on your computer and talks to its own provider under your own agreement with that provider.
  • The SphereHarness server (optional). Where it is offered to your account, you can choose our server AI instead. Your requests then pass through our server; see the SphereHarness server AI below.

For the first two choices, that service is your relationship, not ours. We are not that provider’s customer, we do not control or monitor it, and what it does with the content you send — how long it keeps it, whether it logs or reviews it, whether it trains on it — is settled between you and that provider, under its terms. The content goes to it because you instructed the software to send it. For those two choices, because we do not handle the request, that provider is not our sub-processor, and we receive no record of the request, its size or its cost.

We do not use your CAD geometry, drawings or chat content to train models.

The SphereHarness server AI (optional)

If it is offered to your account and you choose “SphereHarness server” in the desktop agent, your instructions, the CAD context needed to act on them, the results of the tools the AI calls and the AI’s answers pass through our server to the AI provider we use for this service. The operations the AI carries out in your CAD session are relayed through our server to the add-in on your computer. Nothing is sent this way unless you choose it.

  • Not stored. We do not store that content. It is held in memory only while a request is being answered, and it is not added to any chat history, knowledge collection or training set on our server.
  • Stored. Usage records (time, model, token counts, the weighted charge), your token balance and its history, any token orders, and the irreversible hardware hashes used to limit the free allowance to one per computer (section 2). Section 6 says how long.
  • The provider. When you use the provided (free or purchased) server-AI quota, your requests are passed on to the AI provider we use for that service, which receives the content 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. Weigh that before you choose this option for confidential designs: the other choices keep the content on your computer.
  • Tokens. The allowance is a usage credit, not money; the agreement (section 7c) sets out how it is counted, given, limited per computer, bought and not refunded.

4. Where data is stored

Our server runs in Europe. Account data, licence sessions, support requests, notifications, messaging relay links, the records from before 24 September 2026 described in section 6, community posts and marketplace submissions, and any content your organisation chose to share live in our PostgreSQL database on that infrastructure. Relayed Teams and WhatsApp messages are not stored there or anywhere else on our servers (section 11). Support attachments and the files of content-catalogue and marketplace packages are stored in Cloudflare R2 under EU jurisdiction. Optional encrypted backups go to the storage account you nominate. The AI provider you choose may process your requests outside the EEA, under that provider’s terms with you.

5. What stays on your machine

Your CAD files stay where they are. The add-in reads and modifies them in place through the CAD system’s own interfaces; it does not upload your models to us. With the desktop agent and the add-ins version 1.3.0 or later, the following also stay on your computer, or go only to the services you chose:

  • your instructions, the conversation, attachments and the answers, which go to your AI provider (section 3);
  • CAD operations — the operation, its arguments and its result — which pass between the desktop agent and the add-in over a local connection on the same computer;
  • chat history, kept in your Windows user profile;
  • usage and token counts, kept in a local file; the software does not report them to us;
  • the audit log of actions carried out with administrator rights, where an administrator has allowed administrator-level operation on the computer; it does not contain the text that was typed, and it is not sent to us;
  • your AI provider key and your SphereHarness sign-in (the session tokens that keep you signed in), both stored encrypted for your Windows account — the settings files hold neither;
  • macros, skills, variation templates and automations, kept in folders on your computer unless your organisation switches on sharing;
  • documents you index for search, indexed by a service on your computer unless you choose your organisation’s index service or ours.

Settings are kept in your Windows user profile. Where an integration needs credentials for a system of yours, such as a PDM vault, those are used on your machine.

Earlier versions. The desktop agent and add-ins before version 1.3.0 send each CAD operation (the operation, its arguments and its result) through our server on its way to the add-in, and while connected the add-in reports to our server the name and path of the open document, the window title, and the computer and user name. Update the desktop agent and every add-in to version 1.3.0 to stop this.

Connections and databases

When your organisation sets up connections, the assistant can reach systems you direct it to — including databases, web APIs, e-mail and other network services. Connections are configured and stored on your organisation’s side: in a connections store on your organisation’s own server, or on your own computer. The desktop agent connects directly from your workstation to the destination system. The connection definitions, the credentials, your queries and the data returned do not reach our servers, and we do not store them. The audit trail of connection use and changes is kept in your organisation’s own store, not by us.

Earlier connections. Connections that your organisation set up on our website before this change remain stored with us, encrypted, until an organisation administrator downloads the export (which contains no credentials) and deletes the stored credentials, or asks us to delete them. We no longer run or relay any connection.

6. How long we keep it

  • Account data — while your account exists, then removed or anonymised.
  • Licence sessions — kept for twelve months so that we can investigate a seat dispute or suspected sharing, then deleted. The machine identifier is only ever stored as an irreversible hash; we cannot recover the original from it.
  • Server AI usage records, token balance and history, and token orders — while your account exists, then removed or anonymised; records that the law requires us to keep as accounting records are kept for the period it requires.
  • Hardware identifier hashes for the free allowance — kept for twelve months after the computer was last seen, then deleted. Only irreversible hashes are stored; we cannot recover the identifiers from them.
  • The content of server AI requests and answers — not stored. It is held in our server’s memory only while a request is being answered.
  • Support requests, feedback and attachments — kept while the issue is open and for a reasonable period afterwards.
  • Notifications — while your account exists.
  • Shared content and indexed knowledge on our server — until your organisation deletes it or closes the account.
  • Messaging relay links and Microsoft Copilot sign-ins — until you disconnect the channel, revoke the connection or delete your account. The audit entries recording that a link was made or removed are kept for twelve months and contain identifiers only.
  • Community posts — an approved post stays published until you or a moderator remove it, or until your account is deleted and you chose to delete your posts with it (section 12). A rejected post is deleted 30 days after it was rejected; a removed post 90 days after it was removed. Reports are kept for one year and moderation records (identifiers, actions and reasons, never the text) for two years.
  • Marketplace submissions — a listed package for as long as it is listed. The files of a rejected version are deleted 30 days after the decision, and those of a withdrawn or blocked package within 90 days, unless a report or a legal notice about it is open. Takedown notices and their records are kept for two years.
  • Catalogue installs — while your account exists, unless you clear them; download records for twelve months.
  • Sign-in and form protection — the counts of wrong passwords and form requests are deleted after two days; audit entries of failed sign-ins and locks are kept for twelve months; a Turnstile check’s fingerprint is forgotten after six minutes.
  • Relayed Teams and WhatsApp messages, and Microsoft Copilot requests and results — not stored. A message is held in our server’s memory only while it is being delivered and answered (at most 30 minutes); a picture or file in an answer is held in memory for at most one hour.
  • Chat history, the usage counts the app shows, your AI key and your stored sign-in on your computer — under your control; we cannot see or delete them. Signing out removes the stored sign-in.

Records stored before 24 September 2026

Requests that ran on the AI we hosted until 24 September 2026 left records on our server: the instruction, the answer, the instructions given to the model, and usage records (timestamp, model, provider, token counts and estimated cost). A few users also stored an AI provider key with us; those keys are encrypted and are no longer used for anything. Nothing is added to these records any more. We delete yours when you ask (section 8) or when you delete your account. If we set a fixed period for deleting the rest, we will state it here and announce it (section 10).

7. Who else sees it

The AI provider you chose receives your requests directly from your computer, under your own agreement with it (section 3). If you choose the SphereHarness server AI, the AI provider we use for that service (below) receives them through our server instead. Our hosting and email providers, as processors. If you use the SphereHarness Teams app, Microsoft carries those messages between Teams and our server (section 11); if you connect a Microsoft Copilot agent, Microsoft carries its requests between Copilot and our server (section 11). Cloudflare checks our website forms with Turnstile (section 13). Everyone, for community posts and marketplace packages once they are approved, and your reseller’s customers, for content your reseller publishes to them (section 12). Your organisation’s administrators, who can see seat assignment for their organisation and the usage records from before 24 September 2026 and, for the server AI, the token balances and allowances of their members. Your reseller, if your licence was sold through one, limited to what they need to administer it. We do not sell personal data or share it for advertising.

If your reseller has connected its own support system, your support requests — the subject and description, your name, e-mail address and organisation, the product and add-in version, and links to the files you attach — are forwarded to that system. The assistant names the recipient and what is sent and asks before it sends; if you say no, the request stays in your reseller’s SphereHarness queue only. The reseller’s privacy notice applies to what it receives, and its API key never leaves our server.

Not your CAD vendor. We are not affiliated with, endorsed by, or acting for Dassault Systemes, Autodesk, Siemens or any other CAD, PDM or PLM vendor, and we do not pass your data to them. Where the assistant operates one of their products it does so on your own machine, under your own licence with that vendor. Anything that product itself sends to its vendor — telemetry, cloud services, licence checks — is governed by that vendor’s own terms and privacy policy, not by this one.

Sub-processors. The services that process personal data for us are:

  • our hosting provider, which runs our server and database in Europe;
  • our e-mail provider, which delivers the e-mails we send you;
  • Cloudflare: R2 storage in the EU for support attachments and content packages, and Turnstile for the checks on our website forms (section 13);
  • Microsoft, only when you use the SphereHarness Teams app or connect a Microsoft Copilot agent (section 11).
  • The AI provider we use for the server AI service, only for requests you send with that option (section 3). The provider may change from time to time; ask support which provider is current. It may process data outside the European Economic Area; support tells you the current provider and the safeguards.
  • Anthropic (the AI provider), only for the text of a support request that our AI support agent reads in order to answer it (section 7a). Personal data is removed from that text first.

7a. 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, and a reply may come from the AI agent or from a person. Before the text of the request is given to the AI provider, Anthropic, we remove your name, e-mail addresses, phone numbers, licence keys and account identifiers from it. Attachments, account details, licence records and CAD data are not given to the AI provider. The AI provider receives the redacted text and our public help pages, and returns a classification and a draft answer; only an answer to a how-to question is sent automatically, and it says that it was written by the AI agent. We keep a record of each automatic answer so that a person can review it. Write “human” in a request to have it answered by a person only. Free text can contain more than we can recognise and remove, so please do not write personal data about other people in a support request. The terms are in our licence agreement (section 7b).

8. Your rights

Subject to applicable law you may request access to your data, correction, deletion, restriction, portability, or object to a particular use. Write to support@plmcadutilities.com and we will respond within the statutory period. If you are in the EEA and unsatisfied, you may complain to your national data protection authority; in Norway that is Datatilsynet.

You can delete your account yourself: sign in to your account portal and choose Delete My Account (/org/delete-account). You choose what happens to your forum posts (section 12), your marketplace packages are withdrawn, and records we must keep by law, such as orders and invoices, are kept without your name or e-mail address. If your account administers an organisation, a reseller or this website, the same page sends us a deletion request instead, because what you look after needs another administrator first.

9. Security

Traffic is encrypted in transit. Passwords are stored hashed. Provider keys are held encrypted at rest. Access to production systems is restricted to the people who operate them. No system is perfectly secure, so please report anything suspicious to us promptly.

10. Changes

We will update this page when our practices change and revise the date at the top. Material changes will be announced through the service.

11. Messaging channels: Microsoft Teams, WhatsApp and Telegram

You can send an instruction to SphereHarness from a messaging app instead of typing it into the chat on your computer. The instruction always runs on your own computer, with the AI you chose there (section 3), exactly as if you had typed it. This section adds to the rest of this policy; it does not replace it. In short:

  • Microsoft Teams: your messages to the SphereHarness Teams app are relayed through SphereHarness to your own PC, and the answers back; they are never stored — no message, answer, picture or file is written to our database, our disk or our logs. We keep only the link between your Teams account and your SphereHarness account.
  • Microsoft Copilot: when you connect a Copilot agent to SphereHarness, the requests Copilot sends for you are relayed through SphereHarness to your own PC, and the results back; they are never stored — no request, result, picture or file is written to our database, our disk or our logs. We keep only your sign-in for that connection, which you can revoke.
  • WhatsApp: you use your own Twilio number. Each message is passed through SphereHarness, unchanged, to your PC (or your organisation’s server) and is never stored. Your Twilio auth token never leaves your PC or your organisation’s server, and we keep no phone number.
  • Telegram: your own bot talks to your PC or to your organisation’s server; nothing passes through SphereHarness.

The relays need the desktop agent version 1.3.5 or later, and run only for the channels you switch on.

Microsoft Teams: the SphereHarness Teams app

Your organisation’s Teams administrator adds the SphereHarness Teams app to Teams, or you add it yourself where your organisation allows it. When you message the app, Microsoft (Teams and the Bot Framework) delivers the message to our server, signed by Microsoft. Our server checks that signature, looks up which SphereHarness account your Teams account is linked to, and passes the message to the desktop agent on your computer over the connection that agent opened with your own SphereHarness sign-in. It never goes to anyone else’s computer. The progress lines and the answer travel back the same way and are posted to the Teams conversation by our server, as the SphereHarness app.

What passes through, and for how long.

  • The message as Microsoft delivers it: its text, your display name, your Microsoft identifiers (tenant id and Entra object id) and the conversation it came from. Held in our server’s memory only while it is delivered to your computer and answered — at most 30 minutes — and then forgotten. A restart of our server forgets it at once.
  • The answer and its progress lines: passed from your computer to Microsoft as they arrive; not kept.
  • Pictures and files in an answer: a small picture (up to 80 KB) is sent inside the Teams message. A larger picture or another file is held in our server’s memory for at most one hour behind an unguessable link that is posted only into your conversation, so that Teams can show it; it is never written to disk.

We do not store any of it. No message, answer, picture or file is written to our database, our disk or our logs. Our logs record only identifiers, sizes and outcomes of a relayed message, never its text, your name or your e-mail address.

What we keep.

  • The link between your Teams account and your SphereHarness account: your Microsoft 365 tenant id and Entra object id, your SphereHarness user, your organisation if it claimed your tenant, how and when the link was made, on which of your computers you confirmed it, and your preferred computer. No address, name or message content.
  • Audit entries recording that a link was made, confirmed or removed: identifiers and a computer name only.

How the link is made. When an unlinked Teams account messages the app, our server asks Microsoft for the sign-in name (user principal name) of the account that sent that message, and compares it with the verified e-mail addresses of SphereHarness accounts. Only an exact match with exactly one active account counts; guest accounts and sign-in names on onmicrosoft.com are never matched. The sign-in name is used for that comparison and to show you the confirmation on your computer (“Teams account … wants to use this PC”); it is not stored. Nothing runs until you click Allow on that computer.

  • Microsoft (Teams, the Bot Framework, Entra ID) handles the messages as for any Teams app, under your organisation’s agreement with Microsoft, and keeps the Teams conversation in your organisation’s tenant.
  • Our server, hosted in Europe, relays the messages as described. In carrying them we act for you, or for your organisation; Microsoft and our hosting provider are the services involved on this path.
  • The desktop agent handles a Teams message exactly as if you had typed it into its chat: the message and the CAD context needed to act on it go to the AI provider you chose (section 3), and the same approvals are asked on your computer.

In a 1:1 chat with the app every message you send to it is read. In a team channel or a group chat, only messages that @mention the app are read. What you write in a channel or group chat is visible to its other members, and so is the answer.

Microsoft Copilot: one SphereHarness connection for your Copilot agent

You can add the SphereHarness address (https://sphereharness.io/mcp) to a Microsoft Copilot agent, for example in Copilot Studio, and sign in once with your SphereHarness account. When the Copilot agent decides to use SphereHarness, Microsoft Copilot sends the request to our server with an access token that our server issued to that connection. Our server checks the token, checks that your SphereHarness licence or trial is active, and passes the request to the desktop agent on your own computer over the connection that agent opened with your sign-in. The result travels back the same way and is returned to Copilot. A request never goes to anyone else’s computer. The AI that reads your question is Microsoft Copilot, under your or your organisation’s agreement with Microsoft; SphereHarness runs no AI for this.

What passes through, and for how long. The request (the name of the tool and its arguments) and the result text, held in our server’s memory only while the request is carried out and answered, and then forgotten. We do not store any of it. No request, result, picture or file is written to our database, our disk or our logs. Our logs record only identifiers, the tool name, the outcome and the time it took, never the arguments or the result.

What we keep.

  • Your sign-in for the connection: which Copilot agent (its registered name and return address) you allowed, your SphereHarness user, when it was allowed and last used, and a hashed renewal token. You can revoke it at any time in the desktop agent (Connected apps) and the connection stops at once.
  • Audit entries recording that a sign-in was allowed, renewed or revoked, and that a request ran: identifiers, the tool name, the outcome and a computer name only.

What Copilot may do. Copilot can look up and measure things, report, and make simple builds. Deleting, closing, saving under a new name, exporting, suppressing and renaming are refused when they come from Copilot, and a step that changes your work still needs your click on your computer. The first time a Copilot connection reaches a computer, that computer asks once: “Microsoft Copilot … wants to use this PC”. Nothing runs until you click Allow.

  • Microsoft (Copilot, Copilot Studio, Entra ID) handles your conversation with Copilot and the requests it sends, under your organisation’s agreement with Microsoft.
  • Our server, hosted in Europe, relays the requests as described. In carrying them we act for you, or for your organisation; Microsoft and our hosting provider are the services involved on this path.
  • The desktop agent carries out the request on your computer with the CAD system there, and asks for approval there as it always does.

WhatsApp with your own Twilio number

You keep your own Twilio account and WhatsApp number. The desktop agent gives you one permanent SphereHarness web address for that number, which you (or the agent) enter in Twilio as the address for incoming messages. When Twilio calls it, our server passes the request — unchanged, with Twilio’s signature — to the desktop agent on your computer, or, for a company number, to your organisation’s own SphereHarness server over a connection that server opened to ours. Your computer or your organisation’s server checks the signature with your own Twilio auth token, runs the instruction, and sends the answer to Twilio directly.

  • Not stored. The request (which includes the message text and the sender’s phone number) is held in our server’s memory only for the seconds it takes to hand it over. It is not written to our database, our disk or our logs; our logs record only the first characters of the relay address, the size and the outcome.
  • No token, no phone number. We never receive your Twilio auth token and we keep no phone number. What we keep is the relay address and the SphereHarness account (and organisation) it belongs to, when it was made, replaced or removed, and audit entries with identifiers only.
  • Pictures in an answer. To send a picture, your computer or your organisation’s server places it in our server’s memory for at most one hour behind an unguessable link, from which Twilio fetches it; it is never written to disk.
  • When your computer is not connected. Our server answers Twilio with one fixed sentence, which Twilio sends from your number: “Your SphereHarness PC NAME is not connected right now. Start the SphereHarness agent there and send your message again.” (NAME is your computer’s name), or, for a company number whose organisation server is not connected, “Your organisation’s SphereHarness server is not connected right now. Please try again later.” These sentences are the only thing SphereHarness ever sends on your WhatsApp number. Twilio may charge you for them as for any message.
  • Twilio (and Meta, for WhatsApp) handle your messages under your own agreements with them.

If you pair WhatsApp on your own phone with the desktop agent by QR code instead, its messages pass between WhatsApp and your computer and do not reach our servers.

Telegram

Your own Telegram bot is fetched by the desktop agent on your computer, or, for a company bot, by your organisation’s own SphereHarness server. Its messages pass between Telegram and that computer or server, under Telegram’s terms, and do not reach our servers.

Records from the earlier company channels

Until 24 September 2026 we also offered company channels set up in the SphereHarness portal. From that time we may still hold, until they are deleted, the records they created: for each person who linked such a channel, the organisation, the channel, their identifier on it (for Teams, the Microsoft Entra user object id; for Telegram, the numeric user id; for WhatsApp, the phone number), the SphereHarness user it was linked to and when; organisations’ channel settings; and entries in the audit log. The text of those channel messages was not written to our database.

Unlinking and deleting your channel data

  • Teams. Disconnect Teams in the desktop agent to delete the link between your Teams account and your SphereHarness account. Your organisation’s Teams administrator can remove the app from Teams.
  • WhatsApp. Disconnect WhatsApp in the desktop agent; the relay address stops working at once. Remove the address from your Twilio number too.
  • Telegram, and WhatsApp by QR code. Everything is on your computer or your organisation’s server and in your own Telegram or WhatsApp account; remove the channel in the desktop agent.
  • Anything else. Write to support@plmcadutilities.com from the address on your SphereHarness account and name the channel. If you ask us to delete your SphereHarness account, we delete its channel links with it.

Your other rights are in section 8.

12. Community content: the forum, the content catalogue and the marketplace

Forum posts and marketplace submissions are stored on our server: unlike messages relayed from Teams or WhatsApp, what you post or submit is written to our database and, once a moderator approves it, anyone can read it. Nothing you post is published before a SphereHarness website administrator has approved it; until then only you and the moderators can see it.

The forum

  • What we keep: the public name you chose (your e-mail address is never shown), your topics and replies, the earlier text of a post you edited until the edit is reviewed, the reports you make, and our moderation decisions with their reasons. We do not store your IP address with a post.
  • Who sees it: an approved post can be read by anyone on the internet, with or without an account, and can be found by search engines. A pending, rejected or hidden post is seen only by you and the moderators.
  • Not in our logs: the text and titles of posts are not written to our server logs; our moderation records hold identifiers, actions and reasons only.

When your account is deleted

When you ask us to delete your account, you choose whether your approved forum posts are kept, shown as written by “deleted user”, or deleted with your account; if you do not choose, they are kept. Kept posts no longer name you, and an answered question stays useful to others. You can also delete any of your posts yourself at any time, and download a copy of everything you posted from My posts in the forum.

The marketplace

  • What we keep: the package files you submit, its name, summary and change lists, the licence you chose, the result of our automatic scan, the review decision with its reason, and the version of the contributor terms you accepted.
  • Who sees it: a listed package and its details are public, under your public name. Anyone with a SphereHarness account can install it.
  • Reports and takedown notices: a report records who made it, the reason and the note. A takedown notice holds the details its sender gives us (name, contact address, the work and the statement); we send the notice to the publisher concerned.

The content catalogue

Packages published by SphereHarness are visible to everyone with an account; packages published by a reseller are visible only to that reseller’s customers. When you install a package we record which package and version you installed and when, so that we can tell you about updates and withdrawals and count installs. A publisher, including your reseller, sees only how many times a package was installed, never by whom. A download is recorded with identifiers only. Installing a package puts its files in your own library on your computer; withdrawing a package never deletes them remotely.

The content signature

Each published version of a package is signed by our server, so that the desktop agent and your organisation’s server can check that it came from the catalogue unchanged. Each signature contains the package’s identifier, kind and version, the fingerprint of its file list, the kind of publisher, the publisher’s internal account number (and the reseller’s, for reseller content), who may see it and when it was signed — never a name or an e-mail address. The signature travels inside every copy of the package, so a copy that has already been installed keeps it, also after the package is withdrawn or the publisher’s account is deleted.

13. Spam protection: Cloudflare Turnstile, and sign-in protection

Forms on this website that could be filled in automatically — sign-up, sign-in, password reset, contact, the reseller application, invitations, e-mail confirmation, device sign-in, and the forum, marketplace, report and takedown forms — are checked by Cloudflare Turnstile before we accept them. When such a page loads, your browser fetches Turnstile from Cloudflare (challenges.cloudflare.com), and Cloudflare decides whether the visitor is a person. Cloudflare receives your IP address, your browser’s user agent and TLS fingerprint, and the site key and address of the page; it does not receive what you type into the form. When you send the form, our server sends Cloudflare the result of the check and your IP address to confirm it. Our website is not otherwise routed through Cloudflare.

Cloudflare acts as our processor when it uses that data to protect our website, and as a controller of it when it uses it to improve its bot detection, as its Turnstile Privacy Addendum describes. We do not store the check itself; we keep a fingerprint of each accepted check for six minutes so that it cannot be used twice. The desktop agent and the CAD add-ins do not use Turnstile.

Sign-in protection. To stop password guessing and floods of requests we count wrong passwords and sign-up, forgot-password and contact requests per e-mail address and per IP address. We store an irreversible hash of the e-mail address, never the address, with the IP address and the time; these counts are deleted after two days. After too many wrong passwords sign-in is locked for a while, and the lock and each failed attempt are recorded in our audit log with the IP address, never the e-mail address or the password. A website administrator can lift a lock.

14. Website statistics: our own Umami, without cookies

To see which pages of this website are read and how visitors find us, the public pages of sphereharness.io load a small statistics script from our own server (/stats). It runs Umami, an open-source statistics tool that we host ourselves on our server in the EU. No data goes to Google or any other analytics company, and nobody else receives it.

No cookies, no tracking across sites. The script sets no cookies and stores nothing in your browser. It does not follow you to other websites, and we do not combine it with your account, your desktop agent or the CAD add-ins, which send nothing to it.

What is recorded for each page view: the page address and the page you came from; your browser, operating system and device type, screen size and language; and the country, region and city that your IP address points to, which we look up on our own server without asking anyone else.

Your IP address is not stored. It is used only for that location lookup and, together with your browser details, to form an anonymous visitor code. That code uses a value that changes every month, so visits cannot be linked across months, and it cannot be turned back into your IP address.

Do Not Track. If your browser sends a “Do Not Track” signal, the script records nothing.

How long, and on what legal basis. Statistics are deleted automatically after 26 months. We process them on the basis of our legitimate interest in understanding how our website is used and improving it (GDPR Article 6(1)(f)). You can object at any time: switch on “Do Not Track” or block /stats in your browser, or write to us.

15. The SphereHarness phone app (Android and iOS)

The SphereHarness phone app lets you talk to the desktop agent on your own computers from your phone: you send messages, see the replies and answer the questions the agent asks. It continues the conversation of the chat card on the computer you pick. It works only with the computers signed in to your own SphereHarness account.

Relayed, not stored. Your messages, the replies, the conversation the app loads from your computer, the questions and your answers pass through our server to your computer and back. Our server does not store them; it keeps only what it needs to deliver them while they are in transit (an open question for at most one hour). Pictures and files you send from the phone, and those your computer sends back, are held in our server’s memory for at most one hour so that the other side can fetch them, and are never written to disk.

What we store. The sign-in of the app: a record that your account signed in to the phone app, when it was last used, and an irreversible hash of its refresh token. It lasts 30 days from the last use and 90 days at most, and it is removed when you sign out in the app. If you allow notifications: the push token your phone’s platform gave the app (Firebase Cloud Messaging on Android, Apple Push Notification service on iOS) and which platform it is, so that we can tell you when your computer replies or asks a question. The notification carries only identifiers and a short line; the message itself is fetched by the app. We count how many accounts signed in to the phone app and how many devices accept notifications, by platform; we do not record what you send.

On the phone. The app keeps its sign-in in the phone’s secure storage (Android Keystore, iOS Keychain) and a few settings, such as the computer you picked; the conversation is loaded from your computer. It has no advertising, no third-party analytics and does not read your contacts or location.

Deleting your data. Sign out in the app to remove its sign-in and push token at once. Deleting your account (section 8, /org/delete-account) removes every phone sign-in and push token with it. You can also write to support@plmcadutilities.com from the e-mail address of your account and we will delete it for you.

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