PII and PCI Redaction
Redaction allows you to identify and mask sensitive information from transcriptions to protect privacy and comply with data protection regulations. The Pulse STT API supports two types of redaction: PII (Personally Identifiable Information) and PCI (Payment Card Information), on both pre-recorded and real-time transcription.
Redaction is supported only on language=en and language=hi. On other language codes the API accepts the flag but does not reliably redact.
Redaction requires model=pulse. Pulse Pro (model=pulse-pro) ignores redact_pii and redact_pci and returns an unredacted transcript.
Enabling Redaction
Add redact_pii and/or redact_pci as query parameters. Both default to false. Options: true, false. The parameters are the same on both surfaces.
Pre-Recorded API
Add the parameters to the POST /waves/v1/stt/ query string.
Real-Time WebSocket API
Add the parameters to the WebSocket connection URL.
Redaction Types
PII Redaction (redact_pii)
When redact_pii=true is enabled, the following types of personally identifiable information are automatically identified and redacted:
- Names: First names and surnames
- Addresses: Street addresses and locations
- Phone numbers: Various phone number formats
- Email addresses
Redacted PII items are replaced with placeholder tokens like [FIRSTNAME_1], [FIRSTNAME_2], [PHONENUMBER_1], etc.
PCI Redaction (redact_pci)
When redact_pci=true is enabled, the following types of payment card information are automatically identified and redacted:
- Credit card numbers: 16-digit credit/debit card numbers
- CVV codes: Card verification values
- ZIP codes: Postal/ZIP codes
- Account numbers: Bank account numbers
- Cardholder names: The name on the card
Redacted PCI items are replaced with placeholder tokens like [CREDITCARDNUMBER_1], [CREDITCARDCVV_1], [ZIPCODE_1], [ACCOUNTNUMBER_1], [ACCOUNTNAME_1], etc.
Output Format
When redaction is enabled, the transcription text contains placeholder tokens instead of the original sensitive information.
Pre-Recorded Response
The tokens appear in transcription. A response for redact_pci=true:
Real-Time Response
Each message’s transcript carries the tokens.
Redaction Placeholder Format
Redacted entities are replaced with placeholder tokens following the pattern:
[ENTITYTYPE_N]whereENTITYTYPEindicates the type of information (e.g.,FIRSTNAME,PHONENUMBER,CREDITCARDNUMBER,CREDITCARDCVV,ZIPCODE,ACCOUNTNUMBER,ACCOUNTNAME)Nis a sequential number starting from 1 to uniquely identify each instance
Examples:
[FIRSTNAME_1],[FIRSTNAME_2]- First names[PHONENUMBER_1]- Phone numbers[CREDITCARDNUMBER_1]- Credit card numbers[CREDITCARDCVV_1]- Credit card CVV codes[ZIPCODE_1]- ZIP/Postal codes[ACCOUNTNUMBER_1]- Account numbers[ACCOUNTNAME_1]- Cardholder names (PCI)
For the highest level of protection, enable both redact_pii=true and redact_pci=true flags in your request.
Compliance and Privacy
Redaction helps with compliance requirements for:
- HIPAA: Health Insurance Portability and Accountability Act (healthcare data)
- GDPR: General Data Protection Regulation (EU data protection)
- CCPA: California Consumer Privacy Act (California data protection)
- PCI DSS: Payment Card Industry Data Security Standard (payment card data)
- SOC 2: System and Organization Controls (security and privacy)
Note: Redaction is a tool to help protect sensitive information, but it should be used as part of a comprehensive data protection strategy. Always consult with legal and compliance teams to ensure your implementation meets regulatory requirements.