Privacy Policy – Q Chrome Extension

Prominent Privacy Disclosure (Built for Trust)

Q is a privacy-first browser automation extension designed to help you orchestrate workflows directly in your browser with a minimal, purpose-limited data footprint. Q is engineered to be safe by design: it does not sell, rent, or share your data with anyone.

To deliver automation features you explicitly use, Q may access and process:

Current tab URL Page title On-page content required for automation Extension settings & preferences User-provided inputs (prompts/notes)

Q’s philosophy: collect the minimum, process locally by default, and never use data for anything unrelated to automation.

Affirmative Consent

If a feature ever requires data handling beyond local processing (for example, optional sync in a future release), Q will clearly disclose what is involved before anything happens and will require your affirmative opt-in. You remain in control: you can disable features at any time or uninstall the extension.

Single purpose description

Browser automation.

Q is narrowly focused on orchestrating user-initiated automation workflows inside Chrome—no unrelated tracking, no ad tech, no hidden collection.

Permission justifications

• activeTab — needed for automation orchestration on the page you are actively using.
• scripting — needed to run automation services and actions you explicitly trigger.
• notifications — needed for messaging about automation status, results, and important workflow events.
• storage — needed for local file/storage of project generations, templates, settings, and automation state.
• tabs — needed for automation services that coordinate actions across tabs you control.
• cookies — needed for automation services when interacting with sessions required for your workflow.
• webNavigation — needed for automation services that respond to navigation events as part of your workflow.
• Host permissions — needed for automation services on the sites you choose to automate.

Q does not use permissions to collect unrelated browsing history. Access is purpose-limited and feature-driven.

No. Q does not use remote code. All JavaScript/Wasm required for core functionality is packaged with the extension.

Q does not load executable scripts from external sources, does not inject remote modules, and does not rely on eval() to execute downloaded code.

Data categories

The Chrome Web Store privacy form lists common categories. Q’s posture is “do not collect” wherever possible, and “process locally” when a feature requires page context.

• Personally identifiable information: not collected by default.
• Health information: not collected.
• Financial and payment information: not collected.
• Authentication information: not collected (Q does not ask for passwords or credentials).
• Personal communications: not collected.
• Location: not collected.
• Web history: not collected as a stored dataset. Q may read the current page URL/title only to perform an automation you initiate.
• User activity: not collected for tracking. Q may observe interactions only as required to execute the automation action you invoked.
• Website content: processed only to the extent required for the user-facing automation feature you choose. Q does not publicly disclose website content.

I certify the following disclosures are true:

• Q does not sell or transfer user data to third parties, outside of approved use cases.
• Q does not use or transfer user data for purposes unrelated to its single purpose (browser automation).
• Q does not use or transfer user data to determine creditworthiness or for lending purposes.