Draft extension
What Draft can access
The exact permissions and Draft-site access in the packaged Chrome Web Store extension, explained before you install it.
Effective package v1.0.2 verified September 21, 2026 · Manifest V3
Chrome permission model
What Chrome asks for—and when
Install-time · required
activeTabAccess the tab you explicitly use with Draft- Required when Draft is installed. It gives Draft user-gesture-scoped access to the current tab after you explicitly invoke the extension, including the source-tab access and URL/title metadata needed for the capture handoff.
Not install-time · optional
pageCaptureCreate the high-fidelity page archive- Not requested at install. When you initiate a capture and this permission is not already granted, Draft requests pageCapture with chrome.permissions.request. If granted, it creates the MHTML archive. Chrome may show the broad pageCapture permission warning at that point.
Not requested
tabs- Draft no longer requests the global tabs permission.
host_permissions- The effective packaged Chrome Web Store manifest has no host_permissions entry.
Draft-site access
A bridge on the Draft PWA
The packaged extension registers a content script on https://draft.innosage.co/*, including matching Draft frames. That bridge receives the captured payload from the extension and passes it to the Draft page.
This URL match is content-script access to the production Draft PWA. It is not a host_permissions entry; the effective Chrome Web Store manifest does not contain one.
Capture flow
What happens after your click
- 1You click the Draft extension action on the page you want to capture.
- 2If pageCapture is not already granted, Chrome asks for the optional permission. If you deny it, Draft stops before opening an import tab.
- 3With permission granted, Chrome creates the MHTML archive locally in your browser.
- 4The extension opens the Draft import page at draft.innosage.co and hands the capture to the Draft-page bridge after that tab loads.
Extension tracking
No extension-side analytics buffer
The extension itself does not use third-party analytics or tracking pixels, and it does not send captured content to a third-party analytics service or an InnoSage-owned capture buffer. This statement describes the extension; the Draft web app has its own privacy policy and user-controlled remote actions.