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

Base64, URL encoding, JSON editing, UUID generation, and agent skill building can stay local in the page. Hash generation, JWT decoding, prompt cleanup, and structured output validation currently send request data to ComUtil for processing. IP lookup and Domain WHOIS go further by fetching outside registry or network data.

Open Base64 Privacy Policy
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.
Browser-local workflows
Base64 Encoder/Decoder
Encode or decode payload text locally before you copy or share the result.
URL Encode / Decode Tool
Encode full URLs, decode copied callback links, and escape query parameter values locally in your browser.
JSON Editor
Format, inspect, and clean JSON locally before it reaches another system.
UUID / GUID Generator
Generate browser-local UUID v1 or v4 values, then copy request-ID or fixture helpers without sending the generated IDs back to ComUtil.
Agent Skill Builder
Build a SKILL.md file in your browser without sending draft Markdown to ComUtil.
Server-handled text workflows

These tools stay on ComUtil instead of calling outside registries, but the current implementation still submits the pasted request data to the app for processing.

MD5 & SHA-256 Checksum Generator
Checksum generation submits the pasted text to ComUtil for server-side processing before verification results render.
JWT Decoder
JWT decoding sends the token to ComUtil so the server can parse claims, warnings, and share-safe outputs.
AI Prompt Toolkit
Prompt cleanup and chunking submit the draft to ComUtil for redaction analysis before you move into an external AI workflow.
Structured Output Playground
Contract validation sends the target and sample JSON to ComUtil so the server can compare structure and return issues.
Server-side lookup exceptions

These tools are useful when you need outside registry or network facts, but they are not purely local workflows.

IP Address Lookup
IP lookup sends the queried address to the server so ComUtil can fetch ownership and network data.
Domain DNS & WHOIS Lookup
Domain DNS, WHOIS, and SSL checks send the requested hostname to the server to collect DNS records, registry data, and certificate data. Domain recent history is stored only in this browser for quick repeat lookups.
How to use the boundary
  • Use browser-local workflows when the page can do the job in client-side JavaScript and you want the working text to stay on-device.
  • Use server-handled text workflows when you want ComUtil to parse, compare, or summarize the pasted input without calling outside registry data.
  • Use lookup tools when the value needs WHOIS, DNS, ASN, or certificate data that only exists outside the browser.
  • 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.
Related trust surfaces
About ComUtil
Read the product mission and the practical trust posture behind the browser-first workflows.
Privacy Policy
Review the formal policy for browser-local tools, request handling, cookies, and analytics.
AI Prompt Toolkit
Start with a browser-first prompt cleanup flow before anything moves into an external model.