Privacy policy
The main principle is simple: our application does not send your tool contents out of your browser.
Last updated: November 4, 2026.
Tool data
JSON, JWT secrets and keys, Base64 text and files, IP addresses and QR content are processed locally. The application does not send these values to an API, store them in a database or include them in URLs. JWT secrets and keys are never persisted. The exception is JSON import by URL that you explicitly request: the editor performs a single GET request only to the address you specify, and the response is also processed in your browser. JSON editor settings are stored locally in the IndexedDB of your browser and are never sent to the server.
Browser settings
Theme and advertising consent are stored in localStorage. Some working data may temporarily use sessionStorage for the current tab to survive an accidental refresh; Clear removes it. You can also clear site data in your browser settings.
Technical logs
Hosting infrastructure may record standard HTTP request data such as IP address, time, requested path and user agent. We do not add tool contents to those paths.
Web analytics
Yandex.Metrika is used to measure traffic: it receives the page address, technical data and its own cookies. The session replay of Metrika masks input field contents by default — values typed into the tools (JSON, tokens, secrets, files) never appear in recordings; we do not enable field-content recording and do not mark any field as recordable. A content blocker can disable analytics without affecting the tools.
Advertising and cookies
Third-party advertising scripts do not load while advertising configuration is empty. If Yandex Advertising Network or VK ads are enabled, scripts load only after consent. These providers may use cookies and receive technical data under their own policies. Declining does not limit the tools.
File safety
Do not run decoded files from untrusted sources. The Base64 tool does not execute them, but it is not a substitute for antivirus scanning.