Extension Privacy Policy
The short version
- The extension collects nothing. No analytics, no trackers, and no server of ours that any of your data passes through.
- It only talks to your own computer. It hands downloads to the Pyxils app running on the same machine over a local connection — nothing is sent to us or any third party.
- No ads, no sponsored content, ever — not now, not in any future version. There is nothing in this extension to show an ad in.
- Your extension settings stay on your machine, in your browser's own local storage, until you remove the extension.
1. Scope
This policy covers the Pyxils Download Manager browser extension — the Chrome, Edge, and Firefox builds submitted to each browser's extension store. It does not cover the separate Pyxils desktop application for Windows, which the extension hands downloads to but which is installed and updated independently of any browser store and is governed by its own privacy notice.
2. What Pyxils does
Pyxils is a download manager. The browser extension notices when you're about to download a file or are watching a video, and offers to send that download to the Pyxils desktop app instead of your browser's own downloader, so it can be split across multiple connections, paused, resumed, and tracked in one place.
That's the entire purpose of the extension. It does not track what you browse and does not change what a page says or does. The only thing it adds to a page is the small button on videos, and on a page with no download or video it does nothing at all.
3. Data the extension can access
Browser extensions must declare permissions up front, which is why the list below looks broader than "downloads." Here is what each one is actually used for, and — the part that matters — whether any of it ever leaves your device.
| Permission | What it's for | Leaves your device? |
|---|---|---|
| downloads | Catch a download the browser is about to start, so it can be handed to the Pyxils app instead. | Never |
| webRequest | Read the headers (file type, size, filename) of requests already loading, to recognize downloadable files and video streams. | Never |
| cookies | Read the sign-in cookies for the one page you choose to download from, so files behind a login still work. | Never — passed only to the Pyxils app on the same machine |
| nativeMessaging | The local connection to the Pyxils app itself. | Never — this is the on-device channel |
| tabs | Know which tab a download or video belongs to, so the on-page button and notifications appear in the right place. | Never |
| storage | Remember your extension settings (which file types to catch, on/off toggles) between browser sessions. | Never |
| contextMenus | Add a "Download with Pyxils" entry to the right-click menu. | Never |
| host permissions (all sites) | Because you can start a download from any site, not a fixed list, the extension needs permission to check any page — it only acts when a download or video is actually present. | Never |
4. The extension, permission by permission
In more detail, in case you want it:
- The hover button on videos is drawn directly on the page by the extension's content script. Detecting where to draw it happens entirely in your browser; nothing about the page is sent anywhere to make that decision.
- Cookies are only read at the moment you start a download, only for the exact address you're downloading from, and are handed straight to the Pyxils app over the local native-messaging connection so it can complete a login-gated download on your behalf. They are discarded once that download starts.
- Settings (like which file types Pyxils should catch) live in your browser's local extension storage — the same mechanism every extension uses for its own preferences. Uninstalling the extension clears it.
5. The desktop app, briefly
The extension's only job is to catch a download and hand it to the Pyxils app running on your computer, over the local connection described in the table above. What the app itself does with that download — and what data practices it has — is outside what this page covers, since the app isn't distributed through a browser store and can change on its own schedule. The app has its own separate privacy notice.
6. What we never do
- No analytics, telemetry, or crash reporting that leaves your device.
- No ads or advertising trackers — not now, not in any future version of this extension. This is a permanent commitment about the extension specifically, independent of anything the separate desktop app does.
- No selling, renting, or sharing data with third parties — there is nothing collected to sell.
- No logging of your browsing history or the sites you visit.
- No account or sign-in required to use the extension.
7. Where your extension data lives
The only thing the extension itself stores is your extension preferences (like which file types to catch), kept in your browser's own local extension storage — the same mechanism every extension uses for its own settings. Nothing here is synced to us or to any cloud service, and removing the extension clears it.
Your downloads themselves, and any history of them, are kept by the desktop app on your computer, not by the extension — see its own privacy notice for how that's stored and controlled.
8. Children's privacy
This extension is not directed at children and is not knowingly used to collect information from anyone, of any age — there is no data collection to speak of. If you believe a child has been affected in a way this policy doesn't account for, contact us using the details below.
9. Changes to this policy
If this policy changes, the version number and effective date at the top of this page will change with it. Meaningful changes — anything that adds a new kind of data collection — will also be noted in the extension's store listing.
10. Contact
Questions about this policy or how the extension handles data can be sent to info@pyxils.com.