-
-
Save roaryxu/79bff93d8af43c6dd558508d9c3d17e2 to your computer and use it in GitHub Desktop.
ScrollBlock Privacy Policy
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| # ScrollBlock Privacy Policy | |
| **Effective Date:** 30 May 2026 | |
| **Last Updated:** 30 May 2026 | |
| At **ScrollBlock**, we believe that your attention is yours to keep, and your privacy is absolute. ScrollBlock is designed from the ground up with a **Zero-Permission, Privacy-First Architecture**. This policy outlines how ScrollBlock operates and confirms our commitment to your digital privacy. | |
| --- | |
| ## 1. Zero Data Collection & Storage | |
| ScrollBlock **does not collect, store, track, or share** any personal data, usage data, or browser history. | |
| * **No Telemetry:** We do not use analytics packages, event logging, or tracking pixels. | |
| * **No Server Communication:** ScrollBlock is 100% serverless. It never makes external network requests, connects to API endpoints, or transmits information over the internet. | |
| * **No Cookies or Local Storage:** We do not save cookies, session tokens, or local site settings. | |
| --- | |
| ## 2. Zero-Permission Architecture | |
| ScrollBlock requires **no Chrome extension permissions** (such as `storage`, `activeTab`, or background scripts). | |
| Because we request a blank permission set (`"permissions": []` in our extension manifest), it is **technically impossible** for the extension to: | |
| * Read your browser cookies or passwords. | |
| * Track your browsing history across other tabs. | |
| * Store settings or data locally on your machine. | |
| * Send any information back to a server. | |
| --- | |
| ## 3. Sandboxed Local Content Processing | |
| ScrollBlock operates entirely within a local, sandboxed environment in your browser: | |
| * **Scope:** The content script only runs when you actively navigate to vertical feed pages on Instagram, YouTube, and Facebook. | |
| * **Functionality:** It uses standard DOM event listeners to intercept scroll and interaction inputs, and injects a visual overlay card inside an isolated Shadow DOM. | |
| * **Data Processing:** All URL checking and event suppression are executed **locally and instantaneously** on your device. No URLs, video IDs, or interactions are ever cached or logged. | |
| --- | |
| ## 4. No Third-Party Services | |
| ScrollBlock is completely self-contained: | |
| * There are no embedded third-party scripts, CDNs, or external style dependencies. | |
| * All graphic icons and fonts (Outfit and Inter system weights) are loaded locally from pre-packaged extension resources. | |
| --- | |
| ## 5. Code Transparency & Open Source | |
| To ensure complete peace of mind, ScrollBlock is fully open-source and transparent. You can inspect every line of our codebase on our GitHub repository. We welcome reviews, audits, and contributions to verify our zero-permission, zero-tracking implementation. | |
| --- | |
| ## 6. Changes to this Policy | |
| Because ScrollBlock does not collect user contact information, we cannot notify users of updates directly. Any future revisions to this privacy policy will be updated on our hosting page and reflected in the extension's release notes. | |
| --- | |
| ## 7. Contact | |
| If you have any questions or feedback regarding ScrollBlock's privacy architecture, please leave a review on the Chrome Web Store listing. We are fully committed to keeping ScrollBlock clean, private, and distraction-free. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment