Plivo: DPA, subprocessors and transfers

What to put in your subprocessor list

A ready row. Replace the purpose with what your client actually uses Plivo for.

Questions people ask about Plivo

Where is Plivo's sub-processor list?

Plivo publishes the list of its own sub-processors at https://www.plivo.com/legal/subprocessors/. We last opened that link on 11 October 2026.

Which legal entity does Plivo contract through?

Plivo Inc., registered in United States. That is the name to put in a record of processing or a sub-processor list, not the brand.

What covers a transfer of personal data to Plivo outside the EEA?

EU-US Data Privacy Framework (DPF). A US certification scheme covered by an EU adequacy decision. Transfers to a certified US organisation need no further mechanism for the certified scope. Whether that is enough for a particular processing operation is a judgement for the controller.

Where is Plivo's trust center?

Plivo publishes it at https://www.plivo.com/security/. A trust center, trust page or security page is the same thing under different names: the vendor's own account of how it protects data, and the place it keeps its certifications. It is Plivo's page, so we link to it rather than repeat what it says.

Where to go next

Worked out from the registry and what we have written: the country this vendor contracts from, the guides that answer the question this page raises, and the rest of the registry.

• Vendors contracting from United States644 in the registry
• The vendor registryLegal entities, transfer mechanisms and DPA links, checked by a person
• Download the registry as a CSVFree, for a spreadsheet
• Guides for privacy practicesHow the work is actually done

Other communication

Six of them. All communication in the registry · others that transfer the same way.

• 46elksSE
• AdaDE
• Adish Co.JP
• AgoraUS
• AircallFR
• AuthSMTPGB