AI Security - Private Models, PII Guardrails & Data Protection

​

Responsible AI Principles

• Human in the loop - AI augments human decision-making but never replaces it. Final compliance decisions always rest with your team. AI recommendations include confidence indicators and the evidence they were based on.
• Explainability - Every AI action is transparent. Copilot shows its reasoning steps and tool calls. Alert agents explain the signals that drove their recommendation. Investigation narratives cite the specific data points used.
• No black boxes - Corsa does not use opaque scoring models. When AI produces a risk score, disposition suggestion, or narrative, the inputs and logic are visible and auditable.
• Continuous evaluation - Models and agents are regularly tested against curated benchmarks, adversarial inputs, and edge cases before deployment to production.

​

Privately Hosted AI Models

• No customer data is exposed to public AI APIs during inference
• AI models are accessed through secure, private channels with no external data egress
• Model versions are pinned and updated through the same change management process as any other production deployment

​

Opt-In AI Features

• AI features can be toggled on or off at the platform level at any time
• Changes to AI feature settings take effect immediately
• Platforms that choose not to enable AI features continue to operate with full functionality - AI augments workflows but is never a dependency

​

PII & Sensitive Data Guardrails

​

Input Guardrails

• Prompts sent to AI models are scanned and sanitized before inference
• Highly sensitive PII fields (government IDs, account numbers, financial credentials) are redacted or tokenized before reaching the model layer
• Context windows are scoped to the minimum data required for the task - no unnecessary data is included in prompts

​

Output Guardrails

• Model responses are validated before being surfaced to users
• Outputs are checked for inadvertent PII leakage, hallucinated identifiers, and sensitive content
• Structured outputs (risk scores, alert dispositions) are validated against expected schemas to prevent malformed or dangerous responses

​

Audit Trail

• Meaningful agent operations (alert triage, investigation narratives, due diligence enrichment) are logged with context including timestamp, output, and the user who initiated the request
• Guardrail activations (redactions, blocks, sanitizations) are logged separately for security review
• AI audit logs are retained according to the platform’s data retention policy and can be exported for compliance reporting

​

BYOK as an AI Data Protection Layer

• Fields encrypted with BYOK remain encrypted within Corsa’s environment - they can only be decrypted on the customer’s side using their own KMS
• Because Corsa cannot access the plaintext of BYOK-encrypted fields, these fields are never included in AI model prompts or inference pipelines
• This gives customers cryptographic assurance that their most sensitive data (government IDs, financial credentials, account numbers) cannot be exposed to any AI model - regardless of provider or configuration
• BYOK protection applies across all AI features: Copilot, Alert Agents, Investigation Agent, and DD Agent

​

Data Retention & Training Policies

​

No Training on Customer Data

• This policy applies to all data types: transactions, client records, alerts, cases, investigation narratives, documents, and copilot conversations
• Corsa does not aggregate, anonymize, or pseudonymize customer data for model training or benchmarking purposes
• When third-party AI providers are involved, Corsa ensures that provider agreements prohibit training on customer data passed through the API

​

Data Retention

• AI interaction logs (prompts, responses, metadata) follow the same retention policies as other platform data
• Customers can configure retention periods based on their regulatory requirements
• When data is deleted, it is purged from all systems including AI-related logs, caches, and intermediate processing stores
• No AI-generated data persists beyond the configured retention window

​

Sub-Processor Commitments

• When Corsa’s hosted models process data, sub-processor agreements explicitly prohibit the use of customer data for model training, evaluation, or improvement
• Corsa maintains a sub-processor list (available on request) that includes any AI infrastructure providers
• Changes to AI sub-processors are communicated to customers in advance

​

Contractual Guarantees

• Data handling commitments are codified in Corsa’s contractual agreements
• Customers can request amendments for additional AI-specific provisions

​

Summary