Capture Shield does not collect, store, transmit, share or sell any information about you. It has no servers and contains no networking code. Everything it does happens inside your own browser, and the only thing it saves is the settings you choose, which stay on your device.
This policy applies to the Capture Shield extension for Google Chrome and Chromium-based browsers ("the extension"), published by the operator of webmaghrebi.com ("we", "us").
Questions about this policy can be sent to the contact address published on that site.
It also covers this website. The website and the extension are independent: the extension never contacts this site, and it keeps working normally if this site is offline.
To hide sensitive information on a page, the extension has to look at that page. This is what it looks at, what it does with it, and what happens to it afterwards.
| What | Why | Where it goes |
|---|---|---|
| Text on the pages you visit | To find emails, phone numbers, payment cards, IP addresses and your own protected values so they can be masked. | Held in memory inside the browser tab, for as long as it takes to check it. Never written to disk, never sent anywhere, discarded immediately. |
| Link destinations on those pages | To decide whether a link's target would reveal something if Chrome previewed it on hover. | Same: examined in the tab, in memory, then discarded. |
| The address of the current tab | To apply your per-site rules — the exceptions you configured yourself. | Compared against your own settings in memory. No browsing history is kept, and no record of the pages you visit is created or stored. |
| The settings you choose | So the extension behaves the way you configured it next time you open the browser. |
Saved on your device with chrome.storage.local. See section 4.
|
| A count of masked values per tab | To show the number on the toolbar badge. | A number held in memory by the extension's service worker. It is not stored, and it contains none of the values it counted. It is discarded when the tab is closed or reloaded. |
A value that the extension detects — an email address, a card number, your name — exists only for the moment it takes to replace it on screen. It is not logged, not cached to disk, not included in any report, and not written to storage. The extension's internal logging is built so that it structurally cannot accept page content: it takes only fixed strings and numbers, and it is switched off entirely in released builds.
fetch, no XMLHttpRequest, no WebSocket, no beacon, no remote
script. There is no code path by which anything could be sent.
The only thing the extension saves is your own configuration, using Chrome's
chrome.storage.local API. That means it is stored on your computer, inside your
Chrome profile. It includes:
The custom values are the most personal thing the extension holds, and they are held only because you typed them in and asked for them to be protected. Chrome's synchronised storage is deliberately not used, because it would copy those values through Google's sync infrastructure to your other devices. Keeping them in local storage means they stay on the machine you entered them on. If you want to move them, the options page has an export button that writes a file you control.
| Permission | What it allows | Why it is required |
|---|---|---|
storage |
Saving and reading data in the browser's local extension storage. | To remember your settings and your protected values between sessions. Nothing else is written. |
contextMenus |
Adding one entry to the right-click menu, shown only when you have selected text. | Choosing it saves the selected text as one of your protected values, in the same local storage as everything else. The selection is not transmitted, and no other page context is read. |
<all_urls> host access |
Running the extension's content script on the pages you open, so it can read and modify what is displayed. | The page that needs protecting is whichever one you open while recording. A fixed list of sites would fail on exactly the page you did not anticipate. This access is used to read text and change what is rendered — nothing more. |
These are the only three permissions requested. The extension does not ask for
tabs, history, cookies, downloads,
webRequest, scripting, identity or any other
permission, and it does not request access to anything outside the browser.
The extension reads text from the page in order to check it, and where it finds something that matches, it changes what is rendered so that the real value is not displayed. Both steps happen locally, inside the tab. Page content is treated as untrusted input throughout: it is never evaluated as code, never inserted as HTML, and never used to build anything executable.
The extension uses no third-party services, SDKs, analytics providers, error reporting services or content delivery networks. It makes no third-party requests.
The interface contains two kinds of outbound link, and each opens a page outside the extension only when you click it:
paypal.me/tracklegacy, reached from the
"Keep Capture Shield free" button shown at the top of the popup each time you open it. It
is a button and nothing more: clicking it opens the page in a new tab, and the extension
records nothing about the click — not that it happened, not when, not how often, and not
whether you ever gave anything. Nothing about your settings or protected values is
attached to it, and the button looks and behaves identically whether you have donated or
not, because the extension has no way of knowing.
The donation page is operated by PayPal, a third party, not by the developer of this extension. Once you are on it, that provider's own privacy policy and terms apply to whatever you do there, and this policy stops covering it — a payment you make is between you and that provider. The developer receives from them only what any recipient of a donation receives, and never anything that ties a donation to your use of the extension.
Otherwise the extension has no payment of any kind: no paid tier, no subscription, no in-app purchase, no advertising, and no payment details requested, received or stored by the extension at any point. Every feature works identically whether or not you ever donate. Nothing is locked, limited, delayed or degraded, and no feature is withheld pending payment.
The extension is not directed at children and collects no information from anyone, including children.
Because nothing is transmitted or collected, there is no database to breach and no transmission to intercept. Your settings are protected by your operating system's and Chrome profile's own access controls. Within the extension: page content is never passed to an HTML or code-evaluation sink, stored settings are validated against a strict allow-list before use so a corrupted or tampered profile cannot inject anything, and the extension declares a content security policy that forbids loading or evaluating external code.
There is no request to send us, because we hold nothing. Your rights under the GDPR, the CCPA and comparable laws — access, correction, deletion, portability, objection — are satisfied by the controls above, which operate instantly and without involving us.
Stated here because a privacy policy that overstates a privacy tool is itself a privacy problem. Capture Shield reduces the chance that personal information is visible in a recording, live stream or screen share. It cannot guarantee that information will never be exposed. In particular it does not protect:
<canvas>, WebGL or video;chrome:// pages and the Web Store;The extension is free and provided as is, with no warranty and no guarantee of protection. The terms of use set out that position, and the limits of the developer's liability, in full.
If this policy changes, the "last updated" date at the top changes with it, and the previous substance is not quietly replaced. If a future version of the extension ever processes data differently — and specifically if it were ever to transmit anything — that would be described here before the change ships, and disclosed in the Chrome Web Store listing. As of version 1.0.0 there is no such feature and none is planned.
Questions about this policy, or about how the extension handles anything, can be sent through the support section of the product page. Please do not include real personal information in a report — describe the shape of the value instead.