Grok Clipper Privacy Policy

Effective date: September 13, 2026 · Product: Grok Clipper (Chrome extension) · Developer: Seffy Fisher

This Privacy Policy explains how Grok Clipper (“the Extension”) collects, uses, and shares user data. It is written to meet the Chrome Web Store Program Policies on privacy, disclosure, and Limited Use.

Limited Use (Chrome Web Store User Data Policy). The use of information received through Chrome / Google APIs in connection with this Extension will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.

1. Single purpose

Grok Clipper’s single purpose is to let you, with one click (or keyboard shortcut), save the current page’s reference information to a webhook URL that you configure (typically a Grok Bot / Cursor automation), and show a short on-page animation confirming the save.

2. Data we collect / handle

Data is handled only when you trigger a clip (toolbar icon or Alt+Shift+G), or when you edit Options:

Page clip data (on clip): page URL, page title, optional text selection, a short sample of visible page text, optional meta description, timestamp, and optionally a visible-tab thumbnail image used for the on-page animation.
Settings (Options): the webhook URL and sender key you paste. These are stored in chrome.storage.sync in your browser (and may sync via your Chrome profile if Chrome Sync is enabled).

The Extension does not collect browsing history in the background, does not track you across sites, and does not run analytics SDKs.

3. How we use the data

To build the clip payload and send it to the webhook endpoint you configured.
To render the local on-page “cloud” animation (including the optional page thumbnail).
To remember your webhook settings so you do not re-enter them every time.

We do not use this data for advertising, credit scoring, or sale to data brokers.

4. Who the data is shared with

Your configured webhook host: When you clip, the Extension sends an HTTPS POST to the exact webhook URL you entered in Options. By default this is commonly a Cursor / Grok Bot automation endpoint under https://api2.cursor.sh/ (host permission is limited to that origin). Whoever operates that webhook (you, or the service behind that URL) receives the clip payload.
Chrome Sync (optional): If Chrome Sync is on, your Options settings may sync across your signed-in Chrome browsers via Google’s sync infrastructure.
The developer (Seffy Fisher): Does not operate a separate collection server for Grok Clipper. We do not receive your clips unless you point the webhook at an endpoint we control, or you email us support materials yourself.

5. Permissions (why they are needed)

activeTab — temporary access to the active tab when you clip.
scripting — inject the local clip UI / collect page fields for the clip on your gesture.
storage — save webhook URL and sender key in the browser.
Host permission https://api2.cursor.sh/* — allow the POST to Cursor / Grok Bot webhook endpoints you configure on that host.

All extension logic is packaged with the Extension. We do not execute remote code.

6. Security

Clip data is transmitted to your webhook over HTTPS. The sender key stays in browser storage and is sent only as needed to authenticate the webhook request. Do not share your sender key publicly.

7. Data retention & deletion

On your device: Clear settings by removing the webhook fields in Options, or uninstall the Extension (this removes stored settings from that browser profile).
On the webhook side: Retention depends on the bot / service behind the URL you chose. Delete or manage clips there according to that service’s tools and policies.

8. Children’s privacy

Grok Clipper is not directed at children under 13, and we do not knowingly collect data from children.

9. Changes

If data practices change, this page will be updated and the “Effective date” revised. Material changes will also be reflected in the Chrome Web Store listing privacy fields when required.

10. Contact

Developer: Seffy Fisher
Email: seffyfisher1989@gmail.com