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.

FERPA & AI

Protect student records when education uses AI

Emil detects and redacts FERPA-protected student records before a prompt reaches an AI tool — and for edtech platforms, screens responses for age-appropriate content via one API call.

Protect your team For developers

The FERPA problem with AI

Teachers paste student work and records into AI tools to draft feedback.
Education records in an AI provider's logs can be an unauthorized FERPA disclosure.
Edtech platforms can surface age-inappropriate content to minors.

How Emil helps with FERPA

Detects student names tied to records, grades, and education identifiers
Redacts before prompts reach the AI; blocks unsafe output for minors
Works for staff (extension) and platforms (API)
Audit trail evidences the control; 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 help with FERPA?

Emil redacts FERPA-protected education records before a prompt reaches an AI tool, so student data isn't disclosed to an AI vendor, and it keeps an audit trail of the control.

Does it work for edtech products?

Yes. Platforms route their AI through Emil's API to screen every prompt and response, including for age-appropriate content; staff use the browser extension.

Does Emil make us FERPA compliant?

It's a strong technical control for protecting education records in AI workflows, but FERPA compliance also depends on your policies, consent, and disclosure practices.

Other regulations

HIPAA GDPR EU AI Act