Privacy policy
The extension is a transport. It moves a diagnostic bundle you click from the page it sits on to the analyzer address you configured, and it opens the result. It has no server of its own, collects no analytics, and sends nothing to the developer.
What the extension does with your data
- Reads pages you nominated. On the hosts you list under Trigger domains — and only those — it scans the page's links to find diagnostic bundles and places a button next to them. What it reads is used on the spot and kept nowhere.
- Downloads the bundle you click. The request uses your browser's existing session with that site, because a QNAP NAS hands out diagnostic dumps only to a signed-in user. The extension never reads, stores or forwards your credentials or cookies; the browser attaches them, as it does for any request you make yourself.
- Uploads that bundle to your analyzer. To the address you typed into Options, and to no other destination. The bundle is held in memory for the duration of the transfer and not written to disk by the extension.
- Stores your three settings — analyzer address, trigger domains, maximum bundle size — in your browser profile's extension storage. If you have browser sync enabled, your browser syncs them the same way it syncs your other settings. Nothing else is stored.
What it does not do
| Practice | Applies? |
|---|---|
| Analytics, telemetry, usage statistics, crash reporting | None |
| Advertising, tracking, profiling, fingerprinting | None |
| Selling or sharing data with third parties | Never |
| Remotely loaded or executed code | None |
| Any server operated by the developer receiving your data | None — unless you choose the public demo, below |
| Reading pages you have not nominated | Not possible — see below |
Site access
The extension is installed with no access to any website. Broad access appears in the manifest as an optional permission only, because the hosts involved cannot be known in advance: every NAS sits on its own private address, and analyzer deployments sit on private URLs inside customer networks.
Access is obtained one way only: you type your hosts into Options, click Grant access, and your browser asks you to approve exactly those origins. There is no static content script in the package — the script that adds the button is registered at runtime for granted origins alone, so it cannot run on a site you have not approved. Options shows what is granted and can revoke it, as can your browser's own extension settings.
What is inside a diagnostic bundle
A QNAP diagnostic export describes a real machine. Expect hostnames, serial numbers, IP and MAC addresses, account names, share and volume names, installed applications and system logs. It is not anonymous data, which is why the extension sends it to one destination only: the analyzer you named.
sdlv.qnap.net.pl), then the bundle you click is uploaded to a server we
operate, and we can see it. The demo exists for evaluation, with synthetic sample
bundles provided for exactly that purpose. Uploaded sessions there are rate-limited
per address, expire on their own, and are not used for any purpose beyond letting you
try the tool — but a public demo is still the wrong place for a customer's data. Use
your own instance for real work.
Your own analyzer instance
When the analyzer address is your own deployment, the bundle goes from your browser to your server. No one else is involved, including us. How that instance retains, protects and deletes what it receives is governed by its own configuration and by whoever operates it.
Retention and removal
- The extension keeps only your settings. Uninstalling it removes them.
- Bundles are not retained by the extension at all — it holds one in memory only while transferring it.
- To remove something you uploaded, delete the session in the analyzer that received it. On the public demo, sessions expire by themselves; write to the contact address below if you need one removed sooner.
Children
This is a systems-administration tool. It is not directed at children and collects no data from them.
Changes
Material changes will be reflected here with a new date and a version bump in the extension. The store listing links to this page, so the current policy is always the one you can read.
Contact
Questions, or a removal request: use the developer contact address published on the extension's store listing.