Data Residency for Twilio
InCountry for Twilio Data Residency solution allows Twilio chat data to be securely stored in over 90+ countries and supports storing different records in different countries. This enables customers to use all the benefits of Twilio’s solutions, while still maintaining compliance with regulatory and internal policies.
Twilio allows for data residency only in 1 country and requires all data for any instance to reside only in it
| Category | Twilio | Twilio + InCountry |
|---|---|---|
| Countries for data storage | 1 country | 90+ countries |
| Multi-country data storage | No, all data for a Twilio instance must be stored in a single Twilio region | Yes, a single Twilio instance can store data in any of 90+ countries |
| Country of origin only viewing | No | Yes, can be configured to only show data when viewed in its country of origin |
The InCountry Difference
InCountry Data Residency for Twilio
Features
- Integrates with Twilio’s to deliver a seamless data residency experience and compliance
- Optional full encryption using NIST standard SHA-256 and AES-256 encryption
- Compliant with local regulatory frameworks
- Compliant with internal data residency policies
- Ability to either store all data in specific country or multiple countries based on data requirements
- Minimum code changes required for ease of deployment
Benefits
- Reduce compliance risk
- Enhance value from Twilio’s chat solutions
How it Works
Identify regulated chat data to store into InCountry data stores
InCountry traps all regulated chat data and replaces existing chat log with redacted data
Redacted data can still be searched in Twilio All
All chat log data can be stored in a specific country, or logic can be applied to use an existing chat log such as “Country” to direct storage to multiple countries