Learn how Screen Privacy Blur protects screen privacy without collecting screen content, browsing activity, or personal files.
Compatible with your browser • Free install in 2 clicks • No signup required
The extension does not upload screen content, browsing history, screenshots, recordings, passwords, API keys or form fields for product analytics. Detection and visual masking run locally. Replacement scenarios may save the original and fictional values you select in your local browser profile so you can reuse a demonstration.
Version 2.7.3 offers optional product analytics to measure use of the extension and its protection features. Analytics are off until you explicitly enable them in the extension panel. Declining does not disable protection features. After consent, each Chrome profile receives a random installation identifier stored in chrome.storage.local; it is not synchronized between profiles. Events contain only the event name, installation identifier, cached Pro status, extension version and interface language. A paywall event also identifies the protection feature that opened it. An activity request is attempted at most once per UTC day, following an interaction such as opening the panel, pressing Alt+B or using a protection feature. Starting the background worker or restoring saved protection does not count as activity.
Extension analytics are sent over HTTPS to our Supabase backend and processed in PostHog. Installation identifiers are pseudonymous, not fully anonymous. After consent, welcome, upgrade and uninstall links can carry the installation identifier and extension version to privacyblur.co so those interactions can be associated with the same installation. No visited-site URLs or domains, page text, form values, screenshots, selectors, subscription tokens or credentials are included in extension analytics. We disable IP and location enrichment on the PostHog capture payload and do not forward the user's IP in it. Service providers still receive network connection information and may retain operational access logs under their own settings.
We use product analytics to understand and improve the extension's disclosed functionality. We do not sell this data, use it for advertising or behavioral ad profiles, or transfer it for unrelated purposes. Supabase and PostHog process it as service providers. Received analytics are subject to the configured analytics-project retention settings; infrastructure logs have separate retention settings. You can turn analytics off again in the extension panel to stop future analytics and remove the local identifier from future website links. Turning it off does not undo requests already sent. Clearing extension data or uninstalling removes the local installation identifier but does not automatically delete events already received by the analytics service. Contact support about access or deletion, providing the installation identifier if available so the relevant data can be located.
Manual blur and Smart Auto Blur run locally in your browser. Blur rules are applied on-device before you share your screen, join a call, or record a walkthrough.
If you contact support or purchase Pro, the information you submit for that workflow is handled only to respond to your request, complete checkout, or verify subscription status. The website uninstall survey sends your selected reason and an optional, explicitly submitted website domain to website analytics; the entered URL path, query, and fragment are removed.
Blur processing and replacement scenarios stay in the browser. Extension preferences and site presets may use Chrome storage.sync and follow your Chrome synchronization settings; replacement scenarios, subscription credentials, installation identifiers and the daily activity marker use storage.local. Clearing a blur or stopping protection does not delete your saved scenarios or previously received analytics. Uninstalling removes the extension's local data. Evaluate your organization's own compliance requirements and the actual data flows before use; this policy does not certify compliance with a security standard.
When setting up Privacy Policy for Screen Privacy Blur (Data Protection Policy | Screen Privacy Blur), Screen Privacy Blur runs 100% locally in your Chromium browser so private records, credentials, and financial balances remain hidden or replaced with realistic demo data before any frame is shared.
Use the extension only for lawful purposes
Extension blur processing stays in the browser
Permissions support overlays and preferences