Ejento AI
Guides
QuickstartRecipesREST APIsRelease NotesFAQs
Guides
QuickstartRecipesREST APIsRelease NotesFAQs
Ejento AI
  1. Features
  • Basic Operations
    • Features
      • Organization → Projects → Assistants → Teams Hierarchy
    • Guides
      • Login/Signup
  • Assistants
    • Overview
    • Features
      • Assistant Access Control
      • Assistant Evaluation
      • Evaluation Metrics
      • URL-based Chat Thread Creation and Prepopulation
      • Reasoning Patterns
      • Staging & Publishing
    • Guides
      • Add Assistant
      • Evaluate Assistant
      • Edit Assistant
      • Assistant Edit Access
      • Embed Assistant
      • Delete Assistant
      • Add Favourite Assistants
      • View Assistant Id
      • Voice Calling with Assistants
  • Corpus
    • Overview
    • Features
      • Corpus Permissions
      • PII Redaction
      • ETag Setup for Corpus Incremental Refresh
    • Guides
      • Assistant Corpus Setup
      • Assistant Corpus Settings
      • Corpus Access Control
      • Corpus Connections
      • View Corpus Id
      • View Document Id
      • Tagging
        • Corpus tagging
        • Document tagging
  • Teams
    • Overview
    • Guides
      • Add a Team
      • Edit a Team
      • Delete a Team
      • View Team Id
  • Projects
    • Overview
    • Guides
      • Add a Project
      • Edit a Project
      • Managing Assistants in a Project
      • Delete a Project
      • View Project Id
  • User Settings
    • Overview
    • Features
      • Ejento AI User Access Levels
    • Guides
      • Add new user
      • Invite Users via Link or Email
      • View my User Id
  • API Keys
    • Overview
    • Guides
      • How to generate API Key and Auth Token
  • Workflows
    • Overview
    • Features
      • Workflow Access Control
    • Guides
      • Add Workflow
      • Workflow Chat
      • Workflow Edit Access
  • Tools
    • Overview
    • Guides
      • Tools Overview
      • Create External Tool
      • Connect Tool to Assistant
  • Analytics
    • Overview
    • Guides
      • Analyzing Data in the Analytics Dashboard
  • Chatlogs
    • Overview
    • Guides
      • Managing Chatlogs
      • View Chatlog & Chat thread Id
  • Integrations
    • Overview
    • Guides
      • Email Indexing
      • Microsoft Teams
      • Sharepoint Indexing
      • Google Drive Connector
      • MS Teams Integration Setup
      • Creating a Connection in Credential Manager
      • Slack App
      • Discord Bot
  • Ejento AI Shield
    • Overview
    • Features
      • Understanding Guardrails
    • Guides
      • How to enable Guardrails
  • Assistant Security
    • Overview
    • Features
      • Assistant Red Teaming
    • Guides
      • Red Team an Assistant
  • Permission Sets
    • Overview
    • Guides
      • Add Permission Set
  • Usage
    • Overview
    • Guides
      • Set Spend Limits
  1. Features

PII Redaction

Personally Identifiable Information (PII) is any data that can identify a specific person: names, addresses, phone numbers, email addresses, government ID numbers, and similar details. PII Redaction lets a corpus mask this information automatically, so assistants can use the useful parts of a document without exposing anyone's personal data.

Why PII Redaction matters#

Many valuable documents also contain personal details. Support tickets include customer names and emails, HR files include employee records, and contracts include signatories' contact information. Without redaction, an assistant could repeat those details to anyone who asks. PII Redaction lets you put this content to work while protecting the people in it.
Privacy by default: Personal data is masked before assistants ever see it.
Safer sharing: You can connect a corpus to several assistants, or share it widely, with less risk of leaking personal information.
Compliance support: Redaction helps you meet data protection obligations and your organization's privacy policies.
Trust: Customers and employees can rely on your assistants not to reveal their details.

How it works#

1.
You turn on PII Redaction for the corpus.
2.
Documents are scanned when uploaded. Personal information in each document is detected automatically.
3.
PII is masked. Detected details are hidden or replaced with placeholders.
4.
Assistants use the redacted version. When an assistant searches the corpus, it works with the masked content, so answers stay useful without exposing personal data.
With PII Redaction turned on, only TXT, DOCX, and PDF files can be uploaded to the corpus.

Use cases#

Customer support content: Turn on PII Redaction before uploading ticket exports or chat transcripts, so a support assistant can learn from past cases without repeating customers' names and emails.
HR and recruiting: Redact employee records, interview notes, and résumés before an HR assistant uses them.
Widely shared corpora: For a corpus shared across the whole organization, where you can't control who asks the assistant questions, redaction keeps personal details out of every answer.
To hide personal information in an assistant's conversations instead of its documents, use the PII Redaction guardrail. See Understanding Guardrails.

Where to turn it on#

When you create a corpus: turn on Enable PII Redaction in the Create Corpus panel. See Assistant Corpus Setup.
For an existing corpus: open the corpus Settings tab and use Enable PII Redaction under PII Settings. See Assistant Corpus Settings.
Previous
Corpus Permissions
Next
ETag Setup for Corpus Incremental Refresh