Skip to content
ClipView
Add to Chrome
Back to ClipView

Privacy Policy

Last updated: 11 August 2026

Your clipboard history stays on your own device. ClipView has no servers, no analytics, no telemetry, and no account system. Nothing you copy is transmitted anywhere unless you personally trigger an AI action.

What ClipView stores

When you copy text, ClipView saves the following tochrome.storage.local— Chrome’s own local storage on your machine:

  • The copied text, and its formatted (HTML) version when one exists
  • The title, domain, and URL of the page you copied from
  • The time of the copy
  • Any lists you create and the items you add to them
  • Your prompt templates and extension settings

You control this data completely. “Clear history” deletes it, individual items can be deleted, and “Pause history” stops capture entirely. Uninstalling the extension removes all of it.

What ClipView does not do

  • No data is sent to the developer — there is no ClipView server
  • No analytics, tracking, advertising, or fingerprinting
  • Your data is never sold or shared
  • Your history is not synced between devices

When data leaves your device

There are exactly two cases.

opt in

1. AI templates, only when you run one

If you add your own Google Gemini API key in Settings and then run a template on a clipboard item, that item’s text is sent to Google’s Gemini API to be processed. This happens only for the specific item you choose, only when you click to run a template.

Your API key is stored locally and is sent only to Google, as part of authenticating that request. ClipView ships with no API key of its own; if you never add one, the AI features do nothing and no data is ever sent.

Google’s Gemini API terms
on by default

2. Website icons

To help you recognise where an item came from, ClipView displays the favicon of the source website. These icons load from Google’s public favicon service, which means the domain nameof a copied item’s source (for examplegithub.com) is included in that request.

Only the domain is sent — the copied text itself is never included. If you would rather avoid this entirely, an offline build with favicons removed is a one-line change described in the project README.

Permissions, and why each is needed

clipboardRead

Detects copies made outside a web page, such as from the address bar or the right-click menu.

clipboardWrite

Restores formatting when you re-copy a saved item.

storage

Saves your history, lists, and settings locally.

tabs

Reads the current tab’s URL so an out-of-page copy can be labelled with its source.

offscreen

Runs the clipboard reader in a background document — the only way Chrome permits reading the clipboard outside a focused page.

sidePanel

Displays the extension in Chrome’s side panel.

<all_urls>

Lets the extension notice copies on any site you use. Narrower access would silently miss pages you copy from. ClipView reads only clipboard events and the page’s title and URL — it does not read page content.

Sensitive content

ClipView captures whatever you copy, which may include passwords or other private data. Because everything stays on your device, this is no more exposed than your clipboard already is — but two features are worth knowing about:

  • Pause history stops all capture while it is on.
  • History size caps how many items are kept, so old entries fall away.

Changes and contact

Material changes to this policy will be reflected in an extension update, with the date above revised.

comingbacktolyf@gmail.com