Privacy policy

Short version: the file you choose is processed inside your browser tab, and ExportDecode has no code that uploads it. No account, no cookies, no analytics. See the full walkthrough.

Files you analyze

When you drop a file into an analyzer, your browser reads it from disk and the analyzer code processes it in memory inside that browser tab. ExportDecode has no server-side processing and no upload endpoint: the application source contains no fetch, XMLHttpRequest, WebSocket or form submission. The contents of your file are not transmitted to us and are not stored by us.

The analyzer page additionally declares a Content-Security-Policy in its own HTML, with connect-src 'none' and form-action 'none'. Your browser enforces this, so the page is not able to open network connections at all. Because that policy is defined in the page markup rather than by a hosting header, it is worth checking yourself rather than taking our word for it — the privacy walkthrough shows three independent ways to verify it, including an offline test and a network-monitor test.

Closing or reloading the tab discards the data. Clicking “Clear data & start over” discards it immediately and returns the tool to its initial state.

What this promise does and does not cover

We think it is clearer to state the boundaries than to make a broad promise. The claim “your file is not uploaded” describes what ExportDecode does with a file you choose. It is not a claim about everything else that happens on your device or on the network:

What we collect

ExportDecode sets no cookies and writes nothing to localStorage, sessionStorage or IndexedDB. There are no analytics, telemetry, tracking pixels or advertising scripts in the current build, no advertising identifiers, and no third-party embeds. No account, sign-up or email address is required or requested.

There is one ad integration point in the code, AdUnit, which is an inert placeholder: it has no publisher ID and renders nothing. No ad code is loaded today. If advertising is ever enabled, this policy will be updated first, and the Content-Security-Policy will have to be relaxed to permit it — which is precisely why we are stating now that enabling it would change the enforcement described above.

Hosting logs

Like any website, the server or content network that delivers the pages may keep standard technical logs, such as IP address, requested URL, browser type and time. These logs are controlled by the hosting provider and used for security and operations. They cannot include the contents of a file you analyze, because ExportDecode has no mechanism that transmits those contents in the first place.

Files you download or copy

CSV exports, the printed page and the “Copy summary” text are produced on your device when you click the button. The summary line contains only aggregate figures such as totals and counts — never individual rows. What you do with any of these afterwards is up to you, and exports can contain personal information from your original file.

Links to other sites

Guides link to the official data request pages of other services. Those sites have their own privacy policies, and we are not responsible for them. We have no control over what those services do with your export once you download it.

Children

ExportDecode does not knowingly collect information from anyone, including children. Because it collects no personal data, there is nothing for it to hold.

Changes

If ExportDecode ever adds advertising, analytics or optional paid features, this policy will be updated before they launch and will state clearly that your files are not part of them.

Contact

Questions about this policy? Use the contact page.

Related pages