Privacy Policy — Prax9 - Dark Control
Last updated: September 9, 2026
Prax9 - Dark Control ("Prax9", "the Extension") is a Chrome extension that applies and customizes dark themes on websites. This Privacy Policy explains what information the Extension accesses, how it is used, where it is stored, and whether it is shared.
1. Local-first operation
Prax9 is designed to perform its primary work locally in the browser. The Extension does not operate a developer-controlled analytics server, advertising system, tracking service, or cloud database for Extension usage data. No account is required.
Prax9 does not sell user data and does not use user data for advertising, profiling, creditworthiness, lending, or purposes unrelated to the Extension's dark-mode and customization features.
2. Website access and website content
The Extension runs on webpages so it can apply dark-mode styling. To do this, it may locally inspect and process information related to a page's visual presentation, including CSS rules and stylesheets, colors, backgrounds, DOM structure, element tags, classes, attributes, selectors, computed styles, theme information, and the current website URL or hostname.
This processing is used to determine how the page should be visually transformed. Prax9 does not intentionally collect webpage text, messages, passwords, payment information, or form contents as part of normal dark-mode operation. Website information processed for dark-mode rendering is not automatically sent to the developer.
3. Website URLs and domains
Prax9 processes the current URL and hostname so it can apply the correct per-site settings, exclusions, custom CSS, and built-in site fixes. Domains may be stored locally when they are associated with user-created site settings or exclusions.
Prax9 does not create or transmit a general browsing-history database to the developer or to an analytics service.
4. Extension settings
Prax9 stores Extension preferences locally using Chrome extension storage. Stored information may include:
- whether dark mode is enabled;
- brightness, contrast, saturation, warmth, dimming, and intensity settings;
- rendering and theme preferences;
- interface language;
- per-site preferences and exclusions;
- custom CSS and saved element fixes;
- scheduling preferences;
- optional developer-tool settings and local diagnostic events.
These settings are stored in the user's browser and are not automatically uploaded to the developer.
5. Location information
Location access is optional. Prax9 requests location only when the user explicitly chooses the sunrise/sunset scheduling feature and selects the option to use the current location.
When permission is granted, the Extension obtains latitude and longitude to calculate local sunrise and sunset times. The coordinates may be stored locally so the schedule can continue to work. Location information is not automatically transmitted to the developer, sold, used for advertising, or used to track the user.
6. Scheduling information
If automatic scheduling is enabled, Prax9 may locally store the selected scheduling mode, start and end times, sunrise/sunset status, and latitude/longitude when location-based scheduling is used. This information is used only to decide when dark mode should be enabled or disabled.
7. Optional local diagnostics and telemetry
Prax9 includes optional troubleshooting and developer tools. Local telemetry is disabled by default.
If the user explicitly enables local telemetry, the Extension may keep a small local event log with event timestamps, Extension event names, the hostname on which an event occurred, and technical information related to dark-mode operation. The log is stored only in Chrome extension storage and is not automatically uploaded to the developer or an analytics service.
Disabling local telemetry clears the locally stored telemetry event log.
8. Element Picker and user interaction
Prax9 may provide an optional Element Picker for creating per-site visual fixes. When the user explicitly activates this tool, the Extension may locally process the selected element and generate information such as a selector, classes or attributes, a selected fix action, or custom CSS.
Prax9 does not continuously record mouse movements, clicks, keystrokes, or general browsing activity. Element-selection information is processed only as needed for the feature and may be stored locally if the user chooses to save a fix.
9. Diagnostics export and clipboard access
The Extension can generate a diagnostics bundle when the user explicitly requests it. The bundle may include Extension version, current page URL, current hostname, page title, browser user-agent information, basic document state and statistics, root-page classes or theme attributes, dark-mode runtime state, saved element-fix information, and local diagnostic events if local telemetry is enabled.
The Extension copies this information to the user's clipboard only after a user action. It does not automatically send the diagnostics bundle to the developer or any third party. Users should review diagnostic information before sharing it because it can include the current page URL and title.
Prax9 uses clipboard-write access only for user-requested copy actions. It does not continuously monitor the clipboard and does not use clipboard access to collect clipboard contents.
10. Settings import and export
Prax9 may allow users to export or import settings. Exported settings can include Extension preferences, per-site configurations, schedules, exclusions, custom CSS, and related local configuration. Import and export are initiated by the user and processed locally. Prax9 does not automatically upload exported settings to the developer.
11. Stylesheet and external-resource requests
To correctly process website styling, Prax9 may request stylesheet resources referenced by webpages or Extension-provided site-fix resources. Requests for webpage stylesheets are made from the user's browser to the website or content-delivery network hosting that stylesheet.
Where Prax9 performs its own stylesheet fetch, it is configured to omit user credentials. Extension settings, location coordinates, local telemetry logs, and diagnostic bundles are not attached to these requests by Prax9.
12. Favicons
Prax9 may display website favicons in its per-site management interface. The website domain is used through browser-provided functionality to display the relevant icon and make saved sites easier to identify.
13. Information Prax9 does not intentionally collect
Prax9 is not designed to collect names, physical addresses, email addresses, phone numbers, government identifiers, passwords, authentication credentials, health information, financial or payment information, private communications, credit information, or advertising identifiers.
14. Data sharing and sale
Prax9 does not sell user data. The Extension does not transfer user data to advertisers, data brokers, or analytics providers for advertising or profiling.
Prax9 does not use or transfer user data for purposes unrelated to its single purpose of providing dark mode, visual customization, scheduling, and related user-requested troubleshooting features. It does not use or transfer user data to determine creditworthiness or for lending purposes.
15. Remote code
Prax9 does not download or execute remote JavaScript or WebAssembly code. Executable code required to operate the Extension is included in the Chrome Web Store package. Network requests for website styling resources are not used as remotely hosted executable Extension code.
16. Data storage and retention
Extension preferences and related information are stored primarily in Chrome extension storage. Local data may remain until the user changes or removes the relevant setting, clears or resets data using the Extension, disables local telemetry, removes site-specific settings or fixes, or uninstalls the Extension.
Prax9 does not maintain a separate developer-controlled cloud database containing this Extension data.
17. Security
Prax9 minimizes data handling by performing its main functionality locally in the browser. No software can guarantee absolute security, but the Extension is designed to avoid unnecessary transmission of Extension data and to keep settings and diagnostics on the user's device unless the user explicitly chooses to copy, export, or share them.
18. User choices and controls
Users can control how Prax9 operates by enabling or disabling dark mode, configuring or excluding individual sites, editing or removing custom CSS and element fixes, choosing whether to use location-based scheduling, choosing whether to enable local telemetry, resetting settings, or uninstalling the Extension.
Optional features such as location-based scheduling and local telemetry are not required for basic dark-mode functionality.
19. Children's privacy
Prax9 is a general-purpose browser customization tool and is not designed specifically to collect personal information from children. The Extension does not knowingly operate a system for collecting personal information from children.
20. Changes to this Privacy Policy
This Privacy Policy may be updated when Prax9's functionality, permissions, or privacy practices change. Updated versions will be published at the same Privacy Policy URL with a revised "Last updated" date.
21. Contact
For privacy questions or feedback, use the Prax9 contact form.