Shopping Guard Privacy Policy
Status: 30 September 2026 · Version 0.10.0
Summary
Shopping Guard transfers no data. There is no server, no account, no analytics and no disclosure to third parties. Everything Shopping Guard determines stays on the device and is deleted when the extension is removed.
What Shopping Guard does
During a purchase, Shopping Guard reads the visible content of the page you currently have open and describes what is there: prices, shipping costs, delivery time, additional options, button labels. Comparing two pages of a purchase produces notes such as "shipping costs appeared" or "total price increased".
Shopping Guard gives an assessment based on what is visible on the page. It does not check legal compliance, does not pass judgements and does not replace advice.
Which data is processed — and where it stays
The following list is complete. It names every storage location that the extension creates.
| What | What for | Where it stays |
|---|---|---|
| Visible page content (text) | Detect prices, shipping, delivery time | only in the page's working memory, is not stored |
| Detected order step: merchant host, page URL, prices, shipping, delivery time, availability, additional options including checkbox state, urgency wording, detected shop system | comparing two steps and detecting the shop system | browser.storage.local (session document, at most 50 steps per purchase), on your device |
| Local order history: merchant host, date, amount, URL | Trace what you bought | browser.storage.local (at most 200 entries), on your device |
| Settings: display (light/dark/automatic) and language | so that display and language follow your choice | browser.storage.local, on your device |
| whether the panel was last opened on this merchant, including merchant host and time | reopen the panel on the next page change | browser.storage.local, on your device |
| Installation and update time of the extension | technical storage of the extension | browser.storage.local, on your device |
About the stored URL
The detected order step and the order history include the address of the page on which Shopping Guard detected something (window.location.href, truncated to 1000 characters). This is necessary in order to assign two steps to each other and to detect the shop system.
In some shops this address may contain an order or session identifier, for example /checkouts/<identifier>/thank_you. It is not evaluated and not transferred — it only appears in the address. If you do not want this, delete the session in the panel or the order history in the popup; removing the extension makes both disappear completely.
This storage concerns exclusively the address of the page. Nothing is still written into input fields, and fields for passwords, card and account numbers or one-time codes are skipped before anything else happens to them.
browser.storage.local is your browser's local storage for extensions. It is not synchronised beyond the device and is not readable by the website you visit.
What Shopping Guard never reads
The following fields are detected and skipped before anything else happens to them. They are not read, not stored, not logged and not transferred:
- Passwords
- Card and account numbers, check digits (CVV)
- IBAN and account details
- Login and session tokens, one-time codes, two-factor codes
- Identity card and social security numbers
No value is written into input fields or included in processing. The only exception is the checkbox state (checked) of checkboxes within recognisable additional options — because the pre-selection is a property of the offer and not an input by you.
No transfer
- no network requests from Shopping Guard to its own or third-party servers
- no remote analytics, no cloud, no account
- no disclosure to third parties, no sale of data
- no advertising, no tracking, no counting pixels
- no evaluation of which shop is visited how often
Permissions and why they are necessary
| Permission | Reason |
|---|---|
storage |
Store the local history and your display setting. Without it, the comparison between two steps would be lost as soon as the page reloads. |
Access to all pages (<all_urls>) |
Shopping Guard does not know before loading whether a page is a checkout. Restricting it to known shops would be ineffective, because every shop uses its own paths — the test merchant, for example, uses ?cl=order, another /Bestellvorgang?wk=1. Shopping Guard only reads when an order process is recognisable. |
No further permissions are requested. In particular: no access to bookmarks, history, tab contents, cookies, downloads or the cache.
What the extension deliberately also captures
Two things are deliberately included because they are necessary for the purpose and represent only observations of the visible offer — not your input:
- Additional options. Whether a paid extra is already ticked is a property of the merchant's offer.
- Urgency wording. Whether a page advertises with scarcity or time pressure is recorded as an observation. Shopping Guard does not check whether the statement is true.
Storage period and deletion
Everything is stored exclusively locally. You can
- delete the local order history at any time via the extension icon ("Delete orders"),
- reset the session via the button in the panel,
- remove everything by uninstalling the extension.
When uninstalling, the browser deletes the extension's local storage. No copy exists anywhere else — not with us either.
In detail, so that it is verifiable:
| Storage location | Duration |
|---|---|
| Session document | until reset in the panel; expired sessions are removed on opening. At most 50 steps per purchase. |
| Order history | until deleted in the popup; at most 200 entries. |
| Settings (display, language) | until changed or uninstalled. |
| Panel state | is only read to decide whether the panel opens again; older than 15 minutes no longer counts. |
| Installation/update time | until uninstalled. |
Children
Shopping Guard is not aimed at children and knowingly does not collect data from children.
Changes
If this policy is changed, this happens with a new version of the extension and with an updated date at the top. Since no data is transferred, a change only affects the scope of local processing.
Contact
Information pursuant to § 5 DDG: see https://www.bow-agentur.de/impressum.
Technical verifiability
This policy is not just a promise. It can be verified in three places:
- Manifest: The extension requests exclusively the
storagepermission. There are nohost_permissions— access results solely from the content script pattern. - Bundle: In the shipped code,
eval,new Function,document.writeand inline event handlers occur zero times. The only external URLs are a comment with an MDN reference and the link in the panel footer. - Network: Shopping Guard contains no network requests. If you want to record this yourself: the browser's developer tools show no request originating from the extension during an entire purchase.