Is it safe to put company code into Cursor or Copilot?

Not by default. Whatever you paste or open gets sent to the AI provider's servers, including secrets and customer data. Emil sits between your tools and the model and catches API keys, credentials, customer data, and source code before they ever leave.

Can AI coding tools see my API keys and .env files?

Yes, whenever they end up in the files or prompts you send, which is the most common way secrets leak. Emil detects keys, tokens, passwords, and .env values and redacts them before the prompt reaches the model.

Does Emil slow down my AI?

No. Emil screens in the moment and hands the model a clean prompt, so you get the same responses at the same speed.

Does Emil store my prompts or my code?

No. Emil processes your text in memory and keeps only a short screening record (the decision, risk score, and a redacted preview), never the full content. Classification runs on Emil's own infrastructure, is never sent to a third-party model, and is never used for training.

Which tools does Emil work with?

Anything OpenAI-compatible: Cursor, Claude Code, Copilot, Lovable, v0, ChatGPT, Gemini, DeepSeek, Ollama, and self-hosted models. Point your tool at Emil instead of the provider, or use the browser extension if you don't write code.

Do I need to be technical to use it?

No. Developers change one line of config (the base URL). Everyone else uses the one-click browser extension that screens prompts before they reach the AI.

GLBA & AI

Safeguard customer financial data in AI workflows

The GLBA Safeguards Rule expects controls over customer financial information. Emil detects and redacts account numbers, SSNs, and financial PII before a prompt reaches an AI tool.

Protect your team For developers

The GLBA problem with AI

Staff paste customer financials into AI tools, exposing account and routing numbers.
Financial PII in an AI provider's logs undermines the Safeguards Rule.
You need a demonstrable control over how customer data meets AI.

How Emil helps with GLBA

Detects account, routing, and card numbers, SSNs, and TINs
Redacts or blocks before the prompt reaches the AI tool
Deterministic local mode — data needn't leave the machine to be screened
Audit trail evidences the safeguard; content is never retained

What Emil can't do alone

It doesn't replace your policies, training, or vendor contracts
It can't grant data-subject rights or run risk assessments for you
It's one control within a broader compliance program

Emil is a technical control, not a compliance program. It reduces risk and produces evidence, but duties like consent, recordkeeping, risk assessments, and contracts (e.g. BAAs, DPAs) sit outside any screening layer. Review with counsel.

Questions

How does Emil support the GLBA Safeguards Rule?

Emil provides a technical safeguard that keeps customer financial information out of ungoverned AI tools and evidences the control, supporting Safeguards Rule expectations.

What financial data does it detect?

Account, routing, and credit card numbers (Luhn-validated), SSNs and TINs, plus customer names tied to financial figures.

Does it make us GLBA compliant?

It's one strong control. GLBA compliance also requires a written security program, risk assessments, and oversight that sit beyond any screening tool.

Other regulations

HIPAA GDPR SOC 2