Privacy Policy

Tool input

HAR files, JSON, YAML, schemas, regular-expression test strings, and pasted text are processed locally. The site does not upload or store that content on a backend.

AI-ready context is generated locally from the current result. The site does not call an external AI API.

Chrome extensions: local processing

JSON Unescape processes text you paste, escape and unescape options, decoded results, and diagnostics locally in the extension tab. Chmod Calculator processes permission values, comparisons, and an optional path used to compose a command. It does not inspect your filesystem, change file permissions, or execute commands.

The core extension tools work offline and do not require an account. They do not automatically read your browsing history, cookies, other web pages, or clipboard. Copy buttons write to the clipboard only when you choose to copy. Preparing an AI-ready context also happens locally; no content is sent to an AI provider by the extension.

The extensions contain no analytics or session-replay trackers and do not upload your tool input or output to our servers. We do not sell this content or use it for advertising or profiling. These statements concern the extensions; visiting the companion website is covered by the website analytics section below.

Optional continuation on Developer Tooling Hub

Only when you click the optional Continue action does the extension open the matching page on https://developertoolinghub.com and make your working state available to that page through Chrome extension messaging. You do not need to use this action to process or copy a result inside the extension.

For JSON Unescape, the shared state contains your pasted input, the selected escape or unescape mode, and the applicable formatting or layer options. For Chmod Calculator, it contains the selected calculation or comparison mode and the permission values; the optional filesystem path is not included.

The receiving page is restricted to the matching tool path on developertoolinghub.com. The URL fragment contains the extension identifier and a random, single-use token, not the JSON input or filesystem path. The website reads the working state into its browser-side tool; this handoff is not an upload of the input to our backend.

Opening the website makes a normal web request and brings its analytics and browser-storage behavior into scope. Technical continuation events may describe the tool and whether continuation succeeded, but must not contain your input, output, or the handoff token.

Extension storage, retention, and your controls

During the core workflow, working input and results remain in the open tool page rather than a persistent extension history. The selected color theme is stored in local browser storage. You can clear the input with the tool controls, close the tool tab, and remove stored preferences through browser controls. Content you intentionally copy to the system clipboard is managed separately by your operating system and clipboard settings.

For optional continuation, the extension temporarily stores the selected state in Chrome storage.session on your device. A handoff token is valid for 120 seconds and can be used once. The stored record is removed when successfully retrieved, or when an expired record is requested. Expiration alone does not trigger immediate deletion: an unused record may remain in session storage until Chrome clears that session storage. This is not a persistent history or an account-based cloud record.

After continuation, the website tool holds the received state in the browser. Clear the tool input or close its page to stop working with that state. Closing the extension tab alone does not delete an unused handoff record or content already copied into a website tab or clipboard.

The storage permission supports this temporary handoff. The extensions do not request access to all websites or permission to read browsing history. External messages are accepted only for the matching DTH tool page and a valid handoff token.

Analytics

Google Analytics and Yandex Metrica receive only technical usage events such as the tool identifier, action, success or broad error type, page path, and coarse size or duration buckets. They do not receive tool input, result content, filenames, URLs from captures, headers, cookies, tokens, schemas, or pasted text.

Yandex Session Replay records interactions with the public site interface and embedded tools. Text entered into fields and generated content that may repeat user data are masked or hidden, while safe interface controls such as buttons, tabs, and navigation remain visible in recordings.

Local preferences

Theme choice and supported tool preferences may be stored in browser storage on your device. You can clear them using your browser controls.

Privacy questions

Contact support@developertoolinghub.com with questions about this policy or either extension. If you contact us, we receive the email address and content you choose to send and use them to respond. Do not include passwords, access tokens, or sensitive tool input in a support request.