Tool input and output
Every current tool is marked local-only. Its input, parsed values, previews, and generated output stay in browser memory and are not placed in a request, URL, usage event, or database. Each tool page carries a specific privacy note for the data it handles.
Page requests and operational logs
Loading a page necessarily sends ordinary HTTP request information to the site, including the requested path, IP address, response status, referrer when supplied by the browser, and User-Agent. The reverse proxy writes this metadata to size-bounded, rotating operational logs. Local tool input is not part of those requests.
Anonymous aggregate counts
SQLite stores one daily total per tool for page views and tool runs. A run event contains only the registered tool slug and the event name run; it contains no input, output, file name, search text, or browser identifier. These totals determine the popular-tool ordering once there is enough activity to provide a useful signal.
The usage endpoint uses an IP address briefly in server memory to enforce a per-minute rate limit. That address is not written to the aggregate usage database.
Cookies and browser storage
The application stores the selected light or dark theme in localStorage under tool4-theme. It does not use cookies or browser storage for tool input, output, or history. This build does not load an advertising SDK or consent platform and does not set advertising cookies.
Advertising and third parties
Google AdSense is the planned advertising provider. The current advertising areas are empty layout reservations: they do not request ads or contact Google. A seller entry in ads.txt establishes an authorized seller; it does not itself load advertising.
Before live advertising is enabled, this policy must be updated to describe the implemented providers, consent controls, and data handling. Google advertising can involve page URLs, IP addresses, device information, cookies, measurement, and fraud prevention even when ads are not personalized. Read how Google uses information from sites that use its services and the Google Privacy Policy.
Advertising choices and consent
A consent message configured in the advertising account is not a consent interface active on this site. This build has no advertising consent choice to save or withdraw because it does not load advertising services. Before enabling Google ads, the implementation must verify the required certified consent platform for visitors in the European Economic Area, the United Kingdom, and Switzerland, including refusal and reopening settings.
Contact [email protected] with a privacy question. Do not include the private files, tokens, or documents you used in a tool.
If a tool stops being local
A future server-powered tool must say so on its own page before use and explain what is sent and why. A site-wide claim such as “nothing uploaded” will be removed if it is no longer true for every tool.
Policy changes
Material changes will be reflected on this page with a new effective date. The current policy is always available at this URL.