Secure Microsoft Copilot

Use Microsoft Copilot — with sensitive data protected

Emil's browser extension screens what your team types into Copilot, catching PII, secrets, and confidential content before the prompt is sent.

The risk with Microsoft Copilot

  • Employees paste internal and customer data into Copilot chat.
  • Sensitive content leaves your control once submitted.
  • You can't see or prove what was shared.

What Emil catches in Microsoft Copilot

  • SSNs (with or without dashes), emails, phone numbers, addresses
  • Account, routing, and credit card numbers
  • API keys, tokens, and other secrets
  • Confidential or privileged content via custom rules

How it works

  • Install the Emil extension — it activates on Microsoft Copilot automatically
  • Prompts are screened in the browser, before they're sent
  • Sensitive spans are redacted or you're warned; metadata only is logged

Screening happens locally; only finding metadata (type + severity) is retained, never your content.

Questions

Is Copilot safe for confidential data?
With Emil screening prompts in the browser, sensitive content is redacted before it's sent. Emil adds a data-loss control on top of Copilot.
Does it run on Copilot?
Yes, the Emil extension runs on copilot.microsoft.com.
What does it catch?
PII, financial data, secrets, and confidential content per your policy — including SSNs without dashes.
What's stored?
Only finding metadata, never the content.

Secure other AI tools