Blockify Privacy Policy

Blockify uses website addresses, page elements, advertising signals, and media-player information to decide what to block, hide, or mute. This processing takes place in your browser.

On streaming sites, Blockify may work with player responses, playlists, and the site's existing playback session. Requests needed for playback are made to the streaming service and its delivery infrastructure. For example, Twitch's existing session and playback information may be used in requests to Twitch to keep playback working.

Blockify does not routinely upload the content of the pages you visit to our servers. Its standard Spotify and YouTube reliability reports contain an event label and an identifier, rather than page text or a full browsing history. Technical error messages can include additional context, as explained below.

Blockify uses Chrome's extension storage to remember:

• Your blocking preferences and websites you have allowed.
• Total and per-site blocking counts displayed by the extension.
• Website domains associated with those per-site statistics.
• Installation-related information and whether certain notices have been shown.
• Compatibility settings and filtering information used by the extension.

Per-site statistics use website domains, rather than a chronological record of full page addresses. A domain can be saved even when no blocked requests are recorded for that visit. This site-statistics table stays in Chrome's local extension storage; the current extension does not send that table to Blockify's servers.

Some playback features also use a website's browser storage to remember ad-related filtering information or preserve player preferences, such as volume and playback quality.

The extension may read an identifier already present in Chrome's sync storage. Chrome can synchronize that stored information across signed-in browsers if you have enabled the relevant sync settings. Your blocking preferences and site-statistics table are stored locally by this version of Blockify.

The extension automatically sends limited reports to help us understand whether its features are working and investigate technical problems.

Feature reliability reports indicate whether an ad-related check or action on Spotify or YouTube succeeded or encountered a problem. These reports include the service/event label and an identifier.

Technical error reports can include an error message, the time of the error, the affected extension component, and an identifier. An error message may contain a website address or request details if those appear in the underlying error.

Some reports use an identifier already saved in Chrome; otherwise, the extension generates a random code when needed. These identifiers are codes rather than names or email addresses. Reports that reuse a saved code can be associated over time.

Reliability reports are sent to insights.getblockify.com. Technical error reports are sent to our error-reporting service at sentry.getblockify.com. We use this information to measure feature reliability, diagnose problems, and improve ad blocking.

Blockify periodically retrieves compatibility settings and filtering adjustments, including from blockify.b-cdn.net. Some checks also occur when supported pages are opened. This helps the extension respond to changes in websites and streaming services.

Certain features load supporting resources, such as replacement media or icons, from Blockify's services or content-delivery providers. The sharing interface currently loads icon resources from cdnjs and Iconscout.

When the extension connects to one of these services, that service receives the IP address needed to deliver the response and ordinary request information, such as the requested resource, browser-provided headers, and any referrer information supplied by the browser. This is separate from the local site-statistics table described above.

The extension may open Blockify welcome, update, help, or feedback pages. These visits send ordinary website request information, together with any details included in the link, such as the extension version.

When you remove Blockify, it may open a feedback page. The link can include the extension version, installation-related information, and a previously saved identifier if available. Those details reach the website when the page opens; completing the feedback form is optional.

If you email us or submit feedback, we receive the information you provide, such as your message and any contact details. We use it to respond to your request and improve the extension.

Some feedback, review, and sharing actions open external services, including Google Forms, the Chrome Web Store, and social platforms. Their own privacy policies apply when you use them. You choose whether to submit feedback or publish a review or social post.

We use information to provide and maintain Blockify's ad-blocking features, measure their reliability, resolve technical problems, deliver compatibility adjustments, and respond to support requests.

We do not sell your personal information or use it for targeted advertising. We do not share it with advertising platforms or data brokers for those purposes.

Information is handled by Blockify and the services needed to operate these features. These include our hosting and diagnostic infrastructure; Bunny CDN for resources served through blockify.b-cdn.net; cdnjs and Iconscout for the icon resources mentioned above; and Google services when Chrome sync, Google Forms, or the Chrome Web Store is involved. Streaming services receive the playback requests directed to their own services. Social platforms receive information you choose to share through them, along with their ordinary connection information.

We may also disclose information where required by law or a valid legal request.

Our use of information received through Google APIs will follow the Chrome Web Store User Data Policy, including its Limited Use requirements. Such information is used to provide or improve Blockify's ad-blocking features and their related reliability and support functions.

Locally saved extension information remains in Chrome until it is cleared or the extension is removed. Clearing ordinary browsing history does not necessarily clear extension storage. Information saved in a website's storage or another synchronized browser is managed through the relevant browser and site-data controls.

We retain server-side diagnostic information and support communications only as long as needed for the purposes described in this policy, then delete or de-identify them. Aggregate statistics that do not identify individuals may be retained longer to understand reliability trends.

Blockify's configuration, diagnostic, and feedback endpoints use HTTPS. Locally saved information uses Chrome's storage mechanisms. We apply reasonable safeguards to information handled by our services.

You can change your blocking preferences in Blockify and manage website access through Chrome's extension settings.

Pausing ad blocking changes filtering behavior. Local statistics, compatibility checks, and technical reporting may still continue; the blocking controls are not separate diagnostic controls.

To stop the extension's background activity, disable or remove it through Chrome. Refresh any open pages where it was running to stop scripts already loaded into those pages. Removing the extension clears its local Chrome extension storage and may open the feedback page described above.

For privacy questions, access or deletion requests, or questions about limiting diagnostic information, contact hi@getblockify.com. Diagnostic reports generally do not contain an email address, so we may need additional information to locate related records. We handle requests in accordance with applicable law.

We may update this policy as Blockify changes. The date at the top shows the latest revision. Material changes in how the extension handles information will also be explained through the relevant product disclosures.

Questions about Blockify or your information? Email hi@getblockify.com.