Privacy Policy

Blockify is a Chrome extension that helps you block distracting websites, hide homepage feeds on supported social platforms, and remove individual page elements. This policy describes what data Blockify accesses, how it is stored, and what it is never used for.

Blockify stores the following information in Chrome's local extension storage (chrome.storage.local). This data never leaves your device.

• Blocked sites: The list of domain names you have chosen to block.
• Element rules: CSS selectors and short labels for page elements you have chosen to hide, grouped by domain.
• Feed blocking preferences: Whether feed blocking is enabled, and which supported platforms you have turned it on for.
• Interface state: Whether you have completed the product tour or dismissed the feed blocking beta notice.

To build an element rule, Blockify reads the structure of the page you are viewing so it can generate a CSS selector for the element you picked. This happens entirely inside your browser. The page content itself is never stored, copied, or sent anywhere. Only the selector and a short label are saved.

This data is stored solely to make the extension work across browser sessions. It is never transmitted, never shared, and never used for any purpose other than applying your own blocking rules.

The Blockify extension does not collect, transmit, or share any of the following. This list describes the extension itself; for the one page on this website that does ask you for information, see section 6.

• Browsing history or URLs you visit
• Personal identifiers of any kind (name, email, IP address, device ID)
• Analytics, telemetry, or crash reports
• Keystroke or form data
• Cookies or tracking identifiers

No data is sent to any external server at any time, including servers operated by the developer.

Blockify requests the following browser permissions. Each is used only for the stated purpose:

• declarativeNetRequest: Blocks websites by redirecting matched URLs to a local blocked page bundled with the extension.
• host_permissions (<all_urls>): Blocking rules must be able to apply to any site you choose. Because you decide which domains to block and which elements to hide, the list of sites cannot be known in advance.
• storage: Persists your blocked sites, element rules, feed blocking preferences, and onboarding state across sessions.
• scripting: Injects the element-picker content script when you activate it on a page that has just loaded.

Blockify requests no other permissions.

The Blockify extension does not integrate with any third-party analytics, advertising, or data-collection services. No external scripts are loaded or executed by the extension at any time.

This website is separate from the extension. Most pages on abdullahhamid.ca serve advertising and may use analytics, and those third parties may receive standard request information such as your IP address and browser user agent, as they would on any website you visit.

Advertising is deliberately disabled on this privacy policy page and on the Blockify welcome, update, and uninstall pages, since those are pages the extension may open for you rather than pages you chose to visit.

The page at abdullahhamid.ca/blockify-pro asks for your opinion on features and pricing for a future paid plan. It is the only page on this site that collects anything you type, and it is entirely optional. Nothing on that page is connected to the extension, and using it has no effect on how Blockify works.

If you submit the form, the following is stored:

• Your answers: how long you have used Blockify, how often, what you block for, whether you pay for other productivity software, how you allocated points across features, which of them you think should be free or paid, the prices you gave, and any feature idea you wrote in.
• Your email address, only if you chose to type one in to hear about the launch.
• A random session identifier, the page that referred you, how long you took, and your browser user agent string.

Everything above is anonymous unless you enter an email address. There is no account, no login, and no way for me to connect a response to a person otherwise.

Analytics on that page:

To understand where people lose interest in the questions, that page records page views, how far down you scrolled, which step you reached, which features you interacted with, and when you left. This uses no cookies, no advertising trackers, and no third-party analytics service. The session identifier it uses is random, is held in your browser's session storage, and is discarded when you close the tab, so a return visit is a new anonymous session with no link to the previous one. If your browser sends a Do Not Track or Global Privacy Control signal, nothing is recorded at all.

Responses are stored in a Supabase database and are readable only by me. They are used to decide what to build and what to charge, and are not sold, shared, or passed to advertisers. If you left an email address, it is used to tell you when the paid plan launches and nothing else. To have your response or your email removed, ask through the support page and it will be deleted.

The Blockify extension does not knowingly collect information from anyone, including children under the age of 13. Because the extension collects no data at all, it is compatible with COPPA requirements.

The Blockify Pro feedback page described in section 6 is not directed at children and should not be used by anyone under 13. If you believe a child has submitted an email address there, ask through the support page and it will be deleted.

If this policy is updated, the revised version will be published at the URL below and the effective date will be updated. Continued use of the extension after any change constitutes acceptance of the revised policy.

For questions or concerns about this privacy policy, please use the contact form at: abdullahhamid.ca/support

The canonical version of this document is hosted at abdullahhamid.ca/privacy.