Security &
privacy policy.

01

What Dusk processes

Dusk processes the minimum information needed to provide its dark-mode functionality:

• Global settings. Whether global dark mode is enabled, whether to preserve native dark themes, and the selected page brightness.
• Per-site settings. An on or off preference explicitly chosen for a website, stored using the website hostname as the key. Dusk does not store full page URLs or a general browsing-history list.
• Page visual information. Background colors, color-scheme information, and visual media such as images, video, canvas, SVGs, embeds, and some background media are checked locally while the page is styled.

Page visual information is temporary browser-memory data. It is not copied into extension storage, sent to a server, or shared with a third party.

02

How that information is used

The information above is used only to apply or remove the effect on the current website, remember choices, apply a global preference, avoid reprocessing native dark themes, preserve media colors, and display the extension’s current state.

Dusk does not use this information for advertising, profiling, sale, credit decisions, or any purpose unrelated to the extension’s single user-facing function.

03

Storage, retention, and deletion

Settings are stored locally through chrome.storage.local. They are not synced to a developer server. They remain until you change them, clear the extension’s data, or uninstall Dusk.

You can delete settings by resetting a site in the popup, clearing Dusk’s extension data from Chrome’s extension management page, or uninstalling the extension.

04

Permissions explained

storage

Saves global and per-site settings locally on the device.

http://*/* and https://*/*

Allows the packaged content script to run on regular webpages the user visits so it can apply dark mode, detect native dark themes, and protect media colors.

These permissions are used only to provide Dusk’s dark-mode functionality. Chrome internal pages, the Chrome Web Store, and some built-in PDF pages remain protected by the browser.

05

Security practices

• The extension ships its executable logic with the package and does not load remote code.
• There is no account database, analytics pipeline, advertising SDK, or external synchronization service.
• The extension uses a restrictive extension-page content security policy and stores preferences locally.
• Security and privacy changes are reflected in this policy and its effective date before the behavior expands.

06

Chrome Web Store Limited Use

Dusk’s use of user data follows the Chrome Web Store User Data Policy and Limited Use requirements. Data is processed only to provide the single user-facing feature described in the listing. Dusk does not use data for personalized advertising, sell or transfer data to third parties, or allow humans to read users’ webpage data.

07

Changes and contact

If data practices change, this policy and its effective date will be updated, with any required notice provided in the Chrome Web Store listing or the extension interface.

For questions or a responsible security report, contact the developer through the Dusk issue tracker. Please do not include private browsing data in a report.