# Quietwall Privacy Policy
Effective date: September 27, 2026 (Quietwall 1.3.0)
Quietwall is a Chrome extension whose single purpose is to reduce unwanted, privacy-invasive, and risky web traffic and related page nuisances while giving the user visible controls and breakage recovery.
## Developer collection and use
Quietwall has no developer-operated analytics, telemetry, or data server. It does not sell, share, or use user data for advertising, profiling, credit, insurance, lending, employment, or an unrelated purpose. It contains no remotely hosted code and does not download remote filter updates.
Quietwall does not send browsing data to Quietwall or its developer.
## Quietwall Pro payments (optional)
Quietwall is free to use without an account. Quietwall Pro is an optional paid subscription with a free trial. Checkout, trials, sign-in and receipts are handled by ExtensionPay (https://extensionpay.com) with Stripe as the card processor; Quietwall and its developer never see card details.
- ExtensionPay learns your email address only if you start a trial, subscribe, or restore a purchase on its pages.
- To check your plan, Quietwall sends ExtensionPay an anonymous key that ExtensionPay issued to this installation. The key is created only when you first open a checkout, trial, or restore page. Plan checks never include the pages you visit.
- Opening the Pro page loads ExtensionPay's public price list.
- ExtensionPay's client stores its key and your plan record (including the email you gave it) in Chrome's extension storage, which Chrome may sync to your Google account if Chrome sync is on.
See ExtensionPay's site for how it handles the email and payment records it holds.
## Information processed on the device
To perform its blocking, Pro protections, and user-requested tools, Quietwall may process locally:
- page URLs, domains, request URLs, request types, blocked-request events, and Chrome rule-match records;
- DOM selectors, visible control labels, consent-banner buttons, popup-opening gestures, click targets, attempted destinations, and navigation classification;
- supported video-player response data used to remove ad descriptors;
- canvas, WebGL, audio, WebRTC, advertising-API, and related browser-API calls used by fingerprinting defenses;
- the address of each top-level page you open, checked against a packaged brand list by the Pro look-alike shield; and
- a current or pasted link used by the link-cleaning tool.
Consent-banner handling (Pro) presses a refusal control on the page and records only which consent platform it recognized. The look-alike check, link cleaning, and quiet hours run entirely in the browser.
## Information stored locally
Quietwall stores in Chrome's local extension storage:
- enabled protection settings and Pro settings;
- Standard, Strict, or Trusted site modes and temporary pauses;
- personal block and allow domains, element-hiding selectors, and custom filters;
- quiet-hours sites, schedules, and the current session;
- up to 50 recent domain-level inspection summaries and aggregate counters;
- a privacy report of blocked-request counts per day, by site, blocked host, and tracking company, kept for 35 days (can be turned off, which deletes it); and
- the plan record from ExtensionPay described above.
Quietwall does not intentionally store page contents, form values, passwords, payment information, personal communications, or full browsing history.
## Settings sync (Pro, optional)
If you turn on sync, Quietwall copies its settings (protections, site modes, rules, selectors, custom filters, quiet-hours configuration) to Chrome's sync storage so your other computers can use them. Chrome transmits this through your Google account; no Quietwall server is involved. Inspection history, counters, and the privacy report are never synced.
## Link cleaning and short-link expansion
Removing tracking parameters happens inside the browser without a network request, whether you use the link tool or Pro's automatic cleaning.
When you explicitly ask Quietwall to clean a recognized HTTPS shortened link, the extension sends a credential-free `HEAD` request to the entered URL, follows redirects, and may fall back to `GET`. Quietwall does not render the destination. The shortener and redirect destinations receive normal network metadata and the entered URL. Quietwall refuses to resolve shortened links over unencrypted HTTP.
## Website access
Quietwall has access to HTTP and HTTPS webpages so its packaged popup and redirect guard, cosmetic filters, scriptlets, video-ad handling, fingerprinting defenses, Pro page protections, and user-requested page tools can run. The `webRequest` permission is used read-only to count requests Chrome blocked for the privacy report; it cannot change or delay requests.
## Retention and deletion
Settings remain until you change them, restore a backup, clear Quietwall data, or remove the extension. The privacy report keeps 35 days. The Security Center can clear local activity (including the report) or all Quietwall data. Clearing Quietwall data does not cancel a Pro subscription; manage that from Manage billing.
## Security and scope
Quietwall uses Manifest V3 and Chrome's declarative network rules. It executes no remotely hosted code. The look-alike shield checks addresses against a packaged list and cannot recognise every fake site. The guard cannot promise to stop every server-side redirect after a deliberate navigation.
Quietwall's use and transfer of information received from Google APIs adheres to the Chrome Web Store User Data Policy, including its Limited Use requirements.
## Changes
Material changes to this policy will be reflected in the extension version and in the public policy before the updated version is submitted.
## Contact
Use the developer contact shown on Quietwall's Chrome Web Store listing.