Privacy

GetSVG's promise is that your picture is converted on your device and is never sent anywhere unless you explicitly choose to send it. This page says precisely what that means, and names the only two requests the site makes, because "private" is easy to claim and easy to check.

What happens to your image

• The file is opened by your browser and decoded into pixels in memory.
• Tracing runs in a Web Worker on your computer, using WebAssembly that was downloaded with the page.
• The SVG and PNG you download are generated in the browser and saved straight to your disk.
• When you close the tab, the picture is gone. Nothing is stored by the site — not in cookies, not in local storage, not on a server — unless you used the report box described below.

What the site does not do

• No server-side conversion. There is no API your image is sent to in order to be traced.
• No cookies, no local storage, no session identifiers.
• No analytics or tracking scripts, and no advertising.
• No third-party requests: fonts are served from this site, and there are no embedded widgets or ad networks.
• No account, so there is no personal data to hold.

The two requests this site does make

Both go to this site itself, never to anyone else. They are listed here rather than buried, because the whole point of the promise above is that you can check it.

1. Counting conversions

When a conversion finishes, the page sends one request whose entire body is {} — an empty object. A number on the server goes up by one. There is no identifier, no cookie, no filename, no image, not even the size of your picture, so the count can answer "how many conversions have there been?" and is deliberately incapable of answering anything else. It is sent once per picture, not once per settings change.

2. A report you choose to send

After a conversion you are asked, once, whether the result was any good. Saying it was good sends that one word. Saying it was not opens a box where you can describe the problem, and a tick-box — off by default — offering to send the picture and the SVG it produced.

That tick-box is the only way an image ever leaves your device, and it takes a deliberate tick and a deliberate press. If you tick it, the original file and the SVG are stored so the failure can be reproduced and the tracer fixed. They are kept for that purpose only: not published, not sold, not used to train anything, and not linked to you, since there is no account and no identifier to link them to. Ask at the contact address on the about page and a report will be deleted.

Skip the question, close it, or answer without ticking the box, and nothing about your picture is sent.

What the hosting provider sees

Like any website, the server that delivers the page receives your IP address and the standard request headers in order to send the files. That is the whole exchange: the page's HTML, CSS, JavaScript, WebAssembly and fonts go from the server to you, and the only things that go back are the two requests named above.

How to verify it yourself

1. Open the vectorizer and press F12 (or right-click → Inspect) to open developer tools; choose the Network tab.
2. Drop an image and change a few settings so it traces several times.
3. Watch the request list while it traces. The only request that appears is the one-per-picture counter described above — click it and look at the request body, which is two characters long. Nothing else is sent while tracing or exporting, and loading a built-in sample fetches that sample image from this site and nothing else.
4. For a stricter test, switch the Network tab to Offline after the page has loaded. Tracing and downloading keep working.

Changes

If any of the above ever changes — for example if privacy-respecting, cookieless analytics were added — this page will name the exact service and what it records before it goes live. The claims here are generated from a single file in the source code, so they cannot drift out of step with the FAQ or the rest of the site.