Privacy Policy
Last updated
This policy describes how the SVG Viewer site handles data as it works today: the SVG files and code you open, share links, downloads, feedback and analytics.
Short version
- SVG files, folders and .zip files you open or drop, and code you paste, are read and drawn by your own browser. They are not uploaded to my server, to analytics or to anyone else.
- When you open an SVG from a web address, your browser asks that site for the file directly. If that doesn't return an SVG, the address passes once through this site's server, which fetches the file and keeps nothing (the host's request log may record the address).
- A share link carries the SVG inside the link, after the
#sign, which browsers never send to a server. Anyone with the link can see the SVG. - I count page views and feature use with my own analytics under a random ID. It never includes your SVG code, file names or anything you type. You can turn it off on this page, and browsers that send Global Privacy Control are never counted.
- A feedback message is stored only if you write one and press send.
- The site sets no cookies of its own. I don't sell or share personal information, and I don't use it for advertising.
Who runs the site
SVG Viewer is run by one independent developer, not a company (“I” and “me” in this policy; see About). I decide what the site collects and why, so I am responsible for that data. To contact me about privacy, including any of the requests under “Your rights”, use the Give feedback button on the contact page. There is no public email address.
What is collected at a glance
| What | Where it is kept | Why | How long |
|---|---|---|---|
| The SVG code and file name you are looking at, and the version you first opened (single-file view only), plus the number of gallery files open (a number only) | Your browser's session storage, this tab only | So a reload doesn't lose your work | Until you close the tab |
| An SVG in a share link | Inside the link, after the # sign | So the link reopens the same SVG | As long as the link exists wherever it was pasted |
| A web address you open with From URL (only when the other site blocks direct downloads) | Passes through my server; may appear in host request logs | To fetch that one SVG for you | Not stored by me; host log retention applies |
| Analytics events (page, feature, outcome, random IDs) | My analytics database on Supabase | To see what people use and what fails | Reviewed for deletion at least once a year |
| Feedback message, website hostname, page path | My feedback database on Supabase | To read and act on your message | Until dealt with; reviewed at least once a year |
| IP address for the feedback limit | The feedback service on Supabase | To cap messages at 10 per hour | Only for the rate-limit check |
| Request logs (IP address, browser, time, address requested) | The hosting provider and Supabase | Delivering pages, security, fixing faults | Each provider's log retention |
Files and code you open
Drawing, checking, fixing, editing, formatting, optimizing and exporting all run inside your browser. When you press Open files, drop files, a folder or a .zip on the page, or paste code into the editor, your browser reads them on your device. Zip files are unpacked in the browser too. None of this content is uploaded. Pictures are drawn from temporary addresses (blob URLs) that exist only in that browser tab and disappear when you close it.
The preview draws each SVG the way a web page draws an image, so scripts inside a file never run and the file can't fetch anything from other servers. Optimize uses SVGO, which is bundled into this site and runs on your device.
So that a reload doesn't lose what you were working on, the code in the single-file view, its file name and the version you first opened (so Revert still works) are saved in your browser's session storage under the key svg-viewer:last. Files above about 2 million characters are not saved at all, and files opened from a gallery are never saved; only the number of gallery files is kept, under svg-viewer:gallery, so a reload can say why the gallery is gone, and it is deleted on that reload. Session storage belongs to the one tab and is deleted when you close it. The built-in samples are not saved.
Opening an SVG from a web address
From URL first turns a GitHub or GitLab page link (…/blob/…) into the address of the raw file, so the request goes to raw.githubusercontent.com or the GitLab raw address rather than the page you pasted. It then asks the site that hosts the file for it, straight from your browser, without telling it which page you came from (no referrer). That site sees an ordinary request from your browser. If that request doesn't return an SVG (most often because the site doesn't allow other websites to read its files, but also when it answers with an error or something else), the address goes to my server (/api/fetch?url=…), which:
- refuses addresses that point to private or local networks, such as localhost or a home router, including after redirects;
- fetches the file once, identifying itself as
Mozilla/5.0 (compatible; SVGViewer/1.0; fetches one SVG file on request), and follows up to 5 redirects; - gives up after 12 seconds and stops reading after 5 MB;
- returns the SVG to your browser and does not store it.
The other site then sees a request from my server, not from your device. My hosting provider's request logs may record the address along with the request. Don't open addresses that contain private tokens. The address itself is never sent to analytics.
The icon library
The Icons button loads the icon list and the icon files from this site's own server (files under /icons/). Searching happens in your browser; what you search for is not sent anywhere. The icons come from Tabler Icons (MIT license) and Lucide (ISC license).
Share links
Copy link compresses the current SVG and writes it, with its file name, into the link after the # sign. Browsers don't send that part of an address to a server, so neither reaches my server; whoever opens the link sees the SVG and the file name. Links longer than about 12,000 characters (the SVG is compressed first, so this depends on the file) are refused with a message, because long links break in chat apps.
Anyone who has a link can see the SVG. There is no password and no way for me to revoke a link, which lasts wherever you paste it: chat apps, email, documents and the browser history of everyone who opens it. When a share link is opened, the page removes the SVG part from the address bar; the original link may still be in the browser history.
Downloads and copying
Download SVG, PNG (including the one-click Download PNG button), JPG, WebP and ICO files, the favicon set, and the gallery's Export all as PNG (.zip) and SVGs (.zip) are all made in your browser and saved straight to your device. Copy as SVG markup, data URI, base64, CSS, <img> tag, React component or React Native component puts text on your clipboard. None of these send your SVG anywhere.
Feedback you send
The Give feedback button opens a short form. Nothing is sent while you type. Only if you press send, these details go to my feedback service, which runs on Supabase, and are stored so I can read and handle the message:
- the message you wrote, exactly as you wrote it;
- this website's domain and the path of the page you were on, without any query string or
#part (so the SVG in a share link is never included).
The form doesn't ask for your name or email. If you want a reply, include a way to reach you in the message; I will use it only to answer you. To limit spam, the feedback service allows up to 10 messages per hour from one network, so it processes your IP address to apply that limit. Please don't include passwords, keys, payment details or other sensitive information in a message. If an SVG misbehaves, describe it or paste a small, non-private piece of the code.
Analytics
I run my own analytics service, hosted on Supabase, to learn which features people use and where the site fails. It is not Google Analytics and it is not shared with any advertising network. It records:
- page views, with the page path only (nothing after
?or#); - time on the page and how far you scrolled;
- clicks on labelled buttons and controls (for example Open files, Optimize, Outline, an export format);
- the outcome of a feature, with its name and sometimes a short code or a number: a file opened (and how many files for a gallery), a share link opened or copied, an export or copy that worked or failed (with a reason code such as “draw_failed” or “size_mismatch”), and whether Optimize was applied or held back (“visual_change”);
- a random visitor ID, a random session ID and the time.
It never records the text you type or paste, including SVG code. It does not record your SVG files or any part of them, file names, colors, sizes, your name, your email or anything else that identifies you, and it doesn't store your IP address as a way to identify you. The visitor ID is kept in your browser's local storage and the session ID in session storage, both under keys starting with wa_. They are random, are not linked to any account and are not used on other websites.
The analytics script is loaded from my Supabase project on every page, so Supabase receives your IP address and browser details when your browser fetches the script, as any web server does, even if you have turned analytics off. There is no consent banner: analytics is limited to the items above, is used only to improve this site, and can be switched off here at any time.
Turning analytics off stops all events and deletes the wa_ IDs from this browser. Your choice is saved in local storage under svg-viewer:analytics-off, so it applies only to this browser on this device. If you clear this site's data, the choice is cleared too and you would need to turn it off again.
Cookies and browser storage
The site sets no cookies of its own. It uses your browser's storage as listed below, and you can clear all of it in your browser's settings for this site. One third-party cookie can appear: when the analytics script is fetched, Cloudflare (which sits in front of Supabase) may set __cf_bm on the Supabase domain to tell browsers from bots. It expires after about 30 minutes and is not readable by this site.
| Key | Type | Purpose |
|---|---|---|
svg-viewer:last | Session storage | The SVG code, file name and first-opened version in the single-file view |
svg-viewer:gallery | Session storage | How many files the open gallery has (a number only), deleted on the next load |
svg-viewer:analytics-off | Local storage | Remembers that you turned analytics off |
wa_… | Local storage | Random analytics visitor ID |
wa_… | Session storage | Random analytics session ID, deleted when you close the tab |
Hosting and server logs
The site is hosted on Vercel. The servers that deliver its pages receive technical information with every request, such as your IP address, browser type and version, the address requested and the time. Because share links keep the SVG after the #, those requests don't include it. The host may keep this in short-lived logs for security, abuse prevention and troubleshooting. I don't combine those logs with analytics or feedback. The site's fonts are bundled and served from its own domain, so your browser doesn't contact Google Fonts or a content delivery network for them.
Service providers and transfers
Two service providers process data on my behalf, only for running this site:
- Vercel: hosting, delivery of the pages and running the server code that fetches an SVG from a web address when needed.
- Supabase: the databases that store analytics events and feedback messages, the feedback rate limit, and the server that delivers the analytics script.
These providers may process data in the United States and in other countries where they or their sub-processors operate. Where the law requires it, such transfers rely on the providers' standard contractual safeguards.
Why the data may be used
If you are in the European Economic Area or the United Kingdom, the legal bases I rely on are:
- Providing the feature you asked for when a web address has to be fetched by my server: the address has to reach the server for it to fetch the file.
- Legitimate interests for analytics, server logs and the feedback limit: understanding how the site is used, fixing faults and keeping it safe from abuse. I keep this light by never recording your files, by honoring Global Privacy Control and by offering the switch above.
- Your choice to contact me for feedback: a message is stored only because you sent it, and it is used to read and answer it.
Sharing and selling
I don't sell personal information, rent it or share it for targeted advertising, and I don't combine it with data from other sources. Apart from the service providers above, I would disclose information only if the law required it, to protect the site or its users from fraud or abuse, or as part of a transfer of the site to a new owner, who would stay bound by this policy for data collected under it.
How long data is kept
- The current SVG and the analytics session ID: until you close the tab.
- SVGs fetched through my server: not stored by me at all.
- The analytics visitor ID and your opt-out choice: in your browser until you clear this site's data.
- Share links: as long as the link exists wherever it was pasted; I never receive a copy of the SVG in one.
- Analytics events: only as long as they help me improve the site, reviewed for deletion at least once a year. There is no automatic deletion schedule. I may keep totals with no IDs in them, such as page views per day, for longer.
- Feedback messages: until they have been dealt with, and reviewed for deletion at least once a year.
- Hosting and provider logs: according to each provider's retention period.
Security
The site is served only over HTTPS. SVG files are drawn as images, which browsers sandbox: scripts and event handlers in a file don't run and outside resources aren't loaded. Analytics events and feedback are written through narrow interfaces that accept new records but don't let a visitor read anyone else's data, and access to the stored data is limited to the person who runs the site. No system is perfectly secure, which is one more reason not to put secrets in SVGs you share.
Your rights
Depending on where you live, for example under the GDPR, the UK GDPR or US state privacy laws, you may have the right to ask whether I hold information about you, to get a copy of it, to have it corrected or deleted, to restrict or object to how I use it, and to withdraw a choice you made. You won't be treated differently for using these rights.
To make a request, use the feedback form and say what you want. Because I don't collect names or accounts, I can usually only find a feedback message if you tell me roughly what it said and when you sent it, and I can only find analytics events if you give me the visitor ID from your browser's storage (the wa_ key). Turning analytics off is the quickest way to stop further collection. Anything kept only in your browser you can delete yourself by clearing this site's data. I act on requests within one month; include a way to reach you if you want a written answer. If you are in the EEA or the UK, you can also complain to your local data protection authority.
US state privacy laws
In the past 12 months I have collected, as described above, internet activity on this site (analytics events and server logs) and the content of feedback messages people chose to send. I have not sold personal information or shared it for cross-context behavioral advertising, and I don't use or disclose sensitive personal information. Residents of California and other states with similar laws can make the requests described under “Your rights”.
Global Privacy Control and Do Not Track
If your browser sends a Global Privacy Control signal, the analytics script doesn't record anything and there is no setting to change. There is no common standard for responding to the older Do Not Track signal. I don't track you across other sites, so there is nothing for it to switch off, and you can still turn analytics off above.
Children
The site is a general-audience tool for viewing SVG files. It is not aimed at children, and I don't knowingly collect personal information from children under 13 (or under 16 in the EEA and the UK). If you believe a child has sent me personal information in a feedback message, tell me and I will delete it.
Links to other sites
The home page links to reference pages on MDN and the W3C, and the icon library links to Tabler Icons and Lucide. Those sites have their own privacy policies; nothing about your visit here is passed to them beyond what any link click sends.
Changes to this policy
I will update this page, and the date at the top, whenever the way the site handles data changes. If a change means collecting something new, it will be described here before it starts. Questions about this policy can go through the contact page.