Privacy Policy — qmpo

Last updated: 2026-03-22

Overview

qmpo is a directory:// URI scheme handler that opens directories in your file manager. It consists of three components:

qmpo — the URI handler that receives directory:// URIs and opens them in your file manager
qmpo-lau — a registration tool that sets up qmpo as the system's protocol handler
Chrome Extension — converts file:// links to directory:// on web pages

All components are open-source under the MIT License.

Data Collection

qmpo does not collect, transmit, or store any personal data. Specifically:

No data is sent to any external server, analytics service, or third party.
No telemetry or tracking of any kind is included in any component.
No user accounts or authentication are required.

Data Stored Locally

qmpo (URI handler)

Configuration — qmpo reads a local config.toml file for security settings (UNC server allowlist). This file is read-only and managed by the user or system administrator.
Log file (development builds only) — when built from source with --features logging, qmpo writes an operational log to the local filesystem. Pre-built binaries distributed via GitHub Releases, AUR, and Nix do not include this feature; no log file is created.

Chrome Extension

User preferences — the extension uses chrome.storage.sync to persist your settings (enabled/disabled state, folder-icon indicator toggle, and domain allowlist/blocklist). This data is synced across your Chrome profile by Chrome's built-in sync mechanism and is never sent to any third-party service.

qmpo-lau (registration tool)

qmpo-lau does not store any data. It registers the directory:// protocol handler with the operating system (Windows Registry, macOS Launch Services, or Linux XDG MIME) and then exits.

External Programs

qmpo invokes the following system programs to open directories in your file manager. No data is sent to remote services through these invocations.

Platform	Programs invoked
Windows	`explorer.exe`
macOS	`open`
Linux	`xdg-open`, `dbus-send` (for file selection)

The Chrome Extension triggers the directory:// protocol handler registered by qmpo-lau, which in turn launches the qmpo binary on your machine.

Network Access

qmpo makes no outbound network connections, with one exception:

Windows UNC path validation — when a directory:// URI points to a UNC network path (e.g., \\server\share), qmpo performs a local DNS lookup to verify that the server resolves to a private IP address. This prevents NTLM credential leaks to rogue external servers. The DNS query is handled by the operating system's resolver; no custom network requests are made.

Chrome Extension Permissions

Permission	Why it is needed
`storage`	Save and sync user preferences across devices.
`activeTab`	Present in the manifest for forward compatibility. It is not used by the current version of the extension and does not cause any additional data to be collected or transmitted.
`tabs`	The current implementation may temporarily open a background tab to trigger the `directory://` protocol and then automatically close that tab. No page content from these tabs is collected or transmitted.

Changes to This Policy

If this policy is updated, the changes will be published at this URL and the "Last updated" date above will be revised. Significant changes will also be noted in the release notes.

Contact

For questions or concerns about this policy, please open an issue at github.com/tagawa0525/qmpo/issues.