LabWired ("LabWired", "we", "us") provides firmware development and simulation tools, including:

the web Playground at app.labwired.com;
LabWired Agent — the desk agent CLI and workbench (labwired agent, install from labwired.com);
hosted Model Context Protocol (MCP) tools at api.labwired.com/mcp and the model gateway at api.labwired.com/v1;
the LabWired app for ChatGPT; and
related open-source components (e.g. simulator core) under their own licenses.

Together, the hosted surfaces above are the "Services". This policy explains what data we handle and why. Questions: contact@labwired.com · privacy requests: privacy@labwired.com · security: security@labwired.com.

LabWired is a product and brand owned and operated by Andrii Shylenko e.v.

1. What we collect

Account & sign-in data. When you sign in (including device-code login for LabWired Agent or OAuth via the Playground / ChatGPT), we receive a user identifier and, depending on the flow, your email address. We do not receive or store your identity-provider password. Agent sessions may store tokens on your machine under ~/.labwired/session/ (local to your device).
Content you submit. Firmware source and binaries, board/diagram definitions, prompts and chat messages to the agent or Architect, twin/sim run inputs, and tool arguments sent to hosted MCP. This content is processed to run tools, models, and simulations and return results to you.
Project & usage metadata. Project ids, public model selection (for example labwired-default), request timestamps, approximate usage counts, and error diagnostics needed to operate the service.
Service & technical data. Logs for operation and security — request metadata, IP address, user agent, and basic telemetry for the hosted API and website.
Website analytics. Marketing pages may use Google Analytics for aggregate traffic. The Agent CLI runtime on your machine is not part of that analytics scope unless you use hosted APIs from it.
Submitted build descriptions. When you submit the main build form on our landing page, we may retain the description (limited to 500 characters) for product improvement and show it to allowlisted administrators. This event is not joined to an email address or user identity, and it is not recorded when Do Not Track or Global Privacy Control is enabled.
Local-only data (Agent on your computer). Config under ~/.config/labwired-agent/, skills, and local logs stay on your machine unless you send content to hosted Services (model gateway, remote MCP, Playground).

2. How we use it

To run simulations, agent tools, and model requests and return results.
To operate, secure, debug, bill (where applicable), and improve the Services and prevent abuse.
To authenticate you, associate work with a project, and respond when you contact us.

We do not sell your personal data. We do not use your firmware, source code, prompts, diagrams, or twin runs to train, fine-tune, or develop foundation models (ours or a third party's), except as needed to operate the Services (including abuse prevention and reliability).

3. AI / model processing (LabWired Agent & hosted brain)

The LabWired hosted agent uses hosted model-gateway/CLI conversations. LabWired stores their prompts, rewritten outputs, and normal source or firmware and tool calls embedded in those conversations. Browser Architect instead stores redacted Build Intent prompt/log data, not a full output, source, or tool transcript. Hosted MCP calls are processed but not conversation-content captured; only bounded usage telemetry may be retained.

Automated best-effort redaction masks or omits obvious credentials, private keys, email addresses, signed-token secrets in URLs, and large binary attachments. This removal is not guaranteed or perfect, so do not submit secrets. Customer content is not sold and is not used to train models by default.

When you use LabWired Agent with the hosted model gateway, prompts and relevant tool context are sent to our API (api.labwired.com) and may be processed by model providers we use as subprocessors to generate responses. When you use your own model endpoint (BYO URL/key), that traffic goes to your provider under their terms; LabWired may still receive tool/MCP calls if you use hosted MCP.

BYO Codex, Claude, and other local or direct traffic not sent to LabWired is not stored under this policy. If those clients call hosted MCP, the call is processed under the telemetry boundary above; it is not added to hosted conversation-content storage.

Model output is assistive only. You are responsible for reviewing code and validating on twin and real hardware before deployment.

4. LabWired through ChatGPT

The LabWired app for ChatGPT runs as an MCP connector. When you invoke it, ChatGPT (OpenAI) transmits your request to our MCP server; we process it and return the result. OpenAI's handling of your ChatGPT conversation is governed by OpenAI's privacy policy. LabWired only receives the data needed to fulfil the tool call you made.

5. Sharing

We share data only with service providers that help us run LabWired, under their respective terms:

Hosting & infrastructure (e.g. Cloudflare and our compute provider) to serve the site, playground, API, and MCP.
Model inference providers used for hosted LabWired Agent / gateway responses (under contracts that restrict use to providing the service).
Analytics (Google Analytics) for aggregate website traffic on marketing pages.
OpenAI, as the client application, when you use LabWired inside ChatGPT.
Payment processors (e.g. Stripe) if you purchase paid plans — card data is handled by the processor.

We may also disclose data if required by law or to protect the rights, safety, and security of LabWired and its users.

6. Retention

Primary hosted conversation rows follow our existing cloud-agent lifecycle and account deletion process. To request deletion of hosted conversations and your account, email privacy@labwired.com. We make daily compressed D1 and KV backup snapshots to the private labwired-backups R2 bucket. The working restore window is 7 days (our 7-day working restore window), with a 60-day R2 lifecycle backstop for stragglers. Backup copies may persist until their lifecycle expiration; deleting primary data does not promise immediate deletion from an older backup.

Local Agent config and session files on your device are under your control; uninstall or delete ~/.labwired and ~/.config/labwired-agent to remove them.

7. Security

Connections to hosted Services use TLS/HTTPS. Access is authenticated (OAuth or device-code tokens). No system is perfectly secure; we take reasonable measures to protect your data. Report security issues to security@labwired.com.

8. Your rights

You can request access to, or deletion of, the personal data we hold about you by emailing privacy@labwired.com or contact@labwired.com. Depending on your location (for example under the GDPR or CCPA), you may have additional rights to correct, restrict, or port your data; we will honour applicable requests. We do not sell personal information.

9. International processing

LabWired operates hosted infrastructure that may process data in the United States and other regions where our providers run. If you access the Services from elsewhere, your information may be transferred to those regions.

10. Children

LabWired is a developer tool intended for a general, technical audience and is not directed to children under 13 (or under 16 where a higher age applies).

11. Changes

We may update this policy as the product evolves. Material changes will be reflected by the "Last updated" date above.

12. Contact