Custom Data Retention Policies allow you to control how long data is stored in Garba before it is automatically deleted.
This helps your organization:
Align with internal data governance policies
Meet compliance and security requirements
Reduce long-term storage of sensitive information
Once deleted, data cannot be recovered.
Retention policies can be configured based on:
Data type (Meetings / Calls, Email, or All)
Team scope (specific teams or all teams)
Retention period (e.g., 3 months)
Deletion level for meeting data
Enter a clear, descriptive name.
Example: Standard 90-day retention
Choose what the policy applies to:
All
Meetings / Calls
Select whether the policy applies to:
All Teams, or
A specific team within your workspace
Define how long the selected data should be stored, in days, weeks or months. The default is 3 months.
Example:3 Months
After this period, the selected data will be automatically deleted. A meeting's age counts from the meeting's date, and an email's from when it was received.
If the policy applies to Meetings / Calls, you can choose what meeting data should be deleted once the retention period is reached:
Removes the recording
Keeps the summary, the transcript, the meeting title and the meeting metrics
Removes the recording
Removes the transcript and its translations, and the comments and transcript quotes on scorecard answers
Keeps the summary, the meeting title and the meeting metrics
Removes the recording, the transcript and the summary
Clears the meeting title and the participant list
Removes the meeting metrics, insights, comments, action items, tags, share links and Knowledge Hub entries
Keeps the scorecard scores, which still count in Team Overview. Their comments and transcript quotes are removed.
The meeting itself is not removed: it keeps its date, its owner, its duration and its scorecard scores, without a title or content. It still counts in Team Overview's Meetings Held and Total Call Duration.
Options 1 and 2 keep the meeting title and the meeting metrics for reporting. Option 3 removes them.
If the policy applies to Email, the whole email is deleted.
Before saving, you must confirm:
I understand that deleted data cannot be recovered and confirm this policy configuration.
Once confirmed, click Save Policy to activate the retention rule.
Retention policies apply automatically once saved.
Deleted data is permanently removed and cannot be restored.
Policies only apply to the selected data types and teams.
Multiple policies can be configured for different teams or use cases.
Align retention settings with your internal compliance policies.
Use more restrictive deletion options for highly sensitive teams.
Clearly name policies to reflect their purpose and scope.
If you need assistance defining the right retention structure for your organization, contact support or your Garba account manager.
