Your rules stay in your browser.

What we process locally

The validator and rule diff use the browser's File APIs and local JavaScript. The content you paste or open is held in the page's memory while the tab is open. It is not sent to CleanWeb's server and is not stored in a database by this application. The app does not write these inputs to cookies, localStorage, or IndexedDB.

The generator reads CleanWeb's own static rule snapshots from the same origin. It assembles the chosen output format in the browser and verifies the result with the same local parser used by the validator. What you download is created on your device.

What the server sees

CleanWeb is deployed as a web application. The hosting provider may keep standard HTTP request logs containing information such as an IP address, user agent, requested URL, and timestamp. CleanWeb's application code does not use those logs to profile visitors, and no analytics service is embedded. The operator who deploys this build controls log retention and should disclose their own hosting practices.

There is no user account system, no sign-in, no email collection, and no contact form in this build. The app does not set advertising cookies or load third-party tracking scripts.

Files and clipboard access

• Uploaded files are read only after you choose them. The app does not inspect other files on your device.
• Inputs are treated as untrusted text. They are parsed with fixed size and line limits; they are never executed as code.
• When you click Copy, the app writes the selected configuration to your system clipboard. It does not read the clipboard.
• The Download action creates a local file using a browser blob URL. CleanWeb does not retain a copy.

Third-party requests

The app self-hosts its fonts and does not use third-party analytics, advertising, or embedded media. Source links to The Block List Project open only if you click them. The source rule snapshots themselves are served from this site, so generating a file does not contact the upstream project from your browser.

Following an external link takes you to a site with its own privacy policy and practices. CleanWeb cannot control those sites.

URL checking is not a feature

This version does not submit URLs to the server for checking. If a future version adds server-side URL analysis, it will require a clear, separate design and consent flow. Any such feature must restrict protocols, validate and re-check resolved addresses to prevent SSRF, block local and private network targets and metadata endpoints, cap redirects and request time, and avoid sending user-submitted rules or sensitive data to third parties without explicit permission.

Data sharing and retention

CleanWeb does not sell personal information, does not run advertising auctions, and does not maintain a user profile. The app database does not exist. Any temporary file you create remains under your control in your Downloads folder or clipboard.

If you deploy CleanWeb yourself, you are responsible for your hosting logs, your domain, and any local modifications you make to the application.

Changes

This policy describes the current static version. Material changes to data handling should be reflected here with a new version or date. Continuing to use a modified deployment is subject to that deployment's own notices.

Questions

This build does not provide a contact address or account channel. Privacy questions about this deployment should go to the operator who hosts it. For the source code and data notes, see the About page and the Sources page.