Privacy Policy

The short version

STL to G-code Converter does not receive your model files. They are read, sliced and turned into G-code inside your own browser tab, and discarded when you close it. There is no account to create, no upload, and no server-side processing, because there is no application server — the site is a set of static files.

The short list of things that leave your device is this: a request for the page itself, Google Analytics measurement requests to Google, and an email address, if you choose to send us one. We set no cookies ourselves, and your model files never leave your browser.

Who runs this site

Astha Singh ("we", "us") operates https://stltogcodeconverter.com. We are the data controller for the information described on this page, and the party responsible for it.

This site is not affiliated with, endorsed by, or sponsored by any printer manufacturer, slicing-software project, or the authors of any format mentioned on it.

The files you load

When you open an STL file, the browser hands the file to the page. The page reads its bytes with the browser's ownFile API, computes triangle counts, a bounding box, mesh integrity, layer paths and G-code, and writes the result into a text file you can download. All of that is arithmetic in the tab you are reading this in.

Concretely, the following are true and are not promises about the future:

• The contents of your STL are never sent over the network. They are not uploaded, and there is no endpoint that could accept them.
• Your file's name is held in memory for the length of the session, because the downloaded G-code is named after it. It is not written to storage and not sent anywhere.
• When you close or reload the tab, the file is released. There is no database, no backup, and no copy — the bytes existed only in your browser's memory.
• Nothing is added to your browser's permanent storage. There is no IndexedDB database, no Cache API entry and no service worker caching your model.

Two features move data out of the page, and both take a deliberate click from you:

• Copy to clipboard puts the G-code text on your operating system's clipboard, where anything you paste it into can read it.
• Share hands the file to your operating system's share sheet, and you choose where it goes.

What is stored on your device

Theme preference

The value light, dark or system, written to localStorage under the key theme. It is set when you use the theme toggle, or when you choose a setting your operating system has stored. It contains nothing about you, it is never read by us, and clearing site data in your browser removes it.

Everything else: nothing

Your print settings — layer height, infill, temperatures, speeds — are held in memory for the current page view only. Changing a setting and closing the tab loses it, deliberately: we would rather you could not accidentally print last week's profile.

We do not set any cookies ourselves, and we do not use cookies for preferences or sessions. Google Analytics sets its own cookies for measurement, as described below.

What our host records

The site is served as static files. As with any web host, the service that serves those files — and not our application code — may record ordinary web server logs when you request a page, which can include your IP address, your browser's user-agent string, the time of the request, and the URL requested. That data is processed under the host's own privacy policy and retention schedule, and we do not add to it, read it for our own purposes, or combine it with anything else.

We are telling you this rather than staying silent about it because "nothing is collected" is only ever true of the site's own code, and the honest version includes whoever serves the files.

Cookies and tracking

We use Google Analytics 4 for basic site measurement — which pages are visited, roughly how often. It is provided by Google, loads its script from www.googletagmanager.com, and sets its own cookies for measurement. We do not use advertising code, session recording, error-reporting, A/B testing, or fingerprinting, and we do not identify you from analytics data.

You can block analytics with a content blocker or by disabling third-party scripts in your browser; the converter keeps working either way.

Third parties

The page loads its own JavaScript, CSS and fonts from this domain only — including the typefaces, which are served from here rather than from a font CDN. The exception is Google Analytics: its measurement script is loaded from www.googletagmanager.com and sends page-visit data to Google. Apart from that, no content, script, style or image is embedded from another origin.

This page names other products and services in its text — slicers, printers, model libraries — for the purpose of explaining how printing works. Naming them does not mean we are connected to them, and no link to them carries any tracking.

What happens when you email us

If you write to [email protected], your email address and whatever you include in the message reach us, and they do so through your own mail provider rather than through anything on this site. We use that information only to reply to you and to keep a record of the issue. We do not add you to a mailing list, and there is no list to add you to.

Please do not send a model file, an STL or an OBJ, or any geometry you do not have the right to share. We do not need it to diagnose a slicing question, and we would rather not hold a copy of your client's design.

Your rights

Under the UK GDPR and EU GDPR, and similar laws elsewhere, you have rights over personal data: to access it, to correct it, to have it erased, to restrict or object to its processing, and to complain to a supervisory authority. Where you are a California resident, the CCPA and CPRA give you the right to know what is collected, to request deletion, and to opt out of sale or sharing.

In practice there is very little here to exercise any of those rights against. We hold no account for you, so we have no record of who you are, and we do not hold your model or your settings. The one category of personal data that exists in connection with this site is in our host's server logs, which are under the host's control; we will pass any request about those to them and support it.

We do not sell or share personal data, and we have never done so. We have not used or disclosed it for advertising, and we do not build profiles or make automated decisions about anyone.

Security and retention

The page is delivered over HTTPS. Model data never leaves your device, so there is nothing for us to secure, retain or delete — that is the practical benefit of an application that runs in the browser rather than on a server.

What we do keep: correspondence you send us, which we keep while the issue is open and for a reasonable period afterwards so we have the context if you come back to it. You can ask us to delete it at any time.

Children's privacy

This site is a technical tool and is not directed at children under 13, or under 16 in jurisdictions where that is the higher threshold. It collects no personal data from anyone, of any age, so there is nothing here to obtain a child's consent to. If you believe a child has sent us personal information, contact us and we will delete it.

Changes to this policy

If this policy changes, the date at the top of the page changes with it. A material change — something that alters what we do with data, or who we share it with — will be called out on the home page as well, so it does not depend on you happening to re-read this page.