deepgram-data-handling

# Deepgram Data Handling ## Overview Best practices for handling audio and transcript data with Deepgram. Covers Deepgram's built-in `redact` parameter for PII, secure audio upload with encryption, transcript storage patterns, data retention policies, and GDPR/HIPAA compliance workflows. ## Data Privacy Quick Reference | Deepgram Feature | What It Does | Enable | |-------------------|-------------|--------| | `redact: ['pci']` | Masks credit card numbers in transcript | Query param | | `redact: ['ssn']` | Masks Social Security numbers | Query param | | `redact: ['numbers']` | Masks all numeric sequences | Query param | | Data retention | Deepgram does NOT store audio or transcripts | Default behavior | **Deepgram's data policy:** Audio is processed in real-time and not stored. Transcripts are not retained unless you use Deepgram's optional storage features. ## Instructions ### Step 1: Deepgram Built-in PII Redaction ```typescript import { createClient } from '@deepgram/sdk'; const deepgram = createClient(process.env.DEEPGRAM_API_KEY!); // Deepgram redacts PII directly during transcription const { result } = await deepgram.listen.prerecorded.transcribeUrl( { url: audioUrl }, { model: 'nova-3', smart_format: true, redact: ['pci', 'ssn'], // Credit cards + SSNs -> [REDACTED] } ); // Output: "My card is [REDACTED] and SSN is [REDACTED]" console.log(result.results.channels[0].alternatives[0].transcript); // For maximum privacy, redact all numbers: // ...