Page access
The extension needs page access to place blur overlays on top of sensitive areas. That access is used locally for the current browsing experience.
Understand how Screen Privacy Blur uses browser permissions for local blur overlays, saved preferences, billing, and support.
Compatible with your browser • Free install in 2 clicks • No signup required
The extension needs page access to place blur overlays on top of sensitive areas. That access is used locally for the current browsing experience.
Chrome storage remembers preferences, site presets and Pro status. Some preferences and site presets use storage.sync and follow your Chrome synchronization settings. Replacement scenarios, subscription credentials, the per-profile installation identifier and the daily analytics marker use storage.local.
The extension contacts Supabase for subscription verification, intentionally submitted support requests and, from version 2.7.3, optional product analytics after explicit consent. Upgrade links open the website paywall. Analytics are forwarded server-side to PostHog; the PostHog SDK is not included in the extension. Screen content is not uploaded for blur processing.
Screen Privacy Blur requests activeTab, tabs, scripting, storage and sidePanel. These let it identify the target tab, apply bundled protection code, remember settings and keep controls beside the page. The existing https://*.supabase.co/* host permission supports backend requests. Optional site permissions are requested for replacement scenarios that must remain protected across page reloads. Version 2.7.3 does not add permissions or host permissions for analytics.
When setting up Why Screen Privacy Blur needs browser permissions (Browser Permissions Guide | 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.
No screen recording or screenshot upload
Use the extension only for lawful purposes
Extension blur processing stays in the browser