Use sensitive data redaction to protect customer privacy using conversational analytics

Publisher

Amazon Web Services

URL

https://docs.aws.amazon.com/connect/latest/adminguide/sensitive-data-redaction.html

Published

unknown

Updated

unknown

Accessed

2026-10-01

HTTP status

200

License

AWS documentation; all rights reserved; no-redistribution; short excerpts and locators only

Source notes citing this source

• When redaction is enabled, a redacted analysis file is generated by default, an original analyzed file is generated only when the option to get redacted and original transcripts is chosen, and for voice contacts a redacted audio file is produced in which sensitive data is replaced by silence. in context
• AWS states that the redaction feature may not identify and remove all sensitive data, recommends reviewing redacted output, and states it does not meet the requirements for de-identification under medical privacy laws such as HIPAA. in context
• For voice contacts, the original analyzed file is the only place where the complete conversation is stored; if it is deleted there is no record of the sensitive data that was redacted. in context
• Redacted voice, chat and email files are stored in the instance's Amazon S3 buckets under Analysis/Voice, Analysis/Chat and Analysis/Email paths respectively, and all redacted, unredacted and raw files are reachable through the Amazon S3 console. in context
• For voice contacts, sensitive data redaction is applied after the call disconnects; for email contacts it is applied after the email contact ends. in context
• With redaction enabled Amazon Connect keeps redacted unredacted and raw analysis files in the instance's S3 buckets where they are accessible through the S3 console and the original analyzed file is the only complete record of a voice conversation. in context
• AWS warns that because redaction is machine-learning based it may not identify and remove all sensitive data in a transcript and recommends reviewing redacted output. in context
• AWS states that Amazon Connect conversational analytics redaction does not meet HIPAA de-identification requirements and recommends continuing to treat redacted output as PHI. in context

Cite this source record

APA

WarmTransfer. (2026, October 1). Use sensitive data redaction to protect customer privacy using conversational analytics. WarmTransfer. https://warmtransfer.net/knowledge/sources/aws-connect-sensitive-data-redaction

BibTeX

@misc{warmtransfer-aws-connect-sensitive-data-redaction,
  title  = {Use sensitive data redaction to protect customer privacy using conversational analytics},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/sources/aws-connect-sensitive-data-redaction},
  note   = {Amazon Web Services, accessed 2026-10-01}
}