Core handling
Client-Side Processing
JSON inputs, generated code, preview output, and most formatter or converter flows are processed in browser sessions instead of being posted to a remote formatter backend.
Privacy At A Glance
Privacy Policy
This page describes how jsonformatter.store handles data, analytics events, and local browser storage.
Quick Summary
- Processing model: Most formatting and conversion work is designed to happen in the browser session.
- Stored locally: Theme, history, and saved-state conveniences may use local browser storage.
- How to reset: Clear browser storage or reset local histories if you want a cleaner session footprint.
Measurement
Analytics
Analytics events are used to understand product usage patterns and improve stability, performance, SEO surfaces, and UX. The current analytics model focuses on route usage and interaction events rather than raw document payloads.
Storage
Browser Storage
Theme preference, editor history, saved wishlist state, and similar convenience features may use local browser storage so the app can restore your experience between visits.
Control
User Controls
You stay in control of locally stored history and preferences. Clear browser storage, reset local histories, or avoid saving optional state if you want a clean session footprint.
Policy Updates
We may update this policy when features, analytics instrumentation, storage behavior, or integrations change. The canonical policy URL remains /privacy/.
Privacy Questions
If you need clarification about analytics behavior, storage usage, or route-specific handling, use the contact page for a direct support path.