Privacy policies for published browser extensions.
Last updated: 2026-10-08 · Applies to Duckout v1.x (panic-hide)
Duckout collects nothing, sends nothing, and has no servers. It moves your tabs around inside your own browser. That is all it does.
No personal data of any kind. Specifically, Duckout does not collect, transmit, sell, share, or retain:
There is no account, no sign-in, and no telemetry.
Duckout requests exactly two permissions:
| Permission | Why it is needed |
|---|---|
tabs |
To move a tab into a background window and move it back. Hiding a tab is a tab operation, so this permission is the feature. |
storage |
To remember your settings, and to remember which tabs are currently hidden so they can be restored. |
Duckout requests no host permissions and registers no content scripts. Under
Chrome’s extension model that means it has no ability to read or modify the
contents of the pages you visit — not as a policy promise, but as a limit of what
it is installed with. You can verify this yourself on chrome://extensions: the
permission list shows tab and storage access and nothing about site data.
Everything stays on your device, in Chrome’s own extension storage:
chrome.storage.sync: the on/off preferences
(mute-while-hidden, show-decoy, branded placeholder), plus two things only if you
type them in — the decoy page address, and your “Hide my sites” list. Honest
caveat: if you have Chrome Sync enabled, Chrome itself syncs this storage area
across your signed-in Chrome installations via your Google Account. That transfer
is performed by Chrome, not by Duckout, and it carries only those settings —
never your browsing history, the tabs you have open, page titles, or page
content. Turn off Chrome Sync if you would rather your settings stayed on one
machine.chrome.storage.session, which
Chrome clears when you quit the browser. It holds tab IDs and positions so a
hidden tab can be put back; it is never transmitted anywhere.Uninstalling Duckout removes both.
None. No analytics provider, no crash reporter, no ad network, no CDN, no external fonts, no remote code. Duckout makes no network requests at all.
Duckout is designed for shoulder-surfing: someone glancing at your screen in an office, a café, a classroom, or a shared room.
It does not protect you from network monitoring, your employer’s IT or device management, your internet service provider, software installed on your computer, or your browser history. Duckout has no ability to affect any of those, and you should not rely on it as though it did.
Duckout is not directed at children and collects no data from anyone, including children under 13.
Material changes will be published here with a new “Last updated” date before the build they describe is released.
Questions about this policy: open an issue on the project’s public repository, or use the support link on the Chrome Web Store listing.