This policy explains how PagesTools handles information when you browse the site or use a tool. The central design choice is simple: processing stays in your browser whenever the task does not require an outside network request or a server-only program.
Browser-processed tools
Tools labeled “Runs in your browser” perform their work on your device. Their text, values, or files are not uploaded to the PagesTools application server for processing. Closing or refreshing the page clears in-memory tool state unless your browser itself retains a form value, download, or cached resource. A downloaded result is saved wherever your browser normally saves files.
The privacy notice on a tool page describes the processing mode for that tool. A file tool that says files are processed in the browser does not silently switch to an upload workflow. If browser support is insufficient, the tool should explain the limitation instead of sending the file elsewhere without notice.
Server-assisted tools
Network checks and tools that need system software send the submitted value or file to the PagesTools server. The server uses it to perform the requested operation, enforces input and time limits, and returns the result. Temporary files are intended to be removed after the request completes, including error paths. Do not submit confidential material unless the tool page and your own requirements make server processing appropriate.
Public-website checks request the destination you provide. That destination can observe the PagesTools server address, timing, and ordinary request details. Private, loopback, link-local, and reserved network targets are blocked. Email-domain validation checks syntax and DNS mail records; it does not log in to a mailbox or prove that a person owns an address.
Operational information
Hosting and reverse-proxy systems may record standard technical information such as an IP address, request time, path, response status, user agent, and error details. These records are used to keep the service reliable, investigate abuse, and diagnose failures. Avoid placing passwords, API keys, personal records, or private tokens in a URL because URLs can appear in browser history and infrastructure logs.
Cookies, analytics, and advertising
PagesTools does not require an account and the application does not set a cookie for an ordinary anonymous page response. Google Analytics is included only when a deployment explicitly supplies a GA measurement ID. Advertising placeholders render only when advertising is explicitly enabled. If either service is enabled, its provider may process information under its own terms and the deployment should present any consent controls required by applicable law.
Contact messages
If you email PagesTools, the message, sender address, and any details you include are processed so the request can be answered. Send only the minimum information needed to explain the issue. Do not attach a private source file merely to demonstrate a tool problem; a small synthetic example is usually safer and easier to reproduce.
Your choices and policy changes
You can use browser tools without providing an identity, decline optional analytics through browser or consent controls, and avoid server tools when local processing is required. Material changes to this policy will be published on this page with updated wording. Questions about a specific tool’s data flow can be sent through the contact page.