Overview
This article explains how Twilio handles Programmable Voice recordings when using External Storage (such as Amazon S3), what happens when you disable external storage, and how data deletion and retention policies affect access to recordings and metadata.
Environment
legacy Twilio Console
What You Need To Know
- Voice Recording External Storage: Twilio allows you to store call recordings in your own external storage (e.g., Amazon S3) instead of Twilio’s default cloud storage.
- Recording Metadata: Information about a recording, such as the Recording SID and creation date, which is separate from the actual audio file.
- Data Retention Policy: Twilio’s policy on how long deleted recordings and their metadata remain accessible.
Frequently Asked Questions
What happens to new recordings if I disable External Storage?
If you disable External Storage (such as your S3 bucket) for Voice Recording External Storage, all new call recordings will be stored in Twilio’s cloud storage by default. These new recordings can be accessed via the Twilio Console or API.
What happens when I delete a recording from Twilio?
When you delete a voice recording from Twilio, the audio file is permanently deleted. However, the recording’s metadata (such as the Recording SID and Date Created) remains accessible in the Console and via the API for 40 days after deletion. After this period, the metadata is also purged and is no longer retrievable.
What if I disable External Storage and delete the files from my S3 bucket?
If you disable External Storage and then delete the recordings from your S3 bucket, those files will no longer be accessible for playback or download neither from S3 nor from Twilio. Twilio does not retain a backup of externally stored recordings. After 40 days, any associated metadata or references in Twilio’s system will also be purged, and API fetches for those recordings will return no data.
Conclusion
- After disabling External Storage, all new recordings will be stored in Twilio’s cloud and can be accessed as usual.
- If you have specific requirements for handling metadata after disabling External Storage, consider documenting your needs and reaching out for tailored guidance.
Summary Table
| Scenario | Recording File Access | Metadata Access (up to 40 days) | After 40 Days |
|---|---|---|---|
| Recording deleted from Twilio cloud | Not accessible | Accessible | Not accessible |
| Recording deleted from S3 after disabling External Storage | Not accessible | Accessible (if metadata exists) | Not accessible |
| New recordings after disabling External Storage | Accessible in Twilio | Accessible | Not accessible after deletion and 40 days |
Below you will find references to useful documents: