Local tool processing
Text, passwords, conversion inputs, supported PDFs and images are processed inside the browser by the tools included in this build. Those inputs are not sent to an application server for the core operation.
The core rule is simple: a local tool should not quietly turn your input into server data.
Text, passwords, conversion inputs, supported PDFs and images are processed inside the browser by the tools included in this build. Those inputs are not sent to an application server for the core operation.
Third-party ad networks may process device, network and consent information. Advertising is therefore isolated from tool logic and disabled by default until the correct regional consent flow and vendor policy are configured.
When a feature genuinely needs an external resource, the interface says so. For example, currency conversion requests daily reference rates from Frankfurter; DOI and ISBN lookups contact Crossref or Open Library only when requested; and a YouTube thumbnail preview loads a public image from YouTube’s image CDN only after a valid video ID is entered. Other tool inputs stay outside those requests.