Your prompts aren’t the reporting database.

Inspection happens on-device.
Prompts are checked by the browser extension, and clipboard activity by the Windows agent. There’s no Privelin inspection server.
Reporting carries metadata, not content.
Activity events never include prompt text, clipboard text or the values that matched.
Actors are identified by installation.
Events can include a device ID and, in Chrome when available, the Chrome profile email.
Admins see decisions, not messages.
Your team can be reviewed without anyone reading an employee’s prompt text.

Inspected in the extension · not sent to Privelin

“Draft the renewal email for p.osei@example.com and attach the pricing sheet.”

Activity event · sent to your dashboard

{
  "event": "submission.decision",
  "site": "chatgpt.com",
  "action": "text_submit",
  "categories": ["email"],
  "decision": "warned",
  "redacted": true,
  "policy_version": 12,
  "actor": {
    "device_id": "7f3a…c21",
    "chrome_profile_email": "amara@northwind.example"
  },
  "at": "2026-03-11T09:42:18Z"
}
Illustrative event. Neither the prompt nor the matched value appears in it.

What is inspected locally?

Checking happens on the device, in two places:

The browser extension
When you submit a prompt through a supported path in Chrome or Firefox, the extension reads the text in the message box and checks it against your team’s rules.
The Windows clipboard check
On Windows devices with the agent, clipboard activity it covers is checked with the same rules. To do that, the agent processes clipboard text on the device.

Processing on the device isn’t the same as sending or storing: prompt and clipboard text aren’t sent to Privelin. A message you’re allowed to send still goes to ChatGPT or Claude as usual.

What is sent to Privelin?

A short record of the decision: which kind of information was found, what the policy decided, where, and when. It also says which installation it came from — a device ID and, in Chrome when available, the Chrome profile’s email.

That profile email identifies the Chrome profile only — it isn’t available from Firefox, and it isn’t proof of which account was signed in to ChatGPT or Claude.

The activity record, field by field.

Every field in an activity event, and what is never included.

Data included in activity events
DataExampleIn activity events
Site and actionchatgpt.com · text_submit Yes
Categories found["email"] Yes
Decision and redaction flagwarned · redacted: true Yes
Policy version12 Yes
Device ID7f3a…c21 Yes
Chrome profile email (Chrome only)amara@northwind.example When available
Timestamp2026-03-11T09:42:18Z Yes
Prompt text— Never
Clipboard text— Never
Matched values— Never
AI responses and conversation history— Never
Attached file contents— Never

Fields shown are for browser submissions. The Chrome profile email is only available from Chrome, and it doesn’t verify which account was used inside ChatGPT or Claude. Clipboard events follow the same metadata-only principle; their exact fields aren’t listed here.

Activity is one of three kinds of data.

Running the service needs more than activity records. Each kind is kept for its own purpose:

  • Activity metadataDecision records from the extension, as described above. No prompt text or matched values.
  • Account and organisationYour email address, sign-in method (email and password with a passkey, Google, or Microsoft), the organisation you belong to, your role, invitations, protection-seat assignments, and the organisation’s policy and configured company names.
  • Subscription and billingYour plan, seat quantity, billing interval and subscription status. Card details are handled by our payment provider, Stripe.

This page is an overview of how the product handles data. It isn’t a complete privacy policy.

Privacy questions

Know what leaves your browser.

Try Team for 14 days with five protection seats. Set your policy, connect installations, and review activity without collecting prompt text.

Start your Team trial