Home › Terms
Terms of Use
Direct answer: the tools are free to use, run entirely in your browser, and are provided as-is. Repaired, salvaged, and recovered output is a starting point for your own verification — not a guarantee of correctness for production data. The MCP validator checks a file against a published schema version; the registry's decision is final and is not ours to make.
1. The service
JSONSalvage provides browser-based tools for repairing, salvaging, recovering, and validating JSON, together with explanatory guides. The tools run locally on your device; the site does not receive, store, or process your inputs on any server (see Privacy). No account is required and no fee is charged.
2. Your responsibility for output
Repair and recovery transform data. The tools are designed to make every transformation visible (a change report for repair; a recovery note for truncation) and to refuse transformations that would require inventing data. Even so, you are responsible for verifying any output before relying on it — particularly before using recovered or repaired data in production systems, financial records, or safety-relevant contexts. Recovered documents are by definition incomplete; values flagged as suspect in a Recovery Note must be treated as unverified.
3. No warranty
The tools and content are provided "as is" and "as available", without warranties of any kind, express or implied, including fitness for a particular purpose. We work to keep the tools correct — they are checked against a fixed set of test cases covering every rule — but no tool can guarantee that a given input will be repaired, salvaged, or recovered correctly or at all.
4. The MCP validator
Validation results are produced against the bundled official schema version named on the tool page (2025-12-11). A "valid" result means the file conforms to that schema version; it is not certification, endorsement, or a promise that a registry will accept, list, or continue to list any server. Registries authenticate namespace ownership and make their own decisions.
5. Acceptable use
Use the tools for data you own or are authorised to process. Because processing is local, we cannot inspect your inputs — the responsibility for lawfully handling the data you work with rests with you.
6. Changes
Tools, guides, and these terms may change over time. Material changes to how data is handled would be reflected first in the Privacy page — and the architecture commitment stands: tool inputs are processed locally and never uploaded.