Last updated: 2026-07-18

Vineyard Clipper is an internal tool built by Vineyard for its own team. It is not intended for use outside Vineyard, and it does not collect data for advertising, analytics, resale, or any purpose other than the one described below.

What the extension does

Vineyard Clipper lets a Vineyard team member save a webpage (a person, company, fund, or article) into Vineyard's internal Notion workspace. It only runs when a team member actively clicks the toolbar icon, uses the keyboard shortcut (⌘⇧K / Ctrl+Shift+K), or selects "Clip to Vineyard" from the right-click menu. It never reads or transmits page content in the background or without that explicit action.

What data is read from a page

When you invoke the clipper on a page, it reads, from that page only:

• The URL, page title, and any canonical link
• Standard meta tags (description, site name, author, publish date, preview image)
• Structured data (JSON-LD) if present, e.g. a person's name/title/employer or an organization's name/description
• Any text you have currently selected on the page
• A short excerpt of the page's visible article text (headings and paragraphs, capped at ~7,000 characters), used to help pre-fill the clip

The extension does not read pages you have not chosen to clip, does not track browsing history, and does not run continuously in the background.

What data is sent, and to whom

• The shared team access key used to authenticate to Vineyard's backend

The data above, together with:

• The name you chose when you set up the extension (so clips are attributed to the right team member)

...is sent directly to Vineyard's own backend (a Supabase project operated by Vineyard) over HTTPS, in order to create the corresponding entry in Vineyard's internal Notion workspace. No data is sent to, or shared with, any third party other than Vineyard's own infrastructure providers (Supabase, and Notion as the storage destination).

What is stored locally

Your display name, theme preference, and other settings are stored in Chrome's synced storage (chrome.storage.sync), so they roam with your Chrome profile. Your access key is stored only in local, unsynced storage (chrome.storage.local) and is never included in Chrome's account sync.

Data retention and deletion