Privacy Policy
XML Viewer · updated 27 August 2026
The short version
XML Viewer collects nothing. There are no accounts, no analytics, no crash reporting and no server of ours for anything to be sent to. The documents you open are read inside your own browser, drawn on the screen, and gone when the tab closes.
Nothing is sold, shared with anyone, or used to advertise to you, because nothing is gathered in the first place.
What is stored
Only your own settings: theme, text size, how many levels are open when a document loads, which view opens first, whether XML served as plain text should be handled, whether documents with a stylesheet should be taken over, and the list of sites you have asked the extension to leave alone.
These live in Chrome’s extension storage. If you have Chrome sync switched on, Chrome syncs them between your own signed-in browsers, exactly as it syncs your bookmarks — that is between you and Google, and we never see them. Removing the extension removes them.
What it reads, and where that goes
When you open an XML document, the extension reads that document in order to draw it: element names, attributes, text, the lot. It is the same file your browser already downloaded because you asked for it. It is parsed in the tab, rendered in the tab, and never written anywhere, never queued, never uploaded.
The extension makes one kind of network request, and only in two situations: showing you the original bytes of the document, and quoting the failing line when a document does not parse. In both cases it re-reads the very same address you are already on, normally straight from the browser cache. It never requests anything else, from anywhere.
Why it asks for every site
XML can be served from any address, and there is no way to know in advance which page will turn out to be an XML document — so the extension has to be allowed to look. What it actually does on load is check the document’s content type and stop immediately if it is not XML.
On ordinary pages it does nothing, reads nothing and leaves no trace. If you would rather it never woke up on a particular site — an intranet, a client’s admin panel — add the domain to the exclusion list in its settings and it will not run there at all.
What is never collected
- Browsing historyNo record is kept of which pages you visit. The list of excluded sites is one you typed yourself, not one the extension observed.
- Document contentsWhat is in your feeds, sitemaps and exports never leaves the tab. Copying and downloading happen only when you press the button yourself.
- Anything identifying youNo name, no email address, no account, no installation identifier, no advertising identifier. There is nothing to attach to a person.
- UsageWhich features you use, how often you open it, what you searched for — none of it is measured or transmitted.
Third parties
There are none. The extension bundles all of its own code — no libraries fetched at runtime, no fonts from a CDN, no remote configuration, and no code evaluated from a string. What you install is the whole of what runs.
Your rights
Under the GDPR and Turkey’s KVKK you may ask what is held about you, ask for it to be corrected, or ask for it to be deleted. In this case the honest answer is that nothing is held: your settings are on your own machine and you can clear them yourself by removing the extension. If you would like that confirmed in writing, or have a question this page does not answer, write to hello@madeit.ist.
Changes
If what the extension does with data ever changes, this page changes with it and the date at the top moves. There is no version of this policy that is more current than the one you are reading.