Overview
Organizations subject to GDPR or other data privacy regulations may need to control the retention and deletion of voice call data, including archives and backups. This article explains Twilio’s current capabilities and best practices for managing voice call archive (Bulk Export) data.
Product
Programmable Voice
Environment
Twilio Console
What You Need to Know
-
Disable Call Recordings:
Ensure all recording options are disabled in your application code, TwiML, and API logic if you do not wish to retain call recordings. -
Custom Data Retention Needs:
If your organization requires a custom data retention policy or has specific GDPR requirements, contact Twilio Support to discuss your needs.
Below you will find references to useful documents:
Frequently Asked Questions
Can I Disable Voice Call Archive Backup in the Twilio Console?
At this time, Twilio does not provide a self-service option in the Console to disable the automatic archiving (Bulk Export) of voice call data. All customers should be aware of the following:
- Bulk Export is a feature that allows exporting call records for reporting or compliance purposes.
- There is no toggle or setting in the Console to disable the creation of these archives.
How Can I Prevent Access to Archived Voice Call Data?
If you wish to prevent further access to archived data:
-
Delete Active Export Jobs:
Remove any active Bulk Export jobs you have created in the Console. This will stop new exports from being generated. -
Delete BulkExport Call Records via API:
You can delete BulkExport Call records using the BulkExport API DELETE request.-
Important Notes:
- BulkExport Call records are separate from the main Call resource.
- Deleting a BulkExport Call record does not delete the associated Call resource for calls less than 13 months old.
- If you delete a Call resource, its BulkExport record is also deleted.
- Calls older than 13 months are only accessible through BulkExport, and deleting the BulkExport record will remove the call record.
- BulkExport deletions are processed asynchronously and in batches; it may take up to one week for records to be fully removed.
-
Important Notes: