Privacy first

Privacy by architecture

The core rule is simple: a local tool should not quietly turn your input into server data.

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.

Advertising is a separate boundary

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.

Network-optional features are labelled

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.

Policy in practice

Product privacy rules

  • Do the work locally when modern browser APIs make that practical.
  • Never describe a network-backed feature as fully local.
  • Do not require an account for the core utility workflow.
  • Keep advertising and analytics outside the data path of the tool input.