Last updated 18 September 2026 · PLM CAD Utilities AS
This policy explains what CAD Co-Pilot 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 hosted service behind them. It forms part of the End User Licence Agreement you accept when installing the software.
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.
| Category | Examples | Why |
|---|---|---|
| Account | Name, email, organisation, hashed password, licence and seat assignment, reseller relationship | To create your account, control access, and apply your licence |
| Chat content | The instruction you type, and the conversation history of the current session | To understand and carry out the request |
| CAD context | Names, dimensions, feature and face identifiers, mass and bounding-box values, file paths, and screenshots when a request needs visual confirmation | To act on the right geometry and verify the result |
| 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 |
| Usage records | Timestamp, model name, provider, input and output token counts, tool-call count, elapsed time, estimated cost, and whether your own provider key was used | Billing, quota enforcement, and the usage statistics shown in the add-in |
| Diagnostics | Error messages, operation names and outcomes, and support attachments you choose to send | To investigate faults you report |
| Optional knowledge | Documents, specifications or part libraries you deliberately index for search | Only to answer your own queries, within 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.
Carrying out an instruction requires sending it, and the relevant CAD context, to a large language model. That happens in one of two ways:
Providers we support include OpenAI, Anthropic, Google, xAI, DeepSeek and Groq, and which one is used depends on the model selected for your organisation or by you. They are independent controllers or processors under their own terms, and their handling of your prompt is governed by those terms. Where we hold a provider key on your behalf it is stored encrypted and is never returned to the client.
When you use your own key, your own hosted model, or a local agent, 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. Where the request runs through a local agent or a model on your own machine, the prompt and the CAD context do not reach our servers at all; we still record the usage metadata in the table above so that we can show you your own consumption, and where you supply a key to the hosted service it is stored encrypted and is never returned to the client. The providers named above, together with the hosting and email providers in section 7, act as our sub-processors only where we call them under our platform key.
We do not use your CAD geometry, drawings or chat content to train our own models. Whether a provider does so is determined by the agreement covering the key in use; the major providers' API terms exclude training on API traffic by default.
The service runs on servers in Europe. Account data, usage records, support tickets and indexed knowledge live in our PostgreSQL database on that infrastructure. Support attachments are stored in Cloudflare R2 under EU jurisdiction. Optional encrypted backups go to the storage account you nominate. Calling an AI provider may transfer the request outside the EEA, under the safeguards in that provider’s terms.
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. Settings and any locally recorded usage log 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.
An administrator can configure a connection to an external system, such as an ERP or CRM, to execute in client-direct mode. In that mode the business data of each call flows directly from your workstation to that system and does not transit our servers — we never see the request or the response. Each release of a credential or short-lived token to a workstation is recorded in our audit trail, and, when your organisation enables call auditing, a metadata-only record of each call (method, path and status — never the payload or the response body) is kept as well.
When your administrator enables connection capabilities, the assistant can reach systems you direct it to — including databases, web APIs and other network services. Business data exchanged with those systems flows between the executing component and the destination system; where a connection runs directly from your workstation, that data does not transit our servers. We record an audit entry for each connection and database operation containing only metadata — who, when, which connection, which protocol, whether it was a read or a write. We do not record the contents of your queries, the data returned, or your credentials.
The AI provider handling your request, as described above. Our hosting and email providers, as processors. Your organisation’s administrators, who can see seat assignment and usage for their organisation. 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.
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.
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.
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.
We will update this page when our practices change and revise the date at the top. Material changes will be announced through the service.