Home › Privacy
Privacy
Direct answer: your JSON is processed locally in your browser — on your own device — and is never uploaded, stored, or transmitted by any tool on this site. There are no accounts. You do not have to take this on trust: the section below tells you how to verify it in under a minute.
How processing works
When you paste text or drop a file, your browser reads it locally — the same way it opens any file in a web page — and the page itself does the work: it computes the repair, salvage, recovery, or validation right there in the tab and shows you the result. The heavy lifting runs apart from the part of the page you interact with, so the tab stays responsive on big files. No step involves a network request carrying your input, because there is no server waiting to receive it — everything a tool needs arrives with the page, and the tools keep working even if you disconnect after the page has loaded.
Verify it yourself
- Open your browser's developer tools and go to the Network tab.
- Paste or drop the most sensitive payload you are comfortable testing with, and run any tool.
- Watch the request list while the tool runs: you may see the page's own usage-statistics requests (Google Analytics — see Usage statistics below), but no request carries your input anywhere — your payload appears in none of them, and the result is computed without a single upload.
If you prefer, disconnect from the network after the page loads: the tools keep working, because everything they need is already on your device.
What this site does and does not collect
- Your payloads: never collected, never stored, never logged — by architecture, not just by policy. Downloads (repaired files, reports, recovered files) are generated in your browser and saved by your browser.
- Cross-tool transfer: when you send text from one tool to another on this site, it passes through your browser's session storage and is cleared when read. It never leaves the tab's origin storage on your device.
- Usage statistics: page visits are counted with Google Analytics — what it collects, and what it never receives, is set out in Usage statistics below.
- Advertising: not connected. If it is connected in future, ads will never be placed inside the tool workspaces and will never see your data.
- Contact email: if you write to us, your message is handled as ordinary email. Do not send credentials or personal data — a redacted sample or a Repair Report is enough (see Contact).
Usage statistics
This site uses Google Analytics to count visits and see which pages and tools are useful. It records anonymous page-view and usage data — the pages visited, approximate location, device and browser type, and how a visitor arrived at the site — and it sets cookies in your browser so a repeat visit can be told apart from a first visit. Google processes that data and reports it back to us in aggregate.
The boundary is absolute: Google Analytics never receives the text you paste, type, or drop into a tool. Nothing you put into a tool is sent to Google Analytics or to anywhere else — the statistics describe page visits only, never payloads, file names, or results. You can block analytics cookies in your browser settings, or install Google's opt-out add-on, and every tool will work exactly as before: the tools do not depend on the statistics in any way.
The caution this architecture cannot remove
Local processing protects your data from us. It cannot protect it from your own environment: a compromised browser extension, a shared machine, or a screenshot can expose a payload regardless of where it was processed. Handle sensitive JSON — keys, tokens, personal records — with the same care here as anywhere else.