Privacy policy

Buddy Outreach
Chrome extension

Last updated: May 25, 2026

What this extension does

Buddy Outreach is a companion to your Buddy account at buddyy.co. When you save a lead to your CRM, the extension automates sending the outreach message youdrafted (via Buddy's AI) to that lead on Reddit or Facebook, using your already-logged-in social media session. The extension acts on your behalf, only after you save a lead.

Data the extension reads

  • Reddit / Facebook / Messenger session cookies — read indirectly, only by opening tabs on those sites under your existing logged-in identity. The extension never extracts, copies, or transmits the cookie values themselves.
  • Post pages on Reddit and Facebook — the extension reads visible post content (title, body, author handle, comment count) on lead pages so it can correctly send a reply/DM to the right person.
  • Reddit inbox— every 5 minutes the extension checks your Reddit inbox to detect replies from leads you previously messaged, so your CRM moves those leads to “Interested” automatically.

Data sent to Buddy's servers

The extension sends only the following to buddyy.co (HTTPS):

  • The lead ID being processed (so we can match it to your CRM row).
  • The outreach message Buddy's AI drafted for that lead.
  • The result of the action — success / failure / which action ran (DM, comment, reply, reply-received).
  • Optional reply snippet (first ~100 chars) when a reply is detected.

All requests are authenticated against your Buddy account. We do not transmit any data outside of Buddy's own backend.

Data stored locally on your computer

The extension uses Chrome's chrome.storage.local to store, on your device only:

  • Buddy API base URL (defaults to https://www.buddyy.co)
  • Paused / running toggle state
  • Counters: messages sent today, leads queued
  • A rolling list of your last ~20 sends, for the side-panel activity feed
  • A dedup record of replies already reported (so we don't report the same reply twice)

This data never leaves your machine. Uninstalling the extension removes all of it.

What this extension does NOT do

  • Sell, share, or transfer your data to any third party.
  • Use any analytics, tracking pixels, or telemetry of any kind.
  • Read, store, or transmit your passwords or any credentials.
  • Modify, scrape, or transmit any content unrelated to a lead you saved.
  • Run any code outside of the explicit per-lead workflow you triggered.
  • Auto-message random people — every action is tied to a CRM lead you saved.

Permissions the extension requests, and why

  • storage — to save your settings + activity log on your own device (see above).
  • alarms — to run the 60-second polling loop that checks for new leads to process, and the 5-minute reply-detection loop.
  • tabs — to open Reddit / Facebook / Messenger tabs in the background to perform the outreach action.
  • scripting— to inject the per-page content scripts that type and submit the message into the platform's composer.
  • cookies — required by Chrome so the extension can open tabs that use your existing session. The cookies themselves are never read or transmitted.
  • sidePanel — to render the Buddy Outreach side panel UI in your browser.
  • activeTab / screen capture— only used as a fallback when the extension can't locate a button on a Facebook page via the page's HTML alone, so it can ask Buddy's vision API where the button is. Screenshots are sent only to Buddy's server, only when this fallback triggers, and are not stored after the request completes.
  • Host permissions (reddit.com, facebook.com, messenger.com, buddyy.co) — required for the extension to interact with those sites and to communicate with your Buddy account.

Account deletion + data removal

To remove all extension-stored data: uninstall the extension fromchrome://extensions. To remove your Buddy server-side CRM data, email us at support@buddyy.co.

Contact

Questions, security reports, or data-removal requests: support@buddyy.co.

Changes

If we change anything material about what the extension reads, sends, or stores, we'll update the “Last updated” date above and push a new extension version through Chrome's update channel.