Legal and privacy
Privacy Screen Guard — Privacy Policy
A detailed explanation of what Privacy Screen Guard can access, what it processes locally, what it stores, and the choices available to you.
1. Who this policy covers
This policy applies to the Privacy Screen Guard Chrome extension published by Netbase JSC. Privacy Screen Guard is a visual privacy aid intended to reduce accidental exposure of sensitive-looking webpage content during screen sharing and local captures. “We,” “us,” and “our” refer to Netbase JSC; “you” refers to the extension user.
2. The product’s privacy model
Privacy Screen Guard is local-first. When Live Privacy is active, bundled extension code examines eligible webpage content in the tab, identifies configured sensitive-looking patterns, and changes only the page’s visual presentation. Detection does not require a Netbase JSC account, cloud service, or remote processing endpoint.
The extension is a visual assistance tool, not a data-loss-prevention system or guarantee that every sensitive value will be detected.
3. Information processed locally
Depending on your settings and the page, the extension may temporarily examine:
- Eligible visible DOM text and text added by dynamic or single-page applications.
- Configured form-field values, including detected sensitive values or all filled fields if you select that mode.
- Text inside accessible frames and open Shadow DOM.
- The current page URL and origin to determine whether the page is supported or excluded.
- Areas and phrases you explicitly choose to hide for the current tab session.
These values are used only in memory to provide masking and page-status information. Detector results use category names, numeric character ranges, and counts instead of copied raw matches.
4. Sensitive-looking categories
You can enable or disable each category in Settings. The current detector set covers:
-
Email addressesPhone numbersPayment cardsTokens and keys
Bank accounts and IBANsGovernment and tax IDsPassports and licencesDates of birth
Street addressesIP addressesCrypto walletsOne-time security codes
Precise coordinatesSensitive linksMedical and insurance IDsVehicle IDs
Validation, labels, checksums, and formatting rules are used where practical to reduce false positives. Detection can still miss information or mask ordinary text by mistake.
5. Data-handling overview
| Information | Purpose | Where handled | Retention | Sent to us? |
|---|---|---|---|---|
| Eligible page text and configured form values | Detect and visually mask sensitive-looking values | Current browser tab | Not stored by the extension | No |
| Website origin and protection state | Show status and apply exact-site exceptions | Chrome permission state and local storage | Until changed, cleared, or uninstalled | No |
| Detector and appearance preferences | Apply your chosen protection behavior | chrome.storage.local | Until changed, cleared, or uninstalled | No |
| Manual areas and custom phrases | Hide user-selected content | Current tab memory | Current tab session | No |
| Safe Capture image | Save a user-requested protected screenshot | Browser and local device | Controlled by you after saving | No |
| Coverage codes and mask counts | Explain current protection status | Extension message channel | Transient | No |
6. Information stored on your device
The extension uses chrome.storage.local for detector choices, mask color, mask style, display length, form-protection mode, exact website exceptions, and safe settings-schema migration information. Raw page text, raw form values, detected matches, session phrases, manual selections, and screenshots are not saved in extension storage.
7. Information we do not collect
- No webpage text, form values, detected values, screenshots, or browsing history is uploaded to Netbase JSC.
- No telemetry, product analytics, advertising identifier, fingerprinting, or behavioral tracking is used.
- No account, name, email address, payment information, or subscription information is required by this extension version.
- No extension-processed personal information is sold, rented, or shared with data brokers or advertisers.
- No remote AI service or human reviewer receives the webpage content processed by the extension.
8. Chrome permissions
activeTab- Supports visible user-triggered tools for the current tab, including Safe Capture.
scripting- Registers, updates, and removes the bundled local masking runtime.
storage- Keeps your preferences and exact website exceptions on the device.
- Optional HTTP/HTTPS website access
- Allows automatic protection on regular websites only after you press the approval action and accept Chrome’s prompt.
The extension does not declare permanent host_permissions or a static universal content script. Chrome internal pages, the Chrome Web Store, and other browser-restricted surfaces remain inaccessible.
9. Website access and revocation
Chrome’s permission state is authoritative. You can turn off global website access in Settings or remove the permission through Chrome’s extension controls. You can also pause individual origins through exact website exceptions. When access is removed, the extension attempts to clean its visible masks before unregistering the masking runtime and removing permission.
10. Safe Capture
Safe Capture starts only when you press its visible action. It creates a PNG of the visible protected tab and saves it locally. The extension does not silently capture tabs, upload the image, keep a server copy, or retain the capture in extension storage. Your browser and operating system control the final file location and any later use.
11. Extension messaging
The popup, service worker, Settings page, and masking runtime exchange validated messages to coordinate settings and protection state. These messages remain within the Chrome extension environment. They may contain status codes, enabled categories, character ranges, and counts; they are designed not to include copied raw detector matches.
12. Third parties, transfers, and automated decisions
The extension has no analytics SDK, advertising SDK, remote code, cloud-processing provider, or page-data transmission path. Because extension-processed page content is not sent to us, we do not transfer that content internationally or provide it to subprocessors. Detection is used only to display local masks and is not used to make decisions about eligibility, employment, credit, insurance, health, or access to services.
13. Retention and deletion
Local preferences remain until you change them, clear extension data, or uninstall Privacy Screen Guard. Current-tab phrases, manual areas, and reveal state end when the tab is closed, navigated, cleaned, or reloaded as applicable. Locally saved captures remain under your control and can be deleted using your operating system.
14. Security measures
The extension uses bundled Manifest V3 code, an extension-page content security policy that blocks remote scripts and network connections, sender and message-shape validation, local storage, and optional website access. These measures reduce risk but cannot eliminate all browser, webpage, device, or user-operation risks.
15. Coverage limitations
Images, video, canvas, WebGL pixels, browser controls, native applications, Chrome internal pages, inaccessible cross-origin frames, closed Shadow DOM, and some complex or rapidly changing page structures may remain visible. First-paint protection requires permission before navigation. Always inspect the page and test the exact sharing or recording workflow before showing sensitive material.
16. Your choices and privacy requests
You can change detector and mask settings, pause one website, remove all optional website access, clear local extension data, delete saved captures, or uninstall the extension. Because page content is not transmitted to Netbase JSC, we generally do not possess that content to access, correct, export, or delete. For questions about this policy or any information you believe you sent directly to support, contact us using the details below.
17. Children’s privacy
Privacy Screen Guard is a general productivity tool and is not directed to children. The extension does not knowingly collect personal information from children or other users through its masking features.
18. Changes to this policy
We may update this policy when the extension’s behavior, permissions, publisher information, or applicable requirements change. The effective date and product version at the top identify the policy revision. Material changes will also be reflected in release notes or the Chrome Web Store listing when appropriate.
19. Chrome Web Store Limited Use
Privacy Screen Guard’s use of information received through Chrome APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. Information is used only to provide the extension’s user-facing local privacy-masking features and is not used for advertising, profiling, creditworthiness, or unrelated purposes.