Privacy Policy

JSController – JavaScript Execution Control

This Privacy Policy describes how JSController is designed to handle information when you use the Chrome extension. JSController helps users inspect JavaScript resources on websites and choose which scripts to allow or block.

1. Information Processed

To provide its core functionality, JSController may process website addresses, JavaScript resource URLs, and user-defined script-blocking preferences within your browser. Such information is used to identify scripts and apply your chosen rules.

2. Local Storage

JSController is designed to store user-defined script control rules and preferences locally in the browser using Chrome extension storage. These settings allow rules to persist between browsing sessions.

3. Data Collection and Transmission

JSController is intended to operate without sending script lists, browsing history, or user-defined blocking rules to the developer's servers. It does not require users to create an account.

4. Browsing History

JSController may inspect the current website and its JavaScript resource URLs to perform script control. It is not designed to compile or transmit a browsing history to the developer.

5. Analytics, Advertising, and Sale of Data

• No analytics or user-behavior tracking is intended to be included.
• No advertising functionality is intended to be included.
• User information is not intended to be sold or shared for advertising purposes.

6. Browser Permissions

JSController may use Chrome permissions such as activeTab, scripting, storage, sidePanel, and declarativeNetRequest, as well as website access, to inspect JavaScript resources, display its control interface, save preferences, and apply blocking rules. Website access is used to support user-directed script control across sites.

7. User Control

Users can manage their script-blocking preferences through the extension interface. Users may also remove the extension through Chrome's extension management page.

8. Security Considerations

Blocking JavaScript can affect website appearance, sign-in flows, and functionality. Users should review their rules when a website does not behave as expected. Website and script URLs may contain sensitive information, so exported or shared diagnostic information, if any, should be reviewed before sharing.

9. Changes to This Policy

This policy may be updated if the extension's functionality or data-handling practices change. The latest version will be made available on the extension's published privacy policy page.

10. Contact

For privacy-related questions, please contact the developer using the support contact information published on the JSController Chrome Web Store listing.