ProvokeAI
Transparency

Browser permissions

What the current Provoke Deck beta asks Chrome for, and why.

ProvokeAI's goal is to request only the capabilities necessary for user-facing features. The permission set is reviewed before store submissions and when features change.

Current extension permissions

PermissionWhy Provoke Deck uses it
downloadsStart and monitor downloads explicitly requested through Provoke Deck, track completion or failure, and support retry/history features.
storageStore settings, favorites, history, queue state, duplicate-prevention state, diagnostics, and licensing state in Chrome storage.
tabsIdentify and organize supported tabs, react to navigation changes, and provide tab-related workflow features.
tabGroupsGroup supported album/file tabs to make large browsing sessions easier to manage.
scriptingSupport page-level extension behavior where browser scripting APIs are required for the user-facing feature.
clipboardWriteCopy user-selected links or values to the clipboard when the user invokes a copy feature.
alarmsWake persistent download/retry work and periodically refresh license status without requiring the popup to stay open.

Cookies permission: not requested

Provoke Deck does not request Chrome's cookies permission and does not use the Chrome Cookies API to read, list, edit, or delete cookie values.

One supported-site preview request uses the browser's existing credentials for that third-party site. As a result, cookies already belonging to that site may accompany that request. Provoke Deck does not extract those cookie values and does not send them to ProvokeAI.

Website access in the current beta

The current beta manifest matches HTTPS pages broadly using https://*/*. This allows the extension to detect whether the current page belongs to a supported workflow and to respond to supported-site navigation.

Important: broad host access means Chrome can technically expose page context across HTTPS sites even though Provoke Deck is designed to act only on supported pages. ProvokeAI is reviewing this scope before the next Chrome Web Store submission and intends to narrow permissions wherever the product can retain its existing functionality with less access.

This page will be updated if the manifest permission set changes.

Local processing and network traffic

Page content used for supported-page features is processed locally in the browser. Provoke Deck's licensing service receives the limited activation and device information described in the Privacy Policy. Downloaded file contents are not sent to ProvokeAI as part of licensing.

Permission minimization

Before a public store submission, ProvokeAI reviews each required and host permission against the current feature set. Permissions are not intended to be requested merely for possible future features.

If you have a question about a permission, contact support@provokeai.com.