Legal

Privacy Policy

Last updated: September 5, 2026

Pin and Send (“the Extension”) is a Chrome extension that lets you pin feedback on webpages and send that context to tools you choose. This policy explains what data is handled, where it stays, and when anything leaves your device.

Summary

• Pins, notes, and page snapshots are stored locally in your browser with Chrome local storage.
• We do not require an account and do not operate a Pin and Send cloud backend for your pins.
• Nothing is sent off your device until you use Send (or an equivalent share action).
• Optional credentials you add in Settings (for example a Slack webhook or Linear API key) stay in local storage and are used only for the destinations you configure.

Who this covers

This policy applies to the Pin and Send Chrome extension and the product website at pinandsend.com. The marketing site is static and does not collect account sign-ups through the Extension.

Data the Extension stores on your device

Depending on how you use Pin and Send, the Extension may store:

• Pins and notes — text you write or dictate, severity, status, and related metadata for each pin.
• Website content snapshots — HTML and computed-style fingerprints of elements or regions you pin, used to preview context and detect when a page changed after you sent a pin.
• Page URLs and titles — used to group pins by page (origin and path) and to include context when you send.
• Settings — preferences such as whether the widget is enabled, speech language, FAB position, and which send destinations appear in the send bar.
• Optional authentication information — credentials you choose to save, such as Slack or Microsoft Teams incoming webhook URLs, a Linear API key and team ID, or a GitHub owner/repo path. These are stored only in Chrome local storage on your device.

You can export, restore, or delete pins from Settings. Uninstalling the Extension removes its local storage according to Chrome’s normal behavior.

Microphone

If you use dictation (Mic), Chrome may ask for microphone permission once for Pin and Send. That single approval covers the notes panel and other extension windows — Chrome cannot show the prompt inside the side panel itself. Speech recognition is handled by the browser’s built-in Web Speech API. Pin and Send does not upload audio to a Pin and Send server.

When data leaves your device

Data leaves your device only when you explicitly send or share. Destinations you may choose include:

• Clipboard or the system share sheet
• Email (via your mail client)
• Agent deeplinks such as Cursor or Claude (with clipboard fallback for long prompts)
• Slack or Teams (via the webhook URL you configured)
• Linear (via the API key you configured)
• GitHub (opens GitHub’s new-issue flow for the repo you configured)

What is sent is the content you chose to share (typically notes, page URL/title, and related pin context). Those third-party services process that content under their own terms and privacy policies. Pin and Send does not sell your data and does not use it for advertising.

Permissions

The Extension requests Chrome permissions needed for its single purpose:

• storage — save pins, snapshots, and settings locally.
• activeTab and scripting — show or inject the widget on the tab you are reviewing when you ask from the popup.
• Host access — run on pages you visit (including localhost and staging) so you can pin feedback anywhere you work; Slack host access is used only to post to a webhook you configure.
• sidePanel and tabs — open the notes panel and associate pins with the correct page.

Website

The Pin and Send website is a static marketing site. Hosting and delivery may involve standard server or CDN logs (for example IP address, user agent, and requested URL) as part of normal website operation. The Extension itself does not rely on those logs to store your pins.

Children

Pin and Send is not directed at children under 13, and we do not knowingly collect personal information from children.

Changes

We may update this policy as the product changes. The “Last updated” date at the top will change when we do. Continued use of the Extension after an update means you accept the revised policy.

Contact

Questions about this policy or the Extension: open an issue on GitHub.