Dusk for Docs

Privacy Policy

Effective August 1, 2026

Dusk for Docs never collects, reads, stores, or transmits the contents of your Google documents. It has no analytics, advertising, tracking, accounts, or developer-operated servers.

Information Dusk does not collect

Dusk does not collect or transmit document text, titles, comments, suggestions, images, account details, browsing history, visited URLs, cookies, analytics, diagnostics, identifiers, financial information, health information, or location. No document content is made available to the developer or any third party.

Settings stored by Chrome

Dusk stores only the preferences needed for its appearance features: enabled state, system appearance mode, workspace theme, paper mode, glare reduction, and text contrast. These preferences are saved using chrome.storage.local and remain in the current device's Chrome profile. They are not synchronized through Chrome Sync or sent to Dusk's developer or any third party.

The “Disable on this tab” state exists only in the current page's memory and is discarded when that page reloads or closes.

Google Docs page access

Dusk runs only on https://docs.google.com/document/*. This access is used to apply local CSS and appearance attributes to Google Docs. Dusk does not inspect, copy, parse, save, or transmit document content. The popup checks whether the active tab is Google Docs only to enable its tab-specific recovery control; that result is not retained or transmitted.

Dusk also checks a fixed, allowlisted set of Google Docs interface elements—such as the toolbar, editor workspace, paper canvas, and dashboard shell—to detect when an interface change may require a Dusk update. It checks only whether those elements exist. It does not read text, titles, HTML content, document canvas pixels, or account information. Results remain in page memory and are not stored or transmitted.

Network activity and third parties

Dusk makes no network requests to developer-controlled services or third parties. It does not sell, rent, share, or transfer user data, and it does not use data for advertising, profiling, credit decisions, or unrelated purposes.

Selecting “Report an issue” opens Dusk's public GitHub issue form in a new tab. The link includes the Dusk version and, when Dusk detects missing interface hooks, only the affected interface area and friendly hook labels such as “editor toolbar”—never selectors or document content. Dusk sends nothing automatically. Information reaches GitHub only if the user chooses to complete and submit the form. The form warns users not to include document contents, account information, private URLs, or other personal data. Information submitted to GitHub is handled under GitHub's own privacy terms.

Retention and deletion

Device-local appearance preferences remain in Chrome storage until the user changes or resets them, clears the extension's site data, or removes the extension. The popup's Reset settings control restores Dusk's defaults.

Security and limited use

Dusk is a Manifest V3 extension with no remotely hosted code. Its use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.

Policy changes

If Dusk's data practices materially change, this policy and its Chrome Web Store disclosures will be updated before those practices are released.

Contact

Privacy questions and support requests can be submitted through the Support section of Dusk for Docs on the Chrome Web Store.