FAQUpdated 2026-05-13·1 min read

What does the Clipus extension capture?

Exactly what the Clipus extension reads from your product, and what it does not.

The Workbench campaign flow starts only after you open the Clipus side panel and click Create campaign from this page.

What the extension can see

  • The current tab you choose in the Workbench
  • Selected screenshot evidence for campaign creation
  • Visible page text and DOM layout context
  • Page title, domain, and non-reversible page reference
  • Workbench evidence labels, bounding boxes, and scene hints

The Workbench preview does not send inline screenshot data to AI providers. The screenshot is uploaded to Clipus only when you confirm campaign creation.

Limited intelligence snapshots

When you are signed in, Clipus may also collect limited metric-like DOM snapshots from SaaS product pages to power intelligence features. These snapshots are separate from the Workbench campaign flow, run at most once per domain per hour, and are designed for aggregate product metrics rather than full page recording.

What it cannot see

  • Your browsing history
  • Your bookmarks
  • Cookies or saved passwords
  • Audio or video from your screen
  • Pages outside the host permissions granted to the extension

Permissions in the manifest

  • activeTabCapture selected evidence from the current tab after you start the Workbench campaign flow.
  • storageStore Clipus sign-in state, tokens, Workbench session state, and limited local extension state.
  • offscreenRun locally bundled image and text processing without opening a visible tab or window.
  • scriptingRun locally bundled content scripts on the active tab during user-initiated Workbench flows.
  • sidePanelShow the Clipus Workbench after you click the toolbar icon.

Host permission: https://*/* — used for user-started Workbench capture and limited signed-in intelligence snapshots on SaaS pages.

Still need help? Contact us.
Was this helpful?