Privacy Policy

Your save file is never uploaded

This is the whole point of the site, so it is worth being precise about it. When you drop a save into an editor, the file is read by JavaScript running inside your own browser tab, using the standard FileReader API. The parsed values are held in that tab's memory while you edit them, and the file you download at the end is generated in the tab as well.

There is no upload step anywhere in that sequence. No request carrying your save is sent to this site or to anyone else, which also means we never store one, never see one, and could not hand one over if we were asked to. Close the tab and every trace of the file is gone from the browser too — nothing is kept in local storage, in a cache, or in a database.

You can check this yourself rather than taking our word for it: open your browser's developer tools, switch to the Network tab, and use an editor normally. You will not see a request containing your save, because there isn't one.

No accounts, one kind of cookie

There is no sign-up, no login and no user profile, so there is no name, email address or password for us to hold. The site itself stores nothing in your browser — no local storage and no cookies of its own.

The one exception is Google Analytics, described in the next section. It sets its standard _ga cookies so that two page views from the same browser count as one visitor rather than two. Those cookies contain a random identifier — not your name, not your email, and nothing from your save file — and we do not use them for advertising.

What we collect

We use Google Analytics 4 (property G-XRYEJWSPEN) to see how the site is used: which pages are visited, which sites people arrive from, an approximate location derived from the IP address (Google states GA4 does not log the address itself), and what kind of device and browser is in use. What we look at is aggregate — we can see how many people opened an editor, not what any one of them did with their file.

Nothing you do inside an editor is sent to Analytics: no file names, no file contents, no edited values. The save file never leaves your browser, and the analytics script has no access to it. There is no advertising on the site and no advertising features are enabled in Analytics.

Separately, as with every website, our hosting provider handles the request that delivers each page to you. In doing so it processes standard technical connection data — your IP address, the time of the request, the page requested, and your browser's user-agent string — to serve the page and to block abuse. We do not use that data to build a profile of you, and it is not linked to anything you do inside an editor, because nothing you do inside an editor reaches a server in the first place.

If we ever add advertising or change what is measured, this section will say so — before it goes live, not after.

Your rights

Privacy laws such as the GDPR give you rights over personal data held about you: to access it, correct it, have it deleted, or object to its processing. Those rights apply here in a fairly short form, because we hold almost nothing — no account and no save file. The identifier in the Analytics cookie is a random string we cannot connect to your name or email address, and the technical connection data described above is processed by our host on our behalf and is not linked to your identity.

If you want to ask about any of this, or believe we hold something about you, get in touch at the address below and we will answer.

Children's privacy

The site is a utility for editing files you already own and is not directed at children. Since we collect no personal information from anyone, we do not knowingly collect any from a child either.

Changes to this policy

If this policy changes, the date at the top of the page changes with it. A change that affects what is collected — adding advertising or a new analytics tool, for example — will be described in plain language rather than folded into a general update.