← QuietWeb

Privacy policy

Last updated 29 October 2026.

What QuietWeb processes

QuietWeb examines public page headings, summaries, publisher names, link domains, and nearby text to apply the filtering instructions you choose.

Rule compilation

When you save a natural-language rule, the rule text is sent to the QuietWeb API and its AI provider so it can be converted into structured topics, sources, entities, preferences, and exceptions. Reused rules may be returned from a server-side cache.

What QuietWeb avoids

QuietWeb does not intentionally collect passwords, form entries, private editor content, full link URLs, query strings, or payment card details. Card data is processed by Stripe.

Cloud classification

Cloud classification is optional and available only to Pro users. When enabled, limited public content snippets and link domains required for classification are sent to the QuietWeb API and its AI provider. Requests fail open.

Billing and identifiers

QuietWeb uses an anonymous installation identifier and a random installation credential to enforce usage limits and connect a subscription to one extension installation. The credential is stored by the extension; QuietWeb stores only its one-way hash. Stripe stores billing records and payment details.

Contact

Questions can be sent to support@quietweb.app.