Your JSON-family contents are processed locally.

Last updated: 16 October 2026

This policy covers JSON File Tools and its JSON viewer and editor desktop app, operated by Shipit Software Limited.

Local file handling

Selected JSON, JSONL and NDJSON files, pasted text, parsed values, edits, searches, and generated outputs are processed on your device. We do not intentionally transmit file names, paths, keys, values, or document contents to our servers or include them in analytics or diagnostics. No account is required for local editing.

Browser-local batch conversion may write temporary results to this site’s private storage on your device. Removing a result clears its temporary copy. Interrupted conversions or downloads can leave temporary files until later cleanup; unused copies older than 24 hours are eligible for cleanup during subsequent conversions. Clear this site’s browser data to remove these local copies. Downloaded files remain until you remove them.

Browser-local recovery

The website may store original selected files and pasted inputs in browser-local IndexedDB to carry them into the app and recover them after a refresh. Recovery records expire after 30 minutes and are cleaned up on later use. Expiry does not guarantee that stored bytes are physically deleted at that exact time. Clear this site's browser data to remove stored records immediately. Back to website and Resume editing keep current edits in the same live tab. Refresh reopens the original input, so download edits before refreshing or closing the tab.

Desktop files and automatic opening

The Windows desktop editor reads files you select or open through Windows. Saving writes to your selected local destination; temporary local files may be used to complete a save. Editing state is held in memory. Closing the app ends that session and does not delete your saved files.

When automatic opening is enabled, a local background helper watches your Windows Downloads folder for new supported files. File detection, names, paths, and file contents remain on your device. The app stores its automatic-opening preference locally. You can turn automatic opening off in the app and control sign-in startup through Windows Startup settings.

Website requests and analytics

Loading pages, policies, scripts, styles, and the favicon sends ordinary request information to Cloudflare, such as IP address, browser details, requested path, time, and security signals. Cloudflare hosts and protects the website. Website requests are used to deliver and secure it and diagnose availability. The website does not currently set analytics cookies, create advertising profiles, or run product analytics.

The Microsoft Store badge loads from get.microsoft.com and sends ordinary browser request information to Microsoft. Choosing to install may fetch an installer from Microsoft. Your JSON file contents are not sent with these requests.

Desktop analytics and diagnostics

Release desktop builds send limited app-start analytics to PostHog and application lifecycle and unexpected error diagnostics to Sentry to measure aggregate activity and improve reliability. Reports contain app and technical metadata such as app name, version, platform, build environment, and sanitized error categories or stack information. Document-bearing messages, names, paths, contents, and contact details are excluded. Debug builds do not send production telemetry; locally signed release builds can.

Analytics uses a random identifier for this app installation stored in local webview storage and a fresh random session identifier held in memory for each launch. Neither identifier comes from an account, hardware, operating-system identity, or document. If local storage is unavailable, analytics uses an explicit session identifier instead. PostHog person-profile creation is disabled.

PostHog and Sentry receive ordinary network information, including IP addresses, when reports are sent. The configured desktop collection endpoints are in the United States. PostHog can retain IP addresses and derive approximate location from them; this does not request your device's precise location. Random identifiers and disabled person profiles do not make these reports anonymous.

Retention and controls

The installation identifier remains in local app storage until that storage is cleared; a later launch may create a new identifier. Clearing it does not erase reports already received. Session identifiers and editing state are held in memory. The current desktop editor has no in-app analytics opt-out. Operating-system network controls can restrict connections; failure to deliver telemetry does not prevent local document editing.

We retain technical, analytics, and diagnostic records as reasonably needed for reliability, security, and legal obligations, subject to service-provider retention controls. Cloudflare, PostHog, and Sentry may also retain information under their own operational policies. No fixed retention period is promised here.

Security, contact, and changes

Local processing limits exposure, but no software or network service is risk-free. Keep backups and check saved outputs. For privacy questions, use the contact route described on our support page without including private document contents or credentials. Connected Loam services have their own data-handling information.

We may revise this policy as the utility changes. The date above identifies the current version. Use is also subject to the Terms.