Permissions

Permission justifications (paste into the Web Store form)

Single purpose: Let the user control and reshape web pages by chatting with an AI assistant that runs in their browser with their own API key.

Host permissions (http:///, https:///) The user asks qozu to act on any website: restyle it, read a table, fill a form. We cannot know in advance which sites, so access is requested for all http(s) pages. The same access lets the extension call the AI provider the user chose (for example api.openai.com, api.anthropic.com, generativelanguage.googleapis.com, or the user’s own compatible endpoint) directly from the extension. qozu reads or changes a page only when the user’s request needs it, and nothing from a page is sent to a qozu server (there is none). Page content goes to the user’s chosen provider only as part of a task the user asked for.

debugger A powerful permission, used only on pages that cannot be read from their HTML: reading Chrome’s accessibility tree of app-style pages and clicking or typing on those elements. It is attached to a tab only while qozu is working on that tab and detached after 20 seconds idle. It is never attached in the background to tabs the user did not ask about. Chrome shows its standard “debugging this browser” bar while it is attached. In “Asks first” mode each of these actions needs the user’s approval. Chrome does not allow this permission to be optional.

scripting To inject the extension’s own page-reading and click/type code, and the styles (CSS) for site changes the user asked for, including saved changes re-applied on later visits. Scripts written by an AI model are never run.

storage To keep the user’s API key, provider settings, saved site changes, recorded recipes and panel state in the browser profile. The key is stored unencrypted in the extension’s local storage and is sent only to the provider the user chose.

sidePanel The chat interface is the browser side panel.

alarms To run the user’s scheduled jobs (for example a price check) and send a daily digest.

offscreen To read the browser’s light/dark colour setting so the panel and toolbar icon match it. No page content is involved.

Remote code: No. The extension does not load or run any code from the internet. All of its code, including the AI provider libraries, is in the package. The model’s answers are used only as text and as inputs to the extension’s own tools; the only thing it can write to a page is CSS the user asked for. Model-written JavaScript is never executed.

Data usage disclosures (form answers)