Privacy policy.
What the extension collects, what stays in your browser, and how to contact the controller.
At a glance
Ad Block Streaming is a free browser extension that filters web requests and page elements. It processes browsing-related information and device signals; use is not anonymous and processing does not all stay on your device. This policy covers the extension and adblockstreaming.com.
1. Who is responsible
Ad Block Streaming is the controller identified by the operator for the practices described in this policy. Our contact address is Pl. Numa-Droz 2, Neuchâtel, 2000, Switzerland. Privacy inquiries and requests should be directed to the controller through our contact form.
Personal information includes information that identifies you or can be linked to you, such as an IP address, installation identifier, device fingerprint, or browsing-related record. An identifier or domain record linked to an installation is not necessarily anonymous.
2. Browser extension data
Permissions and processing on your device
The supplied build requests access to all websites, together with declarativeNetRequest, scripting, storage, unlimitedStorage, activeTab, and webNavigation. These permissions support request filtering, applying page scripts and styles, saving settings and filter data, using the element picker in an active tab, and responding to navigation. All-site access also enables the installation and domain collection described below. The build does not request the browser's history API permission.
Filtering code reads or changes page elements, observes navigation URLs, and handles tab and popup information on your device. This is distinct from what is sent to the API. The inspected build has no general uploader for page contents, passwords, form entries, or website cookies.
What is sent to the configured API
| Category | Information and timing |
|---|---|
| Installation identity | A persistent server-issued installation identifier, the extension ID and version, identity-migration status, and synchronization state and timestamps. The identifier is used to recognize a returning installation. |
| Installation attribution | The hostnames of tabs open when the extension is installed, and any an, cid, and sid campaign parameters found in a Chrome Web Store tab. Hostnames can include subdomains. These records support installation attribution and marketing fraud monitoring. |
| Visited domains | A rolling map of up to approximately 50 root domains and their visit counts. Visits are recorded after a short dwell and include allowed or paused sites. Local records also contain last-visit timestamps; the API payload sends counts, rather than those per-domain timestamps. This supports understanding use and improving filtering. |
| Preferences and custom rules | The acceptable-ads preference, user allowlists and blocklists, and custom element-hiding selectors grouped by hostname. Selectors can contain page-derived IDs, classes, attribute text, or link addresses. The domain telemetry fields exclude URL paths, but custom selectors are a separate field and can contain URL information. |
| Device fingerprint signals | When no installation identity is available, or an identity migration is requested, the extension collects CPU core count, reported memory, GPU vendor and renderer, WebGL extension count, language, colour depth, timezone, screen resolution, touch capability, user agent, battery charging state and level where available, an automation indicator, a generated canvas image, and an offline audio rendering fingerprint. These signals support installation recognition, identity recovery, and fraud monitoring. The audio test generates sound data internally; it does not record your microphone. The canvas image is a generated test image, not a screenshot of a visited page. |
| Request information | Receiving infrastructure sees the originating IP address and ordinary connection information when the extension contacts it. The client code does not establish which of these details the server logs or how long it stores them. |
The supplied build sends these records to the configured extension API. Synchronization is triggered by installation or updates, identity collection, advertising-preference changes, and navigation when an update is due. Its default interval is three hours; the server may return a different interval. It also downloads filter rules and styles from URLs supplied by that API. The extension API and databases are hosted in the Netherlands. The collection described here reflects the supplied extension code; the retention and access practices below have been confirmed by the operator.
On removal, Chrome can open a removal page that receives the extension ID, version, and installation identifier when available. This allows removal to be linked to an installation and exposes the usual request information to the receiving service.
Local and browser-synchronized storage
Local extension storage holds preferences, allowlists, blocklists, paused sites, custom hiding rules, identity and attribution records, installation domains, the rolling domain map, synchronization records, cached filters, and counts of pages processed and popups blocked. Those blocking counts are not included in the inspected API payload.
The blocked-popup list uses browser session storage and can contain full popup URLs, domains, tab IDs, and timestamps. This list is not included in the inspected API payload and is cleared with the browser session. Raw fingerprint signals are held in memory before transmission rather than written to the extension's local storage. Any fingerprint information retained on the server is subject to the retention limits below.
The extension also writes selected records to chrome.storage.sync: installation identity, campaign attribution, installation domains, the visited-domain map including local timestamps, extension version, acceptable-ads preference, allowlists, blocklists, paused sites, and YouTube and cookie-banner settings. Depending on your Chrome profile and synchronization settings, Google may synchronize these records across devices and they may be recovered after reinstalling. Custom hiding selectors and the local blocking counts are not included in this sync mirror.
Diagnostics
The inspected build writes diagnostic messages to the local extension console. It contains no automatic remote crash-reporting integration or Google Analytics integration. A locally packaged substitute for an analytics script is a blocking compatibility resource, not a Google Analytics tracking integration.
3. Website data and cookies
The supplied website consists of static pages. Its code does not set first-party cookies, create accounts, or include analytics or advertising scripts. Cloudflare is the CDN identified by the operator. Cloudflare and the website host may process IP addresses, requested URLs, request times, browser or connection details, and security information to deliver pages and protect the service. Provider-side cookie settings, logging, retention, and processing locations have not been verified from this static code.
The current contact form validates your entries in your browser and opens your email application with a message addressed to [email protected]. You must press Send in that application to deliver it. The site itself does not submit or store form entries. If you send the message, its recipient receives your name, email address, topic, and message, and email providers process delivery. This email address is the contact route for privacy requests. Messages are used to handle your request and are not retained as a correspondence archive. Email providers process message delivery under their own service arrangements. Do not include passwords, payment information, or unnecessary sensitive information.
4. Purposes, advertising, and legal grounds
Data is used to deliver and configure filtering, recover installation identity and selected settings, improve blocking rules, understand extension use, attribute installations, monitor marketing fraud, protect the service, and answer requests. Ad Block Streaming is free to use and has no payments or subscriptions.
In selected markets in North America, Europe, Latin America, and Asia-Pacific, we may allow some advertisements and receive a percentage of the revenue. The acceptable-ads preference defaults to on in the supplied build. Changing it saves and sends your preference and requests a fresh configuration from the API. Actual filtering changes depend on server-supplied rules; the toggle does not independently remove all exceptions bundled with the extension. Turning it off does not stop domain telemetry or fingerprint collection when identity is missing or requires migration.
For processing subject to UK or EU data protection law, each purpose needs an applicable legal ground. Our intended grounds include legitimate interests in service security, fraud prevention, filtering improvement, and answering inquiries, subject to necessity and a balance with users' rights; contractual necessity only where processing is genuinely necessary to provide a requested service; and a legal obligation only where a specific applicable obligation exists. Consent is required for processing where the applicable law requires it.
The supplied build has no separate telemetry or fingerprinting consent control, age verification, or parental-consent flow. Privacy requests, including requests to opt out, are handled by email. An email opt-out route is not consent before collection, and this notice and installation of the extension do not by themselves establish valid consent.
6. Retention and security
The operator confirms that the following retention limits are enforced on the server.
| Data | Retention limit |
|---|---|
| Server-held extension records | Preferences, installation identifiers, attribution, visited-domain records, retained fingerprint information, and marketing or fraud-monitoring records are deleted after six months without recorded extension activity, or earlier where an applicable erasure request requires it. |
| Routine IP and request logs | Deleted after 30 days from each request. IP addresses are not used as the identifier for saved preferences. |
| Email correspondence | Used to handle requests and not retained as a correspondence archive. |
| Backups | Wiped weekly. |
Inactivity means the absence of an actual extension-use signal, such as a successful synchronization triggered by use. Administrative access, backup operations, and housekeeping do not restart the inactivity period. Continued use may extend retention of records still needed for their stated purpose, but does not restart the 30-day lifetime of old request logs. Records must not be kept longer than necessary merely because an installation remains active.
Any longer retention must be limited to information necessary for a specific applicable legal obligation, active fraud or security investigation, or concrete legal dispute. The reason, relevant records, review date, and deletion trigger must be documented; information must be deleted or effectively anonymized when the justification ends. A commercial advertising-provider contract does not itself create a statutory obligation or justify retaining all identifiable data indefinitely. Mandatory legal requirements and applicable deletion rights take precedence. An installation identifier, hashed IP address, or device fingerprint is not automatically anonymous.
Locally, the visited-domain map is limited by relevance and size rather than a fixed expiry period; settings and identity records remain until removed or replaced. Browser session records are temporary. Disabling the extension stops its ongoing activity but does not erase stored records. Removing it does not send a server deletion request and may open the removal page. Browser-synchronized information can be restored on reinstall, depending on browser behaviour and settings. The server inactivity limit does not automatically erase Chrome-synchronized copies. Contact the controller by email to request deletion of remotely held information and manage browser synchronization through Chrome.
The extension's API connections and removal page use HTTPS. Only the administrator has access to the server-held personal information. Raw device signals are held temporarily in memory on the client. No service can guarantee absolute security.
7. Your choices and rights
You can edit allowed and blocked sites, remove custom hiding rules, and change feature preferences through the extension settings. Pausing protection on a site or switching off acceptable ads does not switch off telemetry. You can request an opt-out or deletion by emailing the controller through the contact form. The inspected build has no separate in-extension telemetry switch. An email request does not itself immediately disable the installed extension: disable or remove it in Chrome to stop ongoing collection, and manage browser synchronization separately through Chrome.
Depending on applicable law, you may request access, correction, deletion, restriction, or a portable copy of your personal information, object to processing based on legitimate interests, and withdraw consent where processing relies on consent. Where applicable, you may object to direct marketing. These rights have conditions and exceptions; a general reference to fraud prevention does not automatically defeat a request.
To request access, deletion, correction, or an opt-out, email the controller through the contact form and select “Privacy question”. The administrator handles these requests. We may request proportionate information to verify and locate your records. Do not post your installation identifier publicly or send raw fingerprint data unless specifically necessary for your request. You can also report concerns to the Swiss Federal Data Protection and Information Commissioner (FDPIC), lodge a complaint with the competent EU/EEA supervisory authority where GDPR applies, or contact the UK Information Commissioner's Office where UK data protection law applies.
8. Children and families
The operator intends Ad Block Streaming for a general audience, including children. The supplied extension does not ask a user's age, distinguish children's installations, or provide a parental-consent flow. The collection described above can therefore apply when a child uses it; this policy does not claim that children's information is never collected.
Children deserve particular protection. The operator must assess applicable children's privacy requirements, use age-appropriate explanations, and establish any required consent and protective defaults. If you are a parent or guardian with a concern about a child's information, contact the controller through the contact form to request a review or exercise applicable rights.
9. Changes to this policy
We may update this policy when the extension, providers, or data practices change. The date at the top identifies this version. Material changes require any additional notice or consent required by applicable law. Continued use alone does not replace consent where it is required.
10. Contact the controller
For privacy questions, concerns, or requests, contact:
Ad Block Streaming
Pl. Numa-Droz 2
Neuchâtel, 2000
Switzerland
Open the contact form and choose “Privacy question”.