Browser-First Developer Tools Privacy Guide

See which workflows stay in your browser, which ones submit request data to ComUtil, and which lookup tools reach outside services before you paste sensitive text.

Short version
Browser-local today Base64, URL, JSON editor, UUID generation, and agent skill building can operate without sending the working data to ComUtil first.
Server-handled on ComUtil Hash, JWT, prompt toolkit, and structured output submit request data to ComUtil for processing.
External lookup tools IP lookup and Domain WHOIS submit the query so ComUtil can reach registry, network, or certificate sources.
How to use the boundary
  • If the input is sensitive, start with a browser-local tool or redact first, then move into a server-handled or lookup workflow only when it is necessary.
  • Browser-local is not the same as encrypted. Text you paste is still visible to browser extensions and to anyone using the device.
  • Server-handled requests are processed to build the response only. ComUtil does not store the submitted input.
  • Lookup queries reach outside registries, so the hostname or address you check becomes visible to those third parties.