SecureDevTools / privacy

Privacy, security & disclosures

Your tool inputs are processed in your browser. This page explains local processing, website traffic, security and commercial disclosures.

Your inputs and outputs

Pasted tokens, generated secrets, JSON samples, configuration text and synthetic datasets are processed in the current browser tab. The tools do not submit those values to our server or place them in page URLs. Inputs are not automatically saved to cookies, local storage, session storage or a database. Reset clears the current tool; leaving the page or closing the tab releases its state through normal browser behavior.

Local files, clipboard and downloads

Images and JSON files you select are read locally and are not uploaded. Copy writes to your system clipboard only when you select it. Download creates a file on your device only when requested. Clipboard history, browser extensions, device backups and downloaded files can retain copies outside this website’s control. Store secrets securely and clear copies you no longer need.

Hosting and network requests

Your browser requests pages, scripts and static assets from our hosting infrastructure and content delivery network. These providers may process IP addresses, browser information, timestamps, requested URLs and security logs to deliver and protect the website under their own policies and settings. Tool values are not included in those requests. Avoid placing sensitive information in URLs.

Browser state and external services

Tool fields stay in memory. The light/dark button saves only your chosen color theme in first-party local storage under toolbox-theme; it never stores tool inputs or results. Each companion site remembers its own preference. Advertising, measurement or affiliate services used on a page may process technical information such as IP addresses, browser details, page URLs and cookies under their own policies and any applicable privacy choices. Tool engines do not pass your inputs or generated output to these services. Links to CleanThisText, documentation and other external websites are governed by those websites’ privacy practices when you visit them.

Security

Secrets use cryptographic randomness provided by the browser. The tools validate input and apply limits to file sizes, JSON nesting and batch generation. Security headers restrict resource loading and embedding. These controls do not guarantee that software is free of defects. JWT inspection does not verify signatures, DNS suggestions do not check live records, and generated policies and schemas need testing in the systems where you use them.

Disclosures

This website may display advertising, sponsored placements and affiliate links. We may earn a commission when you follow an affiliate link and make a qualifying purchase. Labels such as Advertisement, Sponsored or Affiliate identify commercial placements. A paid placement or recommendation does not guarantee that a product is suitable for your needs. Software and platform names describe compatibility rather than certification. The bundled gitignore patterns were independently authored and are available under CC0 1.0; third-party libraries retain their respective licenses.