Privacy Policy
Last updated November 7, 2026
This policy describes how Thompson Labs LLC (“we”, “us”) handles personal data for text-to-cad: the text-to-cad plugin and its skills, the text-to-cad software they run (the packages cad, cad-server and cad-mcp, named cadgen before 0.10), and this website, texttocad.dev. text-to-cad runs on your computer. Your prompts, models, drawings and files stay there, and we do not collect them.
1. Personal data we collect
- The plugin and its software: your prompts, models, drawings, file names and paths never leave your computer. There are no accounts. Your agent and the local runtime process your work on your computer and do not send it to us.
- Telemetry: usage counts and crash reports, when it is on. text-to-cad’s long-running parts -- the CAD app that shows models in your agent app (the plugin’s
cad-mcpserver) and the CAD viewer in your browser (cad viewer), and in earlier releases the build daemon that built models for them -- send to api.texttocad.dev, with whatcadcommands and model scripts counted, at most once every five minutes while you use them and once as each stops:- a random install ID created on your computer, a random ID for each time one of them starts, and a random ID for each batch, with the time it was made by your computer’s clock, so that a batch sent again after a failed send is counted once;
- which of them sent it, the text-to-cad version, where it was installed from (a plugin directory, the Cursor Marketplace, GitHub, or a development install, as the plugin’s CAD app names it and notes on your computer for the viewer and text-to-cad’s commands to report too), your operating system and processor type, and the name and version of your agent app and how it shows CAD (or that it is the browser viewer);
- counts, added up over those five minutes: how many times each CAD tool was called and failed, and why each failure happened, as one of a fixed set of words text-to-cad chooses (such as no file at the path the agent gave, no view open, a view that did not answer in time, or a bug in text-to-cad) -- never the error’s message or the path; how many times you touched a CAD view; which of a CAD view’s tools and settings you used (such as Select and its filters, Measure, Pencil and Shapes and what they draw with, Explode, Clip, the display modes and Grid, Projection, Preview and its settings, playback, a model’s joints, the sidebar’s sections, a part’s menu, the view cube, Quick Edit’s Copy, Queue and Send, Export, the Models and Files menu, Theme and Language, and the home’s search, filters, layout and card menus), each as a name from a fixed list, with how many times each was used and, for a tool that stays on (the tool in hand, or Preview), how many whole seconds it was on -- never what you typed, a value you chose (other than a choice that is itself a name on the list, such as a display mode or a clip axis), or the name of a file or a part; how many different live models and files of each format (such as XBF, STEP or STL) a CAD view showed for the first time that day, told apart on your computer and sent only as a number; how many models were built and files exported, with live models counted separately from each exported file format, whether a model script or a
cadcommand asked, how they ended (finished, failed, crashed or stopped), how many were reused from an earlier build rather than built again, and how long they took; how many snapshots were drawn, of a live model or which file format, how many failed and how long they took; why each build or snapshot failed, again as one of a fixed set of words text-to-cad chooses from the kind of error and whose code raised it (such as an error in your model’s code, a CAD operation the geometry kernel could not do, a module or file that is not there, a picture that could not be drawn, no graphics context to draw it in, or a bug in text-to-cad) -- never the error’s message, your code or the path; for a snapshot request text-to-cad turned down, which part of the request it turned down (such as the display mode, the clip, the camera or the size), as a name from a fixed list -- never the value given; how many times assemblies, mesh exports, posed joints, animations, engineering drawings and Quick Edit were used; and how many of the CAD engine’s build workers started, crashed or were retired (and, from earlier releases, how many builds were turned away for want of memory); - crash reports, when text-to-cad’s own code fails unexpectedly: the error’s type (such as “KeyError”), whether the program carried on, and where in code it failed -- file paths inside text-to-cad, Python’s standard library, text-to-cad’s own open-source dependencies or the CAD app’s and viewer’s page scripts, with function names and line numbers -- or, for a build worker that crashed, its exit status. Any part of the failure in your own code is replaced by a placeholder, and a crash report never includes the error’s message, any values, your files, or file or folder names.
cadcommand or model script sends nothing itself: it keeps what it counted (a build, an export, a snapshot, a drawing, a crash) on your computer for the next part of text-to-cad that sends; when nothing has sent it for five minutes, the nextcadcommand starts a short-lived sender in the background, which sends it and exits. Like any request over the internet, each one also reaches our host with your IP address, the time and a user agent (just “cadgen”, the software’s name before 0.10); see section 4 for what happens to them. Section 5 says when telemetry is on and how to turn it off. - The version check: at most once an hour, text-to-cad (the CAD app or the CAD viewer) asks api.texttocad.dev which text-to-cad release is the newest, so it can tell you when there is an update. The request carries no ID and nothing about you or your work; like any request, it reaches our host with your IP address, the time and a user agent (“cadgen”). It is never made in CI or for a copy that a plugin directory or the Cursor Marketplace updates, and section 5 says how to turn it off. An update you ask for (CAD’s update button, or
cad update) asks again, then downloads the release from PyPI, as the install command does. - This website: page views, with the referring page, browser, device type and country, through Vercel Web Analytics, which sets no cookies. Each request also includes standard metadata: your IP address, the time and the user agent.
We do not collect payment card data, health information, government identifiers, passwords, API keys or other credentials, or any sensitive category of personal data.
2. How we use it
- Request metadata: only to deliver, secure and troubleshoot api.texttocad.dev and this website.
- Page-view statistics: only to understand, in aggregate, how this website is used.
- Version checks: only to answer them; we keep nothing from them beyond our host’s request logs.
- Telemetry: only to understand, in aggregate, how many people use text-to-cad and how often, how many files they work on and in which formats, what they build and how long it takes, where in the world it is used, which features are used, which of the CAD views’ tools and settings are used and for how long (so we know which to improve and which matter less), which agent apps and operating systems to support, and how often tools, builds and snapshots fail; and, from crash reports, to find and fix the bugs behind them.
We do not sell personal data, use it for advertising, or build profiles of you, and we do not track you across other sites or services.
3. Who receives it
- Vercel Inc., which hosts this website and api.texttocad.dev and processes their requests for us, and PostHog, Inc., which stores and analyzes telemetry for us. PostHog never sees your IP address: only our server sends it telemetry, with the country it worked out and PostHog’s own location lookup turned off.
- Services the software contacts directly, under their own privacy policies. The agent app installs the pinned text-to-cad runtime from the Python Package Index (PyPI) the first time it starts after an install or an update. Skills reach the services you ask your agent to use, such as a fabrication service’s public specifications or your own printer on your local network. These requests send no personal data of ours; each service sees the request’s IP address, time and user agent.
We share personal data with no one else, except where the law requires it.
4. How long we keep it
- Vercel, our host, records each request to api.texttocad.dev and this website in its request logs, with the IP address, time and user agent it arrived with. We use those logs only to run and secure the services, and they are deleted within 30 days.
- Website analytics are kept as aggregate page-view statistics. The visitor identifier Vercel derives from a request is discarded after 24 hours.
- Telemetry is kept by PostHog for as long as our plan with it keeps events, currently one year, then deleted. We do not store IP addresses with it. Your install ID travels in the body of each request, which our host’s request logs do not record, and we never combine telemetry with those logs. The one exception is a batch our server refuses as malformed: its logs then keep the name of the rule it broke and the text-to-cad version that sent it, never your install ID or any other value from it. Turning telemetry off deletes everything stored under your install ID; PostHog carries the deletion out in the background, which can take some days. If our server cannot be reached at that moment, text-to-cad asks again until it can.
- Everything text-to-cad stores locally stays on your computer until you delete it.
5. Your choices and controls
- The plugin works without contacting us, apart from the hourly version check.
- Telemetry is on once text-to-cad has told you. The first
cadcommand you or your agent run says, once, in its output, that text-to-cad sends usage stats and crash reports and how to turn them off, and nothing is sent before that. A command’s help, and a command whose answer is JSON for a program to read, say nothing of it: the next one does. If we ever send more than this policy describes, text-to-cad says so again before it does. Nothing is sent by default in CI or from a development install. Your choice is kept on your computer, as thetelemetrysetting in text-to-cad’s settings file, through restarts and updates, and one choice counts for every part of text-to-cad; a no stays a no. Turning telemetry off also turns off analytics in an earlier version still installed, and deletes what it sent. Nothing waits to send: what a command or a model script counts, and what any part of text-to-cad counted since its last send when it exits, wait in small files beside that setting until the next part of text-to-cad sends them, or a sender the next command starts once they have waited five minutes; turning telemetry off deletes those files too. - To turn telemetry off, run
cad telemetry off, use Telemetry in the menu of the CAD app or the CAD viewer (the logo at the top left, over any open model), or ask your agent to turn off CAD telemetry. Turning it off deletes the install ID on your computer and asks our server to delete everything stored under it. Turning it on again starts a new install ID, so nothing links the two.cad telemetry onturns it on, andcad telemetry statusshows the setting and your install ID. - Setting
DO_NOT_TRACK=1orCAD_TELEMETRY=0(CADGEN_TELEMETRY=0before 0.10) where text-to-cad runs (your agent app’s environment, or the shell that runs acadcommand or a model script) turns telemetry off for that process and the builds it asks for, whatever your setting says;CAD_TELEMETRY=1turns it on for that process the same way. Neither changes your setting, and the parts of text-to-cad that process starts to run on their own, a viewer started in the background and the short-lived sender, go by your setting. - Setting
CAD_UPDATE_CHECK=0(CADGEN_UPDATE_CHECK=0before 0.10) where text-to-cad runs turns the hourly version check off; CAD then never says when there is an update. - You can uninstall the plugin at any time. Deleting text-to-cad’s cache and state folders removes everything it stored on your computer, including its recent-files list.
- You can block this website’s analytics with your browser’s settings or a content blocker.
- You can ask us what personal data we hold about you, or ask us to delete it, using the contact below.
6. Children
text-to-cad is not directed to children under 13, and we do not knowingly collect their personal data.
7. Changes
We will post any change to this policy on this page and update the date above.
8. Contact
Thompson Labs LLC. For privacy questions and requests, open an issue at github.com/earthtojake/text-to-cad/issues.