Redact Sensitive Interview Data in Dovetail
Use Dovetail’s current input-specific redaction controls where available, then inspect the processed result. Manual and automatic redaction require the Enterprise plan; a transcript edit alone does not prove sensitive audio or video is protected.
Before you start: Have the required Enterprise capability, appropriate project access and an approved data-handling policy. Use synthetic values to test the workflow before importing sensitive research.
Worked example: An interview includes a spoken email address and an account number visible on screen. Check transcript, audio, video and reused highlights rather than assuming one hidden phrase covers every surface.
Step-by-step guide
Inventory sensitive content
Identify spoken, visible and textual information that should not be retained or shared. Keep the original according to the authorized research policy.
Choose the input control
For recordings imported into a project, inspect the current import redaction setting. Sources and calendar connections have their own controls; do not follow obsolete project-wide instructions.
Review automatic results
Check that relevant content was detected and that useful non-sensitive context remains. AI detection can miss data or over-redact it.
Apply supported manual redaction
With Full or Can edit project access, select the sensitive text in the transcript and choose Redact from the action menu. In the modal, choose the video and audio/transcript protections needed, then press Redact. Review the exact interval; redaction ranges cannot overlap.
Wait and inspect
Confirm processing completed and replay the affected interval. Check the output as a recipient would see it.
Check reused references
Redactions also apply to the relevant project highlights and their references in workspace docs. Inspect those reused excerpts after processing to confirm that the protected output preserves enough context, then verify access before sharing.
Common mistakes
Old settings path reused
Current controls depend on how data enters. Follow the current documentation.
Transcript-only assumption
Sensitive information may remain in audio or video.
Processing ignored
The protected result may not yet be visible.
Tips
Test with synthetic sensitive values.
Review both missed and excessive redactions.
Check previously reused highlight references.
Sources and verification
Based on product documentation checked on 2026-10-24. This is a documentation-based guide, not a hands-on benchmark. Features and availability can change.