SEva — AI Technical Support Powered by PII Firewall
SEva (SupportEva) is the AI technical support agent built into the PII Firewall Developer Console.
But SEva is more than a support chatbot.
SEva runs on the full PII Firewall stack. Every time you ask SEva a question, you are experiencing PII Firewall's complete protection pipeline in action — in real time.
SEva = A Live Demo of PII Firewall
Your question
│
▼
① detectAllInjections() ← SQL injection + prompt injection checked simultaneously
│
▼
② fw.mask() ← Any PII in your message (name, email, phone…) is auto-masked
│
▼
③ Secure RAG search ← Knowledge base (pre-anonymized via rag/ingest) is queried
│
▼
④ Claude API ← Response generated from masked text + RAG context
│
▼
⑤ fw.restoreAll() ← Mask tokens restored to original values
│
▼
Displayed in the SEva panelThis is the same architecture as the Full Pipeline you'd build in your own production system using PII Firewall.
Secure RAG — How SEva's Knowledge Base Works
The knowledge base SEva uses to answer questions (PII Firewall docs, integration guides, FAQs) was pre-processed with rag/ingest before being stored in a cloud vector database for vector search.
Source documents (docs/)
│
▼ rag/ingest
Anonymize + tokenize + chunk
│
▼
Cloud vector DB (vector index)
│
▼ at query time: search_embeddings()
Retrieve relevant chunks → pass to ClaudeSEva is "an AI that uses PII Firewall's Secure RAG to answer questions about PII Firewall."
The product's philosophy is demonstrated by the product itself.
Real-Time Protection Stats in the SEva Panel
The counters shown in the SEva panel reflect actual numbers processed by the PII Firewall engine.
| Display | Meaning |
|---|---|
| 🛡️ Masked this month: N | PII detected and protected by fw.mask() in this session |
| ⚡ Attacks blocked: N | Injection attempts detected and blocked by detectAllInjections() |
As developers use the Console and ask SEva questions, these counters increment in real time.
It's a live visualization of what PII Firewall is doing for you.
Privacy by Design — What SEva Knows
SEva is built on the same Privacy by Design principles as the rest of PII Firewall.
What SEva knows (behavioral metadata only)
| Data | Example |
|---|---|
| Current endpoint in view | /detect-all-injections |
| Your plan | Free / Starter / Business |
| Session request and PII detection counts | 3 req / 5 PII |
| Language setting | ja / en |
What SEva never collects
| Information | Reason |
|---|---|
| Text you type in Console input fields | You may be testing with real PII |
| API response bodies | May contain masked tokens or restored PII |
| Your actual API key values | Security risk |
🛡️ SEva does not read your input content
This is not a UI disclaimer — it is a design guarantee.
The same principle applies across PII Firewall: after installation, all processing runs locally. Only API call counts leave your environment.
What You Can Ask SEva
Integration & implementation
"What's the minimum code to use mask with the SDK?"
"How do I install the MCP Server in Cursor?"
"I want to implement the Full Pipeline: mask → LLM → restore in Node.js"
"What's the difference between detectAllInjections and detectInjection?"
"Why is the candidates array empty in /detect responses?"Secure RAG
"What is Secure RAG?"
"How do I use rag/ingest vs rag/resolve?"
"Walk me through ingesting internal documents into Secure RAG"
"SRAG token restoration is failing — how do I troubleshoot?"Shadow AI detection
"What is Shadow AI monitoring?"
"Show me an example of shadow-ai/check"
"How can I detect and log employees using ChatGPT?"Plans & upgrades
"How many API calls does the Free plan include?"
"What changes when I upgrade to Starter?"
"Which plan is required to use Secure RAG?"Error resolution
"I'm getting a CORS error. How do I fix it?"
"The OTP code isn't arriving in my inbox"
"I issued an API key but requests return 401"How to Use SEva
Click the ? button on the right edge of the Developer Console (piifirewall.com/console) to open the panel.
┌──────────────────────────────────┬──────────────┐
│ Developer Console │ 🤖 SEva │
│ (API test / code samples) │ │
│ │ ● Online │
│ │ 🛡️ No input read │
│ │ │
│ │ [chat] │
│ │ │
│ │ [input] │
└──────────────────────────────────┴──────────────┘
`?` on right edge → ← 340px →Language support: Japanese and English — switch with the JA / EN toggle in the Console header.
FAQ
Q: Is it safe to share my API key with SEva?
Please don't. Avoid pasting real API keys into any AI service, including SEva.
Manage API keys through the API Keys panel.
Q: Can I paste real PII into SEva for testing?
We recommend against it. To test with PII-like data, use the TRY IT panel in the left sidebar — it routes requests through PII Firewall's full masking pipeline.
Q: What's outside SEva's scope?
SEva specializes in PII Firewall. General programming questions, legal advice, and medical advice are outside scope.
Q: What if my issue isn't resolved?
For critical issues (data loss, billing problems, security incidents), SEva escalates and notifies our team.
For general inquiries: support@piifirewall.com.
Related Documentation
- API Test Console — The Console where SEva lives
- Secure RAG —
rag/ingest/rag/resolvedetails (the technology powering SEva's knowledge base) - Composite Attack Detection —
detectAllInjections()details (the engine protecting every SEva message) - REST API Reference — All endpoint details
- SDK Reference — Node.js SDK guide