Check when redaction applied before treating an older recording as safe for playback, because configured settings apply to new calls according to Gong.
Key takeaways before using buyer recordings
- Processing timing: Gong documents that numeric redaction removes single digits and sequences of digits from calls and their related transcripts.
-
Output formatting:
According to
Deepgram, Flux replaces each redacted span with a single
*rather than using[REDACTED]placeholders or specific entity tags like[CREDIT_CARD_1]. - Scope limitations: AssemblyAI notes that Redacted Properties PII only redacts words in the text property.
- Consent mechanism: To start a feature and give consent, click Start, according to Google.
- Exit action: If you want to exit the meeting, click Leave, according to Google.
Sales coaching privacy checklist: what to check first
The first item on your sales coaching privacy checklist is verifying the temporal scope of your information redaction settings. You must distinguish between recordings captured after configuration and those captured before it. A setting that looks active in your dashboard does not automatically mean every file in your library has been processed under that rule.
This establishes a clear boundary: the automated processing targets future interactions, not past ones. If you are preparing a team session using a call from last quarter, that file predates the current configuration window.
To handle recordings made before your current settings were active, you cannot rely on the standard interface to trigger retroactive changes. To apply redaction to older content, contact Gong Support. This step requires manual intervention outside the normal recording lifecycle. Do not assume that saving a new policy updates historical data. Instead, identify any buyer conversations recorded prior to your setup date and flag them for a separate review process.
Before selecting a recording, check when redaction applied
Verify the processing status of your selected file before assuming it is ready for team review. Gong needs to process your call recording in order to redact the audio and resulting transcript. This requirement means that simply having a recorded file does not mean the sensitive data has been removed; the system must complete its processing cycle first. If you pull an older recording from your archive, confirm whether this processing step has already occurred or if the file remains unprocessed. Treating an unprocessed file as redacted risks exposing buyer information during your coaching session because the necessary technical step has not yet taken place.
Understanding how different configurations affect output helps you verify what the processed file actually contains. The documentation notes that tables show how calls will be transcribed and what the audio will sound like when data redaction has been configured to sequences of 1, 2, 3 or 4 digits ( Gong). These specific digit thresholds illustrate that the output depends on the exact settings applied during the processing phase. When you select a recording for playback, check which configuration was active at the time of processing. A recording processed under one threshold may look different than one processed under another, so matching the file to its intended setting is part of your pre-meeting verification.
If you discover that a recording was captured before your current redaction rules were established, do not assume retroactive application. You cannot rely on the interface to silently update past recordings with new privacy settings. Instead, treat any file from before your current configuration as requiring manual verification or a specific request to support to determine if and how it can be redacted.
Before preparing playback, distinguish audio from transcript treatment
Check the specific output format your engine produces before you share a file. Redaction behavior differs between text and audio streams, so verify which one applies to your coaching material.
Deepgram
documents that its Flux service supports number redaction only. The
redact
parameter accepts
numbers
and
aggressive_numbers. Any other value, including
true,
pci,
pii,
phi, or entity types like
ssn
or
credit_card, is rejected. The WebSocket connection fails to open with an HTTP 400 at connection time rather than being silently ignored. This distinction matters because unsupported settings do not process quietly; they stop the stream entirely.
Understand how tags persist in streaming scenarios. If you use a service where indexes persist for the whole stream, a value tagged
[NAME_1]
early in the stream keeps that tag in later segments. New values continue the count. This means the same identifier remains linked across the entire duration of the recording in the text output. You must review the full transcript to see if an initial tag appears again later, as the system does not reset these labels for each segment.
Verify your software version if you run self-hosted infrastructure. Self-hosted number redaction requires release 260430 or later according to
Deepgram. Specific language support has higher version requirements: Bulgarian, Chinese, and Cantonese require 260611 or later. Malay requires 260714, Korean requires 260728, and Japanese requires 261001. If you set
language=multi, the requirement is 260611 or later. Confirm your current build meets these minimums before assuming redaction will function.
Differentiate between text substitution and audio replacement. While some engines replace words in the text property, others may alter the audio track itself. Check whether your tool replaces sensitive information with beeps or silence in the audio file. Entity-name substitution is a documented text option in some systems, but it does not automatically imply the corresponding audio track is modified. Do not assume that because the transcript shows a redacted name, the spoken audio has been muted or altered. Listen to the actual audio file to confirm what the buyer hears during playback.
Before the session, identify participant feature choices
Keep interface actions distinct from legal recording permission when preparing buyer conversations for coaching. The specific buttons and prompts vary by platform, so verify which actions apply to your chosen tool before playback. For the "Record a video meeting - Computer - Google Meet Help" context, Google documents three separate user actions related to features in meetings. These actions define how a participant engages with or exits a session after a feature is activated.
- Consent action: To start a feature and give consent, click Start. This specific button initiates the feature and registers the user's agreement to proceed with it.
- Continuation action: To stay in a meeting after a feature is turned on, click Continue. Selecting this option keeps the participant in the active meeting while the feature remains enabled.
- Exit action: If you want to exit the meeting, click Leave. This action removes the participant from the session entirely.
These three options—Start, Continue, and Leave—represent distinct interface states. A manager should confirm which of these states a buyer occupied during the recorded call if the recording includes feature activation. Do not assume that clicking one of these buttons covers all privacy requirements; it only reflects the documented behavior for that specific product interface. Verify whether your team’s recording tool uses similar prompts or different mechanisms for managing participant presence and feature engagement. If the tool does not document these specific button labels, check its help documentation for equivalent actions. Ensure your coaching notes record which interface choice the buyer made, as this data point helps contextualize the interaction without conflating it with broader legal compliance. Focus on the factual state of the participant's presence relative to the feature at the time of recording. For note layout, see sales call review.
Privacy reference table: engines and output behavior
The following table summarizes documented redaction behaviors for Gong and Deepgram. Each row lists only what that publisher's documentation states about scope or settings and the resulting output or limit. Do not apply one row's behavior to another tool; each cell is traceable to its named source.
| Publisher | Redaction Scope or Setting | Output Behavior or Limit |
|---|---|---|
| Gong | Configured for sequences of 1, 2, 3, or 4 digits Gong | Removes single digits and digit sequences from calls and related transcripts Gong |
| Deepgram (Flux) |
Accepts
numbers
and
aggressive_numbers; rejects other values with HTTP 400
Deepgram
|
Replaces each redacted span with a single asterisk (
*) without entity recognition
Deepgram
|
| Deepgram (Nova/Streaming) | Indexes persist for the whole stream; new values continue the count Deepgram |
Uses specific entity tags such as
[CREDIT_CARD_1], distinct from Flux's single asterisk
Deepgram
|
Check your specific engine version and setting value before assuming an output format matches another platform's behavior.
Notes for the next buyer recording
Mark unresolved output or setting questions before playback.
Note that
AssemblyAI
advises using its downsampling guide for files over 1 GB to reduce size before redaction. If your workflow requires both redacted and unredacted transcripts from the same request, you must explicitly set
redact_pii_return_unredacted
to true; if
redact_pii
is not also true, the request is rejected with a 400 error. Remember that PII redaction only affects words in the text property, while separate redacted audio files can replace sensitive information with beeping sounds or silence. Entity name substitution in the text might appear as "Hi, my name is [PERSON_NAME]!" according to the documentation. Mark any question about whether your specific engine supports these exact outputs as unresolved until verified.
Illustrative example: one older buyer call
A manager plans to play a call recorded in 2026, before redaction was set up. The manager treats it as needing a support request, then checks the output format. The file is over 1 GB, so the manager uses the downsampling guide before redaction.
Your next step today
Pull the recording date for each buyer call on your list, and send a support request for any file recorded before your redaction setup. For related privacy checks, see coaching survey privacy.
FAQ: buyer details in recorded coaching
What belongs on a sales coaching privacy checklist?
A complete checklist covers five distinct areas before playback. You must verify the recording age and processing status, engine-specific output limits, transcript compared with audio treatment, file settings, and participant feature choices. These items ensure you distinguish documented behavior from assumptions about data removal. Each check addresses a specific gap where buyer information might remain visible or audible during your team session.
Does Flux support the same redaction settings as Nova?
No,
Deepgram
documents that Flux supports number redaction only. The
redact
parameter accepts
numbers
and
aggressive_numbers, but rejects other values like
true,
pci,
pii,
phi,
ssn, or
credit_card. When you send an unsupported value, the WebSocket connection fails to open with an HTTP 400 at connection time. This differs from Nova, which uses specific entity tags such as
[CREDIT_CARD_1].
Can Gong apply redaction to older buyer recordings?
No. Configured redaction applies to new calls after they undergo recording processing. To apply it retroactively to existing files, you must contact Gong Support directly. The platform does not automatically process historical recordings with current settings. If you have older buyer conversations scheduled for coaching, initiate this request before selecting the file for review.
Does AssemblyAI transcript redaction also produce redacted audio automatically?
Transcript redaction through PropertiesPII only redacts words in the text property. Redacted audio is a separate option that replaces sensitive information in the audio track with a beeping sound or silence. Check both settings if your coaching material includes both spoken and written components.
How can a participant leave after a meeting feature is turned on?
If you want to exit the meeting, click Leave according to Google. Continuing keeps a participant in the meeting after activation, while leaving exits it entirely. Verify your local consent rules separately from these technical controls before starting any recorded session.