Privacy and what Studio sends

Studio works on your computer. Studio itself sends only what starting a trial and activating and renewing a paid licence need. There is no telemetry, no update check and no automatic crash upload. If you connect the AI assistant to a cloud service, your messages and what you attach go to that service: see The AI assistant and cloud services. This chapter lists what goes out, what stays on the computer, and how to remove it. The website's privacy policy, twinwright.com/privacy, is the binding text.

What Studio sends

When	To	What
You start a trial of a paid edition	Twinwright's licence server, over HTTPS	The edition, a hash of the computer's fingerprint, Studio's version
You activate a paid licence	Twinwright's licence server, over HTTPS	The activation code, a hash of the computer's fingerprint, Studio's version
Studio renews a paid licence (see Renewal)	Twinwright's licence server, over HTTPS	The licence's number, the same hash, Studio's version

That is all Studio itself sends to Twinwright. The fingerprint never leaves the computer as it is; only a hash of it does. A computer activated offline sends nothing at all.

Three things go out only when you set them up:

The AI assistant, connected to a cloud service. It sends your messages and what you attach to that service; see below.
An AI client you connect over MCP, such as Claude or ChatGPT. The client sends what it reads from the twin to its own service, under its terms.
A web page Studio opens, such as the licence page. Your browser opens it; Studio adds nothing to it.

The AI assistant and cloud services

The AI assistant works with the provider you choose in it: a cloud service such as Anthropic, OpenAI or DeepSeek, with your own account and API key, or a local model.

When you send a message to a cloud service, Studio sends to that service, from your computer and with your key:

your message, with the conversation so far;
the window's machine, setup, program (with line numbers) and the problems the checks found, while Attach the window's program, setup and check results (when they changed) is ticked. The box is ticked at first. Studio attaches them to the first message, and again only when they have changed;
the results of the tools the assistant uses in Studio, such as the check or simulation of a program, the machine's status or entries of the log, and pictures of results for services that accept pictures.

Before the first message goes to a cloud service, Studio shows once what it will send.

The service handles all of this under its own terms; Twinwright receives none of it. To send less, untick the box before you send, or start again with New conversation.

With a local model (LM Studio, Ollama), all of this stays on the computer.

On this computer, the audit log keeps the first 180 bytes of each message (see The audit log), and the API keys are stored encrypted (see What Studio keeps on the computer).

What Studio keeps on the computer

What	Where (Windows)	Who sees it
Settings, the state of the twin, AI keys	`%LOCALAPPDATA%\Twinwright\Studio`	Your Windows account
Program versions	`Documents\Twinwright Studio`	Your Windows account
The audit log	`Documents\Twinwright Studio\logs`, unless Settings name another folder	Your Windows account
Inspection reports, setup sheets, diagnostic files	`Documents\Twinwright Studio\Reports`	Your Windows account
Reports of unexpected exits	`%LOCALAPPDATA%\Twinwright\Studio\crash`, deleted after 30 days	Your Windows account
Licence files, trials included	`%ProgramData%\Twinwright\licence`	Everyone on the computer

AI keys are stored encrypted for your Windows account (Windows DPAPI). Other accounts on the same computer cannot read them.

The audit log

The audit log is a file a day, audit-YYYY-MM-DD.jsonl, in the log folder. It records:

what the AI and you had the machine do;
the first 180 bytes of each message in the AI panel;
licence checks: the licence's number, the edition and the result, without the holder's name.

Keys, tokens and passwords are written as ***. Settings set how much the log records and how long it keeps it. The log stays on the computer; Studio never uploads it.

If Studio closes unexpectedly

At the moment of the failure, Studio writes a small report: where it failed, the order of calls that led there, and the list of program modules. It writes no memory contents.

At the next start, Studio adds the version information and the last 200 lines of its log, cleaned:

paths and file names are replaced by placeholders;
names and e-mail addresses are removed;
there is no G-code, no AI conversation, no licence code and no fingerprint.

Studio then asks once. You can open the report's folder, save the report as a file, or close the message. Nothing is sent. To help us find the cause, send the file to hello@twinwright.com yourself.

Diagnostic information

When you ask us for help, we may ask for diagnostic information. In the Help menu, choose Collect diagnostic information. Studio saves a ZIP file in the reports folder with the items you tick:

Item	Ticked at first
Version, system, graphics, language and units	Yes
Settings, without the AI keys	Yes
The machine profile and the controller's `$` settings	Yes
The last 7 days of the log and the reports of unexpected exits, cleaned as above	Yes
The licence status: edition and end date, without codes or the fingerprint	Yes
The current program and setup: your part's data	No

Open the file and read it before you send it. Nothing is sent automatically.

What listens on the network

Studio's servers for AI clients (MCP) and for sender software listen only on this computer (127.0.0.1). Other computers cannot reach them.

The command-line option --bind any opens the twin's network ports, such as the one for sender software, to your network. The MCP server stays local.

⚠ Warning

In shadow mode, the sender port passes commands to the real machine. With --bind any, anyone on your network who reaches that port could move the machine. Use --bind any only for the twin, on a network you control.

What our server keeps

For each paid licence, the licence server keeps:

the hashes of up to three computers a seat, with the dates each was first and last seen, so that you can free one on the licence page;
the activation code only as a hash: not even we can read it back;
for 90 days, a log of trials, activations, renewals and changes, with the computer's hash, Studio's version and your IP address shortened to its network part.

For each trial, it keeps the computer's hash with the edition and the trial's dates, so that each computer has each trial once.

Nothing about your work reaches the server.

Removing what Studio keeps

Free the computer on the licence page, so that it no longer counts (see Move a licence to another computer).
Uninstall Studio.
Delete the folders in the table above that you no longer need. Result: nothing of Studio remains on the computer.

Uninstalling removes the program, not your files: your projects, program versions, logs and reports stay until you delete them.