1. Data kept on your device
Dark Genius stores its settings in chrome.storage.local. These settings include the master switch, theme settings, automation times, saved hostname overrides, and page paths that you have paused. Saved page rules omit query strings and fragments.
To reduce bright flashes on later page loads, Dark Genius may keep a temporary appearance cache in chrome.storage.session. This cache contains a limited number of successfully converted hostnames and known native-theme page paths. These session hints omit query strings and fragments and disappear when the browser session ends.
Temporary tab or document identifiers can also be used to prevent duplicate insertion of the same styling helper after the browser background worker sleeps. These identifiers are session-only and do not contain page text, page titles, passwords, or query data.
2. Local appearance detection
Smart detection inspects original computed CSS colors and visible surface geometry within each authorized document to decide whether a website needs Dark Genius or already has an effective native dark appearance.
Dark Genius can work with accessible open-shadow components, supported gradients and embedded documents. The surrounding document's supported CSS filters can be considered when checking an embedded report so a page that is already visually dark is not darkened a second time.
Detection can re-run after relevant page changes so that a native dark theme applied after loading can be preserved. This processing stays in extension/page memory and does not create a page-content archive, capture screenshots, or inspect the drawn contents of canvas/WebGL visuals.
3. Website access
Dark Genius requests access to regular HTTP and HTTPS websites because automatic darkening is its primary function. Browser permission dialogs may describe this as permission to “read and change site data” because page styles are part of the website.
Dark Genius uses this access to inspect and adjust CSS, surface colors, borders, controls and compatible page elements. It does not add browser-history, cookie, local-file or account-management permissions.
4. Network behavior
The Dark Genius interface and executable JavaScript are bundled locally with the extension. Dark Genius does not use advertising, analytics, remotely hosted executable JavaScript, remote configuration, third-party AI services, API keys, or sign-in services.
To understand a website's appearance, the theme engine may read stylesheet and image resources that the page already references. Normal page-context requests remain subject to the browser's CORS and credential rules.
A narrowly scoped background helper may read a stylesheet from a host that the user has already authorized. It uses a GET request, omits credentials, rejects redirects and non-CSS responses, and applies response-size and duration limits. Dark Genius does not send page contents or settings to a Dark Genius endpoint.
5. Chrome Web Store data disclosure
For Chrome Web Store disclosure purposes, Dark Genius may handle the following categories strictly to provide its single-purpose dark-theme functionality:
- Website content: styling, computed colors, visible surface information and compatible page resources needed to determine and apply appearance changes.
- Web history / site information: locally stored hostnames and user-selected page paths used for site/page preferences and limited session appearance hints.
Dark Genius does not sell user data. It does not use or transfer user data for purposes unrelated to its single purpose, and it does not use user data for creditworthiness or lending decisions.
Dark Genius does not intentionally collect personally identifiable information, health information, financial/payment information, authentication credentials, personal communications, precise location, keystrokes, mouse movement logs, or advertising profiles.
6. Controls, export and deletion
You can pause conversion for the current page, disable a site, or turn off Dark Genius entirely. Resetting a site removes its saved override so global defaults apply again if browser access remains granted.
Uninstalling Dark Genius removes the extension's local and session storage maintained by Chrome. Files you explicitly exported remain wherever you saved them. Dark Genius does not maintain a server-side copy of those files.
7. Third-party component
Dynamic CSS processing uses a locally bundled, MIT-licensed Dark Reader API component. The executable component is included inside the Dark Genius package; Dark Genius does not load Dark Reader code remotely at runtime. Dark Genius is not affiliated with the Dark Reader project.
8. Changes to this policy
If Dark Genius changes how it handles user data, this policy will be updated so that the public disclosure continues to match the extension's actual behavior. Material privacy changes should accompany an updated effective date and, where required, updated Chrome Web Store disclosures.
Effective date: 18 October 2026.