What happens to your file

On supported browser conversion pages, an assistant connected through WebMCP can inspect and convert the file you select. CAD bytes stay in the tab. Tool responses contain dimensions, units, warnings and conversion reports; these responses may be sent to the assistant's model provider.

We count tool calls in daily totals by tool and outcome, with aggregate duration. These counters contain no filenames, document IDs, tool arguments, reports or agent identities. They measure calls, not unique visitors.

We count tool operations started, completed, failed or cancelled, and clicks on download links. Daily totals distinguish supplied examples from selected files and group activity by tool, operation and format. These counters contain no file names, file contents, document IDs, addresses or visitor identifiers.

A completed operation does not mean a download was saved. These are action counts, not unique people. Local development and signed-in private previews are excluded from normal analytics.

When Google Analytics is enabled, we also send tool starts, outcomes and download clicks with the tool, operation, format and whether you used an example or a selected file. This helps us understand which visits lead to tool use. These events contain no CAD file contents or file names.

Your file is read by JavaScript and WebAssembly running in your own browser. It is never sent to us. There is no upload request to intercept, no bucket it lands in, and nothing to delete afterwards. Closing the tab is the deletion. You can check this yourself: open the network panel, convert a file, and watch that no request carries it.

STL-to-STEP uploads the selected file when the service is available. The other 14 STEP pairs are core-only references with no public upload route. The page states whether the hosted service is unavailable or paused before file selection. The upload is stored in object storage under a lifecycle rule that expires each file one hour after it is written; the result is written after the upload, so its hour starts later. The download link stops working one hour after the job is queued. Expired files are removed by the storage service, which says it typically removes expired files within 24 hours of the expiry time, so a stored copy can outlast its link. Download expiry and storage cleanup are separate.

A job row exists so the queue can run and so we can measure what conversions cost. It holds the format converted from and to, the size in bytes, the triangle count, a status, an error code if it failed, and how much processor time it used. It holds no IP address, no filename, no account and no file contents. There are no columns for them, so there is nothing to forget to delete.

One more table exists for this lane: a rate limit of ten uploads per address per hour. It stores a salted hash of the address and the hour, not the address, links to no job, and is removed by the next upload that arrives after it is more than two hours old. This limits repeated uploads; the rate-limit hash is separate from the job record.

The upload path uses Cloudflare Turnstile for bot verification. Your browser connects to Cloudflare's verification service, and the server sends the verification token and your network address to Cloudflare to check it. These verification data are separate from the job record and usage counts.

Every capability claim on a format page (what a format stores, which applications open it) carries a link to the vendor's or standard's own documentation and the date it was checked. Where a source doesn't confirm something, the page says "unconfirmed" and keeps the value visible. Where sources disagree, it says "disputed" and shows both. An inferred yes is never published.

Every conversion claim is generated from a test run rather than written by hand. A pair that fails its tests has no page.

After a conversion or a viewer open, the page reports what happened in counts only: the two formats, the file's size in bytes, its triangle count, how long it took, and whether it worked. That is what lets us see which conversions people use and how large the files are. It does not include the filename, the file, your address, your browser, or anything that would tie two reports to the same person, and the endpoint that receives it reads no headers. The aggregates are public at/api/stats.

The preparation tools send a feature name and a bounded event name for starts, inspections, applied changes, export results, cancellations and failures. Those events contain no CAD bytes, filenames, model dimensions or persistent visitor identifier. Disabling a feature prevents its endpoint from accepting new events.

Sending the feedback form shares your message, the tool and page it concerns, any expected behavior you describe, and your email if you choose to include it. These reports are kept in a private inbox so we can improve the tools and respond. They are separate from anonymous usage totals and are never included in public statistics.

The form does not attach your CAD file, file name or model data. Please leave private file contents out of your message. To limit spam, a temporary rate limiter uses a salted hash of your network address; that hash is not stored with your report. A flag in your tab’s session storage prevents repeated feedback invitations. It is not a visitor identifier.

When analytics are enabled, we count feedback-form opens, successful submissions and support-link clicks by tool and placement. Message text and email addresses are never sent to analytics. A support-link click does not tell us whether a payment was completed.

Video previews are served from this site. The YouTube player loads only when you press play. Playback uses YouTube’s privacy-enhanced embed and connects your browser to YouTube, which handles playback data under Google’s privacy policy. The CAD files you open in our local tools are not sent to the video player.

When site analytics are enabled, we count play requests by video and placement. A play request does not tell us whether you watched or finished the video.

Google Analytics measures page views and how visitors use the site. It may use browser identifiers such as cookies; it never receives the CAD files you open or convert in your browser. There are no accounts: nothing to sign up for and nothing to sign in to.