Privacy
How jsonformatters.org handles editor data, browser storage, URL imports, sharing, and optional advertising.
Editor data
Formatting and conversion run inside your browser. The public application does not send pasted editor content to our server. Do not enable third-party browser extensions you do not trust.
Local storage
Tool settings, mode, output view, and pane size are stored in this browser profile. After you edit a tool, its input is also saved locally so it survives a return or refresh. The always-visible Clear saved data toggle keeps current work in memory but removes that tool's saved input and settings on refresh or tab close; the toggle selection itself remains saved. Browser storage is not sent to our server.
Imports and encoded links
URL import contacts only the address you enter and requires that server to permit CORS. Share links contain URL-safe encoded data; they are not encrypted and may be visible to browser history, clipboard tools, and extensions.
Advertising and consent
Optional advertising is disabled until consent. When configured, ads render outside the editor in a sandboxed cross-origin frame and never receive editor values from this application.
Diagnostics and consent
Essential failures may send privacy-filtered error details and server traces to Sentry. Optional browser traces, error Replay, profiling, logs, and metrics load only after analytics consent and while Global Privacy Control is off. When enabled, normal tool telemetry contains only tool, action, status, and coarse duration and input-size buckets—never exact values. We exclude editor input and output, drafts, user identifiers, request bodies and headers, cookies, URL queries and fragments, breadcrumbs, and console output. Replay masks all text and inputs and blocks media and the complete editor workspace. Sentry screenshots, attachments, and feedback UI are disabled.
Tool reports
A report is sent only after you submit the report form. The submitted summary, details, expected behavior, optional contact email, and public tool metadata are delivered to our admin inbox through our email provider; editor input and output are never attached. Short-lived, one-way identifiers are kept in Redis to limit abuse. Report emails are retained only as long as needed to investigate and respond.