[CRO-MUXON] Privacy Policy

Last updated: 2026-08-31

Cro-Muxon is a keyboard-driven window-tiling workspace manager for Chrome. This policy explains what data the extension touches and, more importantly, what it does not do with it.

Summary

Cro-Muxon does not collect, transmit, sell, or share any data. Everything it stores stays on your device, in your own browser's local extension storage. The extension makes no network requests of its own by default. The one opt-in exception is the URL queue's "Prefetch queue previews" setting (off unless you turn it on, and asks permission the first time): when enabled, fetching a queued link's title/thumbnail is a direct request from your own browser straight to that link's own destination — never through a server of ours, and never carrying anything besides the URL itself.

What Cro-Muxon stores, and where

All data is kept in Chrome's chrome.storage.local, which is private to your browser profile and is never synced to a server or sent anywhere:

• Workspace layout — the tree of split panes you create, the window IDs belonging to each workspace, and the screen bounds of each pane, so the extension can restore and re-tile your layout.
• Tab titles and URLs of windows you have chosen to manage — used only to show the pane picker (the on-screen list of your workspaces) and to restore a workspace's tabs when you save/load a layout to a local JSON file.
• The ID of your last-focused window — used to highlight the correct pane when you open the picker.
• URL queue entries — links you've explicitly queued (via the right-click menu or a keyboard shortcut), each with its own URL and, if "Prefetch queue previews" is on, a title/thumbnail/short description fetched directly from that link. Removed the moment you use or discard the entry.

None of this is readable by other extensions, other websites, or by us — it lives entirely inside your own browser installation.

Permissions Cro-Muxon requests, and why

• tabs — to read tab titles/URLs for the windows you manage, and to open, switch, or navigate tabs when you use the pane picker.
• storage — to save your workspace layout locally, as described above.
• sidePanel — to host the extension's dashboard UI.
• system.display — to read your screen's usable work area so panes can be tiled to fill it correctly (no display content is read, only geometry).
• history / bookmarks — to power the :open command's autocomplete suggestions when you're typing a URL to navigate to. Searches are performed locally via Chrome's own history/bookmarks APIs; nothing is sent anywhere.
• alarms — to keep the extension's background service worker alive during multi-step window operations (e.g. splitting a pane); this does not read or store any user data.
• clipboardRead / clipboardWrite — to support copying a pane's URL and pasting it into another pane directly from the dashboard (the y / p shortcuts). Clipboard contents are only read at the moment you press p, are used solely to navigate the pane you're pasting into, and are never stored or sent anywhere.
• contextMenus — to add Cro-Muxon's own items (split, open in a new workspace, yank to queue, and so on) to Chrome's right-click menu.
• downloads — to write a workspace layout to a JSON file on your own device when you use Export.
• Optional: access to http/https pages — not granted at install, and never requested unless you turn on "Prefetch queue previews" in Settings, at which point Chrome shows its own permission prompt. Used only to fetch a queued link's own page directly, for its title/thumbnail/description — declining, or leaving the setting off, means nothing is ever fetched.

Local export/import

If you use the Save/Load-to-disk feature, your workspace layout (pane structure, bounds, and tab URLs) is written to or read from a JSON file you explicitly choose on your own filesystem. This file is created and read only on your device — Cro-Muxon never uploads it anywhere.

Third parties

Cro-Muxon does not use analytics, advertising, or crash-reporting services, and does not communicate with any server operated by us. The one exception is the opt-in "Prefetch queue previews" setting described above: when it's on, fetching a queued link talks directly to that link's own destination, the same as visiting it in a tab would — never to a third-party server acting on our behalf.

Changes to this policy

If this policy changes, the "Last updated" date above will be revised and the new version will be published at this same location.

Contact

Questions about this policy can be sent to:

← Back to Cro-Muxon · [T]heme