In short
- Your files are opened and converted by your own browser. They are not uploaded to SVGCS or to anyone else.
- There are no accounts. SVGCS never asks for your name, your email address or any other detail about you.
- A few settings are kept in your browser so the site remembers them. Each one is listed below.
- Visits may be counted by Google Analytics and by Cloudflare Web Analytics, as described below. Your files, their names and their contents are never part of it.
Who is responsible
SVGCS is run by , who is responsible for the visit data described on this page (the controller, in the words of the GDPR). To ask about it, write to .
This page does not yet name who runs SVGCS. Until it does, Google Analytics stays switched off: the site's configuration will not load Google's script without a named operator and a way to reach them.
Your files
When you choose, drop or paste a file, the conversion runs in your browser, in code the page downloaded from svgcs.com. The file, its name and the result stay on your device. There is no server that converts files, so there is nothing to upload them to.
When you send a result on to another tool with “Continue to…”, the file is put in your browser’s own storage for the next page to open. That page deletes it as soon as it opens it, and it can no longer be opened after one hour. The link between the two pages carries only a random key after the # sign, and browsers never send that part of an address to a server.
How this is checked: an automated browser test adds a file whose name and contents carry unique markers, with analytics switched on and accepted, which is when the most is sent. It runs against local stand-ins for the Google and Cloudflare scripts, not the real ones, so nothing leaves the test machine. It records every request the page makes and checks the address and body of each as plain text and as base64. It fails if the file’s name or its marker appears in either form, if any request to the two analytics services is larger than 8 KB, if anything is posted to another host, or if everything sent after the file was added comes to more than 5% of the file’s size. Because the stand-ins are not Google’s script, the test does not cover what Google’s script adds by itself; that is described under Google Analytics below.
What is stored in your browser
| Name | Where | What it is for | How long |
|---|---|---|---|
theme | Local storage | The theme you chose with the theme button: light or dark. | Until you clear this site's data. Written only when you press the theme button. |
svgcs.advanced.<tool> | Local storage | Whether you left a tool's Advanced options open or closed. One entry per tool. | Until you clear this site's data. Written only when you open or close Advanced. |
analytics-consent | Local storage | Your answer about Google Analytics: accepted or declined. | Until you clear this site's data. Written only while Google Analytics is switched on, when you answer. |
svgcs-handoff / entries | IndexedDB | A file you send on to another tool with “Continue to…”, and its name, so the next page can open it. | Deleted when the next page opens it. Unreadable after one hour, and removed the next time a file is sent on or opened this way. |
SVGCS sets no cookies of its own. You can delete everything above at any time by clearing this site’s data in your browser’s settings. The tools keep working if your browser blocks storage; the settings are then forgotten when you leave the page.
Google Analytics
Google Analytics is not switched on for SVGCS at the moment. No Google script loads, no Google cookie is set, no consent question appears and the footer has no “Privacy choices” button. The rest of this section describes what will happen once it is switched on.
Google Analytics is switched on for SVGCS. This section describes what it does.
When it loads. In the European Economic Area, the United Kingdom and Switzerland, and wherever your country cannot be told, a banner asks first, and nothing from Google loads until you choose Accept. If you choose Decline, or do not answer, it never loads. Elsewhere it loads once the page has finished loading, or at your first click or key press, whichever comes first. Outside those countries it does not load if your browser sends the Global Privacy Control signal and you have not said otherwise. Your country comes from Cloudflare, which hosts the site; it is used only to choose between these rules and is not stored.
What it may do. Only measure visits. Advertising storage, advertising data, ad personalisation and Google signals are all switched off, in every country. Anything that happens on a page before you accept is dropped, not saved for later.
What is sent. For each page: its address with everything after a ? or # removed, its title, and the page you came from (only the site’s name when it was another site). Then SVGCS’s own code sends these events, with only these values:
| Event | Sent when | Values it carries |
|---|---|---|
file_added | A file is added to a tool. |
|
sample_used | You choose “Try a sample”. |
|
convert_success | A conversion finishes. |
|
convert_error | A conversion fails. |
|
option_change | You change an option. |
|
download | You download a result. |
|
chain_click | You follow a link from one tool to the next. |
|
feedback | You answer “Did this work?”. |
|
web_vitals | Once per page and measurement: how quickly the page loaded, stayed still and responded. |
|
exception | The page's own code fails unexpectedly. At most five times per page. |
|
Each event also carries the page address, shortened in the same way. SVGCS sends sizes, durations and counts only as the ranges listed.
What SVGCS itself never sends. File names, file contents, pasted code, the values you choose for options, exact sizes, times or counts, error messages, and anything you type. Google’s script sends some exact values of its own, described next.
What Google adds. The Google script also sends events of its own, which SVGCS does not choose: first_visit the first time you visit, session_start when a visit begins, and user_engagement while the page is in focus. With them it sends a random visitor number kept in the cookies below, a session number, a count of your visits to the site, and how long the page was in focus, in milliseconds; every event it sends also carries your browser’s language and your screen resolution (Google’s list of automatically collected events). The page view is sent by SVGCS, as listed above, not by Google’s script. Google’s optional “enhanced measurement” events, which record scrolling, clicks and file downloads by themselves, are switched off in the site’s Google Analytics settings, and the site’s configuration will not load Google’s script until the owner has confirmed that setting. Google uses your IP address to estimate where you are; it says it does not log or store the IP addresses of visitors from the EU, Switzerland or the UK (Google’s explanation). How long Google keeps detailed event data depends on the property’s retention setting, which Google offers at 2 or 14 months (data retention). Google describes how it uses this data in How Google uses information from sites that use its services.
| Name | What it is for | How long |
|---|---|---|
_ga | A random number that tells one browser's visits apart from another's. | 2 years, Google's default. Deleted by SVGCS when you turn Google Analytics off. |
_ga_<container-id> | Keeps track of the current visit. | 2 years, Google's default. Deleted by SVGCS when you turn Google Analytics off. |
Changing your mind. Use “Privacy choices” in the footer, which is there whenever Google Analytics is switched on. Turning it off stops all sending at once and deletes the two cookies above. Your answer is kept in your browser as analytics-consent, listed above.
Cloudflare Web Analytics
Cloudflare Web Analytics is not switched on for SVGCS at the moment, and its script does not load. The rest of this section describes what will happen once it is switched on.
Cloudflare Web Analytics is switched on for SVGCS. This section describes what it does.
A small Cloudflare script reports each page view, in every country and without asking, once the page has finished loading and again when you leave it. It sends the page’s address, the address of the page you came from, how long the page took to load at each stage (finding the server, connecting, the request, the response, processing, the first paint), and three measures of how the page felt to use (Largest Contentful Paint, Interaction to Next Paint, Cumulative Layout Shift), each with a short description of the part of the page it measured (load times, Core Web Vitals). Like every request, it reaches Cloudflare with your IP address and your browser’s user-agent string, the text that names your browser and system. The site’s owner sees counts by country, browser, operating system and device type; neither the IP address nor the user-agent string is among them (what the owner sees). It is loaded without a question because Cloudflare says it uses no cookies or other storage in your browser and does not fingerprint visitors (Cloudflare Web Analytics). Cloudflare says it does not record the part of an address after a ?, keeps the full data for 7 days and then keeps about a tenth of it in summary form (Cloudflare’s answers). It is not told anything about your files.
Hosting
SVGCS is hosted on Cloudflare. Every request for a page passes through Cloudflare, which handles your IP address and the details of the request to deliver the page, under its own privacy policy. The site’s own server code keeps no record of visits. It writes a log line only when it fails to answer a request, and that line holds the error, not your IP address.
Ads
There are no ads on SVGCS. If ads are added, this page will say so before they appear, and visitors in the European Economic Area, the United Kingdom and Switzerland will be asked first through a consent tool certified by Google.
Questions about your data
SVGCS keeps nothing about you on its own servers, so there is nothing for it to look up, correct or delete. What the site stores is in your browser, and you can clear it yourself. For data held by Google or Cloudflare, their policies linked above say how to reach them. For anything else, write to the contact named under “Who is responsible”. The Terms and the Licences page cover the rest.
Changes to this page
When what the site does changes, this page changes with it, and the date at the top says when.