Privacy Policy
The extension collects nothing. There are no analytics, no telemetry, no advertising, no accounts, and no third-party services. It never sends data to a server operated by us or anyone else, because there is no such server. Everything it handles either stays in your browser's local storage or is passed to the oxdm application running on the same computer.
The only destination data reaches
When you send a download to oxdm, the extension passes it to the desktop application on your own machine, by one of two routes:
- a WebSocket connection to
127.0.0.1(loopback: traffic never leaves the computer, and the extension binds to no other address); or - native messaging, where your browser launches the local
oxdm-native-hostprogram and exchanges messages with it over a pipe.
Both are local. The extension makes no other network requests of any kind.
What is sent to the oxdm application
Only for a download you are handing over, and only at that moment:
| Item | Why |
|---|---|
| The download URL | It is the file to fetch. |
| The page you came from (referrer) | Many hosts reject a download without it. |
| Cookies for that URL | So downloads behind a login work. Only cookies matching that one URL are read; your cookie jar is never enumerated or copied elsewhere. |
| Your browser's User-Agent | So the server sees the same client that loaded the page. |
| Suggested filename, file size, MIME type | Details the browser already reported about the download. |
oxdm's own handling of this data is governed by oxdm, not by this extension.
What is stored on your device
Three items, all in the browser's local extension storage, none synced to any account:
- Your settings: the pairing code (which contains the local port number and the access token for your own oxdm installation), transport choice, the auto-capture and Add-dialog toggles, and your chosen queue.
- Capture rules cached from oxdm: the file types, size threshold and skip lists you configured in oxdm, so the extension keeps working while oxdm is closed.
- A diagnostic log: the most recent 100 entries shown in Options → Logs, recording connection failures and downloads oxdm refused. These entries can include the URL of a download that was rejected. They are only ever written to local storage and displayed back to you. Clear them at any time with the Clear button on that page.
What the extension can see but does not collect
To place its download button and to offer "Download with oxdm" on right-click, the extension runs a content script on pages you visit. That script inspects link addresses in the page and any text you select, looking for downloadable URLs. This happens entirely inside your browser. Page content, browsing history, form input and selected text are never stored and never transmitted. A URL leaves the browser only when you act on it, or when auto-capture intercepts a download you started.
Permissions
| Permission | What it is for |
|---|---|
downloads | Notice a download starting, and cancel it so oxdm can take over. |
cookies | Read the cookies for the file being downloaded, so authenticated downloads succeed. |
nativeMessaging | Talk to the local oxdm host program. |
storage | Keep your settings and the diagnostic log. |
tabs | Identify the page a download came from, for the referrer. |
contextMenus | Provide the right-click entry. |
notifications | Tell you when oxdm refuses a download. |
| Access to all sites | Downloads can start on any site, so the extension cannot know in advance which ones to watch. This access is used only to detect download links and read cookies for a file you are downloading. |
Children
The extension is a utility with no accounts and no data collection, and is not directed at children.
Removing your data
Uninstalling the extension deletes everything it stored, since all of it lives in browser extension storage. The log can be cleared separately from Options → Logs, and clearing the pairing code from Options removes the stored token.
Changes
If this policy changes, the revised version is published on this page with a new date, and the change is visible in the project's public commit history.
Contact
Questions or concerns: open an issue on the project's GitHub repository.