Privacy policy for Send to Grok Bot

Effective date: 16 October 2026
Publisher: James Pendry
Applies to: the Send to Grok Bot Chrome extension
This page: https://sendtogrokbot.com/privacy

Send to Grok Bot adds a button on an X post. When you click it and pick a destination, it sends that post to the destination you set up. This policy says what that handles, where it goes, and what the extension does not do.

What is handled

The extension handles the post you choose to send. On that post's own page it also reads the author's thread and the post being replied to, because those are already on the page. The payload can include:

• the post text, URL, author handle, and display name
• the time the post was published and the time you sent it
• whether the timeline cut the text off with Show more
• expanded links, a link card, and engagement counts shown on the post
• image addresses and alt text, and video or GIF thumbnails and any caption visible in the player
• a quoted post, the reply parent, and the author's thread on that page
• a plain-text digest of those fields
• the reply preset you picked (General, Research, Job hunt, Buy or skip, Learn later, Content ideas, or Custom) and the prompt text for that preset

That data is sent only to a destination you configured and then picked in the menu. The preset and prompt travel with the post so the destination follows them. Destinations are:

• Grok Bot, or any other webhook you enter. The extension POSTs the post as JSON to the https URL you saved. If you saved a key, it is sent on that request as Authorization: Bearer and X-Sender-Key.
• Claude. If you leave the routine fields blank, the extension opens a claude.ai tab with the post in the address. If you save a routine URL and token, it POSTs the post to api.anthropic.com and sends the token as the credential for that request.
• ChatGPT. If you leave the agent fields blank, the extension opens a chatgpt.com tab with the post in the address. If you save a Workspace Agent trigger and token, it POSTs the post to api.chatgpt.com and sends the token as the credential for that request.
• Codex. The extension opens a chatgpt.com/codex tab with the post in the address. You press Send there.

It reads a post when you click Send on it, and on a post's own page it also reads the author's thread and the reply parent shown there. It does not read direct messages. On sendtogrokbot.com/connect, pasting into the box reads that paste and saves it in the extension. It does not read other pages on that site.

Tokens and keys

Webhook keys and API tokens are stored in chrome.storage.local on this device. They are not synced to a Google account. If an older version of the extension still has a webhook URL and key in chrome.storage.sync, those two values are copied to local storage once and then deleted from sync.

A token is sent only to the destination it belongs to, and only as the credential on that request. With Relay left off, the publisher does not receive tokens, keys, or posts. The extension has no account system of its own.

Relay

Relay is off unless you check it and paste a connect code. That code points at a relay you choose, such as https://relay.sendtogrokbot.com. The extension then sends the post to that relay, which forwards it to the Grok Bot webhook or Claude routine saved there. The webhook key and Claude token are stored encrypted on the relay and are not written to its logs. The relay keeps the time, destination, link, author, and result of the last 50 sends, and drops older ones. It does not keep the post text. That list is what sendtogrokbot.com/history shows when you paste the relay code. The history page sends the code only to the relay and does not store it. ChatGPT and Codex from the Chrome extension still open a tab on this computer and do not go through the relay. The iPhone shortcut sends the post link to the relay for whichever destination you pick. ChatGPT and Codex then open with that link filled in. Leave Relay off and the extension talks only to the destination you set up.

What the extension does not do

• It does not use analytics, advertising, or tracking.
• It does not sell data, and it does not transfer data for advertising, profiling, credit, or lending.
• It does not collect your name, email, phone number, location, health information, or payment information.
• It does not keep a browsing history. The post URL is sent only as part of the post you chose.
• It does not keep a copy of the post after the request is made or the tab is opened.

Sites you send to (your webhook, Anthropic, OpenAI, or X) keep data under their own policies. The publisher does not control that.

How long data stays

The post is held in memory only long enough to send it or to open the tab. Tokens, the webhook URL, the reply preset and prompt, and which destinations are checked stay in local storage until you change them, clear them and click Save, or remove the extension. Removing the extension deletes its local storage. Clicking Save after you clear a destination also drops Chrome's permission for that site.

Limited use

The extension complies with the Chrome Web Store User Data Policy, including Limited Use:

• Data is used only to send the post you chose to the destination you chose.
• Data is transferred only when that transfer is the feature you asked for: the request to your webhook, Anthropic, or OpenAI, or the tab opened on Claude, ChatGPT, or Codex. It is also transferred if the law requires it, or to protect security. There is no other transfer.
• Data is not used or transferred for personalized, re-targeted, or interest-based ads.
• With Relay left off, the publisher does not have a server that receives this data, and no person at the publisher reads the posts you send. With Relay on, the post goes to the relay address in your connect code, which forwards it and does not keep the post text.

Contact

James Pendry, publisher of Send to Grok Bot. Use the support contact on the Chrome Web Store listing, or the project repository at github.com/jamespendry/send-to-grok-bot.

This extension is not affiliated with X, xAI, Anthropic, or OpenAI.