Handling personally identifiable information (PII) just got easier. Snowflake's new AI_REDACT function leverages LLM technology to automatically detect and redact sensitive data from unstructured text—no complex regex patterns or manual review required.

The PII Challenge in Modern Data Pipelines

Organizations today process massive volumes of unstructured text data—from call center transcripts and customer support tickets to medical records and insurance claims. This data often contains valuable insights, but it's also riddled with personally identifiable information that must be handled according to strict regulatory requirements like GDPR, HIPAA, and CCPA.

Traditional PII redaction approaches typically involve:

• Complex regular expressions that miss edge cases

• Manual review processes that don't scale

• Rule-based systems that struggle with natural language variation

• Custom ML models requiring significant maintenance overhead

Enter AI_REDACT: Snowflake's fully-managed AISQL function that uses large language models to intelligently identify and redact PII from text data.

How AI_REDACT Works

AI_REDACT is a serverless function that processes text directly within Snowflake's architecture. The function leverages an LLM hosted by Snowflake to understand context and identify PII across multiple categories—then replaces sensitive information with standardized placeholder values.

Basic Usage

The simplest implementation requires just the input text:

SELECT AI_REDACT(
    input => 'My name is John Smith and I live at twenty third street, San Francisco.'
)

Output:

My name is [NAME] and I live at [ADDRESS]

Notice how the function intelligently parsed the street address written in natural language ("twenty third street") without requiring structured data or predefined patterns.

Selective Redaction

For use cases where you only need to redact specific PII categories, pass an optional categories array:

SELECT AI_REDACT(
    input => 'My name is John and I live at twenty third street, San Francisco.',
    categories => ['NAME', 'EMAIL']
)

Output:

My name is [NAME]

This granular control allows you to balance privacy requirements with data utility—redacting only what's necessary for your specific compliance needs.

Supported PII Categories

AI_REDACT recognizes a comprehensive range of PII types, with support for US data and some UK/Canadian identifiers:

The hierarchical category structure means specifying NAME will automatically redact FIRST_NAME, MIDDLE_NAME, and LAST_NAME. The output will consistently use the parent category placeholder ([NAME]) for easy downstream processing.

Real-World Implementation Pattern

Here's a production-ready pattern for processing and storing redacted data at scale:

-- Source table with sensitive data
CREATE OR REPLACE TABLE customer_feedback AS
  SELECT 'Manager Mike Washington in Kirkland was extremely helpful.' AS feedback
  UNION ALL
  SELECT 'William from San Francisco called at (415).450.0973 about his order';

-- Destination table for redacted content
CREATE OR REPLACE TABLE redacted_feedback (
  original_feedback VARCHAR,
  redacted_feedback VARCHAR,
  sentiment_score FLOAT
);

-- Redact PII and analyze sentiment in a single pipeline
INSERT INTO redacted_feedback
SELECT
  feedback AS original_feedback,
  AI_REDACT(feedback) AS redacted_feedback,
  AI_SENTIMENT(AI_REDACT(feedback)) AS sentiment_score
FROM

This pattern demonstrates a key advantage of AI_REDACT: seamless integration with Snowflake's AISQL ecosystem. You can chain AI_REDACT with functions like AI_SENTIMENT, AI_PARSE_DOCUMENT, or AI_TRANSCRIBE to build complete privacy-preserving analytics pipelines.

Processing Flow Diagram

graph LR
    A[Raw Text Data] --> B[AI_TRANSCRIBE / AI_PARSE_DOCUMENT]
    B --> C[AI_REDACT]
    C --> D[AI_SENTIMENT / AI_EXTRACT_ANSWER]
    C --> E[Redacted Storage]
    D --> F[Analytics & ML Training]

    style C fill:#4285f4,stroke:#1967d2,color:#fff
    style E fill:#34a853,stroke:#137333,color:

Enterprise Error Handling

When processing millions of rows, robust error handling becomes critical. AI_REDACT supports graceful degradation through Snowflake's AI_SQL_ERROR_HANDLING_USE_FAIL_ON_ERROR parameter:

-- Enable error collection instead of operation failure
ALTER SESSION SET AI_SQL_ERROR_HANDLING_USE_FAIL_ON_ERROR=FALSE;

CREATE OR REPLACE TABLE redacted_with_errors (
  redacted_text VARCHAR,
  error_message VARCHAR
);

-- Process data and capture any errors
INSERT INTO redacted_with_errors
SELECT
  result:value::STRING AS redacted_text,
  result:error::STRING AS error_message
FROM (
  SELECT AI_REDACT(feedback, TRUE) AS result
  FROM customer_feedback
)

This approach ensures that processing failures on individual rows don't crash your entire pipeline—critical for production data engineering workflows.

Key Considerations and Limitations

While AI_REDACT is powerful, understanding its current limitations is essential for production deployment:

Token Limits

• Combined input/output: 4,096 tokens maximum

• Output only: 1,024 tokens maximum

• Workaround: Use SPLIT_TEXT_RECURSIVE_CHARACTER to chunk large documents before redaction

Language and Quality

• Optimized for well-formed English text

• Performance may vary with other languages or text containing significant spelling/grammatical errors

• Consider text quality preprocessing for optimal results

AI-Based Redaction

Critical: AI_REDACT uses best-effort redaction via LLM models. Always implement secondary validation for high-compliance environments. As stated in the official documentation:

"Always review the output to ensure compliance with your organization's data privacy policies."

For regulated industries, consider:

1. Sampling output for manual validation

2. Implementing secondary rule-based checks for known PII patterns

3. Maintaining audit logs of redaction operations

4. Testing with synthetic data that contains known PII before production deployment

Cost Optimization

AI_REDACT follows Snowflake's token-based pricing model for AISQL functions. Optimize costs by:

• Pre-filtering: Remove non-textual data before calling AI_REDACT

• Selective categories: Only redact necessary PII types for your use case

• Batch processing: Process data in bulk rather than row-by-row

• Caching: Store redacted results to avoid reprocessing static data

Refer to the Snowflake Pricing Guide for detailed token pricing information.

Use Cases in Production

AI_REDACT shines in scenarios requiring privacy-preserving analytics:

Call Center Analytics

-- Redact call transcripts before sentiment analysis
SELECT
  call_id,
  AI_REDACT(AI_TRANSCRIBE(audio_file)) AS redacted_transcript,
  AI_SENTIMENT(AI_REDACT(AI_TRANSCRIBE(audio_file))) AS sentiment
FROM

Healthcare Data Analysis

-- Remove PHI/PII from medical notes before training ML models
CREATE TABLE training_data AS
SELECT
  diagnosis_code,
  AI_REDACT(clinical_notes, ['NAME', 'DATE_OF_BIRTH', 'ADDRESS']) AS redacted_notes
FROM

Insurance Claims Processing

-- Prepare claims data for third-party analysis
SELECT
  claim_id,
  AI_REDACT(claim_description) AS anonymized_description
FROM insurance_claims
WHERE status = 'PENDING_REVIEW'

The Bigger Picture: AI-Native Data Privacy

AI_REDACT represents a shift in how we approach data privacy—moving from rigid, pattern-based systems to context-aware, AI-native solutions. This approach offers:

• Semantic understanding: Recognizes PII even when expressed in non-standard formats

• Lower maintenance: No regex patterns to update as data formats evolve

• Faster deployment: Production-ready functionality without custom ML model development

• Unified platform: Native integration with Snowflake's data and AI ecosystem

As organizations increasingly use LLMs for data analysis, having privacy controls that operate at the same semantic level becomes essential. AI_REDACT allows you to safely leverage AI throughout your data pipeline—from ingestion to insights—without compromising individual privacy.

Getting Started

AI_REDACT is currently available in Preview to all Snowflake accounts. To start using it:

1. Review the official documentation for regional availability

2. Check Regional availability for your Snowflake deployment

3. Test with sample data using the examples above

4. Implement error handling and validation for production workloads

5. Monitor token usage and costs as you scale

For questions or issues with PII redaction accuracy, Snowflake encourages users to provide feedback to help improve the function before general availability.