The short version: XML you paste into this site is processed inside your browser and is never sent to us. The site sets 0 cookies, loads 0 third-party scripts and runs 0 analytics. This page explains what that means in practice, and the small amount of data any website hosted on the public web necessarily involves.
Data handling at a glance
| Question | Answer |
|---|---|
| Cookies set | 0 |
| Analytics scripts | 0 |
| Advertising scripts | 0 |
| Third-party requests | 0 |
| Upload endpoints | 0 |
| Copies of your XML stored | 0 |
| Accounts | 0 |
| Local storage / session storage keys | 0 / 0 |
| External fonts | 0 |
| Network requests while formatting, validating or minifying | 0 |
| Client-side JavaScript files | 2 |
| Stylesheets | 1 |
| XML bytes sent to a server | 0 |
| Max XML bytes processed locally | 2,097,152 (2 MiB) |
| Clipboard read actions | 0 |
| Clipboard write actions | 1 (only when you press Copy result) |
| Host request-metadata fields | 4 (URL, time, IP address, user agent) |
| Mailing lists | 0 |
| Data sale or sharing | 0 |
What we collect from the editor
0 records. There is no upload endpoint, no logging of editor contents and no database. When you click Format XML, Minify XML or Validate XML, the browser reads the text from the textarea and runs a JavaScript function that was already delivered with the page. The document you paste is never transmitted, saved or associated with you. Closing the tab discards it, exactly as it would with a local text editor.
Where processing happens
All parsing, formatting, minification and validation run client-side in the browser tab. The site is a set of static files: HTML pages, 1 stylesheet, 2 JavaScript files and 1 icon image. There is no application server and no processing queue behind the page. That is also why the tools keep working offline after the page has loaded once, and why the 2,097,152-byte input cap exists: the work is limited by the memory of your own tab.
Hosting and server logs
The site is served by a static hosting provider (Cloudflare Pages). Like any web host, it processes standard request metadata to deliver pages and protect the service from abuse: the requested URL, the time of the request, an IP address and a user agent string — 4 fields. That data is handled under the provider’s own privacy terms, is not linked to the XML you paste (0 bytes of which leaves the browser), and is not used by us to build profiles. We keep 0 access logs and 0 analytics stores of our own.
Cookies, local storage and third parties
This site sets 0 cookies. It writes 0 entries to localStorage, 0 to sessionStorage and 0 to IndexedDB. It loads 0 third-party scripts, 0 analytics, 0 advertising networks, 0 social widgets and 0 external fonts — the stylesheet uses fonts already installed on your system. Every asset needed to render a page is served from this domain: 2 JavaScript files, 1 stylesheet and 1 icon.
Clipboard access
The Copy result button writes the result to your clipboard — 1 action, and only after you click it. The site performs 0 clipboard reads. Browser permission prompts around clipboard access, if your browser shows one, are handled by the browser itself rather than by this site.
If you email [email protected], we receive your email address, your message and anything you choose to attach. That information is used only to reply and to fix what you reported. There are 0 newsletters and 0 mailing lists, so your address is not added to one. Please do not send sensitive XML; a minimal sample that reproduces a problem is enough.
Children, changes and contact
This site is a developer tool and is not directed at children under 13; because the tools collect 0 personal information, there is no special data category to address beyond the 4 host metadata fields above. If the site ever adds a feature that changes these facts, this policy will be updated before that feature ships, and the change will be reflected in the visible “last updated” date.
Questions about privacy can be sent to [email protected]. We usually reply within a few working days.
Frequently asked questions
Is my XML uploaded when I use the formatter?
No. Parsing, formatting, minification and validation all run inside your browser tab. There is no upload endpoint and no copy of the document is stored anywhere.
Do you use cookies or analytics?
No. The site sets no cookies, uses no local storage and loads no analytics, advertising or third-party scripts. All assets are served from this domain.
Does the site work offline?
Once the page and its assets have loaded, the tools keep working without a network connection, because using them makes no requests.
What does the hosting provider see?
Like any web host, the static hosting provider processes ordinary request metadata — requested URL, IP address, user agent, time — to deliver pages and protect the service. It is not linked to the XML you paste, because that never leaves the browser.
Related XML tools
XML Tools
Format, validate and minify XML — the three topic guides in one place.
Open →About
Who runs this site and how the tools are built and tested.
Open →XML Formatter
The main guide: pretty-print XML with 2/4-space or tab indentation.
Open →XML Validator
Check XML and get exact line and column errors in plain English.
Open →