Skip to main content

Behavry Integration — Browser Extension

The Behavry browser extension monitors AI service usage in the browser — capturing paste events, form submissions, and page visits across 12 AI web services and sending them to the Behavry backend for audit logging and DLP scanning.

Supported browsers: Chrome, Edge, Brave (Chromium-based only). Firefox support is planned.


Covered AI Services

ServiceDomain(s) Monitored
ChatGPTchatgpt.com, chat.openai.com
Claudeclaude.ai
Geminigemini.google.com
Perplexityperplexity.ai, www.perplexity.ai
DeepSeekchat.deepseek.com, deepseek.com
Copilotcopilot.microsoft.com, www.bing.com
Poepoe.com
HuggingChathuggingface.co/chat
You.comyou.com
Phindphind.com, www.phind.com
Mistral Le Chatchat.mistral.ai
GitHub Copilot Chatgithub.com/copilot

What Is Captured

EventTriggerData Captured
pasteUser pastes text into AI inputPasted text (DLP scanned)
submitUser submits a promptPrompt text (DLP scanned)
visitUser navigates to a covered serviceURL, timestamp

DLP scanning runs in the content script — text is scanned before being sent to the backend. The backend only receives the event metadata and any DLP findings (pattern names, severity) — not the full raw text for high-severity findings.


Installation

Option A — Load Unpacked (Development)

  1. Open Chrome → chrome://extensions
  2. Enable Developer Mode (top right toggle)
  3. Click Load unpacked
  4. Select the extension/ folder from the Behavry repo
  5. The Behavry icon appears in the toolbar

Option B — Install from the Chrome Web Store (Packaged)

The extension is published on the Chrome Web Store, and Edge installs it natively from there — no Edge Add-ons listing required.

Install Behavry from the Chrome Web Store

This is the right option for most people: updates arrive automatically, and there is nothing to host.

Deploying to more than one machine?

Don't install by hand. See Extension — Managed Deployment for force-installing across an Edge or Chrome fleet via Intune or Group Policy, and for pushing the server URL and token by policy so no one has to configure anything.


Configuration

The extension reads its backend URL from:

  1. Extension popup → Settings → Backend URL field
  2. Default: http://localhost:8000

To connect to a remote Behavry instance:

  1. Click the Behavry icon in the toolbar
  2. Go to Settings
  3. Enter your Behavry backend URL (e.g. https://behavry.yourcompany.com)
  4. Click Save

Admin Token

The extension uses an admin token to authenticate events. On first run:

  1. Click the Behavry icon → Settings
  2. Enter your admin username and password
  3. Click Authenticate — the extension stores the token in extension storage (not accessible to web pages)

Or configure via the backend URL directly — the extension will prompt for credentials if no token is stored.


Verify

  1. Navigate to chatgpt.com
  2. Type a message and submit it
  3. Open http://localhost:5173Live Activity
  4. You should see a browser_event action entry for the submit

For DLP testing, paste a string containing a credit card number (e.g. 4111 1111 1111 1111) into the prompt box. The event will appear with dlp_findings populated.


Privacy Notes

  • Text is scanned locally (in the content script) before transmission
  • Raw prompt text is not stored in the Behavry audit log for low-severity events
  • High-severity DLP matches (critical) are flagged; the matched substring is included in findings for forensic purposes
  • Page titles and URLs are captured for visit events but not full page content

Known Limitations

  • Firefox: Not supported (Manifest V3 content script API differences)
  • ChatGPT Desktop App: Not covered — TLS certificate pinning prevents proxy inspection. See the FAQ for details.
  • Private/Incognito windows: Extension is disabled in incognito by default (Chrome security policy). Enable in chrome://extensions if required.
  • Single-page app navigation: Some AI services use client-side routing — visit events are captured via the History API hook.